Table · reads product
Inventory
Stock levels and SKUs.
Rows and columns, sortable and filterable.
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
The reorder point turns a count into a decision. Crossing it raises the item in conversation rather than waiting for someone to open the page.
A sale recorded in Orders decrements the count without anyone saying so, so the number stays true between stock takes.
On order suppresses the alert until the expected date passes — and starts warning again when a delivery is late, which is exactly when you want to know.
Answers "can we do twelve of those by Friday" with the count plus what is inbound, rather than with a guess.
How it works
- 1
Each item gets a count and a reorder point. The reorder point is what makes it operational rather than informational.
- 2
With Orders present, a sale decrements the count without anyone saying so.
- 3
Crossing below Reorder at raises it in conversation the next time the item or stock comes up.
- 4
On order suppresses the alert until the expected date passes, so a known-late delivery starts warning again.
Best for
Comparing many records across many fields.
Not the right choice for
A phone. A table is the first thing that stops working narrow.
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 | Matched against Product catalog where it exists, so the two do not drift apart. |
| In stockrequired | number | A stated count, or decremented when Orders records a sale. |
| Reorder atrequired | number | The level below which it needs ordering. Asked once per item.Without it the count is a number nobody acts on, which is most stock spreadsheets. |
| On order | text | Quantity and expected date when a purchase is mentioned. Text, because "60, due 18 Sep" carries both. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- One location. A business holding the same item in two places needs two rows and gets no combined figure.
- No variants. Sizes and colours are separate items, which makes a clothing range unwieldy.
- The count is what the agent was told, not what is on the shelf. Nothing reconciles against a physical count.
- No cost or valuation — this answers "can I sell it", not "what is it worth".
Before it works
What you have to provide, if anything.
- Set a reorder point per item. Skipping this is the single thing that makes the module useless.
- Pairs with Product catalog: same items, different question — one is what you sell, this is whether you can.
In practice
The same roaster, holding beans, brewers and packaging.
“Sixty kilos of the Guji ordered, due the eighteenth.”
What the agent built
On order set against the item with its date. The low-stock alert stopped firing for it, and the count kept dropping as bags sold.
What changed
The eighteenth passed with no delivery and the alert came back on its own. The owner chased a shipment sitting in customs, four days before it would have run out.
Better with
These do a different job on the same data. An agent can have all of them.
The business sells or recommends specific, nameable things — a shop, a maker, a gallery, a supplier with a range.
Things are sold and then have to be prepared, shipped or collected, and several are in flight at once.
You depend on other businesses to deliver, and their lead times shape your own commitments.
Who uses this page
Restaurant
Answers the menu, the allergens and the opening hours — in every language your guests speak.
Online shop
Answers sizing, stock and shipping — the three questions that lose a sale.
Manufacturer or B2B supplier
Answers spec, MOQ and lead-time questions from your own catalogue, at any hour.
Garage or car dealership
Answers what a job costs and when you can fit it in, without leaving the ramp.
Questions
What data does the Inventory page use?
It reads product records the agent has collected. Stock levels and SKUs. 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 table the wrong choice?
A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.
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
Ceramic pour-over
Brewing
€68
Ethiopia Guji, 250g
Coffee
€14
Cast-iron grinder
Brewing
€180
Subscription, 6 months
Coffee
€78
Product catalog
Items the agent can recommend/sell.
Courgette and mint soup
Starter
€9
Pork belly, apple
Main
€24
Aubergine parmigiana
Main
€19
Almond tart
Dessert
€8
Menu
Courses/dishes with options.
Orders
Purchases and fulfillment.
- Cast-iron grinder11 days ago
- Ceramic pour-over11 days ago
- Subscription, 6 months4 days ago
- Guji, 1kg4 days ago
Cart / wishlist
Chosen items to buy/keep.
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