Why this module exists
Merchandising is built on a set of assumptions about how a shopper behaves: that comparison is expensive, that attention is scarce, that presentation influences choice, that most people see a fraction of the assortment.
A machine buyer violates all four. It compares exhaustively at near-zero cost, has no attention to capture, is unmoved by presentation, and can consider your entire range and everyone else's.
That does not mean merchandising stops mattering. It means the levers move β from presentation to specification, from position to attribute, from persuasion to fit. This module works through which levers move and what to do about each.
9.1 Which levers move
| Lever | Effect | Why |
|---|---|---|
| Merchandised position and placement | Weakens sharply | The agent does not see your grid |
| Photography and creative | Weakens for selection, holds for conversion | Still decides the human's final yes |
| Copy and persuasion | Weakens | Persuasion is not a retrieval signal |
| Structured attributes | Strengthens sharply | This is what the machine actually matches on |
| Price transparency and clarity | Strengthens | Comparison is now free and complete |
| Availability accuracy | Strengthens sharply | Recommending an out-of-stock item is punished |
| Reviews, specifically their content | Strengthens | Grounding material, quoted directly |
| Policy terms β returns, delivery, warranty | Strengthens | Compared as attributes, not read as small print |
| Bundling and cross-sell | Mixed | Machine-legible bundles work; visual merchandising does not |
The pattern: anything a machine can parse and compare gains weight; anything that required a human eye loses it. That is not an argument for worse creative β the human still converts β but it is an argument about where the marginal hour of merchandising effort now goes.
9.2 Attributes are the new merchandising
Module 4 treated attributes as a legibility problem. Here they are a commercial one.
Attributes must answer constraints, not describe products. Most retail taxonomies were built for navigation and reporting β category, sub-category, colour, size. Machine buyers arrive with constraints: washable, fits a 60cm gap, safe for dogs, arrives before Friday, under β¬200, made in Europe. If your data does not carry the constraint, you cannot be matched to it, no matter how well your page reads.
Build the taxonomy from questions, not from your PIM. The method is unglamorous and works:
- Pull six months of customer-service transcripts and on-site search queries.
- Extract every constraint a customer expressed.
- Rank by frequency.
- Check which of the top thirty exist as structured attributes.
Retailers typically find that between a third and a half of their most common buying constraints are not fields anywhere β they live in prose, in a photo, or in a colleague's head.
Attribute values need controlled vocabularies. "Charcoal," "dark grey," "anthracite" and "graphite" are four values for one filterable concept. Humans cope; matching does not. A colour family field alongside the marketing name is one of the cheapest wins available.
Negative attributes matter more than they used to. Not machine washable. Not suitable for underfloor heating. Stating what a product is not prevents a mismatch recommendation, and mismatch recommendations become returns β which is Module 8's cost, created here.
9.3 Pricing under exhaustive comparison
Three effects, distinct and often conflated.
Comparison is complete, not merely cheaper. A shopper who once checked three retailers now gets an answer synthesised across many. Being fourth-cheapest used to be survivable through obscurity; that obscurity is thinner now.
Comparison is total-cost, not headline. Agents compare delivered cost with terms attached: price plus delivery, minus the value of a longer returns window and a better warranty. This is genuinely good news for retailers who compete on service and have been unable to get credit for it at the point of comparison β but only if those terms are machine-readable. An unmarked-up 60-day returns policy is worth nothing at comparison time.
Errors propagate at machine speed. A mispriced SKU used to be found by a few people over hours. It is now found immediately and shared. Price-error controls are a live operational requirement, not a hygiene item.
What this does not mean is a race to the bottom. It means the differentiators must be expressed in fields. The retailer with a better guarantee, faster delivery or a longer returns window now has a way to win a comparison it previously lost on headline price β provided it publishes those facts as data.
9.4 Assortment and range
Two effects pull in opposite directions, and which dominates is category-specific.
Toward the long tail. Machine discovery is unusually good at finding the specific product that matches an unusual constraint. Obscure SKUs that never merited a merchandised slot become findable β if their attributes exist. Long-tail visibility is one of the clearest wins available, and it is almost entirely a data-completeness problem.
Toward consolidation. Exhaustive comparison is brutal on near-duplicates. Three similar SKUs at similar prices previously coexisted because shoppers saw one; now they compete, and the two losers absorb catalogue cost, data-maintenance cost and review dilution.
The practical instruction: enrich the tail, prune the near-duplicates. Both are merchandising decisions with a data prerequisite, and both are visible in your own returns and search data before any AI surface tells you.
Exercise β Rebuild the attribute set
Time: 2 hours. Produces the artefact for this module.
- Extract constraints from six months of service transcripts and site-search logs. Rank by frequency.
- Check the top thirty against your actual structured attributes. Mark each: exists, prose only, absent.
- Design the additions, including at least one negative attribute and one controlled vocabulary.
- Write the supplier rule that stops the problem recurring β no new SKU without the mandatory set.
- Check your policy terms β returns, delivery, warranty β are published as data, not only as page copy.
- List your near-duplicates and propose a consolidation.
Self-check
- Which merchandising levers weaken when the buyer is a machine, and which strengthen?
- Why does a constraint expressed in prose fail where the same fact in a field succeeds?
- How does a longer returns window become a comparison-time advantage, and what is the prerequisite?
- Which pulls harder in your category β long-tail enrichment or near-duplicate consolidation?
- Name one negative attribute that would prevent mismatched recommendations in your range.
Further reading
- Module 4 of this course, for the technical expression of everything above.
- Google Merchant Center product data specification, for the attribute vocabulary the largest surface consumes.
- Your own service transcripts. In this module they outrank every external source.