Attributes by category
Every category,
its own attributes.
Marcus
Amazon01The starting point
A single template
for products that have nothing in common.
When every page shares the same fields, a drill ends up with a “cutting width” and no “torque”. The attributes that matter are missing, and the ones left mean nothing.
- Fields that mean nothingA cutting width on a drill, a torque on a lawn mower: the customer gets lost.
- Key attributes missingWhat makes someone choose a product in its category appears nowhere on the page.
- Different requirements per channelAmazon makes required what your store leaves optional, and vice versa.
02How it works
You ask. The agents take care of it.
- 01Each channel has its taxonomyIts categories and, for each one, the list of attributes it expects.
- 02Required or optionalEach attribute is marked according to what the channel’s category requires.
- 03Allowed valuesChoice attributes keep their value list, specific to the channel.
- 04Applied at generationThe generation agent fills in the category’s list from the product’s master data.
Categories
Attributes
Required
Optional
Value lists
03The result in Upsellr
Pages that speak
their category’s language.
Each page carries its category’s attributes, and only those.
Required ones are filled in, and values stay within the channel’s lists.
- RelevantThe category’s attributes
- CompleteRequired ones filled in
- CompliantValues from the channel’s lists
Illustrative example · sample data
04What makes the difference
A taxonomy that fits your products.
One list per category.
Drills, grinders, lawn mowers: each category has its attributes. Changing category means changing list.
What the channel requires, first.
Each attribute is required or optional depending on the channel. Required ones are filled in first.
Values picked from the list.
For a choice attribute, the master data value is mapped to one of the values the channel allows.
05Results to document
What you’ll be able to measure.
- Share of required attributes filled in
- Number of irrelevant fields removed from pages
- Share of pages accepted by each channel
Your questions.
Practical answers.
What you need to know before your first request.
Where does a category’s attribute list come from?
From the channel: Amazon’s or ManoMano’s for a marketplace, the one you define for your store.
Can each channel have different requirements?
Yes. The same attribute can be required on one and optional on another.
Does my master data change with the category?
No. It stays single. The attribute list lives in the channel and applies at generation.
What happens when a product changes category?
Its page takes its new category’s attribute list at the next generation.
Every category,
its own attributes.
Try it on one category or explore the taxonomy in a personalized demo.
