Skip to main content
OTO sits in the middle of systems you already run. This section is the directory: what connects, how it connects, and where to read the detail.

​
Five kinds of connection

Everything OTO integrates with does one of five jobs. Knowing which one you are dealing with tells you where to configure it and what to expect.

​
Self-serve or scoped

Three of these are catalogs you work through yourself. The rest are built against the API, and the larger ones are scoped with the OTO team.
The hard part of an integration is agreeing what things are calledConnecting two systems is rarely the difficult bit. The difficulty is that your ERP calls a site Plant 04, your POS calls it Store 12, and OTO calls it whatever someone typed into the hub code field a year ago.Two identifiers carry almost every integration: the SKU and the hub code. Agree both across every system before the first import, because they are cheap to decide and expensive to change once historic records key on them.

​
What OTO gives an integration to work with

​
Where to go next

Sales channels

Storefront platforms, global and regional.

Marketplaces

Selling on them, and running one.

Carriers

460+ on your own contracts, 15+ on OTO rates.

ERP systems

Where OTO fits beside the system of record.

POS systems

Shops that also ship.

Messaging providers

SMS, email and WhatsApp, on your own accounts.

Webhooks

Being told instead of asking.