Item or custom list translations cannot be imported
Check language setup, translation mappings, and whether the main record needs to be created first.
Creating an item with translations reports Locale
Message looks like
Invalid Locale Reference Key XX
What it means
The Multi-Language feature is enabled and the item is being created with translation columns in the same file, which this import cannot do in one pass.
Import context: Inventory items and Item translations.
Check this first
First add the item with its required accounting, location, and pricing data, then update it with language and translated display values.
Show the steps
Steps for this error
- This appears when the Multi-Language feature is enabled and a new inventory item imports with translation columns alongside its other fields.
- Import the item first without the Translation Language and Translation Display Name columns.
- Run a second import with Update to add the translations to the imported items.
If that looks right
In the first pass, include the starting quantity price break when required. In the second pass, use Update and map the translation language and translated display name to the translation sublist.
Documentation checked September 16, 2026.
A translation line cannot be added
Message looks like
Adding new line to sublist translations is not allowed
What it means
Translations are being imported while the Multi-Language feature is not fully set up, so the translation sublist will not accept new lines.
Import context: Custom lists.
Check this first
Check that Multi-Language is enabled and at least one language is listed under Enable Features.
Show the steps
Steps for this error
- Check that the Multi-Language feature is enabled and at least one language is listed on the Languages subtab under Setup > Company > Enable Features.
- Retry the translation import after the language setup is confirmed.
Documentation checked September 16, 2026.
Translation rows do not match the default language
Message looks like
Unable to find a matching line for sublist translations
What it means
The Language field uses one fixed mapping value while the file contains translations in more than one language, so most rows find no matching line.
Import context: Custom lists.
Check this first
Map the language from a CSV column or split the file so each import carries one language.
Show the steps
Steps for this error
- Check whether the Language field uses a static mapping while the file contains translations for more than one language.
- A static language mapping works only for a single-language file. Map the language from a CSV column, or split the file by language.
- Retry one list.
Documentation checked September 16, 2026.
Related errors
- Customer type or linked contact data needs attention
- A required field is missing or cannot be written
- NetSuite cannot read the CSV file or its columns
- Sales order terms and payment method conflict
Book a free 30-minute look at your import error
Bring the error and your file to a screen share and I will dig into it live. Thirty minutes is usually enough to find what is wrong and tell you what fixing it takes. Sometimes that settles it on the call; when it does not, you leave with a straight answer instead of a mystery. No cost and no obligation.
An import that keeps failing is often the first visible sign of a larger setup problem. Most of my client work starts exactly here: somebody mid-import, a file that will not load, and nobody on their side to email. If a migration or implementation sits behind this error, that is the work I do every week.