Shopify Market-Driven Shipping: What Changes on October 1, 2026, What Breaks, and How to Prepare Before July 2027

By Lance Allison, Founder of Ruby Digital Agency | September 2026 | ~33 min read

On the morning of September 24, Shopify sent me an email with the subject line “Action needed: Test apps by Oct 1 for fulfillment updates.” It named two small apps I had built for client migrations and said they might need updating for something called market-driven shipping. I suspect a lot of merchants, developers and agencies received a version of that email this month, and I suspect most of them had the same first reaction I did: what exactly is changing, when, and is anything about to break?

The short version is that Shopify is rebuilding where shipping lives. Since 2020, rates have been set up in shipping profiles: groups of products, the locations they ship from, the zones they ship to, and the prices in each zone. Starting October 1, 2026, merchants can move to a model where shipping is configured inside Markets instead. By July 1, 2027, every store will be on it, with no way back. For most small stores the move will be automatic and almost invisible. For stores with more than one shipping profile, shipping apps, custom integrations, several warehouses or a migration in progress, it changes what customers pay at checkout, what your apps can see, and what your developers are allowed to write. I have spent the past week in Shopify’s announcements, developer documentation, help center and developer forums. This article is what I would tell a client who asked me to explain it, including the part nobody puts in the press release: the effect on your shipping revenue, which you can model with the calculator below.

A definition to anchor the rest. Shopify market-driven shipping is Shopify’s new way of configuring shipping, in which a merchant attaches shipping options (Standard, Express, Freight and so on) directly to each market they sell to, and uses product and location conditions on each rate, instead of maintaining separate shipping profiles. In the admin and the help center Shopify calls it shipping options by market; in the developer documentation it is market-driven shipping. They are the same thing.

In This Article

1. What Is Shopify Market-Driven Shipping?
2. The Dates That Matter, October 2026 to July 2027
3. What Changes for Merchants After the Upgrade
4. Rate Consolidation: The Change That Touches Your Revenue
5. Split Shipping and Ship and Pickup: The Two Changes Riding Along
6. What Breaks: Apps, Integrations and the Delivery Profile API
7. The Email We Received on September 24, and Why We Did Nothing
8. What It Means If You Are Migrating to Shopify Now
9. Should You Opt In Early? Our Recommendation by Store Type
10. A Quick Overview of Ruby Digital Agency
11. A Ten-Step Plan to Prepare Your Store
12. What Happens If You Do Nothing
13. Frequently Asked Questions
14. Final Thoughts

What Is Shopify Market-Driven Shipping?

To see why this matters, start with how Shopify shipping works today. Every store has a General shipping profile that covers all products by default. Merchants who need different rules for some products (heavy items, fragile glass, perishables, a range that only ships domestically) create custom shipping profiles and move those products into them. Inside each profile sit location groups (the warehouses or stores that ship those products), and inside each location group sit shipping zones (the countries and regions you deliver to), each with its own rates: flat, weight-based, price-based or calculated live by a carrier.

Markets, meanwhile, grew up alongside shipping as a separate feature. A market decides which countries or regions you sell to, which currency and language they see, which domain they land on, and increasingly which prices and catalogs apply. In practice a store had two maps of the world that had to agree with each other: the zones inside shipping profiles, and the regions inside Markets. When they disagreed, customers hit checkout errors that were hard to explain. I have seen a migrated store with perfect shipping zones refuse international addresses at checkout because those countries were not in an active market. The shipping was right; the map it depended on was missing.

Market-driven shipping collapses the two maps into one. According to Shopify’s partner announcement of July 7, 2026, merchants will manage where they sell and how they ship from the same place in the admin. The hierarchy flips. Instead of product groups at the top and zones underneath, the market is at the top. Inside each market you create shipping options, which are the choices a customer sees at checkout. Inside each shipping option you create one or more rates, and each rate carries conditions that decide which products it applies to (all products, or specific collections) and which fulfillment locations it ships from.

Three details of the new model are worth understanding before anything else, because most of the practical consequences flow from them:

• Inheritance. Shopify’s help center explains that a child market inherits its parent’s shipping options by default. Set up shipping once on a Europe market and the country markets underneath it pick it up. Customize one child and only that child and its own descendants change.
• Conditions replace profiles. The job custom profiles used to do (charge oversized goods more) is now done by a rate whose product condition points at a collection. There is no longer anything mutually exclusive about it: a Shopify staff member confirmed on the developer forum that the same product can now be targeted by more than one shipping option.
• New market types. Shipping can be customized for B2B customer locations and for POS markets as well as for ordinary regional markets, which is new for wholesale and retail-heavy brands.

It is also worth being precise about what this is not. It is not a new carrier, a new label service or a change to Shopify Shipping rates. It is a change to where rules live and how they combine. That sounds administrative, and for a single-profile store selling in one country it largely is. The interesting parts are the combination rules and the API change, which I will come to after the dates.

Concept	Shipping profiles (today)	Market-driven shipping
Top of the hierarchy	Shipping profile (product group)	Market (where you sell)
Where countries are defined	Shipping zones, separate from Markets	The market itself
How special products get special rates	Move them into a custom profile	A rate with a collection condition
How locations are handled	Location groups inside each profile	A “ships from” condition on each rate
Several rates match one cart	Rates from different profiles are added together	Highest rate within an option; options add
B2B and POS	Largely shared with online settings	Their own markets with their own shipping
Merchant-facing name	Shipping profiles	Shipping options by market

The Dates That Matter, October 2026 to July 2027

Market-driven shipping is one of three fulfillment changes Shopify is rolling out together, and the dates overlap. Shopify’s partner post and its enterprise post of August 24, 2026 give the schedule. Here it is in one place, with markers that update against today’s date:

Three things about this schedule are easy to miss.

First, October 1 is an opening, not a deadline, for existing stores. Nobody’s store flips on that day unless the merchant clicks the button. Shopify says existing stores will be upgraded gradually between October 2026 and July 2027, and the help center page on what is changing adds that stores using shipping apps that are not yet compatible will be upgraded later. If you do nothing, Shopify picks the moment. If you plan, you do.

Second, new stores are different. From October 1, a newly created store starts on market-driven shipping. That matters enormously if you are about to launch or migrate, and I will come back to it in the migration section, because it quietly changes how a new store’s shipping must be built.

Third, the rollout lands on top of peak season. Opt-in opens roughly seven weeks before Black Friday. Shopify itself frames October 1 as the date partners should be ready by, precisely so merchants are not surprised in BFCM. Being ready and choosing to change your checkout in November are two different decisions.

Change	Who it affects	Opt-in or preview	Default for everyone
Market-driven shipping (shipping options by market)	All stores	October 1, 2026	July 1, 2027
Split shipping in checkout	Stores that ship from several locations or sell preorders and subscriptions	Phased from August 2026	July 1, 2027 (toggle removed)
Ship and pickup in one order	Shopify Plus and Enterprise	Test Drive since June 17, 2026	July 1, 2027 for eligible stores
Carrier services not auto-added to General profile	Apps on API 2026-10 and later	API 2026-10	As older API versions are retired
Merchant delivery profile APIs deprecated	Apps and integrations	Effective August 1, 2026	Every store by July 1, 2027

What Changes for Merchants After the Upgrade

Shopify’s position, repeated across the help center, is that your existing rates are migrated for you and most merchants will not need to do anything. I think that is true for the settings themselves. What changes is how those settings behave and how you manage them afterwards. Here is what happens to a store when it is upgraded, based on the help center’s upgrade page and the developer documentation.

Your profiles are translated into markets and collections

Each shipping profile is converted into shipping options on your markets. Your shipping zones map to markets, and a zone that covered several countries can be split into per-country markets beneath a parent. Location groups become location conditions on individual rates. Most importantly for day-to-day admin work, the product groupings behind your custom profiles become collections. Shopify names them with a [Shipping] prefix (a profile called Fragile becomes a collection called “[Shipping] Fragile”), keeps them unpublished so customers never see them, and points the right rates at them. Shopify staff have also said they create a general collection that includes every product except those in the other shipping collections, which is how the old General profile survives.

That has a consequence nobody on your merchandising team will expect. Those [Shipping] collections are now load-bearing. A tidy-minded colleague who deletes an odd-looking unpublished collection, or who edits its conditions to use it on the storefront, changes what your customers pay for shipping. Tell your team before the upgrade, not after.

Rates that share a name are merged into one shipping option

Where rates in different profiles carried the same name (Standard in the General profile and Standard in an Oversized profile, for instance), the upgrade consolidates them into a single shipping option with several rates. That is the mechanism behind the revenue change in the next section, so keep it in mind.

Split shipping is switched on, whether you wanted it or not

Split shipping shows a customer, at checkout, that their order will arrive in more than one shipment when products ship from different places or at different times (a preorder alongside in-stock items, say). It has been optional. According to Shopify’s split shipping help page, once a store is upgraded the on/off setting no longer applies, and the upgrade page says it is activated even on stores that had deactivated it. By July 1, 2027 the toggle disappears for everyone. If you run a warehouse or a 3PL that consolidates orders, or you had turned split shipping off because it confused customers, that is a genuine operational change.

Staff need the Markets permission to manage shipping

Because shipping now lives in Markets, a staff account that could edit shipping before may not be able to afterwards. Shopify’s upgrade page tells merchants to check that staff who manage shipping have the Markets permission, since it is not granted automatically. It is a two-minute fix that saves a confused support ticket on the first busy morning.

There is a way back, for a while, at a price

After an upgrade, a merchant can switch back to shipping profiles during an opt-out window from Settings, then Shipping and delivery. Switching back restores the previous setup and permanently removes any shipping changes made after the upgrade, along with the collections and markets the upgrade created. Shopify has not published how long the window lasts, and it closes for good on July 1, 2027. My advice is to treat the window as a safety net for the first week, not as a trial period during which you rebuild anything.

What you have today	What it becomes after the upgrade	What to check
General shipping profile	Shipping options on each market, targeting a general collection	Every market still offers a rate for every product
Custom shipping profiles	Unpublished collections named [Shipping] …	Nobody deletes, renames or reuses them
Shipping zones	Markets (multi-country zones may split per country)	Currency, language and domain settings per new market
Location groups	“Ships from” conditions on rates	Rates still fire for each warehouse and store
Rates with the same name in several profiles	One shipping option with several rates	What mixed carts now cost (next section)
Split shipping switched off	Split shipping switched on	Warehouse, 3PL and customer service briefing
Staff with shipping access	Shipping inside Markets	Grant the Markets permission

Rate Consolidation: The Change That Touches Your Revenue

Every announcement describes this change from the customer’s side, and from that side it is good news. Shopify’s enterprise post gives the example: a store charges $5 to ship regular products and $10 for oversized ones, and a customer buys one of each. Under market-driven shipping, the customer pays the highest applicable rate, $10, rather than a sum. Shopify calls this rate consolidation, and its goal is plainly to stop customers being overcharged when one order happens to touch several product groups.

Now read the same example from the merchant’s side. Under shipping profiles, Shopify’s own help page on combined rates describes the opposite behavior: a $3 rate from one profile and a $5 rate from another are combined, and the customer sees $8. Rates that share a name are added together. That stacking is exactly how many stores recover the cost of a surcharge. The oversized item really does go in a separate, expensive parcel, and the stacked rate paid for it.

After the upgrade, within a single shipping option, the help center says the highest matching rate is charged instead of the rates being added together. Across different shipping options, prices still add up. And the rule depends on the rate type: flat and order-value rates consolidate to the highest, while weight-based and carrier-calculated rates continue to be summed per shipment. So the question for your store is simple, and it is arithmetic: how many of your orders mix products from two rate groups, and what is the smaller rate worth?

Run your own numbers before you decide anything, because the result varies enormously by catalog. A fashion store with one General profile will see no change at all. A furniture or home-goods store with an oversized profile, or a food brand with a chilled profile, can see a five-figure annual difference. None of it is lost in a legal or technical sense. Your customers simply pay less for shipping, which is the point of the change and may well lift conversion. But if the carrier still bills you for two parcels, the difference comes out of your margin, and you should choose that rather than discover it.

If the calculator shows a number you care about, there are three honest responses:

• Reprice the higher rate. If oversized items nearly always ship with something else, set the oversized rate to cover both parcels. Customers buying only the oversized item pay a little more; mixed carts pay what they used to.
• Give the surcharge its own shipping option. Because prices from different shipping options still add together, a surcharge that genuinely must stack can live in its own option targeting its own collection. Test this in a development store with the feature preview before relying on it; the forum threads show developers still working through how carrier and flat rates combine.
• Keep the lower price on purpose. Lower shipping at checkout is one of the few levers that reliably moves conversion. If the margin can carry it, market it (“one shipping charge, however much you buy”) rather than absorbing it silently.

Rate type	Two groups in one cart, today	Same cart after the upgrade	Revenue effect
Flat rate	Added together ($8 + $25 = $33)	Highest rate ($25)	Lower shipping collected
Order-value (price-based) rate	Added together	Highest matching rate	Lower shipping collected
Weight-based rate	Added together	Calculated per shipment and summed	Little or none
Carrier-calculated rate	Added together	Calculated per shipment and summed	Little or none
Rates in different shipping options	Added together	Added together	None

One more commercial point sits beside this. Live carrier-calculated rates remain plan-gated on Shopify: on most plans third-party carrier rates need Advanced or Plus, or Grow on annual billing. If the upgrade tempts you to swap flat rates for live carrier quotes to protect margin, check the plan first, and remember that live international quotes are often far higher than the flat tables stores have been charging.

Split Shipping and Ship and Pickup: The Two Changes Riding Along

Market-driven shipping gets the headlines, but Shopify’s July announcement bundled it with two other checkout changes, and all three become permanent on the same day. For a single-location store they barely register. For brands with several warehouses, retail stores or a 3PL, they are the bigger operational story.

Split shipping becomes the default

Split shipping means checkout shows the customer how many shipments their order will actually arrive in, based on where each item ships from and when it is available, instead of pretending everything arrives together. Shopify’s argument is honesty: separate shipping profiles used to make checkout display extra shipments the merchant never intended, while genuinely separate parcels were sometimes hidden. From August 2026 Shopify has been switching split shipping on in phases, starting with the stores it considers lowest risk, and from July 1, 2027 the setting disappears.

The practical effect depends on how your operation is wired. If a single warehouse ships everything, nothing changes. If you sell preorders or subscriptions alongside in-stock products, customers will see those arriving separately, which is accurate but may prompt questions. If you ship from two locations, checkout may quote per shipment, and your 3PL or order management system has to work at the level of Shopify’s fulfillment orders rather than whole orders. Shopify is blunt about that last point in its partner post: integrations that still work at order level are the ones most at risk. Ask your 3PL directly whether they process fulfillment orders, and test an order that ships from two places.

There is some pushback from developers here. On Shopify’s developer forum, several people argued that merchants who deliberately consolidate shipments should be able to keep split shipping off, and a member of Shopify’s fulfillment team replied in August that it will be enabled by July 2027 with no option to disable it, while inviting merchants with concrete cases to write to the fulfillment team. If your business depends on consolidating orders, now is the time to send that email, not next June.

Ship and pickup in one order, for Plus

The third change lets a customer on a Shopify Plus or Enterprise store choose shipping for some items and in-store pickup for others, in the same checkout. It has been available to test since June through Test Drive, it gains cart support from October 12, and it starts switching on automatically for eligible stores from April 2027. Shopify says no new APIs are involved, but any app that assumes an order has one delivery method, one shipping address or one shipping line will be wrong for these orders. Point-of-sale, click-and-collect and store-fulfillment apps are the ones to check.

Change	What the customer sees	What to test
Market-driven shipping	The same options, with mixed carts often cheaper	Every market, bracket and mixed cart
Split shipping	How many shipments the order will arrive in	Two-location orders, preorders, 3PL handling
Ship and pickup (Plus)	Ship some items, collect others, one checkout	POS, click-and-collect and OMS apps

What Breaks: Apps, Integrations and the Delivery Profile API

This is the part of the change that generated the emails. Under shipping profiles, any app with the right permissions could read and write a store’s shipping configuration through the Admin API’s delivery profile queries and mutations. Shipping calculators, rate-shopping apps, ERPs, order management systems, marketplace connectors and migration tools all use them. On July 1, 2026, Shopify deprecated those APIs for merchant-owned profiles, effective August 1: the deliveryProfile and deliveryProfiles queries, their counts and location-group reads, and the deliveryProfileCreate, deliveryProfileUpdate and deliveryProfileRemove mutations.

What makes this dangerous rather than merely inconvenient is how the old calls behave on an upgraded store. They do not fail loudly. Shopify’s changelog says reads may return a stale snapshot of the old configuration, and that “writes may succeed without errors but will not update the merchant’s live shipping settings.” An app can report success, a developer can see a clean response, and nothing at checkout changes. That is the worst kind of failure to debug, because every log says it worked.

The replacement is the Markets API. From Admin API version 2026-07, a market has a delivery field that holds its shipping configuration, and shipping options and rates are created and changed through marketCreate and marketUpdate, which need the read_markets and write_markets permissions. A store’s features now report whether it is on market-driven shipping, so an integration can check first and use the right model. The full detail is in Shopify’s upgrade guide for apps.

What is not affected

Apps that create and manage their own delivery profiles (app-owned profiles, used by many shipping-rate apps) keep using the delivery profile API as before. In the new model their rates are projected into the merchant’s markets automatically, and merchants cannot edit them, which avoids two parties fighting over the same rate. App-owned profiles also gain the ability to cover every product in the store, which Shopify added in part so rate apps do not need to touch merchant settings at all.

The carrier service change riding alongside

A separate change catches some of the same apps. Shopify announced on June 26, 2026 that from API version 2026-10, creating a carrier service (the hook that lets an app return live rates) only registers it. Shopify no longer adds it to the General profile automatically, so a merchant or the app must attach it to shipping explicitly, or checkout will quietly show no rates from it. Older API versions keep the old behavior until they are retired.

What merchants will see

From October 1, apps that Shopify has not marked compatible show a warning when a merchant installs them. Merchants who opt in while an incompatible app is installed may see it misbehave. Shopify also says it holds back the automatic upgrade for stores whose shipping apps are not yet compatible, which is sensible, and is one reason the rollout runs until July 2027.

If you use…	Likely impact	What to ask for
A shipping-rate app that manages its own profile	Low; app-owned profiles keep working	Confirmation it is marked compatible
A rate app or carrier service that reads or edits your General profile	Must be updated	Written compatibility date before you opt in
An ERP, OMS or 3PL that syncs shipping settings	Must be updated; also test split shipping	A test in a feature-preview store
A marketplace or feed app that reads shipping to publish rates	Reads may go stale	How it reads shipping on upgraded stores
A custom app or script your agency wrote	Depends on what it does (next section)	A code review of every delivery profile call
No apps touching shipping	None	Nothing

The developer forum has been busy, and it is worth knowing the tone. Developers have asked how to reproduce rates that must add up under the new rules, reported cases where carrier rates were still being summed while native rates were not, and pointed out that a checkout extension cannot yet easily tell which market a buyer resolved to. In the thread I read, a Shopify staff member acknowledged that last gap on September 22 and said they would raise it with the team. None of that is alarming for an API three months old, but it is why I would not let a critical integration be the first thing you test in November.

The Email We Received on September 24, and Why We Did Nothing

Back to that email, because it is a useful case study in reading these notices calmly. Shopify’s message named two apps. Neither is a product anyone can install. Each is a small custom app that my agency created for a single client store during a BigCommerce to Shopify migration, used purely to give our migration tooling secure access to that one store’s Admin API. On both projects, part of the work was copying the source store’s shipping zones and rate tables into Shopify so the new checkout charged exactly what the old one had. That meant calling deliveryProfileUpdate on the store’s General profile a handful of times, weeks ago.

Shopify’s scanning is automatic. It saw two apps that had written to merchant delivery profiles and told the developer they may need updating. The email said as much: it asked us to test before October 1, pointed to the upgrade guide, and offered a form for developers who believe their apps are already compatible. It did not say anything was broken, and nothing is.

I decided to leave both apps exactly as they are, and not to submit the compatibility form. The reasoning is worth spelling out, because it applies to a lot of custom apps:

• Nothing in them runs on its own. They hold credentials. Code runs only when we run it, by hand, during a project. There is no scheduled job, webhook or storefront feature that could fail at a customer’s checkout.
• What they created is now ordinary store data. The zones and rates we built are the merchants’ own shipping settings. When those stores are upgraded, Shopify migrates them like any other store’s settings.
• Deleting them costs more than it saves. Removing a custom app revokes its access token, and one of the two projects is still active. Rebuilding access later is a nuisance with no upside.
• Claiming compatibility would be untrue. Those scripts use the old API. The honest position is that they are retired, not that they are compatible.

What did change is our playbook. Before any shipping script runs on a client store now, we check which model the store is on and read its live configuration first, and new builds are written for the market model. That is the real lesson of the notice. Many merchants have a custom app somewhere in their history, often built by a previous agency, sometimes long forgotten. If you receive one of these emails, the question to ask is not whether the app was flagged, but whether anything calls it automatically. If nothing does, there is usually nothing to fix. If something does, that integration needs a developer before your store is upgraded.

What It Means If You Are Migrating to Shopify Now

This is the section I most wanted to write, because it is where market-driven shipping will cause real damage that nobody notices until launch day. Shopify’s announcement says new stores are opted in to market-driven shipping automatically from October 1, 2026. A migration almost always starts with a new Shopify store. So any replatforming project that creates its Shopify store from October onwards is building on the new model from day one.

Now combine that with the silent-write behavior above. Most migration tooling that copies shipping, whether a commercial migration app, an agency’s scripts or a developer’s one-off import, was written against delivery profiles, because that was the only model there was. Pointed at a new store, a script that rebuilds zones with the old mutations may report success and create nothing a customer can use. The first sign would be a launch-day checkout showing no shipping options for some addresses, which is one of the most expensive bugs a new store can have.

Here is how we are handling it on migrations from BigCommerce, WooCommerce, Magento and the other platforms we move stores from:

• Check the model first. Every project now records whether the target store is on market-driven shipping before any shipping work begins, and old delivery-profile scripts are not run against a store on the new model.
• Map source zones to markets, not profiles. BigCommerce shipping zones and WooCommerce zones translate far more naturally into markets than into profiles anyway. A BigCommerce store with a US zone, a Canada zone and a Rest of World zone becomes three markets, each with its own shipping options.
• Translate surcharges deliberately. Source platforms often stack per-product shipping costs on top of a zone rate. Under rate consolidation that stacking does not happen automatically inside one shipping option, so we decide with the client, before launch, whether to reprice, separate or absorb it, using the same arithmetic as the calculator above.
• Verify with real rate quotes. We check rates by asking Shopify to price real carts for real addresses in every market and bracket, not by reading configuration back. Configuration can look right and quote nothing.
• Record it in the migration report. Every migration we run ships with a written reconciliation. Shipping now gets its own line: which model, which markets, which options, which test carts, which results.

If you are mid-migration with another provider, ask them one question this week: is our new Shopify store on market-driven shipping, and has your shipping import been tested against it? A confident, specific answer is a good sign. A pause is worth following up. For brands still choosing a platform, none of this is a reason to delay a move to Shopify. It is a reason to make sure whoever moves you knows it has happened. Our BigCommerce to Shopify and WooCommerce to Shopify migration guides cover the rest of what moves, and what does not.

Migration step	Old approach (shipping profiles)	Approach from October 2026
Target store	Profiles and zones by default	New stores start on market-driven shipping
Copy zones and rates	deliveryProfileUpdate into the General profile	Shipping options on markets via the Markets API
Special product rates	A custom profile per product group	A collection plus a rate condition
Countries you ship to	Zones, plus a matching market	The market is the zone
Verification	Read the profile back	Price real carts per market and bracket

Should You Opt In Early? Our Recommendation by Store Type

Shopify would like merchants to opt in, and there are real benefits: a simpler model, one map of the world, per-market control for B2B and POS, and checkout prices that do not punish customers for buying across product groups. Some commentators have argued that nobody should touch it before the new year. I think the right answer depends on the store, so here is the advice we are giving clients, followed by a checker you can run against your own setup.

Your store	Our recommendation	Why
New store, or migrating to Shopify now	You are on it already; build natively	New stores start on market-driven shipping from October 1
One General profile, flat rates, one or two markets	Upgrade in any quiet week, or let Shopify do it	Little changes; the automatic migration covers you
Several profiles with surcharges (oversized, fragile, chilled)	Model the revenue first; opt in January to March 2027	Rate consolidation changes what mixed carts pay
Shipping-rate apps or carrier-calculated rates	Wait for written compatibility from each vendor	Incompatible apps misbehave after an opt-in
ERP, OMS, 3PL or custom integrations writing shipping	Treat it as a project with a test store	Old API writes can succeed silently and change nothing
Shopify Plus, several locations, B2B or POS	Plan a staged upgrade alongside split shipping and ship and pickup	Three changes land together by July 2027
You switched split shipping off on purpose	Brief operations and customer service first	The upgrade switches it back on

To make the table concrete, here are three composite stores of the kind we work with, and what I would tell each.

A single-market apparel store

One warehouse, one General profile, a flat $6 rate with free shipping over $75, selling in the United States. For this store the upgrade is a formality. Its rates move into a United States market, the free shipping threshold carries over, and no cart combines two rate groups. I would still capture the setup first and place two test orders afterwards, one under the threshold and one over. Then I would stop thinking about it.

A home-goods store with an oversized profile

Two profiles: everyday items at $9 and a furniture profile at $49 that ships by freight, with roughly one order in ten mixing the two. Today a mixed cart pays $58; after the upgrade, if the rates share a name, it pays $49. That is the store the calculator was built for. I would decide the pricing before the upgrade (most likely raising the freight rate slightly or giving freight its own shipping option), check whether its rate app is compatible, and opt in during February, after the holiday returns have settled.

A Plus brand with stores, a 3PL and wholesale

Three retail locations, a 3PL for online orders, B2B customers on their own price lists, and an ERP that syncs shipping settings nightly. This store is exposed to everything at once: market-driven shipping, split shipping, ship and pickup and the API change. It needs a proper project: a feature-preview development store, a developer to move the ERP sync onto the Markets API, the 3PL confirmed on fulfillment orders, B2B shipping rebuilt on its own markets, and an upgrade date agreed with operations in the first quarter.

A word on timing, because it is the question I am asked most. Peak season is the worst time to change how checkout calculates shipping. Customer service is busiest, promotions are running, and a change that looked fine on a quiet Tuesday meets real carts at scale. Unless your store is simple, I would use October and November to prepare and the first quarter of 2027 to move. That leaves three months of margin before Shopify moves you, which is enough to deal with a slow app vendor or a surprise in testing.

A Quick Overview of Ruby Digital Agency (and Why We Care)

For readers meeting us for the first time: Ruby Digital Agency is a Shopify Plus Partner that does one thing on purpose. We move brands onto Shopify and Shopify Plus and make the move pay for itself. Most of our clients arrive from BigCommerce, WooCommerce, Magento and Adobe Commerce, OpenCart, Shift4Shop, PrestaShop or a custom build, usually because their platform has become expensive to run, hard to change or both. We are a boutique team: the specialists who plan a project are the people who deliver it, and every migration is run on our own AI-driven migration technology, with every record checked by a person against the source store before go-live.

Service	Who it is for	Typical timeline
Standard Shopify Migration	Mid-market brands, $2M–$20M/yr	8–12 weeks
Shopify Plus Replatforming	Enterprise brands, $20M+/yr, from Magento, Adobe Commerce or custom builds	3–6 months
Multi-Store & Subscription Integration	B2B wholesale, subscriptions, multi-brand architectures	Scoped per project
Ecommerce Website Audits	Any platform: Shopify, WooCommerce, BigCommerce, Magento, custom	Fixed-scope engagement
RDAI SEO and AEO	Brands that need to be found in Google and cited by AI assistants	Ongoing
Shopify POS Implementation	Retailers uniting stores and online	Scoped per project

The economics are why brands call us. Across our migrations, clients recover the investment in under 18 months, see conversion rates about 15% higher on average, and cut total cost of ownership by around 29%; infrastructure costs alone fall by as much as 80% when a self-hosted stack goes away.

Shipping is one of the least glamorous parts of a migration and one of the most consequential. It is where a new store most often charges the wrong amount on launch day, and where a small mistake is paid for on every order. We rebuild source shipping tables line by line, verify them against live quotes, and document the result, which is why a change to how Shopify stores and combines rates goes straight into our playbook. It is also why we offer existing Shopify merchants a shipping readiness review as part of our audit work: we map your profiles, apps and integrations against the new model, run the rate consolidation numbers on your real orders, and hand you a dated plan.

A Ten-Step Plan to Prepare Your Store

This is the checklist we are working through with clients. Most stores can do the first five in an afternoon.

1. Capture your current setup. Screenshot or export every shipping profile, location group, zone and rate, including rate names and conditions. Switching back during the opt-out window restores the old setup, but it discards later changes, and you will want a baseline to compare against either way.
2. List your product groups and why each exists. For every custom profile, write down the business reason (oversized, fragile, cold chain, domestic only). After the upgrade these become [Shipping] collections, and you need to know what each one is protecting.
3. Run the rate consolidation numbers. For each extra profile, use the calculator in this article with your real rates and the share of orders that mix products from both groups. Decide now whether to reprice, separate the surcharge into its own option, or absorb the difference.
4. Inventory every app and integration that touches shipping. Rate apps, carrier services, ERP and OMS connectors, 3PLs, marketplace and feed apps, and any custom app a previous agency built. Ask each vendor, in writing, whether it is compatible with market-driven shipping and when.
5. Fix staff permissions. Give the Markets permission to everyone who manages shipping, so the first busy day after the upgrade does not start with a locked screen.
6. Brief operations on split shipping. If you ship from several locations or had split shipping switched off, tell the warehouse, the 3PL and customer service what customers will see at checkout, and update your shipping FAQ.
7. Test in a development store. Shopify’s feature preview runs on development stores. Recreate a representative slice of your shipping, install the same apps, and place test orders across markets, rate brackets and mixed carts.
8. Choose your window. Pick a quiet week between January and March 2027, outside promotions, with a developer on call. Avoid opting in between Black Friday and the end of the holiday returns period.
9. Verify after the upgrade. Place or simulate orders to every market, every rate bracket and every mixed combination, including free shipping thresholds, local pickup and local delivery. Confirm that the [Shipping] collections are unpublished and untouched.
10. Decide inside the opt-out window, and diary July 1, 2027. If something is seriously wrong, switch back early and fix it before you try again. Either way, put July 1, 2027 in the calendar, because after that date there is no switching back.

What Happens If You Do Nothing

For a simple store, genuinely not much. Shopify will upgrade you at some point before July 1, 2027, migrate your rates, and your customers will carry on checking out. That is the honest answer, and it is why I would not frighten a single-profile store into a project it does not need.

For everyone else, doing nothing means letting Shopify choose the moment, which could be a week you are running a promotion. It means discovering the rate consolidation effect in your month-end numbers rather than in a spreadsheet, and explaining to your finance team why shipping revenue fell while carrier invoices did not. It means an ERP or custom integration that keeps reporting success while writing settings nobody reads, which is the kind of fault that can run for weeks. It means split shipping reappearing at checkout, followed by customer service tickets asking why an order is arriving in two boxes. And it means finding out that a staff member cannot open shipping settings on the morning you most need them.

None of those is a disaster on its own. Together, landing unannounced, they are the kind of week that makes merchants feel the platform changed under them. The difference between that week and a boring one is about a day of preparation.

Frequently Asked Questions

Final Thoughts

Market-driven shipping is a good change. It fixes a long-standing oddity of Shopify, two maps of the world that had to agree, and it gives wholesale and retail brands controls they have asked for for years. For most small stores it will arrive quietly and cost nothing. But it is not only a settings migration. It changes how checkout combines rates, which moves money, and it retires the API that a whole generation of shipping apps, integrations and migration tools was built on, in a way that fails silently rather than loudly.

So my advice is the same as it would be for any platform change with a hard date: understand it now, prepare in the quiet months, and move on your own schedule. Capture your setup, run the numbers, ask your vendors, test in a development store, and pick a week in the first quarter of 2027 when nothing else is happening. If you receive one of Shopify’s notices about an app, ask whether anything calls that app automatically before you panic. And if you are migrating to Shopify this autumn, make sure the people moving you know the target has changed.

The stores that come through this well will not be the ones that opted in first. They will be the ones that knew, before the upgrade, exactly what their checkout was going to charge.

Related Reading

• Shopify Scripts to Functions Migration
• Shopify Scripts Are Retiring: Here’s Your Plan
• BigCommerce to Shopify Migration Guide
• WooCommerce to Shopify Migration Guide
• Weebly to Shopify Migration Case Study: SoSlanty
• When Should You Upgrade from Shopify Advanced to Shopify Plus? 2026 Guide
• Ecommerce Website Audits
• More Shopify Guides on Our Blog

Lance Allison
Founder & CEO, Ruby Digital Agency

Lance Allison is a Shopify Plus Partner and eCommerce migration specialist based in Salt Lake City, Utah. He has helped hundreds of merchants move to Shopify and Shopify Plus, and specializes in complex, data-heavy platform migrations, including the shipping tables that decide what every order costs.