Stay in WhatsApp chat
Customers can complete the whole ordering or booking process through the guided WhatsApp chat. The web link is optional.
Understand setup, payments, notifications, platform credits, storage and the scope of the Ordering module.
Customers can complete the whole ordering or booking process through the guided WhatsApp chat. The web link is optional.
One optional link opens a branded page with pictures, descriptions and clear selection buttons. Customers can browse, review and submit on mobile or desktop, then return to the original WhatsApp conversation.
Web selections and form steps use mobile data or Wi-Fi and do not generate an additional WhatsApp exchange for every choice. Replacing those chat steps can reduce platform-credit usage and applicable Meta delivery charges.
From chat to the web page and back: one connected customer journey, with the original business number and your existing merchant workflow.
Savings come from fewer chargeable WhatsApp messages—not from mobile data itself. Actual WhatsApp replies, alerts and reminders still follow platform-credit rules and applicable Meta charges. Normal internet/data costs still apply.
The visual web menu is optional. Customers can follow its link or continue using the existing chat ordering flow.
Yes. Both channels can offer the same responsive menu. Notifications remain associated with the number/device that started the conversation.
Yes. Product cards, cart and checkout adapt to phones and larger desktop screens. No additional customer app installation is required.
Web browsing and form submission do not use WhatsApp inbound processing credits. Real WhatsApp replies and notifications still use platform credits; applicable Meta charges are separate.
Yes. The web preview can complete a simulated checkout with a TEST reference, without creating a live order, sending notifications or deducting credits.
No online payment gateway is added. Existing pay-on-pickup and configured DuitNow QR workflows still apply. QR payment instructions follow merchant acceptance; staff verify actual funds.
No. Staff must verify payment in the bank account. Uploading a receipt is evidence for review, not automatic payment verification.
Live POS delivery is not included in this release. Saved provider preferences and neutral order JSON are a foundation; each provider still needs an authorised, tested adapter.
The current flow uses a private, time-limited link generated from WhatsApp or merchant preview. The bare subdomain is not a public shop directory or a permanent storefront link.
Repeated submissions through the same invitation return the same order. A newly generated invitation can be used for another order.
No. Customers can complete the entire process in WhatsApp chat. The web link is optional and leads to a branded page; customers can return to the original business conversation afterward.
Web selections and form steps use mobile data or Wi-Fi and do not generate an additional WhatsApp exchange for every choice. Replacing those chat steps can reduce platform-credit usage and applicable Meta delivery charges. Savings come from fewer chargeable WhatsApp messages—not from mobile data itself. Actual WhatsApp replies, alerts and reminders still follow platform-credit rules and applicable Meta charges. Normal internet/data costs still apply.
Restaurants, cafés, bakeries, home kitchens, florists, gift sellers and businesses with straightforward fixed-price products. It is suited to pickup and merchant-managed delivery; specialised stock, logistics or pricing workflows require separate assessment.
Yes. A basic keyword can send a menu or a link. Ordering guides the customer through outlet selection, fulfilment, details, products, quantities, options and confirmation, then saves an order for merchant approval and updates.
Yes. One shop profile can serve several outlets, each with its own settings. Your quoted Ordering subscription includes one outlet; additional outlets can be added to your subscription. Increasing the allowance does not create outlets automatically.
Yes. Share one menu for common pricing, or duplicate it for independent edits. Existing image files are referenced within your account rather than copied when menus/outlets are duplicated.
The optional visual web menu shows product pictures, descriptions and Add buttons. Customers can also use the existing paginated text catalogue in WhatsApp, where a product picture appears after selection. The shop can greet customers with an optional logo.
Yes. BACK, cart inspection and removal controls help customers review and edit an incomplete order. Confirmed-order changes should be discussed with the outlet. One order cannot combine products from different outlets.
Normally no. The system uses your WhatsApp sender phone when available. The customer still supplies their full name. If the channel cannot resolve a usable number, a manual phone step is shown; a PHONE option allows an alternative contact.
Pay on pickup is available for pickup orders only. An outlet can also offer a merchant-uploaded static DuitNow QR. Delivery orders require QR currently. QR payment is requested after merchant acceptance.
No. The customer uploads a receipt through a private browser order link. Staff must verify actual bank funds and mark payment verified. QR orders cannot enter preparation until payment is verified. Refunds remain manual.
Choose email, WhatsApp or both for each outlet. Review and act from the dashboard, a private mobile link, or authorised WhatsApp commands. Declines/cancellations require a reason and send the customer an update with outlet contact instructions.
Meta and Personal WhatsApp are supported through the same Ordering engine. Use your own eligible number/device. Meta merchant alerts and customer updates outside the service window require configured approved templates. Channel eligibility and limits depend on the base platform plan.
Ordering uses one platform credit for each processed inbound WhatsApp message and one for each outbound WhatsApp message, including merchant alerts and customer updates. Unmatched inbound messages have no Ordering charge. Emails, account preview and browser actions use no Ordering message credits; resulting WhatsApp messages are charged.
Allow about 25–35 credits for a simple one- or two-product order as a planning guide. A specific one-outlet pickup example uses 24 credits for one product or 28 for two different products, including five dashboard-triggered customer updates and one merchant WhatsApp alert. Extra browsing, modifiers and WhatsApp merchant commands increase usage. See the costing page for assumptions.
The service reserves a WhatsApp credit immediately before sending. A definitive failure refunds any reservation once. An uncertain submission retains the reservation because delivery may have occurred; it is not automatically resent. Duplicate provider message IDs are handled idempotently.
No. WebWMS2U subscriptions and platform credits are separate from applicable Meta charges. Check the current Meta rate schedule for your message categories and recipient markets; no fixed Meta rate is promised here.
Ordering is an annual add-on including one outlet, with a lower annual fee for additional outlets. It requires a compatible base WebWMS2U subscription. Confirm the displayed launch rates and selected services in your quotation.
Yes. View creation-period/current-status order statistics over seven days, a month or a year, export CSV and use browser Print/Save as PDF. The order list supports name, phone/reference and status search. Notification logs also support filters, pagination, sorting and CSV.
Completed, cancelled and rejected orders can be archived and restored. Archived orders remain in reports and still occupy storage. Archiving keeps your records available; contact support to discuss any permanent removal and retention needs.
Product images and uploaded QR receipts usually matter more than basic order fields. A starting storage arrangement of 2 GB per account, plus 0.5 GB per extra outlet, is available subject to quotation, with optional expansion as your records grow. Use compressed images; there is no built-in automatic resizing yet.
POS integration is deferred until the core ordering system is stable. Future adapters will use a common order schema and mappings for individual POS APIs. Compatibility is assessed separately; universal POS support is not promised.
No. Ordering and Booking are separate modules and must be individually activated. The current Booking module is Meta-only. Ordering works with both supported WhatsApp channels.
Contact us to arrange activation and setup. Test your customer journey, channel, Meta templates where needed and merchant notifications before accepting live orders. A general platform trial does not automatically activate Ordering.
Tell us your outlet count, catalogue size, preferred WhatsApp channel and expected order volume. We will help you assess the setup and confirm a quotation.
Contact us to arrange Ordering activation and setup. A platform trial does not automatically activate Ordering.