Menu

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Allergens are structured data, not words in a description, so "is anything here gluten free" is answered by filtering rather than by reading — the difference between a correct answer and a confident one.

Courses group automatically, so the menu reads as a menu rather than an alphabetical list of dishes.

A dish edited here changes on the site and in the chat at once. The printed menu and the answer given at 8pm on a Friday stop disagreeing.

Prices carry no tax logic and no currency assumptions: what you type is what the agent quotes.

How it works

1
A dish is added or swapped in a sentence, with its dietary marks parsed from the same sentence.
2
The agent answers dietary questions by filtering these marks rather than by reading a description.
3
A change takes effect on the site and in the chat at once.
4
A removed dish leaves the published menu without being deleted from the record.

Best for

Things chosen by eye — products, venues, people.

Not the right choice for

Long lists someone needs to scan quickly.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Dishrequired	text	What it is called on the menu.
Courserequired	text	Starter, main, dessert — the grouping a menu reads by.
Pricerequired	money	What it costs. No tax logic; what you type is what the agent quotes.
Dietaryrequired	text	Allergens and dietary marks, structured rather than written into the description.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Allergen data is only as good as what was entered, and the consequences of an error are real.
No portion sizes, calories or provenance.
One price per dish, so lunch and dinner pricing needs two entries.
No stock awareness — a sold-out dish stays on the menu until somebody says so.

Before it works

What you have to provide, if anything.

Enter the dietary marks properly on day one. This is the module where an omission has consequences.
Pair with Bookings, which is where the dietary requirement is usually first mentioned.

In practice

A twenty-eight cover bistro that changes its mains twice a week.

“Aubergine parmigiana replaces the pork tonight. Vegetarian, has dairy, nineteen euros.”

What was said to the agent

What the agent built

The main swapped, dietary marks set from the sentence, and the old dish moved out of the published menu without being deleted.

What changed

A visitor asking for something vegetarian without nuts got both dishes and no false positive. Before, that question went to whoever answered the phone.

Better with

These do a different job on the same data. An agent can have all of them.

BookingsLive

Customers reserve time, capacity is finite, and double-booking would be a real problem.

Product catalogLive

The business sells or recommends specific, nameable things — a shop, a maker, a gallery, a supplier with a range.

FAQLive

Visitors ask the same handful of things — hours, delivery, pricing, whether you do X — and the answers should be identical on the page and in the chat.

Who uses this page

Caterer

Quotes the obvious, captures dietary requirements, and never loses a headcount.

Restaurant

Answers the menu, the allergens and the opening hours — in every language your guests speak.

Private chef

Takes the brief — dates, guests, diets, budget — while you are still cooking.

Food truck or street food

Tells people where you are today, and takes the private-hire bookings that pay the rent.

Questions

What data does the Menu page use?

It reads menu_item records the agent has collected. Courses/dishes with options. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a cards the wrong choice?

Long lists someone needs to scan quickly. It is best for: things chosen by eye — products, venues, people.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.