ZANUS AI FOR E-COMMERCE & RETAIL — CATALOG & POLICIES
The catalog, the spec sheets, the size charts, the return and shipping policies, the supplier contracts — loaded into curated libraries the AI reads from. Ask in plain language; get the answer with the source cited, whether the asker is your newest hire or your storefront chat.
Private tenant or your own server · unlimited staff users · the chat never invents a product or price

Libraries: the current price file outranks last season’s, the signed supplier contract outranks the draft.
PDF catalogs, supplier spreadsheets, scanned contracts, product photos, packaging artwork — the ingestion pipeline turns what lands in your inbox into queryable knowledge.
The same library that answers your storefront chat answers your staff: when the return window changes, you update one document and every answer everywhere updates with it.
The warehouse asks about carton dimensions; the buyer asks about supplier terms: each gets answers scoped to their role, enforced server-side.
“What did we pay for this SKU last spring?” “Which products contain latex?” “What is our marketplace return policy versus our own store’s?” The archive answers in seconds with documents attached — instead of an afternoon of folder spelunking.

Yes — the customer-facing chat reads only the libraries you approve for it. Internal documents like supplier costs stay internal, enforced by permissions, not by hope.
Never. Your tenant is isolated; your catalog, costs and contracts are yours alone — and the on-premises option keeps them physically in your building.
← Previous: Back Office · Sharing with a colleague? 📄 Get the PDF · ✉️ Email this page ·