Odoo

Odoo is a modular ERP with sales, inventory, accounting and CRM apps on one data model, reachable through its external RPC API. A confirmed sale order in Odoo becomes a load in Load Hub, a carrier is booked in Freight Procurement, and delivery status, tracking, POD and the customer invoice are written back to the same Odoo records. Operations usually requests it at companies where Odoo already runs sales and stock; the Odoo admin creates the API user.

What teams use it for

Move a sale order into procurement

When a sale order is confirmed, Cargofy reads it and its delivery into Load Hub as a load, with the customer and addresses matched from res.partner. A digital worker moves the load into Freight Procurement and requests rates from the Carrier Network carriers on that lane. The planner picks one, and the order shows its carrier in Odoo.

Keep the delivery in step with the truck

The warehouse works from stock.picking, where delivery status often goes stale after the truck leaves. Cargofy writes the load status to the delivery as it changes, so the picking shows loaded, dispatched and delivered without the warehouse clerk updating it. When a pickup is rescheduled, the digital worker updates the delivery date in Odoo, and the sales rep sees the new date on the order.

Answer the customer from the sale order

A customer calls sales asking where six pallets from Lisbon to Madrid are. Each Tracking milestone is written back to the sale order, so the rep opens it in Odoo and reads the latest one. If the delivery is at risk, the digital worker flags the exception in Tracking and customer service contacts the customer first.

Get the POD and invoice into Odoo together

The carrier sends the signed POD from the driver's phone. A digital worker files it in Documents, checks it against the load, and attaches it to the delivery in Odoo. It then creates the customer invoice as an account.move on the sale order, with the freight lines from the load. The billing clerk finds the invoice with the POD attached, ready for the existing accounting flow in Odoo.

Keep carriers as partners you can report on

When a planner books a carrier in Freight Procurement, Cargofy matches it from Carrier Network to its res.partner record in Odoo, creates the partner if it is missing, and writes the load, rate and documents against it. Every haul by that carrier ties to the same partner. At renegotiation time, the procurement lead opens Reports and sees cost per carrier and per lane from Odoo's own records: which carriers took which orders at what price.

How it fits your stack

Odoo stays the system of record. Cargofy reads sale orders, partners, deliveries, invoices and the field schema of those models through search_read and fields_get. It writes order and delivery status, tracking, attached documents and new invoice records, and creates a partner record for a carrier that has none. Setup is per database: your Odoo admin creates a dedicated user with access rights to sale.order, res.partner, stock.picking and account.move, and Cargofy maps models and fields through the n8n layer. Cargofy does not delete records in Odoo, even though the API allows unlink, and it does not install or configure modules.

Who it is for

Small and mid-size shippers and distributors that run Odoo 18 or 19 for sales, stock and accounting and buy their own transport. Transport planners work orders and deliveries in Load Hub, AP clerks see invoices in Finance, and the Odoo admin owns the API user.