ORBCART DOCUMENTATION

What makes OrbCart different

What OrbCart is, what it is not, and how its approach compares with the other ways to take an order online.

OrbCart is the transaction layer of a shop: Cart, checkout, tax, shipping, payment and Order. It has no catalog. Your products, prices and stock stay in the systems that already own them, and OrbCart asks them through small contracts whenever a buyer needs a binding answer. One core serves your storefront and AI agents, and it runs as a Worker in your own Cloudflare account. The model is in Concepts.

What it is not

  • Not a catalog, PIM or CMS. No products, categories, images or pages. Your storefront shows them; OrbCart never manages them.
  • Not a storefront. You build the shop in the framework you like. A React checkout and an order page are included.
  • Not search, an ERP or a warehouse. Invoices, fulfillment and stock records stay in your systems. OrbCart hands them the Order.
  • Not an email sender. It tells your systems what is due, and you send the buyer's emails in your own design.
  • Not a hosted service. No OrbCart server sits between your buyers and your account. A managed offering is a future direction, not a product today.

Compared by approach

ApproachYour catalogYou runYou get
Shop platformsMoves into the platform.Nothing; it is hosted.A complete shop around their catalog.
Headless commerceSKUs mirrored into the suite; live price and stock take glue.A storefront on their API.Cart to Order around their catalog.
Open-source shop systemsIn their product model.Servers, a database, often queue, cache and search.A complete shop you operate.
Payment checkoutsNot needed; you pass the items in.Nothing.The money collected, some even tax. Cart, stock and Order stay yours.
Your own buildStays where it is.Everything.What you build, including retries, unclear payments and tax.
OrbCartStays where it is, asked live.A Worker per environment in your account.Cart to Order, the same for your storefront and AI agents.

What you get without building it

  • A signed price. The buyer pays exactly the signed Quote they agreed to, or sees the new one first.
  • Honest payment states. A provider timeout is unknown, resolved by asking again, never a double charge or a lost Order. How →
  • Agents through the same door. AI agents check out over UCP, with AP2 mandates when the buyer agrees inside the agent. AI agents →
  • One call to end a sale. admin.offers.invalidate() stops the old price for every new Quote once it returns.
  • Orders that say what needs a person. Payment, shipping and the ERP hand-off are separate states, and problems appear as issues.
  • Events without personal data, signed by the Environment, so your receiver can check them with its public key.

Choose OrbCart when

  • Your products, prices and stock already live in an ERP, PIM or pricing service, and you don't want a second copy.
  • You build your own storefront, or want to.
  • You want AI agents to buy under the same rules as your shop, without moving platforms.
  • You sell in the EU and need EU VAT and the payment methods buyers there expect.
  • You want the commerce runtime in your own cloud account, under Apache 2.0.

Choose something else when

  • You want a shop with a catalog, themes and an admin out of the box. A shop platform fits better.
  • You have no developers. OrbCart is code: a Worker, your contracts and a storefront.
  • You only need to charge a fixed price. A payment link is simpler.
  • You need subscriptions, B2B approvals and payment on account, or a marketplace with several sellers. None of these is built.
  • You can't run on Cloudflare. The runtime needs Workers and Durable Objects.
  • You need packages on npm today. OrbCart is pre-release.

On this page