Prices and option ordering act as anchors
Aliases: price framing · price anchoring · strikethrough price · anchor audit
What it is
Anchors in an interface rarely happen by accident: most are placed there by designers. Strikethrough original prices, ordering options from expensive to cheap, default package tiers, minimum and suggested purchase quantities, price-history displays — each is a carrier. Price framing is the collective name for these reference values and ordering arrangements: the same price reads as expensive or cheap depending on what reference it arrives with. Every carrier answers the user's question "what counts as normal here," and the designer writes the question.
Why it happens
Display order and reference-value injection are designer choices. Laid out from expensive to cheap, the priciest item seen first calibrates everything after it, so the middle tier looks affordable; from cheap to expensive, each next item looks costlier than it is. Default package tiers fix "how much a standard user needs," minimum quantities fix "how much one should buy at once," strikethrough prices fix "what this thing is normally worth." Users do not arrive empty-handed: the last price paid and prices seen on other platforms form an internal reference price — and interface references compete with it, usually winning, because the interface reference is recent (right in front of the eyes) and salient (larger type, stronger placement, visual emphasis) while the internal one must be effortfully recalled, and the recalled number gets contaminated by the one on screen. That is why the same product looks like two different things in two different interfaces: change the anchor and the judgment follows.
Studying it
- Paradigm: the best-supported branch is the field experiment on quantity anchors — supermarket promotions with multi-unit pricing ("several for one price") or purchase limits against single-unit pricing, measuring changes in units bought; quantity anchors shift purchase volume directly, without requiring the multi-unit deal to be met. In the lab, showing one expensive product's price first and then measuring willingness to pay for related products produces the same shift. Field evidence for ordering effects is comparatively thin — most support comes from lab ordering experiments and practitioner observation.
- Variables: presence and level of the reference price, ordering direction (expensive-to-cheap / cheap-to-expensive), default tier and minimum quantity; outcomes are the distribution of tier choices, units bought, and shifts in preference for the middle tier.
- Methodological cautions: quantity anchors have field-experiment support; ordering effects rest mainly on the lab — in the field, users route around the given order with search, filters, and sort controls, and once attention reorders the sequence, the anchor's position moves with it. Porting lab ordering-effect magnitudes straight into conversion forecasts systematically overestimates.
Where it stops holding
Interface anchors work in full only where the user's internal reference is weak: for daily necessities and frequently repurchased categories, the built-in reference is strong and the interface pull shrinks — which is exactly where strikethrough prices proliferate, so the tug-of-war decides the actual shift, and strikethroughs cannot be assumed effective everywhere. Ordering anchors depend on the order actually being browsed: a user who jumps straight to a target price band or filters by price never encounters the sequence anchor; designs that rearrange attention — collapsed cards on mobile, only the top three options expanded — move where the anchor sits. Evidence boundary: reference-value injection is robust in the lab but diluted in the field by search and comparison behavior; for seasoned price-comparers the interface anchor and the internal reference may nearly cancel out.
Applying it
- Turn "what anchors live in this interface" into a checklist audit: walk the pricing decision path and list every number and every ordering users encounter (strikethrough prices, default tiers, minimum and suggested quantities, price history, sort direction), then label each a deliberate anchor or an ownerless number — ownerless numbers work as anchors all the same, just with nobody accountable for them.
- Treat ordering strategy as part of the pricing decision: first decide which tier the business means to push, then choose expensive-to-cheap or cheap-to-expensive — never default to the backend's natural order or the cheap-first habit.
- Leave room for the user's own reference: when prices change or package sizes shift, show the relationship to the last purchase prominently — make the comparison honest instead of letting the interface reference silently overwrite the remembered one.
- To validate: after the audit, run a one-variable experiment — change only the ordering, or only the reference price, and watch whether the tier-choice distribution moves; if it moves, the anchor is working, and you can then check it is pushing the tier you meant to push.