OrbCommerce documentation
Four products. One shop.
OrbCatalog knows the products, OrbSearch finds them, OrbPage tells their story and OrbCart sells them. Start with one and add the others when you need them.
Pick a product
Each product has its own section with the same shelf: an overview, the concepts, guides and a reference. You never need to read about a product you do not use.
OrbCatalog
Knows the products.
Types, variants, prices and pictures in one database, edited in the admin or synced from a PIM.
OrbSearch
Finds them.
Search that understands the query, applies your rules and explains each result it gives back.
OrbPage
Tells their story.
Pages, menus and forms that editors build from your shop's sections. It is built on OrbCatalog.
OrbCart
Sells them.
Cart, checkout, tax, shipping, payment and Order, with prices and stock asked from your systems.
Or follow a path
A path walks through several products in the order you build.
Build a storefront
Products, content and a checkout in the framework you like.
Connect your systems
Your PIM and ERP send products and stock and receive Orders.
Work in the admin
Products, orders and pages in one place for the whole team.
Run it yourself
Your own Cloudflare account, your own keys, your own data.
For AI agents
Every page is also plain Markdown, and every product has its own map. Give your agent the smallest file that answers its question.
| Address | Holds |
|---|---|
/llms.txt | The map of every page, with one line on each. |
/catalog/llms.txt, /search/llms.txt, /page/llms.txt, /cart/llms.txt | One product's pages. |
/llms-full.txt | Every page in one file. |
A page's address plus .md | That page as Markdown, such as /cart/concepts.md. |
/openapi/v1.json | OrbCart's HTTP API as OpenAPI 3.2. |
Agents can also act: they manage the catalog over MCP and buy for a shopper over UCP.
Pre-release
OrbCommerce is pre-release. You build from source today, and npm packages come later. OrbCart's status lists what works.