The digital merchandising operating playbook
How I run digital merchandising, from product data to the product page to the test plan.
Digital merchandising is the work of helping the right customer find the right product, understand its value, and feel confident buying it. Design earns attention. Navigation and search create discovery. Product content resolves doubt. Merchandising connects needs to products. Analytics show where the journey breaks.
The model
| Layer | Customer question | Evidence it’s working |
|---|---|---|
| Brand and entry | Am I in the right place? | Engaged landing sessions, category entry, fewer immediate exits |
| Discovery | Where do I find what I need? | Search success, PLP-to-PDP rate, zero-result rate |
| Evaluation | Is this the right product for me? | Add-to-cart rate, PDP conversion, fewer product questions |
| Transaction | Can I buy it easily and trust what happens next? | Checkout completion, payment errors, contribution per session |
| Retention | What helps me get more from this? | Attach rate, repeat purchase, lifetime value |
Start with these six habits
- Start with customer tasks. Know why people arrive, what they compare and what stops them, before redesigning anything.
- Standardize product truth. Titles, descriptions, images, variants, specs, badges and warranty follow repeatable rules, with category-specific extensions.
- Design mobile-first, validate by device. Use real analytics, not assumptions, to decide where to invest.
- Merchandise the whole journey. Awareness, category, product, cart, checkout and what happens after the purchase.
- Make every change measurable. Tie tests and merchandising changes to conversion, contribution, attachment, returns or search success.
- Govern it together. Merchandising, brand, product, creative, analytics, engineering, operations, customer service and legal all own part of the experience.
The product page
A product page answers the customer’s questions in order: what is it, why is it useful, will it work for me, what does it cost, can I get it, and what happens if it doesn’t work out.
The description follows the same order: a hook that states the most meaningful benefit, then the proof, then the use case, then the specifications in structured fields rather than crammed into the opening paragraph.
The audit
A good audit removes barriers in the shopping experience and makes the brand more transparent. It ends in a prioritized plan, not a list of defects. I look at three things first.
- Traffic. Where shoppers come from, why they click, and whether the landing page keeps the promise the ad or search result made.
- Conversion. Whether the page answers the decision questions, and whether cart and checkout work smoothly on every device.
- Assortment. Which products, categories and price bands deserve visibility, measured on contribution, not revenue alone.
Audits can feel personal, because they expose decisions teams have defended for years. So I frame every finding around the customer’s task and the system, never the person who built the page, and I give every accepted recommendation an owner, a date and a measurement plan.
Testing rules
- Write the customer problem and the hypothesis before choosing the design.
- Pick one primary metric and a few guardrails: contribution, returns, page speed.
- Check traffic and baseline before committing to an A/B test. Small stores may need longer tests or another method.
- Decide duration and stopping rules up front. Don’t stop because an early result looks good.
- Write down every result, including the null and negative ones.