Docs
Firmly Agentic Commerce
Docs
Set theme to dark (⇧+D)
  1. Docs
  2. Solutions
  3. ...
  4. Onboarding
  5. Destinations configuration

Destinations configuration

The merchant chooses which channels on Firmly’s network they want to sell through — AI shopping agents and LLMs, marketplaces, publishers, and social surfaces. The merchant only opts in; Firmly handles the actual enablement work behind each destination on the merchant’s behalf.

​​ How it’s organized

​​ Grouped by category

Destinations are organized under collapsible category sections:

  • AI Shopping Agents & LLMs
  • Marketplace
  • Publishers
  • Social
  • Other (catch-all)

The category header shows a count of destinations in that group; all categories are expanded by default.

​​ Per-destination row

Each row shows:

Column What it shows
Destination Name + a short description
Orders Recent orders the merchant has received from this destination (populated once live and transacting)
Avg. Order Value Mean across orders from this destination
Toggle Enable / disable selling through that destination

​​ Summary tiles

A header strip at the top of the page summarizes:

  • Active Destinations — count of destinations the merchant has opted into
  • Total Orders — across all enabled destinations
  • Average Order Value — across all enabled destinations

​​ Opt-in is just a toggle

The merchant flips destinations on or off — there’s no per-destination configuration form here, by design. Firmly handles every behind-the-scenes integration step with the destination platform.

Coming-soon destinations are listed in the table with their toggle disabled and a Coming Soon marker, so the merchant can see what’s on the roadmap.

​​ Which destinations to enable

A practical default: enable the destinations you actively want to sell through now, rather than everything. Keep your catalog scope aligned with your destination opt-ins — go-live review flags a catalog scope that’s misaligned with the destinations you’ve enabled (see Going Live → common rejection causes). Destinations can be added later from this same page without re-running the full onboarding review, so there’s no need to opt into everything up front.

​​ Save semantics

  • Save Configuration button is enabled when there are unsaved changes, or on the merchant’s first save.
  • First-time save advances onboarding. Same pattern as catalog configuration: the first save during onboarding returns the merchant to the task menu; subsequent saves stay on the page with a “Destinations updated successfully!” confirmation.

​​ Gating

  • KYB-gated during onboarding. The destinations task stays locked until KYB is approved. See Onboarding wizard.
  • Post-onboarding, always reachable. The merchant can opt into new destinations as they become available.