MYOB Acumatica Matrix Item Import Template Builder
A MYOB Acumatica matrix import needs an item class, ordered attributes, permitted values and a base item template before child items can reference them. Build a consistent child ID such as TS-BLK-M from those attributes, map the source columns and check required fields, duplicate IDs and references. Download against the specific import layout and test 3 representative rows in your tenant.
Rows ready for import
$0.00
Show breakdown
Calculation breakdown
- Valid rows
- $0.00
| Valid rows | $0.00 |
|---|
Choose a versioned import layout, map your columns and resolve every blocking error before downloading.
At a glance
- Layouts
- MYOB Acumatica stock items and matrix items, with the selected layout version shown
- Input
- paste or upload your current list, or generate SKU planning rows from attributes
- 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-07 from Gs1
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. The selected import scenario must map the template ID and the corresponding attribute names and values. Its source headers, worksheet, active mappings and update behaviour must match the file. The built-in layouts remain provisional and cannot export until their native workflow is verified.
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 attribute value referenced is defined; no duplicate combinations; ID template produces unique children | 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
How does attribute order affect a matrix item ID?
The item template’s attribute order determines the combinations and the way the child ID pattern is expanded. Define the attribute codes and values before generating children, then check uniqueness and length. The resulting references must match the item class and attributes configured in the tenant.
Can I re-import the same matrix items?
Use the same stable inventory IDs and the correct import scenario for updates. Confirm whether each mapped field overwrites an existing value, then test a small file in a non-production tenant. A valid spreadsheet cannot determine every customisation or import-scenario setting in your system.
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?
The built-in MYOB Acumatica layouts remain provisional and cannot export. A confirmed layout must match your scenario’s provider worksheet, source fields, active mappings and target build. Validation checks your declared reference lists, not the live tenant. Run Prepare and Import on a small test file and check the resulting items and relationships before using the full catalogue.
MYOB Acumatica partner in Brisbane
Bring the validated file to a discovery call and we will size the implementation from it.
Book a conversation