Integrations · Odoo

Count in the aisle, and Odoo gets the corrected number.

Odoo’s own inventory-adjustment screen was not built to be used from a phone at the back of a rack, and it slows down once a count gets big. SoftBo counts where the stock is, holds the whole count on the hub, and writes once at the end — in batches Odoo can swallow.

SoftBo counts where the stock is and writes once at the end, in batches Odoo can swallow.

What moves, and which way.

Down, before the count

Products, barcodes and stock come down and become the counting catalogue. Which Odoo field fills which slot is yours to map, and the mapper shows a live sample beside each one.

Back, after you approve

Corrected counts go back as per-product quant adjustments, paced so a five-thousand-line commit lands without a fight. Odoo prices the adjustment itself, with the product’s own costing method — SoftBo does not send a value.

Nothing is written until you approve it. The count sits on the hub, the variances are reviewed there, and the write is one pass at the end that you start.

The hub talks to your Odoo directly.

What you supply

Self-hosted Odoo or Odoo Online. You hold the credentials and the hub connects straight to your server: nothing passes through a SoftBo machine, so there is nothing of yours for us to lose.

drawing
Odoo connectionnot verified yet

A location you have not mappedis not written to

One countone Odoo company

ValuesOdoo prices them, not us

What it cannot do yet, before you buy rather than after.

[VERIFIED · DATE] and [SETUP TIME]. Both close the first time SoftBo writes to a real Odoo. That one afternoon turns this page, the integrations page and CLAIMS C1–C3 green together.

Your next stocktake could be in Odoo by closing time.

The other five