Discount code patterns
Where the promo code field lives says a lot about how a brand thinks about price-sensitive shoppers. The pattern depends on whether codes are central to acquisition or a rare exception, and how much leakage to coupon sites the brand can tolerate.
Inline field above totals
The promo input sits permanently inside the order summary panel above the breakdown. Always visible, accepts input the moment a shopper has a code in hand. Common on marketplaces and large retailers.
> what's good
- +Always visible, no extra click for shoppers who already have a code.
- +Sits next to the totals, so the discount visibly recalculates after apply.
- +Predictable position across desktop and mobile.
> what's risky
- ·Persistent field invites code-hunting on Honey, Google, or affiliate sites.
- ·Can shrink the perceived headroom of the summary panel.
- ·Empty error states need to be styled carefully to avoid scaring committed shoppers.
Collapsible have a code link
A single text link, hidden by default, that expands an input on click. The most common pattern across modern DTC checkouts because it deprioritises codes for the majority of shoppers.
> what's good
- +Hides the field from shoppers without a code, reducing leakage to coupon sites.
- +Keeps the summary panel visually clean, focuses attention on the CTA.
- +Easy to A/B test, the click-through rate is a clean signal.
> what's risky
- ·Shoppers with a code may scroll past, especially on mobile where the link is small.
- ·Hidden state can feel hostile to legitimate promo holders.
- ·Animation needs to be instant, slow expand creates abandonment risk.
Dedicated step with auto-apply
A full checkout step for codes and rewards. Shows already-applied codes, accepts new entries, and recommends eligible promotions the shopper qualifies for. Used by stores with loyalty programs and complex stacking rules.
> what's good
- +Auto-apply removes friction for first-order, free-shipping, and loyalty discounts.
- +Recommended codes turn the field into a value-add rather than a leak.
- +Clear stacking rules reduce the it didn't work support tickets.
> what's risky
- ·Adds a full step to checkout, only justified when discounts are central to merchandising.
- ·Suggested codes can feel manipulative if not tied to genuine eligibility.
- ·Auto-apply requires solid eligibility logic, false applies create chargebacks.