Checkout that asks your systems.
Your ERP keeps the last word on price and stock. VAT for every EU country, the payment providers you already use, one order.
Explore OrbCart

Order #10476 · awaiting payment
Open source · Pre-release
OrbCommerce is four products around your shop: catalog, search, content and checkout. Replace the part that holds you back. Add the next when you are ready. Nothing moves twice.
Runs in your own Cloudflare account · EU by default



Your shop today.
idempotent by keyone Postgres, one APIrules, synonyms, pinsresolved, never copiedThe family
Own runtime, own data, own deploy. OrbCatalog, OrbCart and OrbSearch each stand alone. OrbPage builds on the catalog.
Your ERP keeps the last word on price and stock. VAT for every EU country, the payment providers you already use, one order.
Explore OrbCart

Order #10476 · awaiting payment
It understands the query, follows your rules and explains every result.
Explore OrbSearch


Design product types without a developer. Keep millions of products in one grid. Your PIM syncs in, one way.
Explore OrbCatalogCampaigns, categories and stories built from your storefront's own parts. Products are resolved, never copied.
Explore OrbPage
Autumn on the ridgeLight packs for long days above the tree line.
How it fits
Each product meets your systems through a seam. When the next product joins, the seam points at it.
How it works
Nothing is copied into a second system that has to be kept in step. Every truth has one owner, and it is asked at the moment it matters.
offers() at quote timeone owner for every truthprices read when they are neededThe search index is the one copy. It follows the change feed with its own cursor.
The admin
Install one product and it is that product's admin. Install four and they share one sidebar, one search and one sign-in.
NG-ALP-30What shoppers need to recognise and trust it.
A few sentences on what makes it worth buying.
The first one leads the product page.

Leave empty to sell at the base price.
An edit shows at once and saves behind it.
Change a hundred thousand products. Take it back after.
Every product trusts the same team session.
For developers
One typed client per product. Install only yours.
import { catalog } from "@orbcatalog/client";
import type { Nordgrat } from "./catalog.types";
const nordgrat = catalog<Nordgrat>({ url: "https://catalog.nordgrat.shop" });
const route = await nordgrat.route("alpin-30", { locale: "en" });
if (route.status !== "found" || route.kind !== "product") throw notFound();
const [found, offers] = await Promise.all([
nordgrat.product(route.ref, { locale: "en" }), // base data, cached long
nordgrat.offers(route.ref, { channel: "en" }), // price and stock, cached seconds
]);Types come from your live schema with one command.
Every route, for people and for agents.
Events and calls between products carry one signature format.
$npm i @orbcatalog/client
Pre-release. The packages are not on npm yet.
For agents
An agent can find, draft and propose. Whatever changes your shop waits for a person.
mcp, per productexpires after 15 minutesprices and stock are not toolsDraft the English description for Alpin 30 from the German one.
find_products"Alpin 30"read_draftNG-ALP-30edit_draftdescription.enA 30-litre pack for long days above the tree line, with a back that breathes and a lid that opens wide.
Approved by Mara · draft saved
Alpin 30 goes live in 3 languages.
Scale
We build and test against four shops.
150orders a minuteThe campaign.The last piece is sold exactly once.
Targets we design and test for. Not benchmark results.
Why it holds
Föhn rain jacket · Red · MSold outPaid · Order #10477
Sold a moment ago. Your bag is kept.
reserve → 1 held · 1 refused
reserve · commit · releaseone Durable Object per cartIdempotency-Keylifetime first, purge secondUnder the hood
TypeScript end to end, on web standards.
any framework · typed clients · react partscloudflare workers · orbsearch on your serverdurable objects · postgres per merchant · r2erp · pim · payment providersPre-release. Some payment methods still wait for their sandbox proof.
Plainly
Four ways to start
Shop platformMove everything in.
Composable suiteWire everything first.
Point solutionsOne piece. Loose ends.
OrbCommerceOne part. Then the next.
No themes, no app store, no years in production. Pre-release, and it needs a developer.
What changes
If you decide
If you build
const quote = await cart.quote()const quote: Quote
If you edit every day
Cost
No licence fee. No share of your revenue. No paid plan.
Estimate for a small shop: a few coffees a month, from the vendors' price lists.
NORDGRAT · NOVEMBER
YOU PAY FOR WHAT RUNS
Questions
No. OrbCatalog, OrbCart and OrbSearch each work alone, with their own runtime, data and deploy. OrbPage builds on OrbCatalog. Most merchants start with the one that hurts.
Keep them. OrbCart asks your ERP for price and stock through one function you write. OrbCatalog takes a one-way sync from your PIM. Your storefront keeps rendering and calls an API where it used to call the old part.
Then there is no quote, and the shopper is told so. OrbCart waits three seconds, keeps the bag and never invents a price.
An offer is good for fifteen minutes unless your ERP says otherwise, and you can cancel it sooner. The price is checked again at payment. If it changed, nothing is charged.
The Workers run in your own Cloudflare account, the database at the Postgres provider you choose, OrbSearch's engine on your servers. Data is stored in the EU by default. Edge services and your payment provider may process it elsewhere.
OrbCart and OrbPage carry the Apache 2.0 licence, OrbSearch's clients MIT. OrbCatalog's licence is decided before its first public release. The repository is not public yet.
No. Everything here is pre-release. Nothing is on npm, and deploying is still manual. Try the demo shop, read the docs and follow each product's status page.
Put something in the demo shop's bag and pay for it. Then read how it would ask your systems.