Product data guide
A supplier feed is not yet a clean store catalogue.
Before automating imports, agree what makes two records the same product, which source takes priority and how errors will become visible.
Collect actual source samples
Request CSV, XML or API examples covering an ordinary product, variants, an out-of-stock item and a missing field. Check access terms, update frequency and permission to use images and descriptions. Column headers alone do not show the values the importer will encounter each day.
Define product identity
Document supplier SKUs, EANs and your internal identifiers. A SKU may be unique only within one supplier, while an EAN may be missing. An identical product from two suppliers should not automatically create two store listings. Handle size, colour and package variants separately, with a review process for conflicts.
Separate pricing and stock rules
Record the price currency, whether the source amount includes taxes, and how margins and rounding work. Decide how supplier stock and delivery estimates appear to buyers. A missing price is not a zero price; a record disappearing from a feed does not always mean it should be deleted. Define explicit handling for these cases.
Run a limited trial import
Import a small product set into a test environment. Check categories, attributes, images and repeated updates. Include a malformed row and verify that it appears in the error report. Before launch, agree who reviews discrepancies and how the previous state can be restored.
Apply this to your needs
Check your assumptions.
Use the planner to explore scope, calculate time value and submit a specific request.
Plan a project →