Yes where they remain valuable and fit Shopify’s extension model. Each rule should be mapped to native configuration, Shopify Functions, theme or checkout extensions, an app, Shopify Flow, an external service, or a redesigned process. Rules should not be copied merely because they exist in the legacy code.
Describe the outcome before deciding where the rule lives
Document the rule using an example: a particular buyer selects a product, qualifies for a price, receives a delivery option, or triggers an internal approval. Include exceptions and identify who owns the decision. This makes it possible to judge alternatives without carrying across obsolete implementation details.
Prove the proposed configuration, app, extension, or external service against those examples. Check plan requirements, timing, and what happens when a dependency is unavailable. If the behaviour needs to change, obtain a clear operational decision and train the affected team. An undocumented workaround should not become the permanent migration strategy.
What to check before deciding
- Record the rule, exceptions, required data, and business owner.
- Verify eligibility and constraints of the chosen implementation.
- Test successful, rejected, and unavailable-dependency scenarios.
- Document accepted changes and ongoing maintenance responsibility.
