Riven Commerce
LiveThe storefront and order layer that runs real trading operations on Riven — four business units sharing one catalog, one identity, and one ledger.
Riven Commerce is not a demo store. It is the commerce engine behind four operating business units, each with its own catalog, pricing, and customers, all running on shared Riven infrastructure. Because the units share one identity layer and one ledger, a customer signing in to one is a known entity to the others.
Business units#
| Unit | Line of business | Notes |
|---|---|---|
| PES Supply | Industrial and process equipment supply | Largest catalog; quote-driven line items alongside fixed-price SKUs |
| BSDyno | Dynamometer and test-cell equipment | Configurable builds — options resolve to a generated bill of materials |
| Clear Case | Display and protective case products | Made-to-measure sizing; price is computed, not looked up |
| DDS | Distribution and direct supply | High-volume reorder flows and account-level pricing |
Each unit is a tenant inside Commerce rather than a separate application. Adding a unit means adding a catalog and a theme, not standing up another stack.
What Commerce handles#
- Catalog — products, variants, options, and the rules that turn a configuration into a priced line item.
- Quoting — for items that cannot be sold from a fixed price, a quote request becomes a tracked document rather than an email thread.
- Orders and fulfilment — order state, shipments, backorders, and the events that other services subscribe to.
- Accounts — customer and company records, shared with Riven Contact Graph so sales context follows the account.
- Documents — invoices, packing lists, and quotes rendered through Riven Deliverables.
Where AI sits in the flow#
Commerce calls the same gateway every other Riven product calls. There is no separate commerce model and no separate key namespace — a Commerce workload authenticates with an rvn_ key and routes through Riven Ultra Router like anything else.
- Product copy and specification normalisation from supplier data sheets.
- Quote drafting — the model proposes line items and the human approves before the quote is issued.
- Search and cross-sell against the catalog, grounded through Riven Grounding so answers cite real SKUs.
- Inbound email triage from Riven Mail into orders, quotes, or support threads.
Model output never issues a quote or ships an order on its own. Every commercial document has a human approval step recorded against it.
Integration surface#
Commerce reads and writes through the same ERP data model described in Riven ERP — inventory, pricing, and customer records live there, not in a Commerce-local copy. Commerce is the transactional face of that data.