List · reads list_item
Cart / wishlist
Chosen items to buy/keep.
One row per item, the plainest possible view.
- Confirm dietary requirementsDue tomorrow
- Send quote to MarchandDue Friday
- Order langoustinesIn progress
- Book second serverNot started
How it works
- 1
Items are listed newest first unless a sort is set.
- 2
Each row shows its title and the two or three fields that matter.
- 3
Filters narrow it without leaving the page.
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.
Questions
What data does the Cart / wishlist page use?
It reads list_item records the agent has collected. Chosen items to buy/keep. 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.
More in Commerce
Seasonal tasting menu
Canapé selection
Service — per waiter
Glassware hire
Product catalog
Items the agent can recommend/sell.
Seasonal tasting menu
Canapé selection
Service — per waiter
Glassware hire
Menu
Courses/dishes with options.
Inventory
Stock levels and SKUs.
Orders
Purchases and fulfillment.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free