Frequently Asked Questions

The customer sends your configured entry keyword, such as ORDER. The guided flow presents your shop and available outlets, then collects the selections and details needed to submit the order.

Yes. Configure categories, pictures, descriptions, prices and optional extras. Customers can use the visual web menu with pictures and Add buttons, or continue the existing paginated text menu in WhatsApp.

Yes. Customers can choose products and quantities and use configured modifier options. Configure required choices and selection limits carefully before testing your menu.

The menu presents up to ten products per page. Customers can use NEXT, PREVIOUS and BACK, and select a category or view all categories.

Yes, according to the outlet settings. Delivery requires an address and your own fulfilment arrangements. Check the address and delivery suitability before accepting the order; WebWMS2U does not provide riders or dispatch services.

Yes. Use a connected Personal WhatsApp device or your own supported Meta number. Meta sends remain subject to its customer service window, approved templates and separate delivery charges.

One outlet is included in the standard Ordering add-on. Extra outlets require an additional allowance and subscription. An account has one shop profile and can use shared or different outlet menus.

Yes. Share a catalogue or duplicate a menu for independent editing. Duplicated menus can reuse existing image references rather than creating additional image-file copies.

Published launch pricing is RM468 per year for one outlet, plus RM228 per year for each extra outlet, subject to quotation. The base plan, additional platform credits, applicable Meta fees, optional capacity and other quoted services are separate. See Ordering pricing.

Using the published figures, Starter RM588 plus Ordering RM468 totals RM1,056 per year before additional usage or other quoted costs. Starter includes 1,000 annual platform credits shared with other account activity. Use a supported Personal WhatsApp connection; own-number Meta use requires a suitable plan.

The quoted Ordering subscription does not add a percentage commission on order value. Subscription, message usage, delivery arrangements and any external payment-provider costs remain separate.

Pay on pickup is available for pickup orders, or you can use your business static DuitNow QR. For QR orders, payment is requested after merchant acceptance. The merchant remains responsible for checking funds received.

No. Customers can submit payment evidence through their private order link. Staff must check actual receipt of funds and mark payment verified; a screenshot alone is not automatic bank verification.

Configure email alerts, WhatsApp alerts or both. Staff can review and act through the dashboard, a private mobile management link or supported commands from the authorised merchant number. Keep private management links within your team.

Yes. Record a reason and send the customer the supported order update. The merchant must handle any refund separately and should provide an outlet contact for enquiries.

Use roughly 25–35 credits as an initial planning range for a simple one- or two-product order, not a fixed charge or limit. Actual usage depends on browsing, modifiers, corrections, notifications and status updates. Each handled inbound message and each outbound WhatsApp message counts separately.

Email alerts and browser actions themselves do not use Ordering platform credits. Any resulting WhatsApp notification does use credits. An authorised merchant WhatsApp command and its acknowledgement also generate message usage.

Yes. Search records by customer, phone, order reference and status. Use supported order printing or browser Save as PDF, and export available CSV reports. Keep order status and payment status under review.

Automatic stock reservation and standard POS integration are outside the current module. Check availability before accepting orders. POS mapping or other custom integration must be assessed and quoted separately.

See the Ordering overview, customer journey, pricing and Ordering FAQs, or contact us for activation.

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.