Running a third-party logistics operation on stock Odoo means constantly fighting the fact that Odoo core is built for a company that owns its own inventory — not for one that stores and ships other companies' goods for a fee. Out of the box there is no clean concept of a "client owner" on a stock quant, no way to bill a client for occupied pallet positions or per-line pick-and-pack activity, and no isolated portal where each of your customers sees only their own stock and orders. Teams end up bolting on analytic tags, spreadsheets for storage invoices, and separate Odoo databases per client — which fragments reporting and makes onboarding a new client a multi-day project instead of a form.

The 3PL Logistic Company module closes that gap by adding a first-class 3PL client dimension across the inventory, sales, and accounting stacks. We introduce a res.partner-linked logistics-client model and stamp an owner field onto stock.quant, stock.move, and stock.picking via a proper inherited model in models/, enforced by ir.model.access.csv plus record rules so a client user physically cannot query another client's quants. Warehousing is modeled with configurable storage units (bin / pallet / shelf classes) and occupancy computed through @api.depends compute fields, while a scheduled ir.cron snapshots daily occupancy so storage billing is based on real dwell time rather than a month-end guess. Fulfillment runs on Odoo's native stock.picking engine — receiving, put-away, wave and batch picking, packing, and carrier dispatch — but every step is tagged to the owning client and to a rate card.

Billing is where the module earns its keep. An activity-based rate engine reads the tagged movements and occupancy snapshots and drafts periodic account.move invoices per client — storage by unit-days, inbound handling per line or per unit, outbound pick-and-pack per order and per line, plus value-added service charges — all with QWeb PDF statements that itemize exactly what the client is paying for. A branded customer portal (OWL/website controllers) lets each client submit inbound ASNs and outbound orders, watch live stock levels, and download their billing statements, while the JSON-RPC / XML-RPC API and inbound webhooks let their WMS, ERP, or store platform push orders straight into your queue. Automated actions handle low-stock alerts, SLA breach flags, and status notifications.

Because this is build-to-order, nothing is a shrink-wrapped download. After a short scoping call we confirm the exact rate-card logic, portal scope, and integrations you need, then build the module against your Odoo 17.0, 18.0, or 19.0 (Community or Enterprise) environment, deliver on staging for UAT, and cut over to production. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-warehouse topology, additional client-facing integrations (carriers, marketplaces, external WMS), localization depth, and historical data-migration volume increase the quoted scope.