Before you start
- The exported file. It is named after the rule and ends in
.rule.json— that is the right file, not a different format. - The condition set the original rule used — importing into a different set is the usual reason conditions get skipped.
Steps
1. Install Nex Reorder
Search Nex Reorder in the Shopify App Store, or use the button below. Approve the permissions and the app appears in your admin under Apps. There is a free trial, and it is free on development stores.
2. Open Import — from the rules list, or from inside a rule editor.
3. Drop the .json file onto the drop zone, click Choose file, or paste the JSON directly into the text box.
4. Click Review. The rule is validated and shown to you, together with anything that could not be brought across.
5. Confirm. Importing into an editor that already has a rule in progress asks you to Replace current setup first.
Replace really does replace
Importing into an open editor discards everything in it, including unsaved changes. If the current rule is worth keeping, export it before importing over the top.
What the importer checks
Before anything is written, it verifies the file is valid JSON, came from this app, describes a single rule, uses a supported format version, and states both a method type and an action.
It also checks the file matches the editor you are in — importing a shipping rule into a payment rule editor is rejected rather than silently converted.
When only part comes across
A file can be valid and still contain things this store cannot use — a condition that is not in the chosen set, an operator a condition does not support, a product that does not exist here.
Rather than fail the whole import, those parts are skipped and listed for you, and you choose whether to Import the rest. Full detail in why parts were skipped.