Products
Connect your shop's catalogue to a brand and your AI can talk about what you sell — recommending products in conversation, showing product cards in chat, quoting prices and stock read live, and following the exact rules you set for each product.
Overview
A brand's catalogue lives at Brand → (your brand) → Products. You connect the place your products come from, we read them, and everything your AI learned about them is kept in step with that source.
The catalogue belongs to the brand, not to the AI agent. Replace or delete the agent and your products stay exactly where they are.
The four tabs
The page is split into four screens, each with its own address, so you can link a colleague straight to the one you mean.
Sources
Where your products come from — a shop's own JSON API or a CSV feed — with its refresh schedule, its security settings and the report from its last read.
Products
Everything your AI can talk about. Open a product to see the keys it carries and which rules apply to it.
Two kinds of source
You choose the kind when you create a source, and it cannot be changed afterwards — switching means adding a new source.
| Product API | CSV feed | |
|---|---|---|
| What it is | Your shop serves its products as JSON at an address we read | A Google Shopping style CSV file we download |
| Your shop can push changes to us | Yes, at any moment | No |
| Can carry rules | Yes — this is the only kind that can | No |
| Custom fields (ingredients, dosage, anything) | Yes | No |
| Versions (flavors, sizes, colors under one product) | Yes | No — every row is its own product |
| Nested categories | Yes | Yes, from the product_type column |
| Address | Must be https | http is allowed |
A product is a base product with versions
A product is the thing you talk about — "Gold Whey". A version is the thing a customer buys — "Gold Whey, pistachio, 1 kg" — and it carries its own price, stock, link and id.
A product you sell in one form only has exactly one version and you never think about it. A product sold in eight flavors and three sizes is one product with up to twenty-four versions, which is what lets the AI say "we have it in eight flavors" instead of listing the same thing eight times.
Categories are a path, not a label
A product's category can have up to six levels — Protein > Whey > Isolate — rather than one flat name. The AI uses that shape to answer questions about your catalogue as a whole, like "what kinds of protein do you have", by asking your catalogue for its structure instead of guessing from whichever products a search happened to return.
How products reach your AI
- A source is read, on its schedule or because your shop pushed a change.
- Each product becomes a search card — its title, category, brand, every option value, its search terms and its description — split into pieces so nothing is cut. Alongside it, we write overview pages: one listing your categories, and one per category listing its products. The chat AI no longer reads these name lists — it may only name products it received in full — but phone calls still use them.
- When a visitor asks something in the chat, the AI searches your help content — knowledge bases, documentation, files, website pages, question-and-answer entries — and the catalogue separately, at the same time, so neither kind can crowd the other out. It can also ask the catalogue directly for its categories and what is in them.
- If a product ends up in the answer — at most 5 products per answer — its full sheet is built at that moment from live prices and stock, and every rule that applies to it is handed to the AI as binding wording it must follow.
Price, sale price and availability are deliberately not part of what the AI learned. Changing a price costs nothing and needs no refresh — the price was already right. You refresh a source to add and remove products, not to correct prices.
Who can open this page
The permission is Content sources (key ContentSources) — the same one that gates the AI sources on Brand → Knowledge. A product catalogue is shared content: it is read by Vex, by your phone agents, by the reply suggestions your team sees in the inbox, and by AI social posting alike.
Where products do and do not appear
A product source deliberately does not appear in the sources list on Brand → Knowledge, so the same thing cannot be deleted from two different screens. Its refresh status, its last error and its product count live only on this page.
The brand Overview shows a summary card and warns you there when a source failed its last refresh.
Limits
| Limit | Value |
|---|---|
| Products per source | 20,000 |
| Products per organisation | 20,000 (raisable on request) |
| Versions per organisation | 100,000 |
| Versions per product | 500 |
| Category depth | 6 levels |
| Product sources per organisation | 100 |
| Product rules per organisation | 20,000 |
| Refresh schedule | Every 1 to 30 days, or off |
On the free plan, products share one content pool with your articles, pages and files, and a product now draws one to a few pieces from that pool depending on how much it carries. The catalogue overview pages are written for you and are not counted against it. If a read fails because the pool is full, upgrade or remove other sources to make room, then press Fetch now.
An organisation with no subscription and no credit balance also gets smaller feed limits — 5 MB and 1,000 products per read or push, six pushes a minute. Product sources has the full comparison.