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.
Getting started
What an Orbit plugin is, and how to build, embed, and authenticate your first one.
Authentication & tokens
Session vs access tokens, the install handshake, and where per-store context comes from.
Store API keys
Connect a store's own systems to the API with a merchant-minted key — no partner account, no plugin.
OAuth scopes
Request, consent to, and enforce scopes — and the singular naming convention.
The SDK
OrbitClient: typed REST resources, GraphQL, billing, and iframe helpers.
Webhooks
Subscribe to events, verify signatures, and handle deliveries reliably.
B2B / ERP integration
Sync companies, buyers, and invoices with an ERP: idempotent upserts, silent user provisioning, incremental polling, and two-way webhook sync.
Background jobs
Work that runs outside the browser — keeping a credential alive, syncing on a schedule, and handling many stores at once.
Storing your own data
Your plugin's own database — what belongs there, why everything is per store, and the query filter that keeps merchants apart.
Testing your plugin
Install your plugin on a real store with an install link, before it is listed or reviewed.
Publishing your plugin
Submit through the partner dashboard and get listed on the marketplace.
MCP
AI assistants and the Model Context Protocol at Orbit: the developer, merchant, affiliate and partner surfaces, and where each one stands.
For partners & developers
Two halves for a plugin or theme developer: a local server that gives your coding assistant the real API contract while you build, and the partner connection that lets your assistant see your plugins, themes, earnings and payouts.
For merchants
Let a merchant point Claude, or any MCP client, at their own store — permission tiers, OAuth discovery, and confirmation on destructive actions.
For affiliates
Live, 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.