Product import template builder for MYOB Acumatica and Odoo
Product imports often fail on duplicate codes, missing tax codes and variants whose attributes do not exist yet. This builder maps your CSV columns to the target product fields and validates identifiers, required fields and references before download. Start with a 3-row trial, review the report and check the target version before importing the complete catalogue into your ERP.
Rows ready for import
0
Show breakdown
Calculation breakdown
- Valid rows
- 0
| Valid rows | 0 |
|---|
Choose a versioned import layout, map your columns and resolve every blocking error before downloading.
PDF for a finished report, Excel for a formatted workbook, CSV for plain data.
At a glance
- Layouts
- MYOB Acumatica stock items and matrix items; Odoo product templates and variants
- Input
- paste or upload a product CSV with a header row
- Validation
- required fields, unique IDs, referential integrity, lengths, types, GTIN check digits
- Output
- CSV or XLSX in the import screen's column order, plus a validation report and import notes
- Import order
- attributes and classes first, then items, then variants or matrix children
- Note
- Nothing is uploaded; the file is built and validated in your browser
How it is calculated
Match source columns to the selected layout, apply explicit defaults and validate every output row. Required fields, identifiers, declared references, types and barcodes must pass before download.
source rows → column mapping → defaults → validation → download- Rates as at 2026-09-09 from Gs1
Try a test import example
Choose a product type, then select Load test example to fill the builder with sample products and matching reference lists. Continue through mapping and validation to see how it works. You can also download a test CSV:
- Odoo product templates test CSV
- Odoo existing variants test CSV
- MYOB Acumatica stock items test CSV
- MYOB Acumatica matrix items test CSV
The products and reference values are fictional. Use actual identifiers and reference lists from your own system for a real import. Loading your own CSV clears the example reference lists.
Start with your product CSV
Paste or upload a CSV with a header row. Choose the product type you are importing, map your columns, supply missing defaults and correct the validation report. Download the resulting CSV or XLSX required by your target system, plus import instructions. The source file stays in your browser.
Why do product imports fail?
Spreadsheet data often lacks the relationships the target system requires. Codes can collide after whitespace and case normalisation; attribute values may not exist yet; and tax codes or units may differ from the tenant’s configured values. The builder checks the selected layout against the reference lists you declare. It cannot query the tenant or reproduce every server-side rule, so a successful validation report must still be followed by a native test import.
What does a MYOB Acumatica matrix item import need?
Prepare the item class, ordered attributes, permitted values and template item before its matrix children. A child ID such as TS-BLK-M identifies a combination, but an ID and flat colour/size columns do not establish the template relationship. Include the template ID and the corresponding attribute names and values in your CSV. MYOB Acumatica product downloads are currently unavailable; you can still map a CSV and check its validation report.
What does an Odoo product import need?
For Odoo 18, select Goods or Service; inventory tracking is a separate Track Inventory flag. Import attributes and values first, then product templates with external-ID references to their attribute lines. Each attribute line also needs its own stable External ID: omitting it can create extra lines and variants on re-import. Additional attributes use continuation rows with blank parent fields, without parent defaults or generated IDs. When updating existing attribute lines, retain their actual exported IDs.
Odoo generates the variants. Export their actual External IDs before updating variant references, barcodes, costs or weights; a new ID or SKU is not a safe substitute. Selling price belongs to the shared template. Use attribute extra prices or a separately configured pricelist for variant price differences, not an independent price column in the variant update file.
When should the import file be built?
Start during discovery, before the full migration. A representative sample makes the catalogue size, variant structure, attributes and tax requirements visible. Validate the source, test it in a non-production tenant, inspect the imported records and repeat an update using the same identifiers. Expand to the full catalogue only after those checks pass; customisations and tenant settings may require a different layout.
| Group | Rules | Blocking |
|---|---|---|
| Required fields | Every required column in the layout is present and non-empty | Yes |
| Identifiers | Unique codes; length limits; allowed characters; trimmed; stable external IDs | Yes |
| References | Item class, tax code, UoM, warehouse, accounts, categories exist in the declared lists | Yes |
| Variants | Every referenced attribute value is declared; no duplicate combinations; stable product and attribute-line IDs | Yes |
| Types | Prices, costs, weights, dimensions numeric and non-negative; dates ISO; booleans normalised | Yes |
| Barcodes | GTIN length and check digit; unique | Yes |
| Text | Length limits; no control characters; initial zeroes preserved | Yes |
| Warnings | Empty description; missing barcode; price below cost; zero weight on a storable item; duplicate rows collapsed | No |
Frequently asked questions
Is my product data uploaded anywhere?
No. The file you paste or upload is read in your browser, validated there, and the output is generated there. Nothing is sent to our servers or anyone else's. If you want to keep your mapping and defaults for next time, turn on "Remember my settings", which stores only the settings, not the data.
Will the file import without changes?
Validation checks your CSV and the reference lists you supply; it cannot check your live database or every customisation. Product exports that are unavailable stay disabled. Check the target version and test a small representative file through its native import workflow before importing the catalogue.
Can it build customers, suppliers and a chart of accounts too?
This version covers product stock items, matrix items, product templates and variants. Customer, supplier and chart-of-accounts layouts are outside the current scope. Choose a product module and check the version shown before preparing the file for a particular tenant.
What if my catalogue has thousands of variants?
The builder supports up to 100,000 CSV source rows within its file-size limits. Include the product identifiers and attribute references your target system needs, map the columns and correct reported errors. For a large or complex catalogue, start with a representative native import test before expanding the file.
moving from Xero or AccountRight to an ERP
Bring the validated file to a discovery call and we will size the implementation from it.
Book a conversation