Product catalog

What it does

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

Answers product questions from the rows themselves, so an edit here changes what the agent says on the next message — no republish, no prompt to update.

Generates an image for an item that has none, marked as generated, so a new range is browsable before the photographer has been.

Publishes as a browsable grid or as a directory with a page per item — the second is what makes a range findable in search rather than trapped behind a filter.

Quotes the price it holds and nothing else. An item with no price produces an enquiry, not an invented figure.

How it works

1
Items are stated, uploaded as a CSV, or built up one at a time in conversation.
2
The agent answers product questions from these rows, so an edit here changes what it says immediately.
3
On the public site it renders as a browsable grid; in the dashboard it is the list the owner keeps current.
4
Set as a directory instead and each item gets its own indexable URL, which is what makes a range findable in search.

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
Itemrequired	text	The name a customer would use, not an internal code.
Category	choice	Grouping for browsing. Derived from the range, asked once when it is not obvious.
Pricerequired	money	What it sells for. Required because a catalogue entry without one generates an enquiry instead of a sale.
Image	image	Uploaded, or generated from the description when nothing is provided.A generated image is marked as such. Passing one off as a photograph of real stock would be a lie about the product.

What it does not do

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

No variants, no options, no stock level — pair it with Inventory for the last of those.
It does not sell. There is no cart, no checkout and no payment; an order still arrives through conversation.
One price per item. Trade pricing needs a second dataset, which is how the two get out of step.
As a directory it publishes every row. There is no draft state, so an unfinished item is a live page.

Before it works

What you have to provide, if anything.

Nothing to configure, but decide early whether it is a page or a directory — changing later changes every URL.
Images are worth the effort here more than anywhere else in the catalogue.

In practice

A coffee roaster in the 11th, selling in the shop and to about a dozen cafés.

“Put the autumn range up — four coffees and the two brewers. I will send prices tonight.”

What was said to the agent

What the agent built

Six items with categories, placeholder images generated from the descriptions, and prices left empty until they arrived. The agent answered "what is in stock" from the same rows that afternoon.

What changed

The range was on the site before the photographs existed. Two of the four coffees sold out before the shoot, which the owner would not have known for a week.

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.

OrdersLive

Things are sold and then have to be prepared, shipped or collected, and several are in flight at once.

MenuLive

Food or drink is served, and questions about what is in it need answering accurately every time.

Who uses this page

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.

Florist or bakery

Takes custom orders properly — date, size, colours, message — without a queue forming.

Coffee shop or roastery

Answers what is on the bar today, and turns a wholesale question into a real enquiry.

Questions

What data does the Product catalog page use?

It reads product records the agent has collected. Items the agent can recommend/sell. 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.