Shopify is changing how merchant-owned shipping configuration is organized across Markets. For a store with international destinations, multiple locations, or custom shipping logic, autumn 2026 is the right time to turn the change into a concrete test plan.
The dates and API behavior in this guide come from Shopify’s published developer changelog. The rollout is staged, so the exact moment of change can vary by store. Treat the guide as preparation, not as a claim that every merchant is already on the new model.
What Shopify has confirmed
Shopify announced market-driven shipping in feature preview on July 1, 2026. The feature preview uses API version 2026-07. Shopify says merchant-owned shipping configuration moves from delivery profiles to Markets, and that shipping options are attached to a market. Rates can still depend on product and location conditions.
The same changelog says app-owned delivery profiles continue to be managed through the API. App rates can be used alongside Shopify’s configuration, and app delivery profiles can target all products. Shopify’s published rollout plan starts on October 1, 2026 and reaches all merchants by July 1, 2027.
That means the useful autumn question is not simply whether shipping works today. It is whether your configuration, custom app, and checkout tests can explain which system owns each shipping decision.
Build a shipping ownership matrix
Before changing settings or code, make one row for each meaningful shipping path. Include:
- market and destination countries or regions;
- products or product groups;
- fulfillment location or location group;
- shipping option and rate conditions;
- currency and customer-facing label;
- carrier or app dependency; and
- fallback behavior when no rate is returned.
Mark each row as merchant-owned configuration, app-owned delivery profile, app rate, or an intentional combination. This is a recommendation for implementation clarity. Shopify’s feature preview documentation is the source of truth for the platform behavior.
The matrix should also show mixed carts. A product that ships from one location may behave differently when combined with a product from another location. A market with a local currency may need different thresholds or customer-facing wording. If the team cannot predict the result from the matrix, it is too early to call the setup ready.
Audit custom apps and integrations
The most important code question is whether an app reads, creates, or updates merchant shipping through the delivery profile API. Shopify explicitly says apps that do this need to update for the market-driven shipping model. Search the app and integration code for delivery profile operations, then document the API version, the owner, and the expected response.
Do not assume that every delivery profile should be rewritten. Shopify distinguishes merchant-owned shipping configuration from app-owned delivery profiles. A custom app may have a legitimate reason to keep its own profile, while a store integration that mirrors merchant settings may need a different mapping.
For a custom app, add tests for empty responses, duplicate-looking options, unsupported markets, rate calculation failures, and retries. For an ERP or fulfillment integration, verify that the location data used in the shipping matrix matches the locations Shopify actually uses at checkout.
Test the customer journey before rollout
Use a development or preview environment where the feature is available, then record expected results for each case:
- a single-product cart in every active market;
- a mixed cart with products from different locations;
- a cart that crosses a free-shipping threshold;
- a destination with no configured rate;
- a product excluded from a shipping rule;
- an app-provided rate beside a merchant-owned option;
- a rate change after the customer changes market or address; and
- the final checkout delivery option and order data.
Test the same matrix after a theme change or app release. Shipping bugs often hide in the interaction between configuration, cart contents, location assignment, and the rate provider, so a screenshot of the settings page is not enough evidence.
A practical autumn 2026 action plan
Before October 1, inventory markets, locations, profiles, apps, and custom code. During the feature preview, compare the current and target configuration in a safe environment. As the rollout reaches the store, monitor missing rates, unexpected options, checkout errors, and orders routed to the wrong location. Keep a rollback or support procedure for the people who answer customer and warehouse questions.
If the store has no custom shipping code, the work may be a focused configuration and QA exercise. If a private app or integration depends on delivery profiles, schedule technical review before the store reaches the rollout window. Shopify’s staged timing means a merchant can use the time before July 1, 2027, but waiting for a customer-facing failure is a poor migration strategy.
Need help with Shopify shipping logic?
If market configuration is clear but the theme, custom app, rate workflow, or fulfillment integration needs engineering, MerchWeave can help with Shopify development, custom apps, and integrations. Contact us for a shipping audit and implementation plan.
Sources and update note
The dates and platform behavior above reflect Shopify’s changelog reviewed on August 8, 2026. The ownership matrix, testing cases, and action plan are practical recommendations and should be adapted to the store’s markets, locations, apps, and fulfillment model.