Self-operated commerce closed loop
Commerce OS
A commerce loop where every money move is decision-gated
The minimal closed loop for self-operated commerce: catalog and SPU/SKU management, a fail-closed channel adapter registry, idempotent order ingestion, zeus-driven money and refund decisions, and full event audit.
See how Commerce OS connects to zeus and Ops Console.
Problem
Money moves need a boundary
Commerce operations touch listings, orders, money and refunds. Ad-hoc scripts and direct API calls make retries unsafe, leave no single audit trail, and put money decisions outside a reviewable gate.
Approach
A minimal, fail-closed loop
Commerce OS keeps the loop small: catalog and SPU/SKU, a fail-closed adapter registry, idempotent order ingestion, zeus-gated money and refund decisions, a refund state machine, and event audit across SQLite and PostgreSQL.
What it does
01
Catalog + SPU/SKU
A small product center, not a full PIM.
02
Fail-closed adapters
Offline sandbox replay until live credentials are present.
03
Idempotent orders
Retries are safe; order ingestion does not duplicate.
04
Decision-gated money
zeus handles listing, money and refund decisions; no gate, no action.
What is real today
Facts taken from the current catalog description.
- Catalog
- category / SPU / SKU
- Adapters
- fail-closed registry
- Orders
- idempotent ingestion
- Money
- zeus decision gate
Boundary
It is not a marketplace, a storefront theme, or a payment processor. It is the minimal self-operated commerce loop, and it stays offline until channel credentials are deliberately connected.
Where it sits
This product →
uses · ConfirmedZeus
Money and refund decisions
Evidence (1)
src/context/LanguageContext.tsxCommerce OS description: zeus-driven money and refund decisions.
→ This product
uses · ConfirmedOps Console
Commerce operations API
Evidence (1)
src/context/LanguageContext.tsxOps Console description: aggregates the commerce-os API server-side.
See how Commerce OS connects to zeus and Ops Console.
Open the product map