Skip to main content
A point-of-sale system runs the till. Connecting it to OTO is what turns a shop into somewhere orders can ship from.

​
Why a shop is a harder case than a warehouse

A warehouse only moves stock because a system told it to. A shop sells over the counter, all day, without any order behind it — which means its stock figure changes for reasons OTO never sees unless the POS says so.
Turn location-based inventory off for shops, deliberatelyBin-level tracking is right in a warehouse with scanners and a process. In a shop where staff sell from the shelf between customers, it is a discipline nobody will keep, and the detail it produces is wrong by Thursday.Hubs Management lets this be decided per hub: warehouses run full bin tracking, branches run one honest figure per SKU. A shop that reports one number correctly is more useful than a shop that reports bin detail badly.

​
What connecting a POS gives you

​
Restaurant and food POS

Foodics connects from the channel catalog directly, alongside Jahez and Fooder. Food orders behave differently from retail — short promises, branch fulfillment, and a delivery window measured in minutes — which is why they are worth configuring against branches with tight preparation SLAs rather than warehouse defaults.

​
How POS integrations are delivered

Foodics is in the self-serve catalog. Other POS systems connect through the REST API — stock updates in, order and fulfillment events out. That can be built by your team, by your POS vendor, or by OTO against your endpoints, as a connector developed for your account and your business rules. The same three routes described under ERP systems apply here, and a till system with no public API is exactly the case the third one exists for. Note that creating branch pickup locations over the API is an Enterprise capability; warehouses are available on every plan. See plan availability.