What must your team finish in Odoo?
Choose a starting point, see what we need to inspect and what your team should accept before go-live. These are proposed working sequences to discuss, not a fixed package or a delivery promise.
Request an Odoo demoSample data. Our team confirms the appointment with you.
Manufacturing with an existing MES
If production orders live in the ERP and actual output lives in MES, first agree which system owns each record and who deals with a failed transfer.
Request a production workflow demoOpens your email app. We confirm the time.
Work through the transaction
- Trace a Sales Order through the Manufacturing Order, material issue, finished goods receipt and scrap. Mark each exchange between Odoo and MES.
- Map product codes, units, bills of materials, lots and work states. Define a shared reference that prevents a repeated message from creating another receipt.
- Test normal, repeated and disconnected transfers in a test environment. Have production, warehouse and accounting owners review the same transactions.
- Bring to the discussion
- Sample BOM and production orders, products and units, MES API documentation or message format, output and scrap records, system administrator and process owners.
- Check before approval
- One output receipt must change stock once. Test retries and delayed messages. Check quantities by lot and the costing method agreed with accounting before approving a live connection.
- Resolve before quoting
- An MES without an API, different units or different posting times can change the integration scope. We assess the connection and reconciliation approach before pricing it.
Wholesale across several warehouses
Total stock may cover an order while the goods sit in the wrong warehouse. Follow one sales order through reservation, transfer, delivery and return.
Request a multiwarehouse demoOpens your email app. We confirm the time.
Work through the transaction
- Map warehouses and storage locations. Agree what sales staff see as available, reserved and in transit.
- Set up a sample order fulfilled from two warehouses. Test shortages, partial delivery, internal transfers, returns and approval rights.
- Run a sample count and reconcile stock by warehouse, product and lot where relevant. Check the effect on inventory value and accounting entries.
- Bring to the discussion
- SKUs and units, warehouse layout, stock by location, sample sales/transfer/return documents, pricing and credit rules, and transaction approvers.
- Check before approval
- The test order must reserve and deduct stock from the right warehouse. In-transit goods cannot be counted twice as available. Partial deliveries and returns must reconcile to documents and accounting.
- Resolve before quoting
- Duplicate product codes, box-to-unit conversions and in-transit goods can distort opening stock. Agree the cut-off and counting method before migration.
Moving from Express or Excel
Before moving every file, decide which history belongs in Odoo, what stays in an archive and who may approve opening balances. Every imported balance needs a traceable source.
Request a migration and reconciliation demoOpens your email app. We confirm the time.
Work through the transaction
- Inventory the old exports and files. Separate master data, opening balances, open documents and history, then assign an owner to each dataset.
- Map source fields to target fields, resolve duplicates, units and missing values, and rehearse the import using a copy in a test environment.
- Reconcile the trial balance, open receivables/payables, stock quantities and value. Record differences, obtain owner approval and rehearse cut-over.
- Bring to the discussion
- Express exports or Excel samples with personal data removed or replaced, chart of accounts, customer/vendor/product lists, trial balance, open AR/AP and stock at the same cut-off date.
- Check before approval
- Record counts and totals must match the agreed scope. Every difference needs an explanation and approval. Accounting and warehouse owners sign off before balances are used in production.
- Resolve before quoting
- Incomplete history and reused codes need correction before import. Agree the history scope, data cleaning cost and rollback plan separately from system configuration.
See what an acceptance document can contain
Synthetic sample created for this page. All IDs, quantities and amounts below are invented. These are not customer records, redacted project documents or evidence of delivered results. Actual fields, scope and pass criteria must be agreed for your project.
Fit-Gap Backlog
Download synthetic CSV| ID / workflow | Proposed approach | Acceptance check / owner |
|---|---|---|
| FG-01 Warehouse-specific reservation | Try standard Inventory configuration before custom development | Test order reserves from WH-A only / Warehouse lead |
| FG-02 Receive MES output | Assess API and shared reference before defining integration scope | Retry MSG-001 and create one receipt only / Production and IT |
Migration Mapping
Download synthetic CSV| Synthetic source data | Target / rule | Check / approver |
|---|---|---|
| ITEM_CODE = DEMO-001 | Product Internal Reference; unique codes required | Compare distinct code counts and rejected records / Warehouse |
| WH = A, QTY = 100, UNIT = PCS | Location = WH-A/Stock; unit = Units | Compare product/location totals at the same cut-off / Warehouse |
Reconciliation & Acceptance
Download synthetic CSV| Synthetic check | Source / imported | Pass criterion / status |
|---|---|---|
| DEMO-001 at WH-A/Stock | 100 units / 100 units | Difference 0 units / Pass in this example |
| Open receivable DEMO-AR-001 | THB 12,000.00 / THB 11,500.00 | Difference must be THB 0.00 / Not passed; investigate THB 500.00 |
The failed receivable check is deliberate. A difference stays open until its cause, correction and approval are recorded.
Customer references listed by Odoo
- Capric (Thailand) Co., Ltd. (บริษัท แคบริค(ไทยแลนด์) จำกัด)Manufacturing / Maintenance
- บริษัท จิ๊กซอว์ บางกอก จํากัด (สํานักงานใหญ่)Wholesale / Retail
- บริษัท โปรเฟส อินดัสเทรียล กรุ๊ป จำกัดWholesale / Retail
Source: our public Odoo partner profile, checked 25 October 2026. These selected listings confirm names and sectors. They do not establish project scope, installed modules or measured results.
Ask to see your workflow with sample data
Tell us your current system, the workflow you want to see and who will join from your team. We will contact you to agree the demo scope and confirm a time. This is an appointment request, not an instant booking.
The demo uses sample data. You can start with blank document layouts or a short description; please keep passwords and personal customer data out of the first email.