The most time-consuming task in marketplace projects is matching products correctly. This technically simple step takes weeks when data quality is weak.
01. The Unique Key
One key must be chosen as the basis for matching: barcode or stock code. Using both interchangeably produces unmatched records in every future bulk update.
02. Barcode Discipline
Every variant needs its own barcode. Using a single barcode for a product broken down by colour and size causes stock to be written to the wrong variant on the marketplace. It produces the same problem in the warehouse.
03. Variant Structure
The variant hierarchy in the ERP rarely matches the structure the marketplace expects. Transformation rules should be defined in the integration layer; the ERP's structure should not be distorted for the marketplace.
04. Category Mapping
Every marketplace has its own category tree and mandatory attributes. Category mapping should be done once and stored; it must not become a task repeated for every product.
05. Content Quality
Title, description and image rules vary by channel. Rejected products usually fail on missing attributes or image resolution. Enforcing mandatory fields when the product is created prevents that rejection at source.
06. Bulk Updates
Changing prices on thousands of products one by one isn't feasible. Rule-based bulk update capability is a feature not to be overlooked when choosing an integrator.