An importer reporting success means its process completed according to its own rules. It does not prove that every product has the right photograph, variant, price or customer-facing description.
Check the result against the prepared source. Use complete checks for fields you can compare mechanically and representative manual checks for presentation and behaviour. Do not use a few attractive examples to stand in for the whole catalogue.
Preserve the comparison source
Keep the exact file or record set used for the import. If you change that source afterward, you can lose the ability to distinguish an import error from a later edit.
Record the import time, destination and available result report. Identify whether the operation created, updated or skipped records.
Do not include secrets or customer details in a widely shared evidence file. The catalogue check should use the product information needed to establish correctness.
Reconcile counts with meaning
Compare source and destination counts, but explain what each count represents. One product with six variants may appear as one parent record in one system and several sellable records in another.
Investigate skipped, failed and duplicate entries individually. A matching total can still hide one missing product and one accidental duplicate.
Keep unavailable and draft products in the comparison where they were meant to transfer. Their absence may not be obvious on the public storefront.
Check critical fields across the whole set
Where export or read access allows, compare stable references, option labels, prices, units and state for every imported item.
A practical checklist includes:
- Each source product maps to the intended destination record.
- Variant combinations remain attached to the correct parent.
- Currency and numeric formats are interpreted correctly.
- Pack quantities have not become individual-piece quantities.
- Unavailable products are not accidentally offered for sale.
- Media references belong to the correct item.
Do not claim a full-field comparison if you only inspected the page visually. Record the boundary of each check.
Inspect representative presentation cases
Choose products that exercise different layouts and content lengths. Check a long title, several images, multiple variants, a set and any product with special fulfilment information.
Open the public page on a phone. Look for truncated meaning, unreadable tables, missing images and option names that no longer match the description.
A source field can be stored correctly but displayed in the wrong place or not displayed at all. That is why data comparison and presentation inspection are separate tasks.
Test the selection-to-order handoff safely
Use an authorised preview or test process to check that the chosen variant and quantity remain correct through the bag and order review. Stop before an unwanted real order or payment.
Check more than the default option. A product may display correctly while sending the wrong selection downstream.
Do not assume that a product import also configured payments, shipping, taxes or stock synchronisation. Those are separate capabilities that need their own verified setup.
Classify differences before correcting them
Sort findings into source-data problems, mapping problems, import failures and display defects. The right repair depends on the cause.
If the source contains an inaccurate material description, rerunning the import will reproduce it. If the importer interprets a decimal incorrectly, manually fixing one product leaves the rest exposed.
Keep a record of corrections and rerun the affected checks. Avoid making simultaneous undocumented changes in both source and destination, which can obscure whether the mapping now works.
Confirm what happens on a repeat run
If repeat imports are part of your workflow, test their behaviour in an authorised environment. Does the operation update the intended records, create duplicates or ignore changes?
Use a stable identifier and the tool's documented process rather than assuming names alone provide reliable matching. Product names can change or collide.
Keep a recovery route appropriate to the operation. An import that updates live prices is not harmless simply because it does not delete products.
Close with an explicit exception list
A useful completion note states the source count, destination interpretation, fields checked, representative cases tested and unresolved issues.
Do not write “all good” while known missing photographs or option errors remain. Assign those exceptions without hiding them behind the successful upload result.
Use catalogue preparation to repair content gaps and the stock guide to reconcile available quantities. The catalogue is ready when its information and buying behaviour match the intended source, not when the progress bar reaches the end.
Examples are illustrative. Confirm current features, charges and suitability before making a business decision.
Explore this topic → · Find an oBizee setup guide · Ask about your store