Why Firmly for Agentic Commerce
Agentic commerce needs three things to be real: a way to reach many merchants without per-merchant negotiation, a way to land orders inside merchants’ existing systems so their back-office workflows continue unchanged, and the commerce plumbing (cart, payment, tax, shipping, attribution) to be done correctly every time.
Firmly already has all three, deployed across production merchant integrations. This page explains what is in place and why that matters for an agentic surface or a merchant evaluating agentic readiness.
What Firmly is
Firmly is the commerce backend that connects an AI surface (destination) to merchant commerce — across industry-standard and custom commerce platforms alike. It provides:
- Discovery across the connected merchant catalogs
- Cart orchestration including line items, addons, shipping, promo codes
- Payment tokenization across PSPs, PayPal, Click to Pay, and Klarna
- Tax and shipping totals relayed from the merchant’s platform, which calculates them from its live rules — Firmly relays the results in the cart, it doesn’t compute them
- Order placement to the merchant’s native platform so it lands as a normal customer order
- Affiliate attribution so commissions and origination credit flow correctly to the destination
What Firmly is not
- Not the merchant of record — the merchant is the seller
- Not a payment processor — the merchant’s PSP charges the card
- Not the agent — the destination owns the conversation and the user-facing surface
The four things Firmly brings to agentic commerce
1. Merchants are already onboarded
Merchants on Firmly are already connected to platform adapters, payment infrastructure, and affiliate routing. Bringing a merchant into agentic commerce means configuring a connection that already exists, not building a new one. A destination that integrates with Firmly reaches every connected merchant automatically.
2. Native platform adapters
Firmly speaks each merchant’s native API across a wide range of industry-standard commerce platforms and custom platforms. Orders land in the merchant’s native order management system as if a customer placed them directly. The merchant’s existing back-office workflows are unchanged. This is the reason merchants are willing to be on Firmly: zero workflow disruption.
3. Payment + attribution infrastructure already in production
Firmly handles card tokenization across PSPs, PayPal, Click to Pay, and Klarna, and identifies traffic origin — detecting intermediary versus direct networks and posting attribution as merchant-originated traffic. These are not new for agentic commerce — they already run for non-agentic flows. Agentic surfaces inherit them.
4. Protocol translation on top of one platform
Firmly speaks UCP (Google’s standard), MCP (Anthropic’s standard), ACP (OpenAI’s standard), and direct REST. The underlying cart and checkout are identical across all of them. A destination picks the protocol that matches its agent stack; merchants do nothing different.
Where vertical specifics live
Firmly preserves the category-specific details that make each purchase correct — apparel size grids, flower delivery windows, furniture assembly options — across discovery, cart, and checkout, so the destination doesn’t have to handle each category itself.
For a worked-out comparison across apparel, beauty, supplements, flowers, furniture, and electronics, see the Vertical Specialist use case.
Who owns what
| Responsibility | Destination | Firmly | Merchant |
|---|---|---|---|
| Conversational / agent UX | ✓ | — | — |
| User consent and disclosure | ✓ | — | — |
| Product discovery + search | depending on integration | ✓ | catalog source |
| Cart, line items, addons | — | ✓ | rules |
| Address validation | — | ✓ | rules |
| Tax calculation | — | relays | calculates |
| Shipping availability + methods | — | ✓ | rules |
| Payment tokenization, PCI scope | — | ✓ | — |
| Order placement to merchant | — | ✓ | — |
| Affiliate attribution | — | ✓ | — |
| Everything after order placement | — | — | ✓ |
Reading the cells: ✓ = owns it outright. “rules” = the merchant’s platform configuration governs the behavior and Firmly applies it. “relays” = Firmly passes the merchant’s result through without computing it. “calculates” = the merchant’s platform computes the value. “catalog source” = the merchant is the system of record for the data. “depending on integration” = ownership varies by the integration pattern you pick.
The destination owns the experience and the consent layer. Firmly owns the commerce plumbing between the destination and the merchant — through to the moment the order is placed. Everything after that lives in the merchant’s own systems.
When Firmly fits
- The destination needs reach across many merchants without negotiating per-merchant deals
- The destination wants orders to land in merchants’ native systems so the merchant’s existing workflows continue unchanged
- The destination wants a single integration that works regardless of the agent protocol (UCP, MCP, ACP, REST)
- The destination is comfortable owning the conversational and consent layer on its side — Firmly does not impose a checkout UX
When Firmly does not fit
- The destination only needs to integrate with one merchant and that merchant has a usable API — direct integration may be simpler
- The destination is itself the merchant (a first-party storefront) — a commerce platform is the right shape, not a routing layer
- The destination needs a payment processor or fraud engine on its side — those are different categories