Quant Onboarding - Migration from Original Solution to Quant
In this manual, you will find how to deploy Quant step-by-step, including migration from original solution to Quant.
1. Preparation of Data and Quant Installation
Preparation of Data
The first essential step for a successful Quant deployment is data preparation.
Detailed information on data preparation can be found in Data Preparation for Import to Quant manual.
Two approaches are possible at the beginning:
A. 3 - 5 Days - Preparation of a limited amount of data for training purposes only
- Product data including dimensions for at least 2 selected pilot categories
- Technical plans of at least 2 shops in PDF or JPEG format
- Information on the dimensions of shelving fixtures at least for selected pilot categories
- (Optional) Product photos
- (Optional) Sales data
- (Optional) Inventory data
B. 1 - 2 Weeks - Automatic data transfer settings
- In case your IT department has the capacity to set up automatic data transfers between your ERP system / DWH and Quant at the beginning, it is possible to set up everything together with our specialists already during the trial period before the initial training of end users.
- Data transfers can be implemented either using Quant's REST API or by exchanging CSV files via FTPS server.
- The Quant manuals include detailed documentation of the API and CSV/FTPS transfer logic.
You can read more about REST API in these manuals.
Quant Desktop Installation
Once your instance of Quant is running, we will send login credentials for your users to the emails you select. The email will contain a link to set up a password and download the Quant Desktop application installer.
If you do not have rights to install applications, you will need the assistance of your IT department to install Quant.
After installing and running Quant, you will be prompted to enter your username and password. Quant Desktop will then attempt to connect to our servers to synchronize with your database.
It is possible that your firewall will block the connection, and you will be informed that the connection attempt failed after entering your password. If this occurs, our support will let you know what combinations of ports and ip addresses Quant is communicating on and your IT will need to adjust your firewall settings.
After the first successful login to the Quant Desktop application, everything is ready for the initial training.
The whole installation process is described in the Quant Installation Process manual.
2. Proof of Concept
Optional option where you can try all Quant features for 2 months and evaluate which ones will be useful for your company and include them in the purchased features. Of course, if the customer prefers to go straight to the yearly subscription, this is possible and step 2 does not apply.
A detailed description of PoC, from data preparation through pilot deployment to the final phase of testing various Quant solutions and PoC evaluation, can be found in the manual Space Planning Proof of Concept.
3. Normal Operation
Transitional phase
Next comes the phase of transition to normal operation, for most companies that have previously used a competing system, there is a transitional phase of migration from the original solution to Quant. For several competing systems, we can offer bulk import of planograms directly into Quant, which makes the whole process much easier (PLNX or XML files).
At this stage, it is possible to take advantage of store specific standalone planograms with a lifecycle, which allows you to share store specific planograms with stores very quickly without having to draw a floor plan of the store, an ideal feature to get you started. The downside of this approach is that you have to manage multiple planogram variants, as Quant doesn't know the actual store layout, and there is no macro-space planning option.
Then you can gradually start mapping the stores and drawing their layout in Quant. For the stores that will already have a floor plan, you can enable the store specific planograms integrated with floor plans function. This will reduce the number of planogram variants you have to manage, while improving accuracy.
Final phase
If you manage to map and digitize all store floor plans, then you will manage all planograms in one place and you will greatly reduce the number of managed variants thanks to the unique concept of shared planogram templates.
Further suggestions on this topic can be found, for example, in the following articles: Best Practices for Macro Space Planning in Retail Stores, Effective Planogram Creation Process: How to Optimize Your Retail Space Planning, Why are store specific planograms better than cluster specific? and in the following manual: Planograms Integrated with Floor Plans.