Stratum Commerce sits between your ERP and every shopping agent that queries it — enforcing your real prices, real stock, and real B2B contract terms before an agent ever speaks to a buyer.
Not hypothetical. Found auditing real agent traffic against live Magento and Oro storefronts before we built this.
An agent pulls a public price list instead of the customer-specific tier pricing in Oro — and quotes it as fact, with your name attached.
Inventory sync lag of even an hour means an agent confirms availability on a SKU that sold out in the warehouse ten minutes earlier.
No log today of what agents asked your storefront, what they were told, or which customers received which answer.
In most B2B stacks, the price an agent should quote is computed inside Oro's Price Lists or Magento MSI — not the ERP, which stores raw cost. In stacks where pricing runs inside the ERP directly (SAP/Dynamics CPQ), Stratum reads from there instead. The rules engine above doesn't change — only the adapter does.
Floor pricing, approval thresholds, and customer-group restrictions are encoded once and apply to every agent query — no agent can negotiate past them.
Every query, every answer, every blocked attempt is logged and queryable — a disputed quote or finance review takes minutes, not a week of digging through server logs.
Stratum Commerce never writes to Magento or Oro unless you explicitly grant it. Deployed as a read replica with rule-based gating — the same posture your team already trusts for reporting and BI tools.
Write access is opt-in, scoped, and logged separately.
No changes to Magento/Oro core. No custom modules to maintain.
EU-hosted on Hetzner Berlin for GDPR-bound merchants.
The adapter layer is isolated — new protocols don't touch your rules engine.
A buyer's admin connects their existing Oro/Magento customer account to their agent once. Stratum issues a scoped, read-only, revocable token tied to that account — never a shared or public key. Every query after that carries the buyer's real identity automatically.
| Platform | How it connects | What the admin does |
|---|---|---|
| Claude | Native MCP connector with built-in OAuth | Clicks connect, logs into their portal once |
| ChatGPT | Custom GPT / Action with OAuth-backed Bearer token | Same one-time login redirect inside Action setup |
| Gemini | Workspace extension, scoped API key (OAuth maturing) | Pastes a short-lived key generated in the portal |
Where OAuth is available, the admin never sees a raw secret. Keys are short-lived, single-account scoped, and revocable in one click — same posture as a Stripe API key.
Most merchants do nothing, or hand it to whoever built the storefront. Neither gives you a rules engine or an audit trail.
| Capability | Doing nothing | Agency / custom dev | Stratum Commerce |
|---|---|---|---|
| Live B2B contract pricing in agent responses | No | Manual, breaks on updates | Yes |
| Margin / approval guardrails | No | Not typically built | Yes |
| Full audit log of agent queries | No | No | Yes |
| Protocol changes (MCP → next standard) | N/A | Re-engineered each time | Adapter swap |
| Time to live | — | 3–6 months | 2–4 weeks |
Predictable base fee for the connection and rules engine. Usage scales with your agent-channel volume.