Shopping list

What it does

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

Consumed rather than completed — next week the list starts again with most of the same entries.

Grouped by where, because that is how the trip actually goes.

Quantities are first-class, since buying one of something you need twelve of is the usual failure.

How it works

1
Items are added as they run out, usually mid-sentence during something else.
2
Grouping by where turns the list into a route rather than an inventory.
3
Got it clears the item for this run without deleting it from the pattern.
4
The list refills next week with most of the same entries, which is what separates it from a to-do list.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

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
Itemrequired	text	What to buy, as it would be said in a shop.
Quantityrequired	text	How many. Buying one of something you need twelve of is the usual failure.
Where	text	Which supplier or shop, because that is how the trip is actually organised.
Got itrequired	choice	Yes or No. Consumed rather than completed — next week it starts again.

What it does not do

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

No price tracking or budgeting; that is Expenses.
No stock awareness unless Inventory exists to say what is low.
Quantities are text, so nothing sums an order across suppliers.
No sharing between people in real time — two people shopping will duplicate.

Before it works

What you have to provide, if anything.

Nothing.
Pair with Inventory so the list populates from what is actually below its reorder point.

In practice

A café ordering weekly from two suppliers and a cash-and-carry.

“Twelve oat milk, four boxes of filter papers, and till roll.”

What was said to the agent

What the agent built

Three items with quantities, grouped by where each is bought.

What changed

The Metro trip stopped needing two visits. The filter papers, ordered from the supplier, stopped being forgotten because they were on a different group.

Better with

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

InventoryLive

Stock runs out, reordering takes time, and selling something you do not have is a real cost.

SuppliersLive

You depend on other businesses to deliver, and their lead times shape your own commitments.

ChecklistLive

A routine must be performed identically each time and missing a step has consequences.

Who uses this page

Caterer

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

Private chef

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

Household or family

Holds the shared brain: who is where, what is due, and what needs buying.

Questions

What data does the Shopping list page use?

It reads list_item records the agent has collected. Things to buy. 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 list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

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.