Connector Extensibility - Introduction
Who is this for?
Profile | Role on this topic |
|---|---|
🔧 System Integrator (SI) | You build and host the connector on behalf of the retailer. This section is your primary reference. |
⚙️ Retailer Tech Team | You own an existing OneStock deployment and want to connect a new PSP, CRM, or carrier yourself. |
🚀 Discovering OneStock | You are evaluating how OneStock connects to external systems. Read the Introduction and the Business Case in each sub-section. |
OneStock provides a set of ready-to-use connectors, but your IT ecosystem might use a different provider.
Our extensibility model lets you plug your own services into OneStock — keeping your existing tools, contracts, and processes while benefiting from OneStock's orchestration layer.
How each connector is set up
Domain | Configuration method | Who configures | Where to start |
|---|---|---|---|
Payment | API — | SI or Retailer Tech | |
CRM | Backoffice — Sales channel > CRM (no API required) | Business Admin or SI | |
Carrier | Hook — endpoint exposed by the SI, called by OneStock | OneStock Professional Services |
|
Gift Card | Hook — endpoint exposed by the SI, called by OneStock | OneStock professional Services |
|
What each connector covers
Payment — connect your PSP or POS payment flow to OneStock order lifecycle events
CRM — plug your customer data platform into the Order In Store identification and checkout flow
Carrier — integrate a carrier not covered by our standard connectors
Gift Card — connect your gift card or loyalty engine to OneStock payment handling