Foundation · 2 min
What you need to know
How should tax settings be migrated?
Rebuild tax configuration from approved registrations, locations, product tax categories, customer exemptions and provider settings. Do not copy labels without confirming their legal and operational meaning.
How should tax calculations be validated?
Create controlled carts covering products, customers, locations, discounts, shipping and refunds, then compare expected and actual tax. Have the responsible tax owner review material differences.
How should shipping zones be migrated?
Map countries, regions, postal rules and exclusions into explicit destination zones. Test boundary addresses and confirm each address matches only the intended rules.
How should shipping rates be migrated?
Recreate rate rules with the correct price, weight, package, product, and zone conditions. Compare representative carts with the old store or an approved rate table.
How should carrier integrations be migrated?
Configure production credentials, origins, package data and enabled services through the carrier-supported integration. Test rating, label creation, tracking, voids, and provider failures.
How do I verify shipping calculations before launch?
Price a matrix of carts across products, quantities, packages, origins, destinations and services. Reconcile the displayed rate, selected service and carrier response before launch.
A quick store check
Build a small test matrix of products, customers, destinations and packages, then obtain tax and shipping owner approval for differences.
Foundation · 2 min
Frequently asked questions
Can tax and shipping labels simply be copied?
No. Rebuild the underlying rules and provider configuration, then validate their calculations.
Should every possible address be tested?
No, but cover representative rules, boundaries, and high-risk exceptions using a documented matrix.