Import dialog body text
Upload a spreadsheet file to validate and generate a preview. No changes are applied until you review the preview and press Save.
Export Import Category Tree
Export creates a spreadsheet snapshot of your category tree. Import validates the file, shows a preview, and applies changes only when you press Save.
Overview
Export Import is a controlled workflow for updating your category tree using a spreadsheet file. Export generates a file from your current tree so you have an explicit snapshot. Import reads that file, validates it, and produces a preview so you can review the result before any changes are applied. After you confirm the preview, you press Save to apply the changes. This approach is designed for careful changes, backups, and intentional reuse of a structure.
When to use
Back up your current category tree before making a large change
Make bulk edits in a spreadsheet editor such as Excel or Google Sheets
Restore or roll back to a previous structure by importing an older export file
Reuse a structure for another store when you intentionally export from store A and import into store B
How it works
Export creates a spreadsheet file based on your current category tree. You can edit it in a spreadsheet editor and upload it back using Import. Import validates the file and shows a preview of the resulting tree. Nothing is applied during preview. The app applies changes only when you press Save.
Step by step
Export current tree
1. Open the Categories Tree page in the app.
2. Confirm you are in the correct store and workspace.
3. Click Export.
4. Download the spreadsheet file to your computer.
5. Keep the exported file as a backup before you edit anything.
6. If you plan to edit, make a copy of the exported file and work on the copy.
Edit in spreadsheet safely
1. Keep the original column headers unchanged.
2. Keep the ID values unchanged.
3. Edit only the fields you understand, such as DISPLAY NAME and PATH IN TREE.
4. Use one row per collection and do not duplicate rows.
5. When editing PATH IN TREE, use the ID based format described in Rules and validation.
6. Avoid adding extra spaces before or after IDs in PATH IN TREE.
7. If you reorder nodes, keep parent rows present so validation can resolve parents.
8. Save the file in a supported spreadsheet format and do not rename the sheets.
Import and preview
1. Return to the Categories Tree page in the app.
2. Click Import.
3. Select the edited spreadsheet file.
4. Wait for the app to validate the file.
5. Review the preview tree and confirm the structure is correct.
6. If validation errors appear, fix the file and import again.
Apply changes
1. In the preview, confirm you are satisfied with the result.
2. Press Save to apply the previewed changes.
3. Wait for the save process to complete.
4. Refresh the page and confirm the current tree matches the preview.
Rules and validation
Import validates the spreadsheet file before it can generate a preview. The rules below describe the minimum requirements for PATH IN TREE and relationships between nodes.
PATH IN TREE must start with /
Example: /100 is valid. 100 is not valid.
The last ID in the path must be the row’s own ID
Example: For a row with ID 200, PATH IN TREE must end with /200.
Every parent ID in the path must exist in this file
Example: If PATH IN TREE is /100/200, then rows with ID 100 and 200 must exist.
A collection can have only one parent at a time
Example: ID 200 cannot appear as a child of two different parents in the same import file.
Do not create loops (circular reference)
Example: If 100 is a parent of 200, then 200 cannot become a parent of 100 in any PATH IN TREE.
Quick examples
Common errors and fixes
Missing parent
Symptom: Validation fails and the preview cannot be generated.
Likely cause: A parent ID in PATH IN TREE does not exist as a row in the file.
How to fix: Add the missing parent row, or update PATH IN TREE to reference an existing parent.
Circular reference
Symptom: Validation fails with a circular reference message.
Likely cause: PATH IN TREE creates a loop where a node becomes an ancestor of itself.
How to fix: Edit PATH IN TREE so the hierarchy is strictly parent to child with no loops.
Duplicate ID
Symptom: Validation fails and reports duplicate IDs.
Likely cause: The same ID appears in more than one row across sheets.
How to fix: Keep a single row per ID and remove duplicates before importing.
Invalid path format
Symptom: Validation fails due to PATH IN TREE format.
Likely cause: PATH IN TREE does not start with / or contains non numeric segments where IDs are expected.
How to fix: Use the ID based format and ensure PATH IN TREE starts with /.
Non existent collection ID
Symptom: Preview is missing nodes or validation reports unknown IDs.
Likely cause: The file contains an ID that does not exist as a collection in the current store.
How to fix: Export again from the current store and re apply your edits on the new export file.
Multiple parents
Symptom: Validation fails or the preview shows an unexpected structure.
Likely cause: The same ID is placed under different parents in different rows or sheets.
How to fix: Ensure each node appears in exactly one place in the tree and keep a single PATH IN TREE for that ID.
Safety notes
Import creates a preview only until you press Save.
Export a backup before you start editing.
You can restore by importing a previous export file and then pressing Save.
FAQ
Yes. Export a backup before you apply changes. If you need to undo, import the backup file, review the preview, and press Save.
No. IDs are used to match rows to collections. Keep IDs unchanged.
No. This file is for the category tree structure and related fields used by the app. It does not rename your Shopify collections.
The import workflow does not change the underlying Shopify collection data such as titles or handles. It updates how collections are organized as nodes inside the app’s category tree.
Yes, when you intentionally export from store A and import into store B. The target store must contain the collections referenced by the IDs in the file.
Update PATH IN TREE to reflect the ordering and parent relationships you want, then import, review the preview, and press Save.
The app will not generate a preview. Fix the spreadsheet file based on the error details and import again.
UI microcopy
Preview screen hint
Review the preview carefully, then press Save to apply these changes.