Audit Shopify market and location mappings before trusting the January stock fix

The January 20, 2026 Shopify change fixed one specific problem, not every availability problem. Shopify said checkout for market-specific inventory now considers only locations that can fulfill the buyer's market instead of being blocked by negative or zero stock at other locations. That matters for makers running stock across a warehouse, studio, and retail or pop-up locations. But the fix only helps when the buyer's country is actually sellable through the rest of the setup. If a country is not in an active market, or if that country has no shipping zone with live rates, positive stock in admin still does not create a valid checkout path. The narrow operating point is simple: check the route to sell first, then check the stock that can serve that route.

Start with one real buyer destination and trace it all the way through. Open the target country inside markets and confirm the market is active. Then check shipping configuration and make sure the same country or region sits inside a shipping zone that has available rates. Stock alone is not enough. A product can look fine in admin and still fail at checkout because the market and shipping setup are out of sync. This is why the fastest audit starts with a country, not with a SKU. If Canada is active in markets but no rate exists for the relevant zone, the January fix cannot help. If the United States has rates but the market is inactive, the same problem appears from the opposite direction. Do not let the team spend an hour arguing about inventory math when the real block is that no sellable destination path exists.

After that, inspect which locations are allowed to fulfill online orders. Shopify's help documents say that preventing a location from fulfilling online orders removes that location's inventory from a product's online quantity. That means retail-only, storage, seasonal pop-up, or app-managed locations should not stay marked as online-fulfilling if their stock is not meant to support web orders. This is one of the easiest ways to misread admin quantities. A maker sees units spread across several locations and assumes checkout will use the right one. In practice, the wrong location may still be influencing what the team thinks is available, or a location that should count may have been left out. Review each location with a blunt question: should this inventory ever be used to ship an online order to the target market? If the answer is no, remove it from online fulfillment instead of leaving the decision to memory.

Then review shipping profiles, because a product or variant can belong to only one shipping profile at a time. Within that profile, any location that can fulfill online orders becomes a possible fulfillment location for those products unless the merchant changes the location groups. This is where many false sold-out investigations get sloppy. The team checks the product, sees stock at the warehouse, and stops. But the product may be assigned to a profile whose active location group does not include that warehouse for the target zone. Or the new warehouse may exist globally but still be missing from the profile configuration that actually governs the SKU. The audit should therefore move product by product for the affected items: identify the profile, inspect the location groups inside that profile, and confirm the destination country appears only where the intended ship-from location can serve it. If that grouping is wrong, the January inventory change still will not create a checkout that works.

The common failure mode is seeing positive inventory in admin and treating that as proof that checkout should pass. A candle variant shows eight units total. Three are in a studio that should not ship online, five are in a warehouse that can ship online, and the buyer is in a country with an inactive market. The merchandiser blames inventory because the product looks in stock, but the real failure is market activation. A second mistake is leaving a pop-up or app-managed location able to fulfill online orders after the event or integration changed. A third mistake is adding a new warehouse and assuming existing profiles picked it up in the right groups. A fourth mistake is testing only from the admin side instead of trying a destination-specific storefront checkout. The practical test is not whether the product page looks healthy. The practical test is whether one buyer country, one SKU, and one valid ship-from path line up at the same time.

There are also limits to what the current sources establish. They document the January 2026 behavior change, but they do not prove that every false sold-out scenario was fixed. They do not identify your merchant's exact root cause, and they do not rule out catalog restrictions, app behavior, or other checkout exclusions outside this inventory-and-location scope. Older stores can add another wrinkle because stores created before April 2024 may still have legacy display behavior that makes products appear available even when checkout will reject unfulfillable orders. Treat that as a separate verification point, not as proof that the stock logic is wrong. The safest operating posture is to keep the audit narrow. Verify one destination, one affected SKU set, one shipping profile, and one group of online-fulfilling locations before expanding the fix to the rest of the catalog.

Formul can support the discipline after this audit by helping teams track inventory by location, review ledger-backed stock movements, inspect transfers between locations, and troubleshoot discrepancies through item-level and batch-level history. That is useful when the same SKU moves between storage, production, and sellable locations and the team needs a clearer record of what should actually count as available before updating commerce settings.