MoySklad
Odoo
amoCRM
Tizimlashtirish
Marketing
AI agentlar
BUline
MoySklad
Odoo
amoCRM
Систематизация
Маркетинг
Маркетинг: обзор
Стратегия и контент
Стратегия и планКонтент и SMM
Рекламные каналы
Google AdsYandex DirectРеклама в TelegramInstagram и FacebookМаркетплейсы
Органический рост
SEO
Измерение и аналитика
Аналитика и KPI
AI-агенты
BUline
MoySklad
Odoo
amoCRM
Systematization
Marketing
AI agents
BUline
Home/Odoo/Transport and logistics
Odooimplemented by BUline
Odoo · Industries · Transport and logistics

Transport and logistics — warehouse, trip and fleet in one database

The warehouse stores and prepares goods, the trip delivers them, and the fleet supports the trip. Odoo connects the three parts: the warehouse and fleet are covered by ready-made apps, while a freight business is assembled from standard apps. We state openly that the documentation does not describe a separate management app for a carrier.

Warehouse and fulfillmentTrip and loadingFleetWaybillTrip sheetCMR
Three directions

Transport and logistics: where and how Odoo works

Warehouse and fulfillment are covered on a separate page. Freight transport and fleet are on this page, below.

Warehouse and fulfillment

Bin addressing, batches, batch picking, barcode, returns and storage of customer goods (3PL). Warehouse page →

Freight and forwarding

Order, trip, waybill, CMR, subcontracted carrier and invoice. It is stated openly that a ready-made app for a carrier is not described in the documentation. Below, on this page →

Fleet management

Vehicle, driver, leasing, insurance expiry dates, service, odometer and cost analysis: the Fleet app. Below, on this page →

In Odoo

Which apps a transport company will need

Which apps are needed is determined at the diagnostic. Planning and Documents are part of Enterprise (they are not in the open-source code repository).

CRM

The shipper’s request, quotation and work with repeat customers.

Sales

Orders for transport and freight forwarding services, contract terms.

Inventory

Transport and delivery documents, loading dock, grouped loading.

Fleet

Vehicle, driver, contract, service, odometer.

Purchase

Subcontracted carrier services, fuel, purchase of repairs.

Scheduling (Planning)

Driver and vehicle shifts, travel time (Odoo 20).

Documents

Contract, copy of the waybill, vehicle documents; in Odoo 20 vehicle documents are sorted by license plate number.

Accounting

Invoice, subcontractor accounting, analytic accounting per trip.

Requests (Helpdesk)

Claims for lost or delayed cargo, SLA. Part of Enterprise.

Section

Freight and forwarding: a ready-made TMS is not described in the documentation; the system is assembled from standard apps

A transport company sells a service: transport, freight forwarding, storage. The Odoo documentation does not describe a separate transport management app (TMS) for a carrier, and no freight package appeared in the industry catalog (25 October 2026). There is only a 3PL package: the Odoo S.A. description lists tracking of inbound and outbound shipments, storage fees and service billing, tracking of transport and consignment, and a customer portal. The package requires Enterprise and is available on Odoo Online, Odoo.sh and your own server; according to the Apps Store dependency list, it relies on the Inventory, Purchase, Sales, Quality, Subscriptions, Website, Studio, CRM, Invoicing, Documents, Employees, Knowledge and Manufacturing apps. For this reason a carrier’s business is assembled from standard apps: the order in Sales, the trip in Project or Planning, the vehicle and driver in Fleet, the subcontracted carrier in Purchase, the invoice in Accounting.

Odoo 20 Inventory has load dispatching, but it is designed for a company delivering its own goods in its own vehicles. Products are grouped by carrier, a batch is assigned to a loading dock, and the vehicle’s capacity (maximum weight and volume) is checked. This requires the Fleet app, a Mapbox connection, and weight and volume on every product. The “Map” button appears only on transfers in the “In progress” status.

For the waybill, Odoo 20 fills in the CMR form from the delivery document with the available data and prints it; missing fields are entered manually. In a batch, a separate CMR is produced for each delivery. The electronic waybill and the trip sheet used in Uzbekistan (the driver’s document with trip details) are not mentioned in Odoo’s ready-made documents: they are covered below together with Uzbekistan’s requirements.

  • Trip schedule: vehicle and driver shifts in Planning; in Odoo 20, Mapbox shows travel time on the Gantt chart: about Planning
  • The subcontracted carrier’s services are handled through a purchase order, and the trip’s costs and revenue go to a single analytic account
  • The tax base under intermediation and freight forwarding contracts follows a separate rule (Article 250 of the Tax Code): the accountant confirms it in writing
  • If the customer’s cargo is stored in the company’s warehouse, 3PL billing: warehouse page
  • GPS tracking (telematics) is not described in the Odoo documentation: the connection is assessed
—
—
—
Section

Fleet: vehicle, driver, deadlines and costs

The Fleet app keeps the vehicle record (model, category, driver), contracts (leasing, insurance), service and repair records, odometer readings and cost analysis. A reminder is sent before a contract expires. The maximum weight and volume are entered in the vehicle category: this is used for the capacity check when dispatching a load.

The Odoo 20 release notes state that Documents automatically sorts vehicle documents by license plate number and links them to the right vehicle; in a vendor bill the vehicle is selected automatically by approximate match. In Payroll, when an employee’s vehicle changes, the driver in Fleet is updated automatically. Uzbekistan is not mentioned in the list of payroll localizations in the Odoo documentation, so the driver-to-vehicle assignment is kept manually: status of payroll localization.

An honest limitation: among the functions of the open-source Fleet module (20.0 branch), a fuel log (liters and price) was not found as a separate model, and tire records and driver working-time control are not described either. Fuel cost can be entered as a service type; this route is checked on a test database. The data required by the electronic trip sheet (the driver’s medical check, remaining fuel) is not fully covered in Fleet.

  • Periodic technical inspection and insurance deadlines are kept as contract records and reminders; we determine at the diagnostic which deadlines are mandatory by law
  • Vehicle costs (service, contract) are analyzed by vehicle and service type
  • Extra fields without code (tires, fuel card): Studio →
—
—
—
Honest scope

What Odoo includes as standard and what we add

The warehouse, fleet records, the CMR form and load dispatching are available in ready-made apps. Carrier management, Uzbekistan’s waybill and trip sheet, and GPS are separate work. The information is based on the Odoo 19 and 20 documentation, release notes and package description; if your version differs, we will check at the diagnostic.

GoalIn standard OdooExtra work (BUline)
Warehouse, batches, batch picking, barcodeAvailable: Inventory and Barcode (Enterprise). Warehouse pageWarehouse map and picking method
Storage of customer goods and service accounting (3PL)3PL industry package in Odoo 19 (Enterprise)Testing the package, rates and calculation rules
Vehicle, contract, service, odometer, costsAvailable: Fleet. Contract expiry reminderCategories, service types, document structure
Fuel log, tires, driver working timeNot described separately in the documentation or open-source codeStudio fields or an external system: assessed
Load dispatch: carrier, dock, capacityAvailable: dispatch in Odoo 20 (requires Fleet, Mapbox, weight and volume)Entering product weight and volume, dock locations
CMR waybillAvailable: in Odoo 20 it is printed from the delivery document, the other fields are filled in manuallyField list and template test
Uzbekistan’s electronic waybillNot mentioned in the Odoo documentationConnection to the operator’s system or the manual entry procedure: assessed
Electronic trip sheetNot mentioned in the Odoo documentationThe terms of connection to the Ministry of Transport system are confirmed in writing
Carrier management (TMS): trip, cargo allocation, settlementsNo separate app is described; no package appeared in the industry catalogAssembled from Sales, Project, Planning and Fleet; assessed
GPS trackingNot described in the documentationIntegration through the telematics provider’s API
Uzbekistan requirements

Local requirements for freight transport and fleet

The following has been checked against official sources. Rules change often: on the day of the decision we re-open the current wording and confirm it in writing with the Ministry of Transport or a lawyer.

Electronic waybill

  • The regulation on the electronic goods-transport waybill was approved by Cabinet of Ministers Resolution No. 249 (28 April 2021); the new wording is in the annex to Resolution No. 168 (18 March 2025, in force from 19 March)
  • If goods are sold at the same time as they are shipped, the electronic invoice can be combined with the waybill. If goods are moved without a vehicle or the sale is not simultaneous, they cannot be combined
  • The goods table requires a national catalog code, IKPU (MXIK): how IKPU (MXIK) works
  • Combining and the operator: invoice and waybill

Electronic trip sheet

  • Cabinet of Ministers Resolution No. 44 (22 January 2024): legal entities carrying cargo and passengers issue the trip sheet themselves in the “Electronic trip sheet” of the Ministry of Transport’s Uztrans system
  • The paper form is not prohibited and the transition is gradual; the ministry was required to propose abandoning paper by the end of 2024. We confirm the current position in writing with the Ministry of Transport
  • The sheet data includes the driver’s daily medical check, the vehicle’s technical condition and inspection status, and the amount of fuel issued and remaining; a sheet is not opened for a vehicle without a periodic technical inspection. The data is stored for 5 years

International transport

  • Uzbekistan is a party to the CMR Convention (since 1995). The protocol on the electronic waybill (e-CMR) has been in force since 14 January 2021 (PQ-4842, 25 September 2020): it is equivalent to the paper waybill but does not replace it
  • The list of permit procedures (ZRU-701) includes the permit to use the International Road Transport carnet (TIR) and the certificate of approval of a vehicle for transport under customs seals
  • On 2 April 2026 the Minister of Transport said that the tested E-Permit platform will be offered to partners and that the integration of E-TIR and e-CMR will be supported
  • We confirm in writing with the Ministry of Transport whether a license or notification is required for carrier activity

Tax and data

  • An invoice is issued in the electronic system (Article 47 of the Tax Code, Resolution No. 522)
  • Businesses whose main activity is trade, catering or services can voluntarily choose a simplified VAT regime from 1 June 2026 to 1 January 2030 (Presidential Decree PF-100, 26 May 2026): 6% VAT on all turnover, 0% profit tax, and VAT paid on purchases is not deductible. Companies with a state share of 50% or more, and large taxpayers, cannot choose it. Odoo’s Uzbekistan package does not mention a ready-made tax for 6%; an accountant confirms whether it applies
  • The taxation of services related to international transport is set out in Article 263 of the Tax Code, and the tax base for freight forwarding in Article 250: the accountant confirms the procedure in writing against the current wording
  • The location of drivers and employees is personal data: before tracking is enabled, the internal procedure and notification are agreed with a lawyer: the law and hosting location
Process

From order to trip profit: seven steps

The warehouse process is on the warehouse page. Here it is the trip: every step leaves a record in Odoo.

01Request and quotation

The shipper’s request lands in the CRM, and the quotation is prepared in Sales as a transport or freight forwarding service.

02Order and trip

The order is confirmed and a trip task is opened. In Planning the vehicle and driver are assigned, and the Fleet category provides the capacity.

03Loading

If goods are involved, a batch is assigned to a loading dock in Inventory, weight and volume are checked, and the waybill and CMR are prepared.

04In transit

Costs (fuel, road, repairs) are recorded against the trip. The trip sheet is issued separately in the Uztrans system.

05Delivery and documents

The delivery document is confirmed, the electronic waybill is closed in the operator’s system, and copies of the documents are uploaded to Documents.

06Invoicing

An invoice is issued for the service. If a subcontractor was used, their bill is reconciled in Purchase.

07Trip profit

Revenue and costs are compared by trip, vehicle and customer; the manager sees the margin.

Integrations

Services that connect to the transport system

Each connection is assessed and built separately. We do not promise that a “ready-made connector exists.”

Electronic documents and government

  • Operator of electronic invoices and waybills: electronic documents and tax
  • Electronic trip sheet (Uztrans), E-Permit: public API documentation has not been confirmed, and the terms are requested in writing
  • Customs declaration systems: the connection is determined at the diagnostic

Maps and tracking

  • Mapbox: routing and travel time (Odoo 20’s own connection)
  • GPS tracking and fuel sensor: through the telematics provider’s API
  • Driver mobile app: assessed separately

Sales and payment

For managers

What the manager sees

Reports are not copied into a separate spreadsheet: they are generated from documents in this same database.

Trip

  • Revenue, costs and margin per trip
  • Revenue by customer and route
  • Delayed deliveries

Fleet

  • Costs per vehicle (Fleet analysis)
  • Vehicles with contracts nearing expiry
  • Odometer readings and service history

Finance

  • Customer invoices and payment status
  • Amounts owed to subcontractors
  • Revenue by service type
The BUline Method

How we implement in a transport company

The stages follow the general BUline Method. The timeline is agreed in writing after the diagnostic. Implementation process →

01Diagnostic1–2 weeks

We study the service types (transport, freight forwarding, storage), the trip process, the fleet, the document flow, the current software and telematics. Result: a business requirements document (BRD).

02Architecture1–3 weeks

We confirm the set of apps, which app will handle the trip (Project or Planning), the fleet structure, the documents and the operator route, and the hosting type.

03Testing and sprints8–16 weeks

First, one route or one customer trip is run end to end: order, loading, document, invoice, margin. Then the vehicle fleet and integrations.

04Training

The dispatcher, driver, warehouse keeper, chief mechanic and accountant are trained by role. Practice uses your own list of vehicles and customers. Instructions and video lessons are provided.

05Post-launch support30 days + ongoing

After launch, 30 days of intensified support, then agreed ongoing assistance. When the rules change, the connection is re-checked.

Preparation

What to gather before we start

This list speeds up the diagnostic. We can start even if not everything is ready.

Vehicle fleet and trips

  • List of vehicles: model, license plate, capacity, driver
  • Leasing, insurance and technical inspection deadlines
  • Trips and routes from the last month

Goods and documents

  • Product weight, volume and IKPU (MXIK) codes (if you transport your own goods)
  • Holders of access rights to the electronic document operator, waybill and trip sheet
  • CMR, permit and TIR documents for an international trip

Rules and system

  • Transport contracts and settlement terms (as text)
  • The current software, the telematics provider and whether data can be obtained from it
  • Roles: dispatcher, driver, mechanic, accountant
Mistakes

Common mistakes and how to avoid them

MistakeConsequenceHow we prevent it
Expecting Odoo to be a ready-made transport management system (TMS)The trip and carrier logic only comes to light at the end of the projectRun the trip process through the standard apps during the diagnostic and agree the result in writing
Not entering weight and volume on productsThe capacity check does not work when building loadsMake weight and volume mandatory when uploading the catalog
Assuming the trip sheet and waybill are issued inside OdooThe document is missing in the operator's system and the ministry's systemConfirm the document route in writing at the architecture stage
Expecting driver pay to be calculated in OdooUzbekistan is not mentioned in the list of payroll localizationsAssess payroll calculation separately
Leaving the Mapbox connection to the last dayRouting and travel time do not workSet up the connection in the test database at the start of the project
FAQ

Frequently asked questions

Does Odoo have a freight transport (TMS) app?

The documentation does not describe a separate app for a carrier, and no freight package appeared in the industry catalog either. There is only the 3PL package and the load-building feature in Odoo 20. A carrier business is assembled from Sales, Project or Planning, Fleet and Purchase; the scope is estimated during the diagnostic.

Does Odoo issue the CMR waybill?

Yes: in Odoo 20 it is printed from the delivery document and filled in with the available data; missing fields are entered by hand. In a batch, a separate CMR is produced for each delivery. A connection to the electronic CMR (e-CMR) is not described in the documentation.

Can an electronic waybill and trip sheet be sent from Odoo?

The Odoo documentation does not mention such a connection. The electronic waybill is issued in the operator's system, and the trip sheet in Uztrans, the Ministry of Transport's system. The connection depends on the capabilities of the operator and the system and is estimated separately.

What does Fleet provide for a vehicle fleet?

Vehicle card, driver, leasing and insurance contract (deadline reminder), service and repair, odometer, cost analysis. A fuel log, tire records and GPS are not described in the documentation: they are handled with Studio fields or an external system.

In which cases does load building (dispatch) work?

When a company delivers its own goods in its own vehicles. It needs Fleet, a Mapbox connection, and weight and volume on the product; vehicle capacity is taken from the category. For a service transporting another company's cargo, this feature needs additional setup, and whether it fits is checked in a test database.

Is there a connection to permits and E-Permit for international transport?

The Odoo documentation does not mention such a connection. E-Permit is a platform of the Ministry of Transport, and its public API documentation could not be confirmed. Permits and TIR documents can be stored in Documents; we request the connection from the ministry in writing.

Odoo Online, Odoo.sh or your own server?

Standard apps work on Odoo Online. If telematics, an operator or a custom module is needed, Odoo.sh or your own server is chosen. The 3PL package relies on Studio, and its hosting limitation is checked during the diagnostic. Hosting types →

How much does the service cost and how long does it take?

The Odoo license depends on the number of users and apps (terms on odoo.com). The scope of BUline's services depends on the number of vehicles, trips, warehouses and users, apps, customization, integrations, data volume and training. The exact cost and timeline are given in a written proposal after the free diagnostic.

Free diagnostic

Let’s decide together which Odoo apps to start with

During the diagnostic, we review your processes and tell you where standard Odoo is enough and where configuration is needed — with an app list, edition and phases.

Free diagnostic