Normalization
Everything that comes in (CSV, your store, the scanner) is sorted into the master product record as it arrives: a consistent data model, independent of the destination store. This is where the product type and its complexity are decided.
Product type detection
Cosmetics, hair dye, appliance, accessory, bundle… Depending on what it is, the product page gets different sections.
Complexity score
Basic, standard or premium, based on the price and what the supplier provides: description, attributes, photos, video. It decides how many sections the product page has and how long it is.
Verified barcodes
EAN, UPC and GTIN codes are cleaned up and their check digit is validated. A code that was copied wrong is flagged in the preview and isn't saved.
Your category tree
Incoming categories are placed in your own tree. Each store gets its own through a confirmed mapping; anything that doesn't match is flagged, never guessed.
Source accumulation
If a product comes in through several routes (two CSVs, your store sync), they're all kept. You decide which sources feed the product record.
Settings available in this stage.
- 01Category mappings per store (category console)
- 02Which sources feed each product record
- 03Review of new brands and categories when importing
Try it with your catalog.
We set up a demo and you run the whole pipeline with your own products. No long-term commitment.