For importers and distributors · Agentic commerce site
A shopping agent over your catalog. Prices from the price list, not from imagination.
A commerce site where the customer describes what they need and the agent answers from your catalog: the product, a price pulled from the price list at that moment, and where to buy it. Behind the scenes, a merchant agent proposes changes and you approve before anything moves.
- Prices pinned to the price list
- Where-to-buy handoff
- Approval gate on every change
- Checkout stays yours
Sound familiar?
- The catalog lives in a PDF and a spreadsheet, and the site shows prices from two updates ago.
- Distributors ask the same 20 questions on WhatsApp: is it in stock, what is the difference between the models, where do I buy it nearby.
- You tried a chatbot and it invented a price. Once is enough.
- Care and warranty questions after the sale land on the sales manager's phone.
What opened today, and what I add
The shopping agent: facing the customer
Lives on your site. The customer describes the need, the agent searches, compares and builds a cart. Every number it shows is pulled from the catalog at that moment.
Price pinned to the price list
The model does not write prices. The server returns the price from your price list and the agent only displays it. Price list updated, site updated.
Where-to-buy handoff
An importer does not always sell direct. The agent knows which distributor or store carries the product in the customer's area, and hands the cart to them with the contact details.
Care after the sale
Usage, maintenance, warranty, spare parts. Answers from your documents, and hands off to a person when the question goes beyond them.
The merchant agent: behind the scenes
Works for you, not for the customer. Reads sales, inventory and pricing, and proposes. It changes nothing on its own.
Approval gate
Every write is a staged change until a person approves it: a price update, a product description, a promotion. You see the proposal and its consequence before it goes live.
Inventory and order alerts
A product that ran out, an order that got stuck, a price that drifts from policy. It reaches you, instead of being discovered by a customer.
Campaign drafts
Drafts a promotion or a mailing about products that are actually in stock, at the price that is actually on the list. You edit and approve.
What stays yours
Checkout, payment and the ERP. The blueprint leaves checkout to the host on purpose: the server returns a payment link, the site renders it, and the model never sees it. The model runs on Claude, through the direct API or through Bedrock, Vertex or Foundry, whichever your data-security requirements call for.
How it works
Step 1 · Free
15-minute intro call
What is in the catalog, who sells, what customers ask. You leave with a map.
Step 2 · Diagnosis
Map the catalog and the systems
Where the price list lives, what the ERP returns, who the distributors are. A fixed price in writing after the diagnosis.
Step 3 · Build
Shopping agent first
Goes live on the real catalog, with real customers, monitored from day one.
Step 4 · Retainer
Merchant agent and upkeep
Approval gate, alerts, and one meaningful improvement every month.
Questions everyone asks
Can the agent invent a price?
No. The model does not generate numbers, it displays what the server returned from the price list. If the price list has no price, the agent says so.
We do not sell direct to consumers.
That is exactly what the where-to-buy handoff is for. The agent helps choose, then passes the cart to your distributor.
What about payment?
It stays in your system. The blueprint leaves checkout to the host, and I do not touch payment processing.
What does it cost?
It depends on scope: catalog size, number of systems, data sensitivity. A fixed price in writing after the diagnosis, not on the site.
Want to see it on your catalog?
A 15-minute intro call. No sales deck. You leave with a map even if we do not work together.