Extend OneStock
Where do you want to start?
OneStock's extensibility platform lets you connect external systems, add custom logic, build UI components, and automate workflows — all without touching the core product. The right starting point depends on who you are and what you need to build.
🔧 I'm a System Integrator (SI) | ⚙️ I'm a Retailer Tech Team | 🚀 I'm discovering OneStock |
|---|---|---|
You're implementing OneStock and you need to understand and develop extensions to influence the core components, to create new UI into OneStock, to cretae connectors. | You own an existing OneStock deployment and want to know how to extend it — custom backoffice views, internal tools, or automating specific workflows. | You're evaluating OneStock's extensibility model or building a proof of concept before a full implementation. |
Start here → Quickstart : Receive your first OneStock event — first webhook in 10 min, zero infrastructure Connector Extensibility — integrate PSPs, CRMs, carriers Workflow Extensibility — hook custom logic into order lifecycle Data Extensibility — add custom fields to orders and items | Start here → UI Extensibility — inject custom pages and actions into the backoffice Workflow Extensibility — trigger external calls on order events API Reference — full REST API documentation | Start here → Quickstart : Receive your first OneStock event — see a live payload in 10 minutes Core Extensibility — understand sourcing and stock view hooks Connector Extensibility — see how integrations are structured |
What can you build?
OneStock extensibility is organised around four pillars. Each pillar addresses a distinct integration need.
Pillar | What you can do | Typical use case |
|---|---|---|
Connect external Payment, CRM, Carrier, and Gift Card systems to OneStock using a standardised contract. | Adyen pay-by-link, Salesforce order sync, custom carrier label generation | |
Add custom fields to orders, order items, and stock locations. Use them in sourcing rules, UI views, and external calls. | VIP customer flag, loyalty tier on order, custom stock zone label | |
Override sourcing rules and stock view logic by calling your own scoring or filtering service at decision time. | Route orders to stores with highest staff availability, custom stock aggregation by zone | |
Inject custom pages, bulk order actions, and single order actions into the OneStock backoffice. Build with Vue 3 and the OneStock Design System. | Custom fraud review panel on order detail, bulk re-route action on order list |
How extensions are built
All extensions communicate with OneStock through four technical enablers. You don't need all four — pick the ones that fit your integration pattern.
REST APIs — read and write OneStock data (orders, stock, sourcing decisions) from any external system.
Webhooks — receive real-time events from OneStock (order created, status changed, payment captured) in your own endpoint.
Hooks — intercept specific OneStock decisions (sourcing, stock view) and return a custom result before execution continues.
MCP Server — expose OneStock capabilities to AI agents through the Model Context Protocol, enabling agentic OMS workflows.