From QR Code to Repeat Order: The Full FMCG Customer Journey on WhatsApp
The walkthrough below is illustrative — a composite of how the pieces of a WhatsApp ordering system connect, not a real customer's data or a specific client's results. Names and specifics are invented for clarity.
It's easier to understand what a complete WhatsApp commerce system does by following one order through it, start to finish, than by listing features in the abstract. Here's what that looks like.
Step 1: The shelf
A shopper — call her Nomvula — is standing in front of a snack display at a spaza shop. A small QR code sits on the shelf tag next to the price. She scans it with her phone's camera, the way she'd scan any QR code now, and it opens WhatsApp with a message already drafted: a product code and the store's location, ready to send.
This is the entire "install" step. No app, no form, no account.
Step 2: The opt-in
She sends the pre-filled message. The business's WhatsApp number replies within seconds — not a human, a conversational flow — confirming the product she scanned, showing the price, and asking if she'd like to see similar items or add it straight to an order. At this point, she's implicitly started a service relationship: the business now has her number, tied to a specific product interest, with nothing more invasive than what she just did herself.
Step 3: Catalog browsing, narrowed to what's relevant
She taps "show similar," and instead of a long product list, the flow narrows by category — snacks, then a few options within that category, each with a price and a one-line description. She picks two items. A running cart total updates in the same thread as she adds them.
Step 4: Checkout, without leaving the chat
She confirms the cart, picks "collect in-store" as the fulfilment option (the flow already knows which store she's near, from the QR code she scanned), and pays via a link that opens a secure payment page and returns her straight to the conversation once done. The whole thing — scan to paid order — happens in a few minutes, inside one app she already had open.
Step 5: Confirmation and status
She gets an order confirmation with a reference number and an estimated collection time. No separate tracking page to check — the same thread updates her when the order's ready.
Step 6: A few weeks later — recognised as a returning customer
Nomvula scans a different QR code at the till on her next visit, or simply messages the same number again. The system recognises her number against her order history and greets her differently this time: "Welcome back — want to reorder your usual, or see what's new?" She didn't have to re-explain anything she'd already told the business.
Step 7: The re-order, in one tap
She taps "reorder my usual." The cart populates with her previous order, she confirms it as-is (or swaps one item), and checks out again — faster than the first time, because the system already knows what "her usual" means.
Step 8: Loyalty, surfaced naturally
After a handful of repeat orders, she gets a message letting her know she's reached a loyalty tier, with a small reward attached to her next purchase — tracked automatically from her order history, not a separate loyalty card or app she'd need to remember to bring.
Step 9: The abandoned-cart case (a different day, same customer)
On a different visit, she starts building a cart but gets interrupted and never checks out. Half an hour later, a short message checks in: "Your cart's still here — want to finish?" with a one-tap action to complete it exactly as she left it. (We cover what the actual recovery-rate data supports for this step in a separate guide on WhatsApp cart recovery.)
Two variations on the same journey
The walkthrough above is one path through the system — a single product, in-store collection, a straightforward repeat customer. The same underlying pieces support journeys that look quite different on the surface:
A delivery-first customer who never visits the physical store at all: their entry point might be a click-to-WhatsApp social ad instead of a QR code, their fulfilment choice is home delivery instead of collection, and their "repeat order" trigger might be a scheduled reminder ("running low on your usual order of X? reorder here") rather than a second shelf scan. The catalog, cart, payment, and loyalty logic underneath is identical — only the entry point and fulfilment choice differ.
A customer who hits a snag — say, the item she wants is out of stock at her nearest branch. Instead of a dead end, the flow can offer the nearest branch that does have it, or offer to notify her the moment it's back in stock at her usual branch. Either path keeps her in the conversation instead of losing the sale to "sorry, we don't have that" with no next step.
What a business sees on the other side
While Nomvula experiences the journey above as a series of quick chat exchanges, a staff member on the retail side would, in a properly connected system, see something different: a live dashboard showing today's WhatsApp orders by branch and status, which conversations are fully automated versus waiting on a human, which customers just crossed into a new loyalty tier, and which abandoned carts are mid-recovery. That dashboard — not the chat interface itself — is usually where the actual day-to-day value shows up for the business, since it turns what would otherwise be hundreds of separate, untracked conversations into one operational view.
What's actually running underneath this, end to end
Walking through Nomvula's journey makes visible what has to work together for any single step to feel simple on her side:
- A product catalog tied to real stock, by branch.
- A conversational ordering flow that narrows choices instead of dumping a full catalog into the chat.
- Payment and fulfilment logic that adapts to collection, delivery, or other options the business offers.
- Customer recognition by WhatsApp number, with order history attached.
- A loyalty engine reading from that same order history automatically.
- A cart-recovery trigger watching for abandoned sessions.
- A live dashboard so staff can see all of this happening across many customers at once, and step in as a live agent if a conversation needs a person rather than the automated flow.
None of these pieces is exotic individually. The value — and the engineering effort — is in making them work as one connected system instead of five disconnected tools that each handle one step and lose the thread between them.
Where Zentrya fits
This is the exact flow Zentrya's FMCG and retail platform is built around: WhatsApp catalog ordering, re-ordering, loyalty tracking, abandoned-cart recovery, and multi-branch stock, all connected to one customer record and one staff dashboard. See the FMCG & Retail solution for the full platform, or read the complete guide to WhatsApp ordering for retail and FMCG for how each piece above is actually built.
Frequently asked questions
Is the journey in this article based on a real customer or client?
No — it's an illustrative walkthrough built to show how the pieces connect end to end, not a real individual's data or a specific client case study. Any names, products, or details are invented for the purpose of explaining the flow.
Does every business need all of these steps, or can you start smaller?
You can start with just ordering and build the loyalty and re-order layers on top later — most businesses do. The full journey below shows where those pieces fit once they exist, not a requirement to launch with everything at once.
What's the minimum needed to get the first step (QR to chat) working?
A WhatsApp Business number, a catalog loaded into the ordering system, and a printed or digital QR code linking to that number with a pre-filled message identifying the product or location — that's enough to go from zero to a working first step.
How does the system know it's a repeat customer and not a new one?
By recognising the customer's WhatsApp number against order history — the same number that placed a previous order is automatically matched, with no login or account creation needed on the customer's side.
What happens if the customer wants to talk to a real person partway through?
A well-built flow hands off to a live agent at any point, with the conversation history visible to the person taking over, so the customer doesn't have to re-explain where they were in the process.
See how Zentrya's Healthcare AI platform handles reminders, booking and live-agent handoff.
Explore the Healthcare AI solution