On this page

In short
- QR codes on bills and shelves turn walk-ins into consenting contacts
- Order, pickup and repair updates as utility; catalog messages for the range; offers to consenting customers by outlet
- Teams per outlet on one number or a number per outlet under one account
Retail stores and chains use WhatsApp to turn walk-ins into contacts with a QR on the bill, to tell customers when an order, repair or alteration is ready, to show the range with catalog messages, and to bring consenting customers back with offers by outlet. VGraple CRM runs the QR flows, the pickup and repair stages, the catalog and the outlet teams; the outcome is a customer list the store owns and offers that sell instead of getting blocked.
The problem in numbers
Retailers know their regulars by face and lose them by number: the customer who bought twice has no record, the alteration is ready and nobody told them, the festive offer went to a WhatsApp group that nobody reads. The fix starts with the bill: a QR that opens a chat makes the customer a contact with consent recorded, and everything after is a utility message about their own order or a marketing message they asked for. Multi-outlet chains add routing: the customer's message should reach their branch, not head office.
Six things retail teams automate on WhatsApp

1. QR on the bill, contact with consent
The QR on bills, the counter and shelves opens a chat with a prefilled message naming the store; the flow thanks the customer, offers Track order, Catalogue and Offers, and asks 'Reply YES for offers' to collect marketing consent with the outlet recorded.
retail_welcome (session, free)
Thanks for shopping at {{1}}, {{2}}. Tap Catalogue to browse, Track for an order, or reply YES to get our offers here.
QR code generator, flow builder, consent capture.
2. Order, pickup and repair updates
POS or store events through webhooks, Zapier or the API move the order through stages; each sends a utility template: confirmed, ready for pickup, out for delivery; repairs and alterations the same way.
retail_ready_for_pickup (utility)
Hi {{1}}, your order {{2}} is ready for pickup at {{3}}. We are open till {{4}} today. Reply if you need it delivered instead.
Webhooks, Zapier, automation rules.
3. Catalog and reservations
Catalog messages show the range with prices; a reserve flow holds an item at the outlet and sends a utility confirmation; payment links close remote orders.
retail_reserved (utility)
Hi {{1}}, {{2}} is reserved for you at {{3}} till {{4}}. Reply to extend or cancel.
4. Outlet routing
A branch question in the flow, or the QR's prefilled text, routes the conversation to the outlet's team; head office sees everything; the Android app puts each outlet's queue on the floor staff's phones.
retail_outlet_intro (session, free)
You are chatting with {{1}}, {{2}} branch. Ask us about stock, sizes or your order.
Team inbox with teams and routing; the Android app.
5. Instagram enquiries
Product questions from reels and stories get the product card and a reserve button from the same flow; comments asking 'price?' get a DM.
retail_ig_reply (session, free)
Hi {{1}}, that is our {{2}} at Rs {{3}}. Reply RESERVE to hold one at your nearest outlet.
Instagram and Messenger inbox, comments.
6. Offers by outlet with consent
Once or twice a month, a marketing template to consenting customers of an outlet, segmented by category bought, with an opt-out, in the morning; retarget readers two days later.
retail_offer (marketing)
Hi {{1}}, this weekend at {{2}}: {{3}}. Show this message at the counter. Reply STOP to opt out.
Broadcasts with consent and delivery protection.
Franchise chains give each franchisee an outlet team and keep the templates and offers central, so the brand voice stays consistent while each outlet answers its own customers.
Feature map
| Job | Feature | Plan |
|---|---|---|
| QR flows with consent capture | Flow builder, QR generator | Free |
| Order, pickup and repair updates | Webhooks, Zapier, automation rules | Free |
| Catalog, reservations and payments | Catalog, payments | Free |
| Outlet teams and routing | Team inbox, Android app | Free |
| Instagram enquiries | Instagram and Messenger inbox, comments | Free |
| Offers with delivery protection | Broadcasts | Free within Meta limits |
| Staff across outlets | Seats | Starter to Scale |
What it costs
A store with 3,000 consenting customers and 800 orders and pickups a month: order and pickup updates (1,600 utility, about Rs 100 after in-window frees); reservations and repairs (400 utility, Rs 46); one offer to 3,000 consenting customers (Rs 2,589) and a retarget to 1,000 (Rs 863). Meta's total is about Rs 3,600 a month; VGraple CRM is Rs 1,499 on Starter for one outlet and Rs 3,499 or Rs 7,999 for chains with more seats.
A 30-day rollout plan
Week 1. Connect the number in coexistence mode; print QR codes for bills, counters and shelves; submit the templates; build the welcome flow with the consent step; connect the catalog.
Week 2. Order and pickup updates from the POS through webhooks or Zapier; reservation flow; outlet teams and routing.
Week 3. Instagram connected; repair and alteration stages; consent collection reviewed.
Week 4. First offer to consenting customers by outlet with a retarget; review contacts added per outlet, pickup replies, offer replies and blocks.
Getting the number ready
Most retail businesses already run WhatsApp on the owner's phone, so the first decision is how to connect: coexistence keeps the WhatsApp Business app working on that phone while the team uses the inbox, with up to six months of history imported; an API-only connection suits a new number for the team. Either way, Embedded Signup takes a few minutes, the display name is reviewed by Meta, and business verification in Meta Business Manager lifts the marketing limit from 250 unique recipients a day to 1,000 and beyond. Submit the templates on day one; most are approved within the hour, and the template library has an industry collection ready to submit.
Consent, privacy and the rules that apply
A customer who messages first has consented to service replies and to utility messages about that transaction; marketing needs an explicit yes, recorded with source and date, and an opt-out on every marketing template. VGraple CRM records consent automatically from inbound messages, YES replies, forms, ads and imports, suppresses opted-out and blocked contacts before every send, honours STOP and Meta's app-level opt-out at once, and keeps marketing to United States numbers paused as Meta requires. Personal fields are encrypted at rest, access is by role and team, and the audit log records exports and deletions, which covers India's DPDP Act and GDPR for retail data in practice. The opt-in rules guide has the detail.
Numbers to watch each week
First-response time on new conversations (minutes, not hours); the share of enquiries that reach the step that matters for retail (a booking, a visit, an order, an enrolment); utility messages sent and how many were free inside open windows; replies to the last marketing send; and blocks on it, which should stay under 0.2 percent. The Analytics page shows them per agent and per campaign on Starter and above; the channel page shows the quality rating and tier, which the blocks feed. A yellow rating is the signal to tighten the segment before the next send, not after.
Common mistakes
- Offers to WhatsApp groups or to every number on the bills; consent first.
- One number for five outlets with no routing.
- Pickup notices by phone call.
- Catalog prices out of date; re-sync after changes.
- Staff replying from personal numbers.
Why VGraple CRM for retail
QR-driven flows with consent capture, POS integration through webhooks and Zapier, catalog messages and payment links, teams per outlet with the Android app, Instagram and comments in the inbox, and broadcasts with consent, retargeting and delivery protection are on every plan. The WhatsApp CRM guide and the jewellery page cover related retail patterns.