Quatrohaus WhatsApp Shopping System
Customer journey and estimated WhatsApp charges
Prepared: 2 November 2026. Audience: business stakeholders, customer-service staff and store operators.
This document describes the implemented shopping journey: WhatsApp chat handles shopping conversations, WhatsApp Flows handle consent and product search, and the merchant dashboard manages products and orders. Screenshot spaces are intentionally empty for the team to complete using the live system.
1. System overview
Customers start from the merchant's WhatsApp number. First-time customers accept the shopping terms and privacy notice, then browse products or search through a native WhatsApp Flow. A selected product returns to the existing chatbot for product options, quantity, basket and checkout. Customers choose an available payment method; the backend verifies the provider's payment status before treating the order as paid.
Store staff use the web dashboard to manage synced products, review orders and payments, and handle fulfilment. Customers do not need access to the merchant dashboard.
Customer path: Start chat → Accept terms and privacy → Welcome menu → Shop or Search → Select product → Choose quantity → Review basket → Checkout → Choose payment → Verified payment → Fulfilment/support.
2. Customer journey: WhatsApp view
Step 1 — Start the conversation
The customer opens the merchant's WhatsApp chat and sends a greeting such as “Hi”. This starts the shopping interaction. The business number and display name should be visible in the screenshot.
Step 2 — Accept the terms and privacy notice
A customer who has not accepted the current terms version is invited to open the consent Flow. The customer reads the summary, opens the full terms/privacy pages if needed, selects the acceptance checkbox and continues. The backend records acceptance for that customer and terms version. Returning customers who have already accepted the current version proceed to the menu; a new version requires acceptance again.
Step 3 — Receive the welcome menu
After completing consent, the customer returns to chat and receives the shopping welcome menu. The available choices are Shop, Search Products, View Cart and Talk to Support. The customer can type “menu” or “reset” to return to the menu.
Step 4 — Browse through Shop
Selecting Shop opens the existing chatbot category/product browsing experience. The customer chooses a category, then a product. This route continues to use the established chatbot rather than opening the Search Flow.
Step 5 — Search and filter through a Flow
Selecting Search Products opens the native Search Flow. The customer can enter a product name or SKU, select a category, or choose a displayed product. Tapping a category refreshes the displayed products for that category on the same screen. Search submission retrieves matching products from the backend.
Products show names, prices, availability and thumbnails where a usable source image exists. The initial view shows up to four featured choices; category and search results show up to eight choices. The selected category remains highlighted. If a category has no available products, the previous products are cleared and an explanatory message is shown.
Products reflect WHC's synced database. Store changes appear after the existing product sync completes. Images are converted into small thumbnails; products with missing or inaccessible images use a placeholder. The Flow uses WhatsApp's native layout and styling.
Step 6 — Select a product and return to chat
The customer selects a product and continues. The Flow closes and the existing chatbot resumes the product journey. Where applicable, the customer chooses a product option or pack size, then a quantity and adds the item to the basket. Selecting a product in the Search Flow alone does not add it to the basket.
Step 7 — Review the basket
The customer opens View Cart to review items, quantities and the total. They can continue shopping or proceed to checkout through the existing basket controls. Actual totals come from the backend, rather than the illustrative prices in concept designs.
Step 8 — Enter checkout and fulfilment details
The chatbot collects the customer's name and offers the existing fulfilment choices: Get Delivery Agent to Contact You or Store Pickup. The customer follows the relevant prompts and reviews the order before confirming. Delivery arrangements retain the existing system behaviour; this Flow work does not introduce a new delivery journey.
Step 9 — Choose a payment method
The payment menu offers Visa/Mastercard, EcoCash and InnBucks. Availability depends on the merchant's enabled provider, currency and supported payment methods. The same backend order and payment integration are used throughout.
Step 10 — Complete payment
Visa/Mastercard: the customer opens the card-payment Flow, reviews the payment information and confirms a contact number. Returning to chat provides the secure payment-provider checkout link. Card number, expiry, CVV and any bank verification are entered on the provider's page. The current implementation does not collect these details inside WhatsApp or its Flow. The contact number is saved against the order and is not an identity or ownership check.
EcoCash: the customer follows the existing mobile-payment prompts and provider authorisation process. InnBucks: the customer uses the existing hosted provider checkout, subject to merchant/currency support. A payment selection or a return from a browser does not by itself confirm payment.
Step 11 — Confirm payment and obtain help
The backend checks the payment provider's result before marking the order paid. The customer follows the existing confirmation and fulfilment messages. Failed, cancelled or pending payments must remain distinguishable from a successful payment. Talk to Support remains available through the chatbot's existing support route.
3. Merchant journey: dashboard view
Products & Sync
Store staff review imported products, prices, availability and images in Products & Sync. If a product has no image, add or correct the image in its source store and run the normal sync. Confirm the updated product appears in a fresh Search Flow session.
Orders & Sales
Staff open Orders & Sales to review orders, item details, totals and payment status. A pending order is not evidence of successful payment. Staff use the verified payment status before arranging fulfilment.
Deliveries and customer records
Staff use the existing Deliveries page for fulfilment operations and Customers for customer records. The journey retains the existing delivery workflow. These are internal merchant views, separate from the customer's WhatsApp experience.
Integrations & Credentials
An authorised administrator manages WhatsApp, Flow IDs, policy settings and payment-provider configuration in Integrations. This page is for merchant setup; it is not part of customer checkout. Mask all access tokens, API keys and other credentials before using a screenshot.
4. What creates a WhatsApp charge?
Meta messaging charges relate to outbound messages delivered through the WhatsApp Business Platform. They are separate from the price of the purchased product and from payment-gateway fees. Rates depend on the recipient's market and the message category, not on which dashboard page staff open. [S1]
The following planning assumptions use Zimbabwe (+263) recipients, USD and one business phone number. Current provider documentation reports October 2026 service-message charging after a monthly free allowance, and chargeable utility templates even inside an open service window. Meta's public overview still describes the earlier free-service arrangement; its detailed developer pricing page was login/rate limited during preparation. These are therefore budget estimates based on dated provider guidance, pending confirmation against the account's current Meta rate card and invoices. [S1–S4]
| Interaction | Estimated Meta treatment | Example in this system |
|---|---|---|
| Customer sends a greeting, text, reply or selection | No inbound Meta messaging fee | Customer sends “Hi” or selects a chat option. |
| Bot sends ordinary replies within the 24-hour customer-service window | Service messages; planning rate US$0.004 each after the first 1,000 monthly service messages per business number | Consent invitation, welcome menu, basket response or payment-method message. |
| Bot sends an interactive message that opens a Flow | Count the delivered invitation according to its message type/category | Search Products or the card-payment Flow invitation. A Flow is not automatically a marketing message. |
| Customer searches, changes category or views product images inside an already opened Flow | No separate chat-message unit assumed for each screen or backend exchange | Repeated category taps refresh the same Flow. Any additional delivered chat replies count separately. |
| Business sends a utility template | Planning rate US$0.004 per delivered template; do not subtract the service-message free allowance | A qualifying order/payment/delivery update. |
| Business sends a marketing template | Planning rate US$0.0225 per delivered template | A promotion or abandoned-cart campaign, subject to consent and Meta classification. |
| Business sends an authentication template | Planning rate US$0.004 per delivered template for the assumed recipient market | An OTP, if introduced later. The current contact-number Flow is not an OTP flow. |
| Staff view products, orders, customers or settings in the dashboard | No Meta messaging fee for viewing/editing alone | Reviewing a payment status. If an action sends WhatsApp messages, those messages are counted separately. |
| Customer pays on the provider's secure page | Payment-provider fees apply under the merchant agreement; no separate Meta card-processing fee is assumed | Visa/Mastercard checkout. A subsequent WhatsApp notification is counted separately. |
Service replies are permitted within the customer-service window, which runs for 24 hours from the customer's latest message. Outside that window, business-initiated contact requires an approved template. Budgeting for templates does not mean automated out-of-window order reminders or campaigns are already implemented. First-time terms acceptance is also not a substitute for marketing opt-in. [S1, S2]
The estimate assumes Flow screen changes are backend data exchanges, rather than additional delivered chat messages. Confirm this treatment with the account's actual billing records. A customer can have a long Flow interaction while the bot delivers only a few chat messages; conversely, several separate bot replies each contribute to service-message volume.
Estimated monthly messaging budgets
Assumed low-volume planning rates: service US$0.004; utility US$0.004; marketing US$0.0225. The first 1,000 service messages per business phone number per month are deducted once across that number, not once per customer or conversation. Utility templates and marketing templates are estimated separately. [S2–S4]
| Illustrative workload | Service messages | Utility templates | Marketing templates | Estimated monthly Meta total |
|---|---|---|---|---|
| 100 shopping journeys × 10 outbound service messages | 1,000 → US$0.00 after allowance | 100 → US$0.40 | None | US$0.40 |
| 500 shopping journeys × 10 outbound service messages | 5,000 → US$16.00 after allowance | 500 → US$2.00 | None | US$18.00 |
| 1,000 shopping journeys × 10 outbound service messages | 10,000 → US$36.00 after allowance | 1,000 → US$4.00 | None | US$40.00 |
| Same 1,000 journeys plus a 1,000-recipient campaign | 10,000 → US$36.00 after allowance | 1,000 → US$4.00 | 1,000 → US$22.50 | US$62.50 |
These are calculated examples, not measured usage or a quotation. Ten service messages per journey is a planning assumption; repeat searches, extra items and support can change actual volume. The separate utility-template message in each example is additional to those ten service messages and illustrates a possible notification, not a claim that a template is always sent.
Monthly Meta estimate = max(service messages − 1,000, 0) × 0.004 + utility templates × 0.004 + marketing templates × 0.0225 + authentication templates × 0.004.
An additional ordinary service reply after the allowance costs approximately US$0.004 under these assumptions. Ten such replies cost US$0.04. Taxes, currency conversion, hosting, WHC subscription/support, AI usage if enabled, advertisements, BSP markups if applicable, and payment-provider fees are excluded. The current integration uses Meta's direct Cloud API; no additional BSP fee is assumed. Different recipient countries may have different rates. Eligible free-entry-point windows and volume discounts are not assumed in these conservative examples.
Where the business checks actual charges
Open Meta Business Suite/WhatsApp Manager for the connected WhatsApp Business Account and review its usage, billing and payment settings. Use the account's current rate card, delivered-message usage and invoice totals to replace the assumptions above. WHC's Billing & Plans page is the system subscription area; this write-up does not claim that it displays or reconciles Meta's live messaging invoice.
5. Screenshot preparation checklist
Use the screenshot IDs in this document as filenames, for example CJ-05-search-category.png and DB-02-order-details.png. Replace each labelled placeholder with the matching image and a short caption. Use screenshots from the latest chat/Flow invitation so the current published layout appears.
Use test customers and orders. Mask phone numbers, addresses, email addresses, credentials and payment information. Never include card numbers, CVVs or OTPs. Keep WhatsApp customer screenshots separate from dashboard screenshots so readers can distinguish the two experiences.
Screenshots are to be supplied by the team. No screenshots or customer records have been captured for this document.
6. Sources and verification notes
[S1] Meta — WhatsApp Business Platform Pricing: https://business.whatsapp.com/products/platform-pricing. Accessed 2 November 2026. Supports delivered-message charging, category/market differences and the customer-service window. Its public free-service wording differs from the October provider guidance below.
[S2] Bird — WhatsApp October 2026 pricing changes: https://bird.com/docs/knowledge-base/whatsapp/october-2026-pricing-changes. Accessed 2 November 2026. Provider guidance on the service-message allowance and utility-template change. The detailed Meta reference linked there could not be retrieved during preparation.
[S3] OmniChannels.ai — Rest of Africa WhatsApp pricing: https://omnichannels.ai/whatsapp-pricing/rest-of-africa/. Accessed 2 November 2026; page states rates effective 1 October 2026. Source for the provisional USD service, utility, authentication and marketing rates and Zimbabwe market mapping.
[S4] FeeHub Zimbabwe — WhatsApp service-message calculator: https://feehub.co.zw/whatsapp-calculator. Accessed 2 November 2026. Independent cross-check of the +263 service-message estimate; it is not a Meta invoice or official rate guarantee.
Meta's detailed pricing reference for account verification: https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing.
Implemented journey checked against the repository's WhatsApp bot engine, shopping/payment Flow services and dashboard pages. This is a customer-facing explanation; it intentionally omits infrastructure secrets, access tokens and session data.