Do these three things first
- Pause staff edits and integrations that can keep changing the Item Library.
- Export the library as it exists now. Do not overwrite the file used for the original import.
- Write down the import time, source file, affected locations, and the first incorrect result you observed.
Classify the damage before changing anything else
Determine whether the import added duplicate items, changed existing fields, changed location availability, or removed information. Test one representative item and one variation from every affected pattern. A second broad import made before this review can make the recovery harder.
Choose the recovery path
If you made a native Square export before the import
Compare it with the current export. Review Square tokens, variation rows, SKUs, taxes, modifiers, and location columns before attempting another import. Work on a copy and test the smallest safe set first. Follow Square's current Item Library import instructions, including its pre-change export recommendation.
If you do not have a native pre-change export
Use receipts, menus, prior files, and recorded Item Library history to identify the intended setup. Correct the affected items manually in Square, checking a small sample before applying the same fix more broadly.
How CatalogTrail helps—and what it does not do
CatalogTrail can compare saved versions recorded after connection, show which supported fields changed, and provide a reference spreadsheet or technical JSON reference. That evidence can shorten the investigation and guide manual corrections.
Verify the correction
- Check item and variation names, prices, and pricing types.
- Check SKUs, categories, taxes, and modifier assignments.
- Check each affected location and sales channel.
- Run a low-risk test transaction where appropriate.
- Save a new native Square export after verification.