Bake the
next visit.

Trigger-based WhatsApp, sent through Wati, based on what members actually buy in store. This is what we want to run and the data we need EPOS to open up for it.

EPOS saleTriggerWhatsApp via Wati
10Use cases
6Need item-level data
4Run on totals only
1Promo WhatsApp per week, max

The goal

01

Use EPOS purchase and member data so Wati can send the right WhatsApp at the right moment: activate new members, get a second and third visit, lift basket size, and win back lapsed members, without doubling up on messages the Rewards system already sends.

10 use cases

Needs itemsTotals ok
#Use caseGoalTrigger and timingMessage angle
01Welcome 20% nudgeTotals okActivate new memberWelcome voucher still unused on day 7, again on day 25"Your 20% is still waiting. Grab a bagel before it goes."
02Second purchaseNeeds itemsSecond visit3 to 5 days after the first order, offer on a different category"Tried [category]? Next one's on the other side: toast or shio pan."
03Win-back into PAWA TrailTotals okReactivate lapsed21 to 30 days with no purchase, then 60 and 90"Miss you. Jump on PAWA Trail: 5 stamps, free Casarine."
04Trail progressNeeds itemsThird visit and beyondAfter each stamp; voucher at 5 of 5"2/5 done, toast next." / "Trail done. Casarine's yours for 14 days."
05Buy-any-5 upsellNeeds itemsBigger basketNear real time, basket of 3 or 4 items"One more and the next bagel's free today."
06Points near a rewardTotals okRepeat visitBalance reaches 80 points"You're [N] points from $5 off."
07Points expiryTotals okReactivate30 days before a batch of points expires"Your points expire [date]. Use them on your usual."
08Birthday monthTotals okVisit and basketStart of the month, reminder mid-month if unused"It's your birthday month: 5% off is on. Treat yourself."
09Favourite item backNeeds itemsRepeat visitMember's top item returns, or a related flavour launches"[Item]'s back at [outlet]."
10Home outletNeeds itemsRelevance in every messageWoven into win-back and Trail messages"See you at [PLQ / JEM / …]?"

Cadence cap: at most one promotional WhatsApp per member per week. Trail stamps and voucher issues are transactional and sit outside the cap.

What EPOS needs to expose

03
Real time

Every sale, as it happens

  • Member ID and phone
  • Date, time and outlet
  • Line items: product code, category, quantity, price
  • Basket total and any voucher used
Profile

Member records

  • Sign-up date
  • WhatsApp marketing opt-in (PDPA)
  • Birthday
  • Points balance and expiry per batch
Read / write

Vouchers

  • Create and cancel through the API
  • Issued, redeemed and expiry status
Reference

Catalogue and history

  • Product list mapped to categories
  • Purchase history lookup by member

Why item-level data matters

04
Needs items6 of 10

These depend on knowing what was bought, in which category, and when: Trail stamps, the second-purchase category switch, one-category cross-sell, buy-any-5, favourite-item alerts, and lapse timing based on each member's usual gap.

Totals ok4 of 10

Totals and dates alone cover the welcome reminder, simple win-back, points and birthday messages.

Fallback

If full history isn't possible, we'd need a live alert for each new sale with its line items, plus a one-time export of the last 12 months. Another option is a per-member summary EPOS keeps updated: last purchase, visit count, average basket, categories bought and top item.

Questions for EPOS

05
  1. Can you send real-time webhooks for each sale, or only scheduled exports?
  2. Do transactions come with item-level and category data?
  3. Can we create and cancel vouchers through the API?
  4. Can we get the live points balance and the expiry date for each batch?
  5. Is the PDPA marketing opt-in flag available, so we only message members who agreed?
  6. What are the rate limits, and is there a cost for API access?
  7. Which WhatsApp messages does Rewards already send itself, so members aren't messaged twice?
  8. Is there a test environment, and how long does setup take?