Structure the catalog
One master data,
organized the way each channel wants.
Marcus
01The starting point
One product,
three ways to file it.
The master data is complete. But Amazon files the drill in its own category tree and expects a color from its list, ManoMano has other categories and other fields, and your store has its own again.
- One category tree per channelEach channel has its own categories: a product well filed on one is lost on another.
- Attributes that change with the categoryA drill doesn’t expect the same fields as a grinder, nor the same ones from one channel to the next.
- Imposed value lists“Teal” in your catalog, “Turquoise” on Amazon: one value outside the list, and the listing is refused.
02How it works
You ask. The agents take care of it.
- 01A complete master dataYour products’ attributes are collected upstream, once, for all your channels.
- 02Each channel has its structureIts category tree, the attributes expected per category and its value lists.
- 03It all happens during generationThe generation agent classifies each product in the channel’s category and puts its values in the expected format.
- 04Compliant pagesEach channel gets pages filed and formatted the way it expects.
Channel category trees
Attributes by category
Value lists
Units
Master data
03The result in Upsellr
One page per channel,
filed the way it expects.
Each product is classified in each channel’s category tree, with its category’s attributes.
Its values follow the channel’s lists, and the master data stays single.
- ClassifiedIn each channel’s category tree
- CompleteIts category’s attributes
- CompliantValues from the channel’s lists
Illustrative example · sample data
04What makes the difference
What makes a page compliant with each channel.
The right category, on every channel.
During generation, each product goes to the right branch of the channel’s category tree, based on its master data.
Each category’s attributes.
Each channel category has its list of attributes. The generated page follows it, field by field.
Values from the channel’s lists.
“Teal” becomes “Turquoise” for Amazon, “18 volts” becomes “18 V”: each value takes the form the channel allows.
05Results to document
What you’ll be able to measure.
- Share of listings accepted first time
- Time spent maintaining mappings per channel
- Number of values refused as outside the list
Your questions.
Practical answers.
What you need to know before your first request.
Which category tree is used?
Each channel’s own: Amazon’s, ManoMano’s or your store’s.
When is the product classified?
While each channel’s pages are generated, from the product’s master data.
Is my master data changed?
No. It stays single for all your channels: classification and value formats live in each channel.
Does each category have its own attributes?
Yes. In each channel, a category has its list of attributes, and the generated page follows it.
What happens to a value that isn’t in the channel’s list?
It’s mapped to the matching allowed value, such as “Teal” to “Turquoise” for Amazon.
One master data,
the right page for every channel.
Try it on your channels or explore structuring in a personalized demo.
