Skip to content

Refactoring issues

This page helps you manage discrepancies that may emerge when you replace an old system with glacom.AI services.

How it works

Refactoring makes your processes more efficient. For example, if your old system calculated a product discount incorrectly or slowly, glacom.AI will apply the correct logic. If you notice a final price is different from what you saw before, it is time to check which of the two results is right for your business.

What you need to do

  1. Report every difference you notice between the old system and the new one.
  2. Verify with us if the previous result was actually correct or if it was an error in the old software.
  3. Identify any rare functions you used sporadically that you do not see yet in the new system.
  4. Check that all data is present, following the data migration guide.

What glacom® does

It analyzes the reported discrepancy, corrects any configuration error, or implements the missing function to align the service with your needs.

Limits

Refactoring cannot predict "hidden" functions or processes that were not documented or shown during the analysis phase. If a piece of data was not present in the original system, it cannot be migrated.

Frequent issues

  • Is a value calculation different from the old system? → Often the old system was wrong: let's verify together which result is correct.
  • Is a function you used rarely missing? → Report it immediately to integrate it, as explained in adding what is missing.
  • Was a piece of data not migrated? → Check if the data was present and accessible in the previous system.
  • Is the system behaving differently than expected? → Open a ticket in ticket for alignment.

From the app

Not available from the app: refactoring issue management happens through support channels and tickets.