QuickBooks Online Item Imports Fail on Limits, Dates, and Subaccounts

QuickBooks Online’s spreadsheet import for products and services looks like a five-minute task, until the mapping screen starts flagging cells in red or silently refuses an account assignment. Users moving an item list into the software keep hitting the same walls, and the accepted guidance on the issue amounts to a field-rule checklist: character limits, date formats, account restrictions, and category syntax, plus two different import screens depending on the account.

Two import screens, one setting

The entry point is the same for everyone: Settings, then Import data, then Products and Services. What appears next depends on the account. The newer version presents a batch-import screen built around a spreadsheet layout, with its own sample file. The older version offers uploads from an Excel file, a CSV file, or a Google Sheet, with the Google option requiring a one-time connection to your Google account. The field rules are shared even where the buttons differ, so the walkthrough below covers both.

The limits, and the 512-versus-100 question

The documented caps read as follows: product and category names at 512 characters, option names and option values at 100, descriptions at 4000, and SKUs at 100. Separately, the guidance attached to the older flow lists a 100-character limit for the Product/Service Name field.

That gap between 512 and 100 is not a typo you can safely ignore. It reflects two screens carrying two documented ceilings for what is essentially the same field. Since you cannot always predict which screen your account will present, the practical resolution is to keep item names at or under 100 characters so the file clears either version. A name that fits under the larger cap on one screen can still fail on the other, and shorter names also behave better across reports and transaction forms. When a name genuinely needs more room, put the detail in the description field, where the allowance is far higher.

Dates, accounts, and the reserved colon

Three field rules do most of the damage. Quantity as-of dates must follow MM/DD/YYYY format, with the older flow also accepting DD/MM/YYYY; during mapping you have to confirm that the format you select matches your data, because a mismatch is exactly the kind of error that turns cells red. Income and expense accounts cannot be subaccounts, so if the account you want sits nested in your chart of accounts, the import will not take it and you need to map to a top-level account instead. Categories use a colon-separated syntax, Category:Subcategory, up to four levels deep, with examples like Clothing:Jackets or Clothing:Shirts. The colon is doing structural work in that syntax, which is the first reason to keep it out of item names entirely.

The special-character rule, made concrete

The guidance says to avoid special characters and points to an approved characters list, but the import flow itself never spells out which symbols are banned. The practical reading: build names from plain letters, numbers, spaces, and simple punctuation, and treat anything beyond that as a suspect. Reserve the colon for category paths only. Symbols that spreadsheets interpret as formula markers or delimiters are the other common trouble source, since what you see in a cell is not always what the file contains. If a name truly needs an unusual symbol, test it on a single row before committing the whole file.

The walkthrough

1. Sign in to QuickBooks Online, open Settings, and select Import data.
2. Select Products and Services, and note which screen appears: the new spreadsheet layout or the old upload screen.
3. Select Import CSV, then download the sample file and open it.
4. Enter your data in the sample’s columns, respecting the limits, the date format, and the account and category rules above.
5. On the new screen you can also paste rows from your own spreadsheet, or reach a manual entry grid through Settings, Import data, and Create products.
6. Upload the file: on the old screen, browse for an Excel or CSV file, or connect your Google account and choose a Sheet.
7. Select Next and map each spreadsheet header to the matching QuickBooks field, confirming the date format as you go.
8. Correct any red-highlighted cells as the error message directs, or fix the file and upload it again.
9. Decide deliberately on the overwrite option, which pushes the values in your file onto existing items and cannot be undone.
10. Select Save on the new screen, or Import on the old one.

Red cells and the overwrite trap

Red highlighting during mapping is the only advance warning that a cell is invalid, and the fix is always local: read the message, correct the cell or the underlying file, and run the import again. If mapping keeps failing on a file that looks clean, the QuickBooks Online troubleshooting pages cover related import errors worth checking before you rebuild the spreadsheet from scratch.

The overwrite setting deserves more caution than the rest of the flow combined. Both screens offer it, phrased slightly differently, and both warn that it cannot be reversed. It exists to update existing items in bulk, and it will do exactly that, including when your file carries an outdated name by accident. Review the mapped preview one more time before selecting it.

The pattern across the accepted answer is consistent: the import itself is simple, and nearly every failure traces back to a rule that was knowable in advance. Build the file against the sample, keep names short and plain, format dates deliberately, map to top-level accounts, and most red cells never appear at all.