Rules are portable. Each one exports as a self-contained JSON file that can be imported into any store running the app.
| Task | Guide |
|---|---|
| Download a rule as a file | Export a rule |
| Bring a rule in from a file | Import a rule |
| Understand a partial import | Why parts were skipped |
What it is good for
- Dev store to live. Build and test somewhere harmless, then move the finished rule.
- Backups before risky edits. Switching a rule’s condition set clears its conditions with no undo.
- Agencies. Roll the same setup across many client stores without rebuilding it each time.
- Support. A rule file tells support far more than a screenshot.
The one thing to expect
A rule can reference things that only exist on the store it was built on — specific products, collections, customer tags. Those references do not always resolve elsewhere.
The importer handles this by checking every part, importing what it can, and telling you plainly what it had to leave out. It will not quietly create a rule that looks right and behaves differently.