Promotions & marketing

Create a code with a percentage or fixed discount, an optional minimum order, usage cap and validity dates. The customer types it at checkout; our server re-prices the real cart and shows the true value before ordering. A code's use is only consumed when an order actually completes with it.

Yes — buy-X-get-Y coupons count the qualifying items in the cart and discount the reward item accordingly. The reward is never force-added to the cart; the customer stays in control of what they're buying.

Yes — coupons can exclude categories or specific items. The discount then applies to the eligible part of the cart, while any minimum-order requirement still measures the whole cart.

One message covers them all deliberately — expired, used up, below minimum, unknown code — so codes can't be fished. Check the coupon's dates, cap and minimum in your panel; the customer-facing message stays intentionally vague.

Rules like 'goes great with' (pair a drink with select mains), cart-threshold treats ('free dessert over 120'), checkout add-ons, and a first-order welcome offer. Offers appear in the item popup, the cart and the summary; every offer is re-validated server-side at checkout so an expired deal can never be charged wrongly.

Pick-N-for-a-price deals ('any 3 mezze for 49'). A bundle is a PRICE, not a discount line: the chosen items are re-priced so the receipt, any minimum-order rule and even VAT all see the deal price naturally. A mystery item can ride inside a bundle too.

Choose a template (seasonal packs included — Ramadan, Eid, National Day), fill in the bracketed blanks — the composer refuses to queue while any [bracket] is left unfilled — pick the audience, and send. Delivery respects every safety rail below.

Four rails, always on: a weekly per-customer cap you set; a review queue that HOLDS any customer matched by multiple campaigns at once until you approve or discard; a 10:00–21:00 local sending window enforced at send time; and automatic exclusion of numbers whose recent messages failed. These exist to protect your WhatsApp number as much as your customers.

On Marketing → Channels, each kind of automatic message has its own row: tick WhatsApp, the wallet card, both — or 'Wallet first', which sends each customer exactly ONE message: to their wallet card when they hold one at send time, on WhatsApp when they don't. The shipped default is WhatsApp only; wallet messages are free, unbannable, and never count against the weekly cap. Untick everything on a row and that promotion goes completely silent. Ticking both is the safest combination (a deleted wallet card can go unnoticed); Wallet first is the cheapest that still reaches everyone — its one honest risk, stated on the page, is that a card deleted without Google telling us can swallow a message. Campaigns are the one exception: they choose their channels per send, in the composer.

A scratch card or prize wheel offered after delivery — the customer plays, wins whatever you configured (a code, a free item), and prizes are minted single-use. Dine-in has its own set: scan-again perks, table streaks, a happy-table draw and a treasure hunt.

A customer shares their link; when the friend's first order is delivered, both sides receive the reward you configured. Rewards are minted as single-use codes and the payout settles exactly once per new customer — a cancelled first order pays nothing until a real one delivers. It ships OFF until you enable it.

After delivery the customer is invited to leave a Google review with a small thank-you attached. A visible policy note is built in: platforms frown on rewards conditioned on POSITIVE reviews, so the invitation rewards reviewing, not praising — keep it that way.

Customers can round their total up to a cause you name. The pledge is computed on our side, itemised separately on the receipt, and correctly excluded from VAT (a donation is not a taxable sale). Totals per order are recorded so the amounts you hand over are auditable.

Rules that react to real local weather — a hot-day drinks push, a rainy-day delivery nudge. Weather is checked platform-side; the resulting messages route through the standard marketing rails like everything else.

Building-level promotions for the towers you deliver to: a building deal that unlocks when enough distinct customers from one building order, and a 'condo captain' perk for the building's most frequent customer. Minimum sizes are enforced so no one's identity can be guessed from a tiny building.

A seasonal mode that switches your page to your Ramadan hours automatically (driven by cached prayer times — never a live lookup during checkout), offers an iftar countdown, and can attach an iftar deal or gift. When Ramadan ends, normal hours return by themselves, everywhere at once.

Complete-the-meal suggestions based on real pairing patterns, a beat-the-rush prompt in quiet windows, and a round-up rescue that suggests the cheapest item that lifts a cart over your minimum order. All display-only salesmanship — the money math stays server-side.

Yes — member-tier discounts apply automatically for qualifying customers, and time-window item pricing exists for happy-hour-style pricing per item. Automatic percentages never stack with a typed coupon: the customer gets the better one.

A gentle analysis of your sending patterns that suggests when a campaign would land better and warns when you're crowding your audience — advice, not automation; nothing sends itself.

Group orders don't accept coupons (a shared cart with one payer makes code discounts messy — this is deliberate), but participants still count for promotions and can be pitched the loyalty card at join time.

The campaign and promotion views show sent/delivered/failed counts, and the dashboard's revenue view shows redemptions itemised on orders (coupon codes are stored on each order). Judge a promotion by orders, not sends.

Two doors, one screen: Marketing → 'Review queue & weekly cap', or Reports → Message history → the 'Marketing review' tab (it carries a badge when something waits). The field is 'Marketing messages per customer, per week' — default 2, maximum 14; set 0 to review every marketing message before it goes. The same screen lists each held message in full with the reason, and offers Approve & send, Don't send, Approve all and Discard all.

No — the cap counts WhatsApp marketing only. Wallet-card messages are free and never counted or held, and order confirmations, delivery updates and rider details are never counted either.

Marketing → the 'Abandoned carts' card, under 'Bring them back' — it opens straight onto the right section. Switch it on, set the wait time and the message, and when somebody fills a cart, leaves their name and number, and does not order, a message is prepared. It is NEVER sent automatically: every abandoned-cart message waits on the Marketing review tab for your explicit approve — permanently, by design, with no setting to change that. Cart details themselves are kept three days at most, and deleted immediately if that person orders. Your Orders board also shows a live count chip — how many carts are currently sitting unfinished — which links to the same settings.

An automatic percentage off every order placed inside a time window you choose — for filling a quiet hour, no code typed. It ships off, and it costs margin on customers who would have ordered anyway. Both times are INCLUSIVE ('before noon' = end 11:59), judged on our server in your restaurant's own timezone, never on the customer's phone.

You do. The pledge is paid to you with the rest of the order — cash at the door or on your card machine — and the platform never receives, holds or forwards any of it; you remit it to the cause you named, and customers are told exactly that at checkout. The Games & extras page shows 'Pledged by customers' — that is what you owe the cause — and your revenue is reported with donations already removed.