更新记录

Adyen joins WhatsMenu's payment options. At checkout, customers get an Adyen-hosted payment link covering the cards and local methods enabled in your Adyen account. Once they pay, the order is automatically marked paid in your dashboard via Adyen's webhook.

Useful if you're already on Adyen for another sales channel and want to consolidate, or if you want access to Adyen's broad coverage of card brands and local payment methods worldwide.

Activate under Settings → Apps → Adyen, then plug in your Adyen API key, merchant account, and HMAC key.

If your storefront is on a custom domain and you used the delivery map at checkout, customers could see a RefererNotAllowedMapError instead of the map. That's because Google Maps API keys are tied to specific domains, and the platform's key was only authorised for the WhatsMenu domain.

You can now plug in your own Google Maps JavaScript API key under the DeliveryMap module settings. When checkout loads on your custom domain, your key is used; on the WhatsMenu subdomain, the platform key continues to be used. No customer change needed — the map just works again.

Only relevant if you're on a custom domain and your map was misbehaving. Keep the field empty to keep using the default.

Coupons used to discount the whole cart. Now you can scope a coupon so it only applies to specific items or to a whole category — without giving the customer a discount on everything else they're buying.

When creating or editing a coupon, choose what it applies to:

• All items — original behaviour, discount calculated on the full cart subtotal
• Specific items — only the chosen products / services count
• Specific categories — everything under those categories qualifies

Use it for things like "10% off all cakes", "$5 off any haircut service", or "free delivery on bouquets only" — without touching pricing on the rest of your catalogue.

You can now plug your own Mailchimp account into WhatsMenu so customer details from your store flow straight into your audience. Each store uses its own API key and audience — no shared list.

Once connected, customers are added to your Mailchimp audience automatically when they register or place an order (you choose which trigger to sync on). Their name, email, and phone come along.

Set it up under Settings → Apps → Mailchimp. You'll need your Mailchimp API key, server prefix (e.g. us14), and audience ID — Mailchimp shows them in your account settings.

If you use Detrack for last-mile delivery, jobs now go across cleaner: Detrack receives proper geocoded coordinates so drivers see the right pin, the payload is leaner, and webhook updates flow back into your order timeline more reliably.

The order details page also shows tracking status from Detrack as the driver progresses — accepted, picked up, delivered.

Nothing to change in your settings. Existing Detrack-enabled stores get the improved behaviour automatically on the next order.

Two settings to make WhatsMenu feel native for your country, wherever you operate from:

• Default country — choose the country your store is based in. Phone number inputs across the admin and storefront default to the right country code, and customer addresses preselect it too.
• Date and time format — pick how dates and times appear (US-style MM/DD/YYYY, UK-style DD/MM/YYYY, ISO, 12-hour, 24-hour, etc.). Applies everywhere dates show up — order timestamps, reports, scheduled deliveries.

Both live under Settings → Localisation. Existing stores keep their previous behaviour; the new defaults only kick in when you explicitly change them.

The WhatsMenu admin and storefront are now available in 18 languages. New additions in this release fill out coverage across Europe and Asia:

Arabic, Chinese (Simplified and Traditional), Dutch, English, French, German, Indonesian, Italian, Japanese, Korean, Malay, Polish, Portuguese, Russian, Spanish, Thai, Turkish, and Vietnamese.

Pick your admin language from the language switcher in the top bar. Storefront languages are managed per-store under your settings — turn on the ones your customers actually speak, and they'll see your menu in their language automatically.

Cashfree joins WhatsMenu's payment options. Once activated, customers checking out can pay with cards, UPI, wallets, or net banking — Cashfree covers 120+ payment methods across India and beyond.

Especially useful for India-based stores that already use Cashfree elsewhere, or merchants who want UPI as a checkout option without juggling multiple integrations.

Activate under Settings → Apps → Cashfree, then plug in your Cashfree app ID and secret key. The hosted payment page handles the rest.

Your store's name and description can now be translated for each language you offer. Customers browsing in Malay see the Malay version, customers in English see the English version — automatically.

The language selector in the admin and on your storefront also got an upgrade: it now uses your store's own language labels, so what you type is what your customers see in the picker.

Set translations under your company general settings; the language switcher is in the top bar.

If you take payments via QR code (DuitNow, Touch 'n Go, bank QR, etc.), customers can now upload a screenshot of their payment confirmation right after scanning. The proof shows up on the order details page so you can verify the payment matches before fulfilling.

Reduces back-and-forth on WhatsApp asking for proof, and gives you a clear audit trail for every QR payment. You can reset a proof if a customer uploads the wrong screenshot.

Available automatically for any merchant using the QR Code payment module — no setup needed.

Group your catalogue into time-based sections — breakfast, lunch, afternoon, dinner, late night — and only show categories during their hours. Outside those hours, the categories quietly hide.

You can configure dayparts per day of week, run multiple shifts a day, and assign each category to one or more dayparts. Customers only see what's actually available right now, no more "we don't serve breakfast after 11" replies.

Activate under Settings → Apps → Daypart, set up your time slots, then assign categories from the catalogue. Works for any time-segmented menu — restaurants, salons with morning/evening services, retail with happy-hour pricing, anything that runs on a clock.

Set a daily ceiling on how many orders or how many total items you'll accept each day. Once the limit is hit, the storefront stops accepting orders for that fulfilment date until tomorrow.

Useful for stores with prep capacity ("we can only make 150 items a day"), perishable inventory, scheduled delivery slots, or to keep weekends sane. Order and item caps are independent — set both, just one, or leave either at unlimited. Limits can be set per weekday, with one-off overrides for specific dates.

For caps on a specific product (only 30 of one item), use Stock Tracking on that item instead. Activate Daily Limit under Settings → Apps → Daily Limit. Counts reset at midnight in your store's time zone.

You can now configure whether the prices you set on items already include tax (common in EU, UK, Australia) or are net of tax with tax added at checkout (common in the US, Canada).

The cart and checkout adapt to your choice — tax-inclusive shows the tax breakdown without changing the total, tax-exclusive adds the tax line on top. Customers always see a clear breakdown so there are no surprises at the end.

Set the mode under your store's localisation or tax settings. Existing prices keep working as-is; switching the mode does not retroactively change item prices.

Customer signup forms on your storefront now have tighter bot protection — invisible reCAPTCHA, a hidden honeypot field, and stricter validation on names. Bots that automate fake account creation get blocked before they ever touch your customer list.

You should see fewer junk accounts, fewer rejected first-order coupons used by spammers, and cleaner customer marketing data. Real customers won't notice anything different.

No setup needed — the protection is on automatically across all stores.

You can now turn off the small "Powered by WhatsMenu" line in your storefront footer. Useful if you'd rather present a fully-branded customer experience or have your own footer copy.

Toggle it under your store settings. Off by default for new stores; existing stores keep the footer until you change it.

WhatsMenu's admin panel and storefront can now be displayed in multiple languages. The first release ships English, Chinese, and Malay — pick yours from the language switcher in the top bar.

Your customers see the storefront in their preferred language too, automatically based on their browser or your default. You'll see the language picker on customer-facing pages so they can switch if they prefer.

More languages roll out in the months ahead. No setup needed beyond turning on the languages you want to offer in your store settings.

A search bar now sits in the admin top bar. Type anything — an order number, a customer name, a product, a settings page — and jump straight to it without clicking through menus.

Especially useful when your catalogue grows past a couple of pages, when you're looking up a specific past order, or when you can't remember which settings tab a particular toggle lives on.

No setup. Open the admin and start typing in the search box at the top. Click a result to go straight there.

You can now plug an email-verification service into your storefront customer signup. When a shopper enters an obvious throw-away or invalid email (mailinator, tempmail, gibberish addresses, etc.), they're asked to use a real one before creating an account.

Helps keep your customer list clean — no more orders tied to addresses you can't email later, fewer fake accounts gaming first-order coupons, and saner marketing exports.

Optional. Activate under Settings → Apps → Email Validation; you'll need an EmailListVerify API key. Leave it off and signup behaves exactly as before.

When you set or change your storefront subdomain (the your-store-name part of your-store-name.whatsmenu.page), the form now catches problems earlier — invalid characters, reserved words, or names already taken — and shows a clear message explaining what to fix.

Previously some invalid subdomains slipped through and only failed later, sometimes mid-checkout for your customers. The tighter validation prevents that and keeps your storefront URL stable.

No action needed if your existing subdomain works — only new changes go through the new checks.