Detect pricing and promotion confusion in stores
A shopper picks up three of something because the sign says it's a deal, then it rings up at full price and they leave it at the till. NEXT reads what shoppers and store staff say across reviews, support contacts, and post-visit feedback, and groups the complaints that describe the same confusing price or promotion. What you get is an alert that names the promotion, the wording that confused people, which stores it's happening in, and how often.
Most of this never reaches you as a clean signal. It arrives as a one-star review, a line in a stand-down, a photo of a wrong sign forwarded from a regional lead — usually after the promo is half over.
What the pricing-confusion alert looks like
Example alert — confusing promotion clustered across stores
Promotion
"3 for £10" mix-and-match on soft drinks
What's confusing shoppers
The shelf edge reads "3 for £10," but single units scan at £4.50, and the discount only applies when all three are the same brand — which the sign doesn't say.
Where it shows up
38 stores, concentrated in the North region; first appeared the week the promo launched.
What shoppers say
"The sign said 3 for £10 but they scanned at £4.50 each and the assistant couldn't override it. I left them at the till."
"Couldn't tell if I needed my loyalty card for the deal. Put two back rather than risk it at the till."
Affected stores
38 of 210, clustered rather than spread evenly — which points at the sign wording, not a till fault.
Commercial exposure
Multi-buy baskets abandoned at the till in the affected stores. The promo was meant to lift basket size and is doing the opposite where the wording is unclear.
Signal strength
Strong and consistent on the "same brand" condition; mixed on the loyalty-card confusion, which shows up in fewer stores.
Example output based on grouped store feedback, support contacts, and review comments. The team starts from the grouped complaints, not a reconstruction.
How NEXT does this
NEXT reads where shoppers and store staff already leave feedback — reviews, support contacts, post-visit surveys, and store-level notes. It groups comments that describe the same problem: a price that doesn't match the sign, a promo condition no one explained, signage that contradicts the till. It keeps a running record of each cluster, so a one-off gripe and a repeating pattern look different. When a cluster crosses a threshold you set, NEXT writes it up — the promotion, the confusing wording, the stores affected, and a few verbatim quotes — and routes it to merchandising and pricing with a suggested fix. The ops team decides what to change and when.
Why pricing confusion surfaces late today
Today you hear about it in fragments. A store manager mentions it in a stand-down. A handful of one-star reviews land. A regional lead forwards a photo of a wrong sign. By the time anyone connects the dots, the promo is half over and the basket-size lift it was supposed to deliver is gone.
The tools you already have don't close that gap. Open a sales dashboard and it shows conversion dipped in the North region — it doesn't tell you a "3 for £10" sign is the reason. It reports what already happened, not what to do next. Ask an AI assistant and you get the loudest recent review, not the pattern across 38 stores.
And the detail thins at every handoff. The manager's exact words get paraphrased into a note, then summarized in a regional roll-up, then half-remembered on a call. By the time it reaches pricing, "the same-brand condition isn't on the sign" has become "some confusion about the soft drinks promo," which nobody can act on.
A faster dashboard still tells you conversion dropped. It doesn't tell you which sign to rewrite.
How this compares to the tools you already know
Approach | Where the evidence lives | What you do at decision time |
|---|---|---|
Mystery shopper / store audits | A scheduled report, weeks apart | Wait for the next cycle, then act on a snapshot |
Store feedback dashboard | Charts you have to open | Notice the dip, then go hunting for the cause |
NEXT | Grouped complaints routed to pricing with quotes and affected stores | Act on a written-up cluster as it crosses a threshold |
What changes for you on the ops floor
Right now, catching a bad promo depends on someone noticing and someone else caring enough to chase it. You find out late, and you find out vague. By the time the wording reaches pricing, it's lost the specifics that would let them fix it on the first pass.
With NEXT, the cluster arrives written up. You can see at a glance that 38 stores are hitting the same "same brand" condition, read two shoppers describing it in their own words, and forward it to pricing with the wording already attached. The promo looked fine in the launch plan; it didn't look fine at the till. That gap is what you now see early.
One ops lead's version of this: the conversion dip in the North looked like a regional softness until the grouped complaints showed it was one sign, in one promo, repeated across 38 stores. Different problem, much cheaper fix.
The judgment stays with you. NEXT brings the grouped complaints and the suggested fix; whether you reprint signage, retrain tills, or pull the promo is your call.
Downstream effects
Faster fixes to the actual wording. Pricing and merchandising get the confusing line verbatim, so they correct the sign rather than guess at it from a conversion chart.
Cleaner promo post-mortems. When the promo ends, you already have a record of where it confused shoppers and why — useful input for whether to run it again or change the mechanics.
Earlier read on store-level patterns. Because clusters are tied to stores, a confusion that's concentrated in one region surfaces as a region problem, not a brand-wide one.
Where the human stays in control
You set the threshold for what counts as a cluster worth routing — how many stores, how consistent the complaint, over what window. Below that line, thin or one-off comments stay out of the way; they're less likely to clutter the route to pricing. You can also require a human to review clusters before they're written into the pricing team's queue, so an ops lead confirms it's a signage issue and not, say, a till-software fault that needs a different owner. That's tuning the inputs, not approving every item by hand.
What to configure first
Coverage matters most. NEXT can only group what shoppers and staff actually write down, so the alert is only as good as your review, survey, and support feedback for the stores you care about. Decide which feedback sources feed it and check that store identifiers come through — a quote with no store attached can't be clustered to a location. Set the threshold to match how fast your promos move: a two-week promo needs a tighter window than an always-on multi-buy. Agree who owns the route on the pricing and merchandising side before you turn it on, so written-up clusters land with someone accountable rather than in a shared inbox.
Where this breaks down
Thin feedback in some stores
Stores where shoppers rarely leave reviews or fill in surveys will under-report. A real confusion there can stay quiet simply because no one wrote it down. Treat low-coverage stores as a blind spot, not a clean bill of health.
Confusion that's really a system fault
NEXT clusters what people say, and shoppers describe symptoms — "it scanned wrong" reads the same whether the sign is wrong or the till price file is stale. The route to pricing assumes a signage or mechanics fix; some clusters need IT or store systems instead, which is why a human check before routing helps.
Fast-churning seasonal promos
When promotions change weekly, a cluster can mature just as the promo ends. Tighten the window for short campaigns, or you'll be fixing signage for a deal that's already gone.
Quotes without store identifiers
If feedback arrives stripped of which store it came from, NEXT can see the confusion but can't tell you where it's concentrated — which removes most of the operational value. Fix the identifier flow before relying on store-level counts.
FAQ
How is this different from our sales dashboard?
A dashboard tells you conversion or basket size moved. It doesn't tell you why. NEXT groups the actual shopper complaints behind the move — the promo, the confusing wording, the stores affected — and routes them to pricing with verbatim quotes. You go from "conversion dipped in the North" to "this sign, this condition, 38 stores."
Does NEXT decide which promos to fix or pull?
No. NEXT surfaces and groups the confusion and suggests a fix. Whether you reprint signage, retrain tills, change the mechanics, or pull the promo stays with the ops, pricing, and merchandising teams. It brings the grouped complaints to the decision; it doesn't make the call.
What sources does it read?
Reviews, support contacts, post-visit surveys, and store-level notes — wherever shoppers and staff already describe what happened. It doesn't need a new app or a new place for people to log issues. Coverage varies by store, so the alert is strongest where feedback is richest.
How does it avoid flagging every minor gripe?
You set a threshold — how many stores, how consistent the complaint, over what window. One-off or thin comments stay below the line and don't reach the pricing team's queue. You can also require a human to confirm a cluster before it's written in.
Can it tell signage confusion from a till or pricing-file fault?
Not perfectly. Shoppers describe the symptom, and a wrong sign and a stale till price can read the same way. NEXT clusters the language and routes it; a human review step lets an ops lead confirm whether it belongs with pricing, merchandising, or store systems before it's actioned.
How quickly does a cluster appear?
A cluster forms as enough matching feedback accumulates and crosses your threshold — sooner for high-feedback stores, later for quiet ones. It's earlier than waiting for the next audit cycle, but it depends on shoppers actually writing the confusion down, so tune the window to how fast the promo moves.