更新记录

Upload an item photo, click one button, get a draft name, summary, and description in your panel language. Useful when you have a folder of product shots but no copy yet — or when "good chair, $30" is all the spreadsheet import left you with.

Where to find it. Open any item edit page. Once a main image is uploaded, Generate from image sits in the top-right corner of the Basic Information card — right next to the name, summary, and description fields it fills in. Click it.

What you'll see. A modal opens with your photo on the left and three suggested fields on the right — Name, Summary, Description. Click Insert into all three fields to fill the form. Nothing saves until you press the item's own Save button, so you can edit any of the three suggestions first.

Re-roll if it's off. Click Generate again for a fresh draft from the same photo. Each generation is 3 credits; the first cached response on the same photo is free if you re-open the modal later.

It only describes what it can see. The AI looks at ingredients, materials, finish, colours, distinguishing features — and writes catalog copy from that. It doesn't invent prices, brand names, or specs that aren't visible. Clear product-on-clean-background photos give noticeably better results than dim or cluttered ones.

Industry-aware framing. The AI pays attention to the right visual cues for your business:

• Food & beverage photos — ingredients, plating, portion size, packaging
• Retail photos — material, finish, colour, dimensions, distinguishing features
• Specialty / handmade photos — materials, craftsmanship details, finish, scale

Hidden when it wouldn't help. The button doesn't appear on service-industry stores (haircuts, lessons, repairs, consulting), where a photo of a storefront or staff portrait wouldn't produce useful catalog copy. Set your Business industry under Settings → General to a product industry and the button shows up.

Works alongside auto-translate. Generate first in the language you're editing in, then turn on AI auto-translate to other menu languages when you save. The same content fans out to every other configured menu language for the price of one auto-translate run.

If you run your storefront in more than one language, you've probably spent more evenings than you want re-translating items. Auto-translate is the fix: tick a checkbox on an item, save, and AI Kit fills in the name, summary, and description in every other language you've enabled — automatically, in the background.

Per-save action, not a persistent setting. The checkbox always starts unticked when you open an item. Tick it for this save if you want translations to fan out — every subsequent save where you leave it unticked is just a normal save with zero AI calls and zero credit spend. No surprise translations, no accidental re-overwrites.

Translates the whole item, not just the description. When you tick it, the AI fans these fields out to every other menu language:

• Item name, summary, description
• The custom title you set for the add-ons group (e.g. "Choose your sides")
• Variant group names (e.g. "Size", "Colour")
• Add-on names (e.g. "Extra cheese", "Side salad")

So the storefront stays fully consistent in every language — not just the long-form description but every label the customer sees on the item modal.

Two modes, on the same form. Tick the main checkbox and a sub-option appears: Force translate all (overwrite manual edits).

• Default mode — empty target-language fields get filled, fields that haven't been hand-edited stay in sync with the source on every save, and hand-edited target fields are preserved. To force a re-translate of a single manual edit, clear it and save again.
• Force mode — every save replaces every target-language field with a fresh AI translation, including hand-edited ones. Useful when a merchant trusts the AI more than past manual edits, or wants a bulk re-translate run (tick force, save, untick force).

The contract is honest about cost. Each translated field is 1 credit. Three menu languages (e.g. English / Bahasa Malaysia / Chinese), one full item save with all three fields needing two non-source translations each — that's 6 credits. But here's where it earns its keep: re-saving the same item without changing the source content costs zero, because the same source text already gave us the same translation, cached. Edits that don't touch the translatable fields = free.

Nothing slows down your save. The translation work happens after your save response is sent back, so the editor still feels instant. Refresh the item page a few seconds later to see the newly-filled languages.

This is different from the AI Enhance button sitting on the same form. AI Enhance rewrites your draft in one language (the panel language). Auto-translate copies your exact content into every other language. Both can run on the same item — write English with AI Enhance, then save with Auto-translate ticked, and Bahasa Malaysia + Chinese fill in to match.

Heads up if your menu is single-language. The checkbox doesn't appear unless your store has more than one enabled menu language. Add another language under Settings → General → Menu Languages first, and the checkbox shows up on every item edit page.

Three new AI-powered reports under Reports → AI Insights. Each one takes your existing sales data and tells you, in plain words, what's worth your attention this week:

• AI Catalog Advisor surfaces slow movers, items where revenue and volume disagree, and quiet hits with strong repeat customers. Period-over-period comparison shows you whether each bucket is growing or shrinking.
• AI Timing Advisor finds your busiest and quietest hours of the week, and flags time windows where activity is trending up or down compared to the prior month. Useful for staffing, off-peak promotions, and noticing when patterns shift.
• AI Restock Forecast predicts which stock-tracked items will run out in the next 14 days, sorted by urgency. Refreshed once a day in the background so you can plan your next purchase order before things hit zero.

Each advisor shows the raw numbers immediately when you open the page. To get the AI-written narrative — three short paragraphs explaining what stands out and what to do — click Generate weekly digest. That part costs 3 credits per generation; re-reads of the same week are free.

The reports adapt to your business. Set your industry under Settings → General → Business profile so the advice fits how your business actually works — whether you sell food, run a salon, manage a workshop, or anything else.

If the Generate button isn't there, the page tells you why: you might be a brand-new merchant without enough order history yet, or the restock forecast might be waiting for you to turn on stock tracking. Once those gates clear, the button appears.

No customer details ever leave your account. The AI only sees aggregated counts and item names — no phone numbers, no addresses, no personal data.

We rebuilt the way your storefront serves products to a customer's browser. On a typical mobile network, pages now appear roughly twice as fast as before:

• Product catalogue is served from a fresh cache that rebuilds the moment you edit an item, category, or page — so customers always see your latest menu without paying the cost of rebuilding it on every visit.
• The first carousel slide loads in parallel with the rest of the page. Previously the browser would only start fetching it after parsing the entire product list, which added noticeable delay on slow connections.
• Uploaded images go through a proper resize step so a 2,400-pixel cover photo gets served as a properly-sized 1,200-pixel image to the customer, not full resolution.

The effect is most visible on storefronts with many items and on slower mobile connections. Customers spend less time staring at a blank screen and more time on your menu.

No setup needed — the speedup applies to every storefront automatically.

Cashiers can now record an order without taking payment immediately, then collect payment when the customer is ready. Works for dine-in, takeaway, and delivery.

Two ways to finalize an order:

The cart now has two buttons:

• Pay now — opens the payment screen so the customer pays before they leave the counter or table. Same flow you've always had.
• Save & continue (new) — records the order, fires the kitchen ticket, and saves it for payment later. The customer hasn't paid yet, but the kitchen is already cooking.

Where saved orders live:

Saved orders show up in the Orders list with a Saved badge. When the customer is ready to pay, tap the Pay button on that row — the payment screen opens preloaded with the order. Once paid, the row flips to Paid.

Common flows this unlocks:

• Dine-in: customer sits down, orders, eats, and pays at the counter on the way out.
• Takeaway: customer orders at counter, browses the shop while food cooks, pays when called.
• Delivery (cash on delivery): cashier records a phone or walk-in delivery order. Driver collects payment at the door.

Cancelling a saved order:

Tap the trash icon next to a Saved row to cancel. The kitchen is notified so they stop preparing it. (You can't cancel a paid order from this list — that's a refund flow, separate.)

Reprinting a paid receipt:

Paid orders now stay on the orders list for the rest of the day with a Reprint button — useful if the customer asks for another copy of the receipt.

What's required:

If your Force Customer Information setting is on, the same fields that gate Pay now also gate Save & continue:

• Dine-in: optional (the table is the identifier).
• Takeaway: customer name + phone (so you can call them when food is ready).
• Delivery: address + phone (so the order is actually deliverable).

No setup needed beyond that.

A small round of POS hardening based on real-world feedback:

• Settings propagate faster. Changes to your POS settings (initial view, show-completed-orders, order-completed-once-paid) now take effect within minutes. Previously the cache held them for up to a day, which made it look like a setting toggle "didn't work."
• More resilient orders queue. If a table referenced by an old order has been deleted from your floor plan, the orders refresh skips it gracefully instead of breaking the list.
• Safer move-order action. Moving an active order between tables now goes through a protected POST request. No functional change for you — just better protection against cross-site request forgery.

No setup needed.

After last week's Tables-as-an-app launch, Reservations gets two changes that complete the multi-industry picture: it works without any resource at all, and the "Seated" status — a restaurant idiom that didn't fit anywhere else — gets renamed everywhere.

Simple booking mode (no Tables required):

If your business doesn't assign customers to a physical spot — consultants, coaches, lawyers, online therapists, freelancers, anyone whose "resource" is just their own time — you can now leave Settings → Apps → Tables off and Reservations adapts:

• The Floor Plan / Tables tab in the panel disappears.
• The confirm flow skips the resource picker entirely — one click confirms the booking with date/time only.
• Bookings don't carry a table assignment, no fake "Zoom" or "Slot 1" placeholder needed.

If you do have tables, chairs, rooms, vehicles or whatever you call them, enable Tables and the existing flow works exactly the same as before — picker included.

Date and time editable on confirm:

The confirm modal now shows the requested date and time as editable fields, pre-filled with what the customer asked for. You can adjust before confirming — "we're full at 7 p.m. but can fit you at 7:30" — and the customer notification reflects the new time. Works in both simple mode and tables mode.

"Seated" → "In session":

The status that means the customer is here, being served used to read as "Seated". That made sense for restaurants but read as odd for salons (a stylist's chair isn't really "seating"), clinics (a patient isn't "seated" — they're in consultation), and impossible for online consultations where there's no seat at all.

The new universal label is In session — natural for restaurants (a seated diner is in their dining session), salons (client in session), clinics (in consultation), coaches and online consultations (call in session). Translated across every supported language: pt "Em sessão", es "En sesión", fr "En session", de "In Sitzung", zh "进行中", ar "في جلسة", and the rest.

What changes:

• The third tab in the Reservations panel: "Seated" → "In session"
• Status badge on every reservation card and in the legacy reservation list
• Action button on confirmed reservations: "Seated" → "Start session"
• Empty-state copy: "Mark a confirmed reservation as in session when the customer arrives or the call begins."
• Toast messages after confirming a status change

Internally the database value stays as seated — only what you see changes — so historical reports, exports and any external integrations that read the status field continue to work unchanged.

Restaurants don't need to do anything:

The new wording reads naturally for restaurants too. Tables stays enabled, the picker still shows, the workflow is identical — only the word on the third tab and the action button changes.

A small polish pass on Reservations that finishes off the multi-industry shake-out: the customer booking form drops two fields that were always restaurant-y, the time picker snaps to 15-minute intervals, and booking duration is now something only you control.

Time picker snaps to 15-minute intervals

Customers no longer pick "7:23 PM" by mistake. The time field on the booking widget (both the embedded chat-bubble widget and the Spreader/Kaleo/Cosmika storefront modal) now offers 7:00, 7:15, 7:30, 7:45 only. Mobile shows a snap wheel; desktop steps in 15-minute increments. Restaurants book on quarter-hours, salon appointments come in 30/45/60 blocks, clinic slots are 15/30 — 15-minute snap fits everyone without a per-merchant setting.

"Number of Guests" → "Party size", and hidden in simple mode

The party-size field used to read "Number of Guests" / "Guests" — restaurant-flavoured wording that didn't fit salons, clinics or 1:1 consultations. Two changes:

• Renamed everywhere visible to "Party size" (the merchant card now shows "4 people" instead of "4 guests").
• Hidden on the customer booking form when Tables is off. Almost every simple-mode booking is for one person (consultant, lawyer, coach, single-room therapist, salon stylist) — asking is friction. The booking submits 1 silently. If a merchant wants party size for couples therapy or family clinic visits, they'll be asked when they enable Tables.

In Tables mode, the field still shows on the customer form (because party size genuinely matters for table-capacity matching) and is required.

Booking duration is merchant-only now

Previously the customer picked their booking duration from a 1-to-4-hour dropdown on the storefront modal. That made sense for restaurants (long lunch vs quick coffee) but was meaningless for salons, clinics and consultations where the duration is fixed by the service type. We've removed the field from the customer form universally.

Instead:

• Set a default in Settings → Apps → Reservations → "Default booking duration" (15 min, 30 min, 45 min, 1 hour, … up to 4 hours). The new default ships at 30 minutes — adjust to whatever your typical booking takes.
• Override per-booking in the confirm modal. When you confirm a pending reservation, the duration field is right next to date and time — pre-filled with your default, change it for atypical bookings ("this haircut is a colour, 90 min").

This is more accurate scheduling for everyone: the customer doesn't have to guess, and you're never overcommitted because someone picked "1 hour" for a 4-hour family dinner.

A note on WhatsApp confirmation templates

The notification class itself (the bit WhatsMenu controls) is industry-neutral — it just passes data fields to your campaign template. If you've configured a custom WhatsApp campaign in WhatsBox that says "Your table is confirmed for X guests" and your business doesn't have tables, you'll want to update the template to match. The data fields available include customer_name, reservation_date, reservation_time, number_of_guests, special_requests, company_name, etc. — use whatever fits your wording.

No action needed for restaurants

Set Tables on, leave Default duration at whatever fits (1.5–2 hours is common for dinner), and the customer form looks the same as before with cleaner time-picker behaviour. Everything else is identical to what shipped on 2026-05-13.

The reservation chat-bubble widget you embed on your own website was rewritten end-to-end. The biggest day-to-day win: customer phone numbers now save in international format automatically, so your WhatsApp and SMS notifications actually reach them.

Phone numbers always save in a format that works:

• A customer typing 0123 456 789 on a Malaysian merchant's site now saves as +60123456789 — directly usable for WhatsApp / SMS.
• Customers can also type their own international format (e.g. +44 7700 900123 for a UK number) and it's preserved.
• If a customer types something we can't recognize, they see a clear message asking them to include the country code, instead of the form silently saving a number you can't reach.
• Coverage spans ~70 countries (SE Asia, Latin America, EU, Mid-East, Africa, NA, Oceania) and uses your Default country setting to fill in missing country codes.

Cleaner form panel:

• Dropped the chat-message styling (the green-bubble look with the speech-bubble tail). It implied a back-and-forth conversation that never actually existed — your customers were filling a form, not chatting. The new design is a clean form panel that opens from the same floating bubble, with your logo and brand colors prominent in the header.
• Field labels are now translated into the customer's language — "Your name" / "Phone number" / "Date" / "Time" / "Guests" / "Special requests" all show in the panel's working language across 19 supported locales.
• Inputs have proper focus highlights in your brand color, the submit button shows a subtle "Sending…" state while the request is in flight, and the launcher bubble is slightly smaller (52 px) to match Intercom / Crisp / Tawk conventions.

Better error handling on submit:

• If the date or time you've configured rejects the booking (outside business hours, beyond your max-advance days, etc.), the customer sees the actual reason inline — they fix it and resubmit without reloading.
• If the network drops mid-submit, they get a clear "Network error, try again" message instead of a hung form.
• Network failures and validation errors no longer hide the form, so a single mistake doesn't make the customer start over.

Spam protection:

• Bots scraping the form are silently blocked via a hidden honeypot field — they think their submission worked, you never see fake bookings clutter your panel.
• Submission rate is capped at 10 per minute per IP, so a misbehaving script can't flood your reservations queue.

Reservation history listing:

• The /reservations/reservation page (linked from the panel as Reservation history) had a heavy bold-everywhere look. Toned down to match the rest of the panel — single emphasis on the customer name, lighter secondary lines, action buttons right-aligned to match Staff and Contacts.
• The "Seated" status icon is now a small armchair instead of an empty square (the previous icon name didn't exist in our icon set, so it never rendered).

No setup needed — open Settings > Apps > Reservation Widget to see the new design in action, and your existing embed code on your website continues to work without changes.

When a customer submits a reservation through your storefront or embedded widget, the panel now reacts in real time — no refresh needed.

What changed:

• Doorbell + on-screen toast — if you (or a staff member) have the panel open, you hear a short doorbell sound and see a toast with the customer name and reservation code the moment the request arrives. Same behaviour you already get for new orders.
• Top-bar bell badge — the new request lands in the bell dropdown in the top navigation, so you see it next time you load any page even if the panel was closed.
• Mobile vendor app push — if you use the WhatsMenu vendor app on your phone, you get a native push notification with the request details.

What didn't change:

The existing Twilio SMS and WhatsApp via WhatsBox notifications still fire when the Notify me when a new reservation is submitted setting is on. They are now an extra channel rather than the only way to find out.

No setup needed — these alerts are on by default for every merchant. If you don't want the doorbell sound, your browser tab controls work as expected.

We tightened up Reservations so you spend less time chasing bad requests and more time confirming the good ones.

New settings in Settings > Apps > Reservations:

• Enable customer-facing reservations on your storefront — controls whether visitors see the booking entry. The panel still works for staff phone bookings even when this is off.
• Maximum days in advance customers can book — leave blank for no limit, or cap at any number of days. The storefront date picker respects the limit automatically.
• Accept bookings outside business hours — off by default, so a customer cannot book a 3 a.m. slot when you are closed. Turn on for venues that handle private events outside posted hours.
• Notify me when a new reservation is submitted — pings your registered phone the moment a request lands, so you do not need to keep the panel open to spot it. Uses the same Twilio or WhatsApp channel as confirm/reject.

Smarter automatic rejections:

Three rules now reject obvious garbage before it reaches your panel — past dates, party sizes outside 1–50, and times outside your business hours (unless you allow off-hours). The customer sees a clear message explaining what to fix and can resubmit.

Mode-aware visibility:

• On a QR Ordering storefront, the customer-facing reservation entry is hidden — your customer is already at the table, so the booking form would be confusing. Staff still take reservations through the panel.
• On a showcase storefront (Disable Ordering), the Reserve / Book button is promoted as the primary call to action — exactly what salons, clinics, and consulting businesses need.

Reservation Widget date input also honours the max-advance setting now, so an embedded widget on your external site can't accept dates beyond your panel's horizon.

Open Settings > Apps > Reservations to try the new controls.

We rebuilt three of the daily-driver pages around Reservations with the same look and feel as the rest of your panel — clearer typography, consistent badges, and a more usable preview where it matters.

Reservations panel cards:

• Status badges now use distinct colors per state — pending (warning), confirmed (primary), seated (success), completed (neutral), late and no-show (danger) — so you can scan a long list and spot what needs attention at a glance.
• Each booking card was tightened up: customer name leads, contact info groups under labelled icons, and the table assignment shows as a chip next to the party size.
• Empty tabs ("No pending reservations", etc.) now include a one-line hint about what would normally appear there, instead of just a heading.

Cleaner panel header:

• The Widget, Contacts, and old "All reservations" buttons collapsed into a single More dropdown next to New reservation, so the toolbar stays tidy on small screens.
• "All reservations" was renamed to Reservation history to make its role clear — the panel is for today's work, the history page is for lookups, exports, and edits to past records.

Contacts list:

• Modals, dropdowns, and the Bulk action menu were rebuilt on the current Bootstrap 5 base, so they open and close reliably across browsers.
• Action buttons (Chat, Reservation, Edit, Delete) collapsed into compact icon buttons with tooltips, freeing up horizontal space for longer names and group tags.
• Status pill ("Subscribed" / "Not subscribed") and group tags now match the rest of the panel's badge style.

Web Widget creator:

• Form is split into three labelled sections — Branding, Content, and Appearance — so you can find a setting without scrolling the whole form.
• The two color pickers sit side by side instead of stacking vertically.
• The live widget preview and the embed-code snippet moved to a sticky right column, so the preview stays visible while you tweak settings on the left.

No behaviour changes — every existing setting still does exactly what it did before. Open Reservations, Contacts, or Settings > Apps > Reservation Widget to see the new layout.

If you run a QR Ordering storefront, your customer-facing reservation entry no longer disappears for everyone — it now appears for visitors who reach your storefront without scanning a table QR code.

The new rule:

• A customer who scans a table QR code (URL has ?tid=) is physically at a table — the Reserve button stays hidden because they're already there.
• A customer who visits your storefront URL directly — from search, a social link, or a saved bookmark — sees the Reserve button and can book a future visit, exactly like on a non-QR venue.

This unblocks QR-mode merchants who also want to take phone-style reservations from remote customers, without forcing them to choose between QR ordering and a public reservation flow.

No setup needed. The behaviour switches automatically based on whether the customer arrived via a table QR code. If you don't want any customer-facing reservations at all, the existing Settings > Apps > Reservations > Enable customer-facing reservations on your storefront toggle still controls that — turn it off and the button is hidden everywhere, just like before.

Starting a catalogue from scratch can feel like a blank page. Now, on the Catalog page, Generate sample items drops in a small set of ready-made example products so you can see how everything fits together before building your own.

The samples cover the main things items can do:

• A basic item with a name, description, and price
• An item with variants — size and colour combined, where size changes the price
• An item with add-ons — optional paid extras with minimum and maximum rules
• An item with variants and per-variant add-ons — where each variant offers a different set of add-ons, plus one shared by all of them
• A display-only showcase item — no price and no "Add to Cart" button, for products or services customers enquire about rather than buy online

Open any of them to see how it's built, or edit them to make them your own. When you're done, the Catalog Actions menu shows Remove sample items — one click clears the samples and their category, and never touches anything you created yourself.

You'll find Generate sample items in the Actions menu on the Catalog page, or on the welcome screen that appears when your catalogue is still empty.

A week after launch, Schedule picks up the next big set of sources: every order, every delivery, every pickup — all on the same calendar as your reservations.

Three new event sources you can toggle on the sidebar:

• Order Created — every order positioned at the moment the customer placed it. Watch the inflow shape across the day or week.
• Delivery — orders set for delivery, positioned at their scheduled delivery time. See exactly when drivers should be heading out.
• Pickup — orders set for pickup or takeaway, positioned at their scheduled pickup time. Spot pickup spikes before they hit the counter.

Each source has its own colour so a busy day stays readable, and you can toggle any combination on or off without leaving the page.

Pre-orders parsed properly. Schedule now understands the full set of timestamp formats your storefront produces — single-time slots like 30_60, day-only pre-orders like 2026-05-08, and the full range form 2026-05-08 07:30am - 10:00am. Pre-orders show a Pre-order tag in the day-detail panel so you can tell them apart from same-day orders at a glance.

A sidebar promotion. Schedule now lives directly under Orders in the main sidebar instead of nested in Apps — one click to your calendar from anywhere in the panel. Enable it once in Settings > Apps > Schedule and the entry appears.

Times in your format. Events render in the time format you set under Settings > Store > General — 12-hour with am/pm or 24-hour, in your store's time zone.

Open Schedule in the sidebar to see the new sources in action. Toggle Order Created off when you only care about what's leaving the store; toggle Delivery and Pickup off when you only care about inflow. The view is yours.

Meet Schedule: a calendar page in your sidebar that lays every reservation across a month, week, or day so you can see what's coming without opening separate panels.

Four views in one place:

• Month — a grid of the whole month with up to three events per day visible.
• Week — a vertical timeline of seven days side by side with hour markers.
• Day — a single day's hour-by-hour timeline.
• List — a compact agenda-style list, especially useful on mobile.

Switch views from the toolbar at the top of the calendar.

Click a day for the full picture. A side panel slides in with every reservation for that date — customer name, party size, time, phone, code, special requests, and a coloured status pill. A button takes you straight to the Reservations panel for that booking.

Colour-coded by status so a busy month is still readable. Yellow for pending, blue for confirmed, green for seated or completed, red for late, grey for cancelled or no-show.

Sidebar source filter. Today only Reservations lives in the calendar. As you turn on more features, additional sources appear automatically — scheduled orders, closed days, and promotion windows are on the way.

Built for every kind of business. A restaurant can spot busy weekends weeks ahead. A salon can check each day's appointment load. A clinic can map tomorrow's consultations. A retail merchant can track scheduled pickups. The calendar adapts to whatever you book.

Mobile-first. The page defaults to the list view on phones because a month grid is hard to read on a small screen. Sidebar collapses on small screens with a tap of the menu icon in the toolbar.

Enable it in Settings > Apps > Schedule. Once on, a Schedule entry appears in your sidebar.

WhatsMenu has always called the things customers occupy "tables" — because most dine-in venues think about them that way. But a salon assigns chairs, a clinic assigns rooms, a co-working space assigns desks, an auto dealership assigns vehicles. Forcing every business to read "table" in their staff panel and on their customer receipts always felt off.

Two changes shipped together:

1. Tables is now an app you toggle on under Settings → Apps

It joins Floor Plan, Reservations, POS and the rest. Enable it whenever your business assigns customers to a physical spot — restaurants do, but so do salons (chairs), clinics (rooms), co-working hosts (desks), auto dealers (vehicles), and any service business with appointment slots. If your business is pure delivery / pickup / showcase, leave it off and the menu stays clean.

2. You pick what to call them

Inside the Tables app card, you'll find two label fields:

• Singular — what you call one of them (defaults to "Table"). Set to Chair, Room, Desk, Vehicle, Slot, or anything else.
• Plural — used in lists and counts (defaults to "Tables"). Set to Chairs, Rooms, Desks, Vehicles, Slots.

Save and the label propagates everywhere the system used to say "Table" or "Tables":

• The sidebar menu link itself.
• The Floor Plan editor — "Add Chair", "Round Chair", "Delete this Chair", every confirmation prompt.
• The Reservations panel — "Select a Chair", "Available Chairs", "Reservations on this Chair", the floor-plan tab, every empty-state message.
• The POS picker when staff opens a dine-in cart.
• The customer cart at checkout — "Chair: 5" instead of "Table: 5".
• The order receipt (printed A4 and 57mm / 80mm thermal).
• The WhatsApp order confirmation sent to the merchant.
• The order-status page customers see after placing an order.
• The analytics dashboard ("Chair Reservations" instead of "Table Reservations").

Sidebar layout cleaned up at the same time

The old "Restaurant" section in the sidebar held three items — Kitchen Display, Status Display, Tables — and only made sense for restaurants. We dropped the section header and moved all three under the existing Apps group, where they sit alphabetically next to Floor Plan, Reservations, and any other modules you've enabled. A salon now sees a clean Apps list with their own labels; a restaurant sees the exact same item set, just labeled "Tables" by default.

Translated across 19 languages

The label override works in every language WhatsMenu supports — Arabic, Chinese (Simplified and Traditional), Dutch, English, French, German, Indonesian, Italian, Japanese, Korean, Malay, Polish, Portuguese, Russian, Spanish, Thai, Turkish, and Vietnamese. The placeholder slots into the localized sentence so a Portuguese salon merchant typing Cadeira sees "Selecione uma Cadeira", a Spanish auto dealer typing Vehículo sees "Vehículos disponibles", and so on.

A small caveat: in languages with grammatical gender (French, Spanish, Portuguese, Italian, German, Russian, Polish), the surrounding sentence keeps the original gender of "table" — so a French salon's "Choisissez une Chaise" reads naturally, but a few phrasings will look slightly off. The label still gets through; minor grammar quirks are the trade-off for one-click flexibility.

Restaurants don't need to do anything special

Enable Tables under Settings → Apps (one click), leave the labels blank, and the system uses the original "Table" / "Tables" wording everywhere — exactly how it worked before.

Why this matters now

Floor Plan, POS, KDS and Reservations cover a lot of business types beyond restaurants — and the next wave of merchants joining WhatsMenu (salons, clinics, co-working hosts, dealerships) shouldn't have to mentally translate "table" every time they look at their dashboard or send a customer a confirmation. This is the smallest change that makes the rest of the platform feel native to whatever they actually do.

If you use Custom Item Fields to let customers attach files to an order — design artwork, prescription, contract, photo of a faulty part — those uploads now go through tighter checks before they touch your storage.

What changed:

• Allowed file types are enforced at upload time, not at checkout. Allowed: images (jpg, jpeg, png, gif, webp), pdf, docx, and txt. Anything else is rejected before the file is saved.
• A 10 MB per-file size limit keeps a single visitor from filling up shared storage with one oversized upload.
• A per-visitor rate limit stops a script from looping uploads to fill the disk.
• Clearer feedback for visitors — when a file is the wrong type, too large, or sent too quickly, the form shows an inline error next to the field so the visitor knows to retry with a smaller or different file.

One small change for new fields. When you add a new File upload field, the default accept list now suggests .gif, .jpg, .png, .pdf, .docx instead of including the older .doc format. Existing fields keep whatever accept list you configured. If a visitor tries to upload a .doc file, they'll be asked to send .docx or .pdf instead — both are widely supported by Word, Google Docs, and Pages.

You don't need to change any setting. The new checks apply automatically to every storefront with Custom Item Fields enabled.

Your Carousels app now has a Carousel height setting — five presets that control how much vertical space the hero slider takes up:

• Compact (400px) — short hero, more room for content below.
• Normal (600px) — the previous default; balanced for most storefronts.
• Tall (800px) — bigger visual impact, great for image-led brands.
• Hero (75% of screen) — the "peek" style: the hero dominates but a sliver of content below is visible, inviting scrolling.
• Cover (full screen) — the Apple/Airbnb landing-page look: the hero fills the entire viewport.

New: scroll-down arrow on Hero and Cover. When you pick one of those two heights, a subtle animated down-arrow appears at the bottom of the hero. Clicking it smoothly scrolls visitors past the hero to your content. Great for signalling "there's more below, keep scrolling" on full-bleed landings.

Tip: Cover and Hero look best with Full width frame (set in Template Settings → Appearance → Page frame width). Boxed frame leaves side margins that break the edge-to-edge feel.

Where to change it:

1. Go to Settings → Apps → Carousels (or the Carousels entry in your sidebar → Settings).
2. Pick a height.
3. Save.

Your existing carousels stay the same — the default is Normal, which matches the previous behaviour. No image re-upload needed.

Mobile tip: Compact, Normal, and Tall use the natural size of your mobile carousel images on phones (so narrow screens don't get a weird super-tall hero). Hero and Cover take up the phone's viewport the same way they do on desktop.

PromoCards just got more dynamic: any card can now use a YouTube video in place of its static image. Pop a video on a "Watch the kitchen at work" card, a product demo, a property walkthrough, a service intro — anywhere a moving image tells the story better.

How to use it:

1. Open a PromoCards group, click into a card.
2. In the Video section, paste any YouTube link:
   • https://www.youtube.com/watch?v=VIDEO_ID
   • https://youtu.be/VIDEO_ID
   • https://youtube.com/shorts/VIDEO_ID
3. Save. That's it.

What visitors see: a thumbnail with a red play button. Clicking starts the video. Until they click, the player isn't loaded — keeps the page fast even with multiple video cards.

YouTube Shorts / Reels work too. Paste a youtube.com/shorts/... link and the card automatically switches to a vertical 9:16 frame so the short plays at its native portrait aspect — no letterboxing. Great for quick recipe clips, before/after reveals, or any short-form content you've already filmed for Shorts.

Some details that may matter:

• Cards with a horizontal video are forced to 16:9 aspect ratio. YouTube videos are 16:9 native; squeezing them into Compact / Vertical / Tall heights would letterbox awkwardly. The Card Height setting still applies to image cards in the same group. (Shorts get 9:16 instead, automatically.)
• The Desktop Image field becomes optional when a video URL is set. Upload one only if you want a custom poster — skipping it uses YouTube's high-quality thumbnail automatically.
• Privacy-friendly: WhatsMenu uses YouTube's nocookie domain, so YouTube tracking cookies aren't dropped on your visitors' browsers until they actually press play. No extra setup on your side.
• Stacked and Beside card styles work best for video. Overlay style still works, but text overlays on a playing video can feel cluttered — try Stacked first.
• For "click anywhere on the card to do something": if you want a video card that also sends visitors to a URL, fill both the Button Text and Button URL fields. The button stays as a separate element; clicking the video plays it; clicking the button navigates.

Not yet supported (let us know if you need any of these): Vimeo, TikTok, Instagram videos. We'll add them based on demand.