Many requirements can map to native Shopify capability, apps, Functions, checkout and theme extensions, APIs, or custom services. Some Magento behavior should be redesigned or retired. Discovery should record every extension, business rule, owner, usage, destination, test case, and fallback before scope is confirmed.
Test the business rule at the supported extension point
Describe each customisation as a scenario rather than a module name. For example: a buyer in a particular company sees an agreed catalog, places an order on terms, and sends it to the correct fulfilment system. This makes it possible to assess alternatives without assuming the Magento implementation must be copied.
Assign the scenario to native Shopify configuration, an app, an extension, or an external service and test its failure behaviour. Confirm plan eligibility and compatibility before treating it as included. If the behaviour cannot be reproduced safely, make the tradeoff explicit: revise the workflow, change the architecture, or reconsider the migration.
What to check before deciding
- Record the trigger, rule, data, output, and business owner.
- Check plan and API constraints for the proposed solution.
- Test exception cases and interactions with other custom features.
- Document maintenance ownership and the fallback process.
