Build and ship plugins on Orbit Commerce.
Task-based walkthroughs for building a plugin end to end, from your first embedded page to a listing on the marketplace. For the exact endpoints and shapes, pair these with the API reference.
Connecting a warehouse or ERP as a supplier? Start with the Supplier API.
- Getting startedWhat an Orbit plugin is, and how to build, embed, and authenticate your first one.
- Authentication & tokensSession vs access tokens, the install handshake, and where per-store context comes from.
- Store API keysConnect a store's own systems to the API with a merchant-minted key. No partner account, no plugin.
- OAuth scopesRequest, consent to, and enforce scopes, plus the singular naming convention.
- The SDKOrbitClient: typed REST resources, GraphQL, billing, and iframe helpers.
- WebhooksSubscribe to events, verify signatures, and handle deliveries reliably.
- B2B / ERP integrationSync companies, buyers, and invoices with an ERP: idempotent upserts, silent user provisioning, incremental polling, and two-way webhook sync.
- Companies, buyers and locationsEvery field on a company, its users and its branches: credit limit, on stop, approval rules, a company's overrides of the store's B2B settings, and per-user limits.
- Cost centresKeep each company's budget codes in step with your own system: replace the list by code in one call, upsert by your own reference, and choose who may charge each one.
- Orders, approvals and pay on accountWhat a company order carries (PO number, branch, a cost centre per line), how pay on account and payment_due work, and how to approve or decline held orders.
- Company statementsA company's orders, payments and balance for a date range, as a PDF or CSV file.
- CSV imports and exportsEvery column of the company, company user, location, cost centre, order, product and customer files, the key each import matches on, and the round-trip rule.
- Customer catalogue and pricesWhat one signed-in customer may see and what they pay, B2B catalogues included, for quotes, price lists and product sheets.
- Background jobsWork that runs outside the browser: keeping a credential alive, syncing on a schedule, and handling many stores at once.
- Storing your own dataYour plugin's own database: what belongs there, why everything is per store, and the query filter that keeps merchants apart.
- Customer timelineA customer's history in one list: orders, returns, emails, abandoned checkouts, conversations and what plugins recorded, and how to record your own events on it.
- Publishing downloadable filesPut a CSV or ZIP into the store's Files at a link that never changes, and replace it on a schedule.
- Testing your pluginInstall your plugin on one of your own development stores and exercise it end to end, served from your machine over a tunnel, before it is reviewed or seen by any merchant.
- Development storesFree stores of your own for building and testing plugins: create one from the partner dashboard, open it, add sample data and place test orders that mark themselves paid.
- Publishing your pluginSubmit through the partner dashboard and get listed on the marketplace.
- MCPAI assistants and the Model Context Protocol at Orbit: the developer, merchant, affiliate and partner surfaces, and where each one stands.
- For partners & developersFor plugin and theme developers: a local server that gives your coding assistant the real API contract, plus a partner connection to your plugins, themes and payouts.
- For merchantsLet a merchant point Claude, or any MCP client, at their own store: permission tiers, OAuth discovery, and confirmation on destructive actions.
- For affiliatesLive, early access: let an affiliate's AI assistant create dev stores, build inside them and hand them to clients. The scopes, the lifecycle and what gates it.