Operations
Operations covers the post-launch work — getting a working sandbox, handling errors and edge cases, and the production launch checklist. Most operational mechanics are shared across solutions; this section calls out the Marketplace specifics.
What’s in operations
- Sandbox Setup — get a sandbox App ID paired with a few test merchants; verify discovery across merchants and a single-merchant checkout end-to-end.
Operational mechanics shared with all solutions
Most operational concerns are universal across Firmly solutions:
| Topic | Where to read |
|---|---|
| Authentication patterns | Authentication |
| Error catalog and retry behavior | Errors & Conventions |
| Idempotency window | Errors & Conventions → Idempotency |
| Rate limits | Rate Limits |
| Production launch process | Going Live |
Marketplace-specific operational concerns
| Concern | Detail |
|---|---|
| Multi-merchant sandbox setup | Marketplace testing benefits from a sandbox App ID paired with several test merchants, so search-across-merchants (discovery) can be exercised. Ask Firmly to provision a few diverse test merchants |
| Merchant enablement and curation | The operator decides which merchants appear in marketplace search. Keep an internal process for enabling, ordering, and removing merchants |
| Discovery latency across merchants | Search spans many merchants; design the results UI to tolerate variable response times as the catalog grows |
| Operator-level reconciliation | Marketplace orders carry the operator identifier in metadata. The operator’s reconciliation system should match orders by operator ID across merchant order management systems |
Related
- Single Product Purchase Flow
- Multi-Product Purchase Flow — multiple items from one merchant
- For Destinations → Going Live — the production launch checklist
- Errors & Conventions — error catalog and retry patterns