The FMCG playbook. Built in the builder, decided by your distributor system.
Ten journeys, five for consumers and five for the trade, each drawn below as it runs. The decision comes from your systems or criteria you set; the journey carries it. Aims are targets to agree in the pilot, not results.
Offer the second flavour the week the pack is scanned twice.
A second scan of the same pack this month asks your distributor system whether the second flavour is stocked nearby, then sends one WhatsApp with Send the code or Not now; a tap sends the code and the redemption comes back from your promotion system.
- Decides
- your stock and listing data.
- Aim
- second SKUs tried without a blanket discount.
Reach the scheme tier with one case, not a rep visit.
An order that lands one case short of the tier checks the count with your distributor system, then sends the retailer one WhatsApp with Add a case or Not this week; a tap adds it to the order and confirms the scheme reached.
- Decides
- your scheme rules and the count your system holds.
- Aim
- more retailers reaching the tier without a call.
Catch the retailer whose weekly order did not come.
An order day that passes with no order in your distributor system sends the retailer one WhatsApp with Reorder last week or Send a rep; a reorder is placed by your system, a rep request becomes a task, and silence across two cycles moves the outlet into RFM At Risk.
- Decides
- your order calendar and your distributor system.
- Aim
- missed orders recovered before the shelf empties.
Bring back the consumer who stopped scanning.
A consumer who enters RFM At Risk on your scan windows gets one recipe Story from the brand, not a discount; a read puts them in the segment for the next recipe, silence for thirty days moves them to Lost and the journey stops.
- Decides
- your RFM windows.
- Aim
- the drifting consumer reached before the brand is forgotten.
Turn the promotion entry into a redemption.
A promotion form completed inside a Story sends the code by WhatsApp after a consent check, waits for the redemption from your promotion system, thanks the redeemer with the second SKU offer, and reminds the rest once before the code expires.
- Decides
- your promotion system.
- Aim
- more codes redeemed at the till.
Turn a built cart into a placed order.
A retailer app session that ends with a cart and no order checks consent and stock, sends the cart back on WhatsApp with a Place the order button, falls back to SMS if there is no tap, and stops when the order lands.
- Decides
- your stock, then the retailer.
- Aim
- orders placed without waiting for the rep.
Capture the sampling name and sell the first pack.
A QR on the sampling stall opens a Story with a contact form; a completed form checks consent, fetches the nearest stockists from your system, and sends one WhatsApp with where to buy and a code for the first pack.
- Decides
- the form; your stockist list.
- Aim
- names from the stall turned into first packs.
Confirm the distributor's order by reply.
An order due from your distributor system sends one WhatsApp with Confirm or Change quantity; a confirmation is written back, a new quantity updates your system, and no reply becomes a call.
- Decides
- your distributor system; the distributor.
- Aim
- orders confirmed without a call.
Run the trade promotion with a hand on the brake.
A retailer list goes out as a bulk send you can pause or stop mid-run; an Interested tap opens the scheme Story and becomes a lead for the rep in your system, and no reply ends the journey.
- Decides
- the reply.
- Aim
- reach with a brake, and the interested followed up.
Offer the family pack to the consumer who scans every month.
A consumer who has scanned the same pack three months running asks your distributor system whether the family pack is listed in their region, then gets one WhatsApp with Send the code or Not now; the redemption comes back from your promotion system.
- Decides
- your listing data and your promotion system.
- Aim
- pack size moved up without a shelf-wide discount.
Where a step says your system decides, the journey calls your system and branches on its answer. xNotify carries the journey; it does not become the model.