Docs
Firmly Agentic Commerce
Set theme to dark (⇧+D)

Onboarding

After signing up at merchant.firmly.ai, every new merchant walks through the same task sequence in the same order. The one variation is CDN whitelisting (Task 6): it’s conditional — Firmly determines whether it applies and, when it doesn’t, skips it automatically, so most merchants never see it. Otherwise most tasks are self-service forms or toggles; only CDN whitelisting involves any technical work.

The merchant submits the tasks they own; Firmly handles two of them on its side; KYB approval gates everything else.

​​ The seven tasks

# Task Who does it What it is
1 Complete integration Firmly Firmly’s integration systems connect to the merchant’s commerce backend — automated; merchant has no “Start” button
2 Know Your Business (KYB) Merchant Company information, brand identity, terms and privacy — submitted for Firmly review
3 Configure product catalog Merchant Pick Entire Catalog (recommended) or a curated subset
4 Configure destinations Merchant Opt into specific destinations on Firmly’s network
5 Sign merchant agreement Merchant Review and sign the participation agreement
6 Complete CDN whitelisting Merchant Whitelist Firmly’s traffic at the merchant’s CDN/WAF (most merchants don’t need it)
7 Go-live approval Firmly Firmly reviews the merchant’s configuration and approves them to go live

​​ How the gating works

The wizard is linear by construction:

  • KYB must be approved before any later step unlocks. Tasks 3–6 (catalog, destinations, agreement, CDN) all show as Pending KYB approval and are not clickable while KYB is pending or rejected. This prevents a half-configured store from progressing while Firmly is still verifying who the merchant is.
  • Go-live additionally requires integration complete. Even after KYB approval, the go-live task stays blocked with Pending integration completion until Firmly has finished the merchant integration.
  • Go-live itself is Firmly-approved. Submitting for go-live moves the task into Awaiting approval; Firmly reviews the merchant’s configuration and either approves (the merchant is live) or rejects (the merchant sees rejection notes inline and can re-address them).

​​ Sub-pages

Each merchant-actioned task has its own page below: