Every capability that runs your storefront, pricing, quotes, orders and payments is already in the platform — none of it waits on a connector. Add one only where a system you already run should stay in step.
Add-on · ERP
If your ERP is the book of record for stock and customers, the connector keeps the commerce side aligned with it rather than asking your team to maintain both. You decide which system owns which record.
Items, warehouse stock, price lists, special prices and business partners mirror in through the Service Layer. At checkout the platform can ask B1 for the live number before it commits the line.
What moves: master data and stock in; orders and invoices back out.
Products, customers, warehouse stock and price lists over JSON-RPC, with per-customer pricing and availability resolved live. Accepted orders are written back as Odoo sales orders.
What moves: two-way, on the schedule you set.
Orders and invoices are pushed into your Business Central company through the standard API as they are created, so finance sees them without anyone exporting a file.
What moves: platform → Business Central, one way.
Browsing reads the platform's own data, so your storefront stays fast and stays up even when the ERP is mid-upgrade. Where a number has to be exact at the moment of commitment, the platform can confirm it against the ERP before the order is accepted. Which records the ERP owns is a setting, not a rewrite.
Add-on · Accounting
Your ledger stays the book of record for money. The connector posts each invoice as it issues — lines, tax and customer with it — and every push is idempotent, so a timeout or a retry never leaves your accountant reconciling two copies of the same invoice.
Invoices and customers post to QuickBooks the moment they issue, and customer and product master data can be pulled the other way. Every push is idempotent, so a retry after a timeout never creates a second copy.
What moves: invoices and customers out; master data in.
Invoices and customers post to Xero as they issue, and contacts and items come back the other way — so a buyer added on your storefront is a contact in Xero without a second entry.
What moves: invoices and customers out; contacts and items in.
For any package without a direct connector: invoices, payments and customers as CSV or Excel, downloaded from the console or delivered on a schedule as a saved report. No integration work, no waiting on us.
What moves: whatever you can see on a screen, on your timetable.
Add-on · Payments
Terms, invoices and offline settlement need no gateway at all — they're built in. Card acceptance through your own merchant account is in development, and you stay the merchant of record when it lands.
Card acceptance runs through your merchant account, so you stay the merchant of record and the money never routes through us. Collection is guarded end to end: a retry, a double-click or a dropped connection cannot charge the same invoice twice.
Status: in development — everything below works today.
A buyer pays by mobile money and reports the reference; the payment lands against the right invoice and is deduplicated by receipt, so the same transfer is never counted twice. Your team accepts or rejects the claim.
Works today: M-Pesa and bank references, reconciled in the console.
Most B2B money arrives on terms, not on a card: credit limits checked before an order is accepted, invoices with due dates, aging buckets and automatic reminders. Wires, cheques and cash on collection are recorded the same way.
Works today: built in, with no gateway and no add-on.
Add-on · Logistics
Delivery is where a promise either holds or it doesn't. Rates come from your own carrier tables, labels are generated from the shipment the order already created, and tracking lands in the buyer's portal without anyone copying a number between two systems.
Buyers see the rates you actually pay, because the tables are yours — a carrier price change is an edit, not a release. Labels are generated from the shipment the order already created.
What moves: your rates in, label and shipment data out.
Tracking numbers and status land in the buyer's portal as they change, so "where is my order?" stops being a phone call and the order page is the single answer everyone reads.
What moves: carrier status in, visible to the buyer immediately.
Scheduled pulls of vendor and supplier inventory, so what a buyer sees on a dropship or vendor line reflects the stock behind it rather than a number someone typed last month.
What moves: supplier stock in, on your schedule.
Add-on · Procurement
Large buyers often can't order from a website — their procurement platform has to do it. These add-ons let you win that business without changing how you operate.
Orders, confirmations and invoices exchanged as structured documents, so a buyer's purchase order arrives as an order in your console — not as a PDF someone has to re-key before it can be picked.
What moves: orders in, confirmations and invoices out.
Buyers browse your catalogue at their own contract prices from inside their purchasing system, then return the basket to it for approval. You keep the catalogue and the pricing; their procurement rules stay theirs.
What moves: catalogue and prices out, an approved basket back.
Staff sign in with your identity provider over OIDC or SAML, and accounts are provisioned on first login with the role you mapped. Leavers lose console access when they lose the directory account.
What moves: identity and group membership in, at every sign-in.
Build your own
There is no private back channel. The admin console, storefront and vendor portal all run on the same documented REST API, so anything you can do by hand you can automate.
Catalogue, pricing, customers, quotes, orders, invoices and payments are all reachable over the same REST API the console itself calls, under the same permissions your staff have.
Scope: every screen in the console has an endpoint behind it.
The OpenAPI description is the contract the platform is built from, not documentation written afterwards — so you can generate a typed client and trust that it matches what is running.
Scope: one published document, versioned with the API.
Subscribe to order, invoice and payment events and have them delivered to your own endpoint as they happen, signed so you can verify they came from us. No polling, no nightly batch.
Scope: signed deliveries with retries you can inspect.
Questions
No. The platform is complete on its own — catalog, pricing, quotes, orders, invoicing, payments and fulfilment are all built in. An ERP connector is an add-on for businesses that already run one.
Nothing has to be rebuilt. You choose which records the ERP owns from that point on, and the connector keeps the two in step. Everything you set up before the connection stays exactly where it is.
Connectors are available for SAP Business One, Odoo, Microsoft Dynamics 365 Business Central, QuickBooks and Xero. Anything else can be connected through the open REST API.
Yes. Bulk import brings products, images, categories, customers, prices and stock in from CSV or an existing store export, validated before anything is written.
Connectors are priced separately from the platform, because most businesses need one or none. Nothing on this page is required to launch or to run.
We'll tell you honestly whether a connector is worth it for how you work.