Shopify merchants should audit markets, shipping rates, fulfillment locations, shipping apps, split shipments, and test orders before opting into shipping options by market.
Shopify is moving merchant-owned shipping configuration from shipping profiles to shipping options by market. The change affects where your team manages shipping, how product and location conditions are organized, how some matching rates are combined, and which staff and apps can safely support the checkout path.[1][2] Treat it as an operations change with a customer-facing test plan—not as a settings rename.
The rollout is gradual. Existing stores keep their current shipping system until Shopify upgrades them, and Shopify says existing rates are migrated rather than recreated. Stores that rely on shipping apps may be upgraded later after those apps become compatible.[1] Merchant opt-in began October 1, 2026, and Shopify says all shops will be on the new system by July 1, 2027.[1][4]
Start with the decision that matches your store’s actual risk:
This is a decision framework, not a Shopify requirement. The right date is the date when the team can test the customer paths that matter and still make a controlled correction if a rate or app behaves unexpectedly.
Shipping options by market use three layers:
A child market inherits shipping from its parent unless you customize it. A customer who belongs to overlapping markets can see shipping options from those markets, so market structure is part of the checkout test—not just an international expansion setting.[2]
The new model also changes how product conditions are represented. Rates can apply to all products or to specific collections, and location conditions determine which fulfillment locations a rate ships from.[2] Shopify’s migration can create unpublished collections with a [Shipping] prefix from existing product groupings; those collections support the shipping setup and are not storefront merchandising collections.[1]
Before changing settings, document one row for each meaningful shipping path.
| Field | Merchant decision |
|---|---|
| Market | Which country, region, B2B market, or POS market is in scope? |
| Product condition | Does the rate apply to all products or a specific collection? |
| Ships-from condition | Which warehouse, store, or fulfillment location can provide the rate? |
| Customer-facing option | What will the buyer see: Standard, Express, Pickup, or another label? |
| Rate type | Is the price flat, order-value-based, weight-based, or carrier/app calculated? |
| Owner | Is the rule managed by the merchant, an app, a carrier, or an operations team? |
| Expected cart result | What should happen for a single item, a mixed cart, and a split shipment? |
| Evidence | Where is the current setting, app response, or test-order screenshot? |
Keep the map versioned. Save the current rate name, price, condition, destination, location, and app dependency before an upgrade so a reviewer can compare the migrated result with the intended one.
Open Settings > Shipping and delivery and note whether the store still uses shipping profiles or already shows shipping options by market. Shopify documents these as the two systems that exist during the rollout.[1] Export or screenshot the current profiles, location groups, shipping zones, rates, package assumptions, and app-provided rates.
Do not rely on memory for duplicate rate names. Under the new model, rates with the same shipping option name can be consolidated into one option. When multiple matching rates sit inside the same option, the highest matching rate is charged instead of adding those rates together.[1][2]
List every active market involved in checkout, including regional, B2B, and POS markets where they affect your operation. For each one, record whether shipping is inherited or customized. Test the parent and child market separately: an edit to a parent can affect its child markets, while an unrelated market should not inherit that change.[2]
For every custom shipping profile, identify the products that need special handling and the collection that should represent them after migration. Check the automatically created [Shipping] collections after an upgrade. Verify membership at the variant level when a rate should apply to only some variants, because Shopify’s shipping-options documentation allows product conditions at the product or variant level through collections.[2]
Shipping moves into Markets after an upgrade. Shopify says the Markets permission is not granted automatically and is not included in existing staff roles, so identify the people who will review rates and give them the needed access before peak support or fulfillment work begins.[1]
Create a list of every shipping-rate app, carrier integration, 3PL connector, ERP, OMS, and custom script that touches delivery or fulfillment data. For each dependency, record:
Shopify’s current help guidance says stores using shipping apps may be upgraded later after those apps become compatible.[1] That is not a reason to skip the audit: it is a reason to make the app dependency visible.
Use real products, real market rules, and a test payment method. Record the address, cart contents, expected shipments, displayed options, prices, transit details, and the final result.
| Test case | What to verify | Guardrail |
|---|---|---|
| One product, one market, one location | The expected option and rate appear for the destination. | No unexpected fallback, missing option, or incorrect label. |
| Mixed products in one shipping option | Matching rates follow the highest-rate rule rather than stacking within that option.[2] | Compare the displayed price with your documented shipping policy and margin rule. |
| Products that map to different shipping options | Prices for separate shipping options add together at checkout.[2] | Confirm the result is intentional and the customer can understand it. |
| Split shipment from two locations | The checkout communicates the number of shipments and calculates rates according to the applicable rate type.[1][2] | Check delivery promises, support copy, and fulfillment ownership for every shipment. |
| Parent and child markets | The child inherits the expected shipping or shows its deliberate customization.[2] | Test a country that belongs to more than one relevant market. |
| Weight-based or carrier/app-calculated rate | Product weights, package assumptions, carrier response, and destination produce a usable rate.[2][3] | No rate error caused by missing weight, missing package data, or an app response. |
| No active market or matching rate | Shopify shows the appropriate no-shipping state instead of a misleading option.[3] | Do not redirect the customer into a rate that the store cannot honor. |
A test order is not complete when the checkout button works. Confirm that the order creates the expected fulfillment records, sends the expected notifications, and gives the warehouse, store, 3PL, and support teams the same delivery story.
A fashion brand may have apparel in one warehouse and accessories in another. Test a single garment, a garment-plus-accessory cart, and a cart that can only be split between locations. The question is not whether every cart should ship in one package; it is whether the shipping price, number of shipments, and delivery language match the promise you are willing to support.
A beauty brand can use product collections to separate shipping logic for a focused range, but the collection is an operational condition rather than a merchandising shortcut. Verify the exact variants included, the market that receives the rate, and whether a bundle or replenishment cart triggers a different path. Keep any delivery or handling promise aligned with the rate and fulfillment team that actually owns the order.
A broader catalog may use parent markets for a group of regions while customizing rates for one country or B2B destination. Test inheritance before adding exceptions. If a carrier or app calculates rates, treat accurate weights, package data, location conditions, and the app’s compatibility confirmation as prerequisites—not as cleanup after a failed checkout.[2][3]
For each scenario, save:
This record turns a one-time migration check into a repeatable release check. It also gives support a precise answer when a buyer asks why a mixed cart has two delivery choices or two shipments.
Choose a primary operational measure before the change. Depending on the store, that may be:
Pair the primary measure with guardrails. A lower displayed shipping price can change contribution margin. A successful checkout can still create a split shipment, a support burden, or a delivery promise the team cannot keep. Report observational changes as observations unless the test design supports a causal conclusion.
If your team is reviewing event ownership at the same time, keep checkout measurement separate from shipping configuration and use the Shopify Meta Pixel setup guide as an adjacent implementation reference. Do not treat an analytics event or a shipping option click as proof that the migration caused a sale.
Use the evidence from the map and test record:
Do not choose “go” because Shopify migrates the settings for you. Migration reduces recreation work; it does not validate your market logic, app behavior, staff access, mixed-cart economics, or customer promise.
Before opting in or approving an automatic upgrade, confirm:
The useful deliverable is not a screenshot of the new Shopify admin. It is a versioned map showing which market, product, location, app, and rate produces each customer-facing shipping result. Build that map first, then choose whether early access or a later automatic upgrade gives your team the safer test window.
[1] https://help.shopify.com/en/manual/fulfillment/setup/shipping-options/whats-changing-with-shipping [2] https://help.shopify.com/en/manual/fulfillment/setup/shipping-options/understanding-shipping-options-by-market [3] https://help.shopify.com/en/manual/fulfillment/setup/shipping-options/setting-up-shipping-options [4] https://www.shopify.com/in/partners/blog/next-gen-fulfillment