Skip to main content
AI & Technology

Odoo for Import-Export Trading: An Illustrative Workflow Guide

A hypothetical guide to purchasing, receipts, landed costs, sales and accounting in Odoo, with evidence and acceptance criteria buyers can discuss with providers. This is not a customer case study.

2 Apr 20267 min
OdooERPImport ExportTradingWorkflow Guide
AI-generated illustration of import documents, a bearing, a parcel and a calculator on a warehouse desk
AI-generated illustration, not a customer project photograph.

The goods have reached the warehouse, but some freight bills are still missing. Which cost should sales use for a quotation, and when can accounting establish the margin on that shipment? This question is a useful starting point for system design before choosing modules.

Content status and correction, 25 October 2026: This article is a guide based on a hypothetical scenario. PinnacleArc, used in the previous version, was an invented company name, not a pseudonym establishing a real customer reference. The personal quotations, project details, before-and-after figures, six-month outcomes and payback period in that version had no verifiable project evidence attached to this article. Those claims, including the claim that Enersys delivered this project, have been withdrawn. The original URL and publication date are retained so existing links continue to work.

Define the scenario before designing the system

Suppose an industrial parts trader buys in foreign currencies, stores goods at several locations and sells to customers in Thailand and overseas. Purchasing manages purchase orders, the warehouse manages receipts and deliveries, and accounting manages bills and payments. Some records remain in separate spreadsheets.

The following is a proposal to test. It contains no company's verified revenue, headcount, budget or achieved results, and does not establish that Odoo fits every business. Buyers should use their own documents and product records to test the proposed process.

Start with one order and collect its purchase order, goods receipt, vendor bill, import charges, customer delivery and payment records. Define the reference used to follow that transaction. Distinguish product lots from shipments: a shipment can contain several lots.

Design the flow from purchasing to payment

Purchasing and receipts

Ask the team to test requests for quotation, purchase order approval, receipts and vendor bill checks in Purchase and Inventory using representative products. Include partial receipts, excess deliveries, returns and bills received before the goods arrive.

Before migration, have an owner confirm product codes, units of measure, vendors and opening balances. Define who can change master data and who approves those changes. Retain the opening balance reconciliation as evidence before launch.

Multiple locations and goods in transit

The Odoo 19 Locations documentation describes tracking goods by location and setting location types, including Internal and Transit. Enabling Storage Locations is part of the configuration.

For this scenario, ask the provider to demonstrate a transfer from origin to destination, stock in transit, quantities reserved for sales orders and quantities available to deliver. Total stock alone does not establish what can be promised to a customer. Test the routes and reservation rules the business will actually use.

Landed costs and foreign currencies

The Odoo 19 Landed costs documentation describes adding charges to product valuation and allocation methods such as quantity, weight and current cost. Applying landed costs through a vendor bill requires the original products to belong to a category using AVCO or FIFO costing.

Have accounting approve which charges form inventory cost, which are period expenses and how each tax is recorded. Then test a freight bill that arrives after part of the stock has been sold. Check the inventory valuation and accounting impact. Do not assume every charge is automatically allocated to every lot.

The Odoo 19 Multi-currency system documentation covers foreign currency transactions, manual or scheduled rate updates, and accounts for exchange differences. Check the rate source and update interval in the proposed system.

Use different rates for the bill and payment dates in the test, then have accounting reconcile the difference to bank evidence. Better visibility does not guarantee lower exchange losses and does not itself provide financial hedging.

Sales, documents and margin by shipment

Ask the provider to demonstrate sales orders, stock reservations, deliveries, invoices and payments with references that can be traced back. Test partial deliveries, returns, credit notes and sales above the company's credit limit. State which rules use configuration and which need development.

A shipment margin report is a requirement to design and accept separately from lot tracking. Specify the revenue and costs included, allocation rules, and how missing costs are shown. Estimated margin before all documents arrive and margin after cost closing need different status labels.

If the business needs customs declarations, certificates of origin or work under BOI conditions, specify each document, reviewer and actual submission channel separately. Holding data in an ERP does not establish that a document has been approved or submitted to the relevant authority.

Agree the scope before agreeing the price

Ask providers to separate standard functions, configuration, integrations and development, naming the proposed version and service plan. Use the same transaction set when comparing providers or the existing system.

The quotation should separate licensing, migration, development, integrations, training, post-launch support and upgrade costs. Include exclusions, owners and scope change terms. This guide gives no benchmark price or implementation duration because the buyer's scope and data have not been established.

Define the acceptance evidence

This is a proposed acceptance checklist. Buyer and provider need to agree the pass criteria before work starts.

Area to test Evidence to request Pass criteria to agree
Opening data Imported product records and reconciliation to source Balances and units match the signed-off dataset
Receipts and transfers Receipt, transfer, partial receipt and return history Quantities and locations remain traceable across the test
Landed costs Bills, allocation method and accounting entries Accounting owner reconciles totals and approves the treatment
Foreign currencies Rate source, applicable dates and difference entries Differences can be explained against source documents
Sales and margin reporting Sales orders, deliveries, credit notes and reports Revenue and costs are traceable, including incomplete items
Access and corrections Role-based test results and change history Unauthorized actions are blocked and reviewers can trace changes
Launch readiness Migration rehearsal, open issues, backup and restore plan Owners sign off open issues and restore test results before launch approval

When an essential item fails, record its owner, due date and retest method. A demonstration covering only the normal path is not acceptance evidence.

Measure results using your own business data

Before work begins, record purchase order processing time, closing time, documents requiring correction and physical count discrepancies. Define the start and end of each timed activity, sample size, date range and data owner. Use the same definitions after launch and show transaction volumes alongside the comparison.

Distinguish time saved from actual cash savings. If estimating payback, include project and recurring costs, state assumptions and the measurement period, and identify unknowns. This article supplies no measured results or payback commitment to substitute for the buyer's data.

What to bring to a provider discussion

Bring a completed order's document set and an exception that caused difficulty, such as a short delivery or a late freight bill. Ask the provider to demonstrate both. State what must pass before launch and request verifiable project evidence when customer references inform your decision.

Discuss scope and acceptance criteria with Enersys, including user count, stock locations, currencies and systems to connect, so the discussion begins with your operation.

Continue with guides on related topics.

Browse all Insights

"Empowering Innovation,
Transforming Futures."

Contact us to make your project a reality.