Staging test
Matching products, variations and brochures
Several sources were describing the same range differently. Match the product before deciding which information belongs on its page.
The problem behind the job
If products, variations and brochures have been managed separately, customers can end up with the wrong download or missing information. The records need a reliable relationship.
What I was working with
A catalogue build involved old website records, scraped product information, brochure material and product variations. I worked on aligning those sources and preparing a staged catalogue. The source history documents the import and matching work, but not a fully verified final live rollout.
One range, several descriptions of it
The sources did not share one simple product structure. The work needed to connect the old records with the relevant product and brochure information without assuming every similar title referred to the same item.
Parent products and variations added another relationship to check.
Keep the mapping visible
The staged work brought the source records together and used the product relationships to structure the catalogue. Brochure information was part of that source alignment.
Product and variation matching explains the kind of distinction that matters here.
What was prepared
The work included product matching, import preparation and staged catalogue records. This was not simply a finished brochure pasted into each description.
The individual source gaps and the final live state still needed checking.
Do your product sources disagree about what belongs together?
If your problem looks similar, send me the current setup and the outcome you need. The implementation may be different, but the same kind of thinking usually applies.
What I'm not claiming
I'm not treating every source record as a published product or claiming that all brochure enrichment was completed. Different totals in source datasets can refer to different things, including parent products and variations.
The purpose of this example is to show the alignment problem and the staged work.
For a similar catalogue
I'd want a small sample from each source and the intended website structure. The priority is an agreed mapping and a clear list of uncertainties.
This fits within product data and imports and migration.
HAVE SOMETHING AWKWARD?
Do your product sources disagree about what belongs together?
Send me the URL, what is happening, what you have already tried and what a useful result would look like. A small anonymised sample is enough to start - do not send passwords, credentials or sensitive customer data.
