Item prices or quantity breaks cannot be imported
Check the starting price, price level, and existing matrix before deciding how the pricing should change.
Choose the message that matches your import.
A quantity price break has no starting price
Message may mention: Please Enter Missing Price(s).
What it means
The higher quantity break is present, but the starting price is missing.
Import context: Item records.
Check this first
Include pricing for quantity zero as well as the later quantity breaks. Check the existing item before changing the price table.
Show the steps
Check the price structure
- Establish whether the change is to a price, a quantity break, a price level, or the entire structure.
- Compare the existing item pricing with the proposed rows.
- Keep every price and quantity break that is meant to remain.
- Check the missing-base-price case separately from the new-matrix-header case.
- If the change would replace pricing, ask the account administrator to review the pricing setup and the conflicting Oracle guidance before proceeding.
This is a check of the intended price structure, not an instruction to enable sublist replacement.
Documentation checked September 16, 2026.
A pricing update introduces a new matrix header
Message may mention: existing headers, existing matrix.
What it means
The pricing update refers to a header that is not already in the matrix.
Import context: Item records.
Check this first
Decide whether you are updating existing breaks or replacing the price structure. Oracle's error-specific article describes supplying the full price matrix and enabling sublist replacement, but its general sublist guidance cautions against that option for item pricing. Do not present replacement as an automatic fix.
Show the steps
Check the price structure
- Establish whether the change is to a price, a quantity break, a price level, or the entire structure.
- Compare the existing item pricing with the proposed rows.
- Keep every price and quantity break that is meant to remain.
- Check the missing-base-price case separately from the new-matrix-header case.
- If the change would replace pricing, ask the account administrator to review the pricing setup and the conflicting Oracle guidance before proceeding.
This is a check of the intended price structure, not an instruction to enable sublist replacement.
If that looks right
Oracle’s error article and general sublist guidance disagree about replacing item pricing. Ask the administrator to verify the relevant pricing setup before replacing the matrix. Read the sublist option guidance.
Documentation checked September 16, 2026.
The price level cannot be matched
Message may mention: price level.
What it means
Check the price level under the accounting lists, including inactive entries.
Import context: Item records.
Check this first
Compare its name with the CSV value. If the import should use one price level throughout, select that level as a mapping default. Do not use a default when the file deliberately includes different levels.
Show the steps
Check the record reference
- Find the field named in the error on the import's Field Mapping page.
- Open its edit control and check the selected reference type.
- Compare that setting with the actual CSV value. A number could be a name, an external ID, or an internal ID. Its appearance alone does not establish the type.
- Locate the intended record in the same account. Confirm its identity and whether it is available for this transaction.
- Correct the file or mapping so they agree. Use a default only when it applies to every affected row.
If you need to see internal IDs, enable them in your personal preferences or include them in a saved-search export. Supported reference types vary by field. Name matching is generally case-insensitive, so changing capitalization alone should not be the standard recommendation.
For a duplicate-record message, determine whether you intend to update the existing record or create a different one. Do not generate new external IDs simply to get past the error. For inactive records or subsidiary restrictions, verify the intended business setup before changing it. Those are account decisions, not text-cleanup operations.
If that looks right
Documentation checked September 16, 2026.
Related errors
- NetSuite cannot read the date or posting period
- Event dates or times are missing or invalid
- Numbers or identifiers changed in the CSV
- NetSuite CSV import says an amount is missing
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite