Why recurring supplier files are different
A one-time cleanup is easy to describe: fix these rows. A recurring supplier workflow is more structured. The same supplier may send a file every Monday with the same logical fields but slightly messy values. The product becomes useful when the cleanup instructions are repeatable.
Saved workflow concept
A supplier profile can hold a known mapping and workflow settings. The goal is that the next file from the same source needs less configuration and produces a more predictable result.
Supplier file
→ saved mapping
→ cleaning rules
→ validation
→ Shopify-oriented exportExamples of repeatable rules
- Map
Item Nameto product title. - Map
Selling Costto price. - Normalize recurring currency formatting.
- Apply a configured price markup.
- Normalize stock values.
- Clean recurring tags and whitespace.
- Flag duplicate SKUs for review.
Compare new and previous files
For recurring imports, change visibility matters. CatalogEaze can compare product records by SKU and surface new, removed, changed, and unchanged records so a store operator can investigate supplier updates rather than comparing two spreadsheets manually.
Frequently asked questions
Does the tool need the supplier's system integration?
Not for the initial workflow. The customer can start with a supplier CSV export. Direct integrations can be added later.
Is the raw supplier file stored on a server?
The launch product is designed so core file processing can happen in the browser, and the launch build does not require server-side storage for basic cleanup.
Is this an inventory system?
No. CatalogEaze is a focused file transformation and validation workflow, not an ERP or inventory database.