Shopify order routing / fulfillment order assigned to the wrong location — routing rules, inventory, Markets, apps.

Several products can look like “the order went to the wrong place.” They do not share a settings panel. This page is only when Shopify assigns a fulfillment order (FO) to a location you did not intend — wrong warehouse, wrong retail store, wrong 3PL node, or a split you never configured — after payment, while inventory and shipping still look “fine” at a glance. An order stuck On hold / cannot release is fulfillment hold stuck. POS stock that does not match online available is POS inventory not syncing. Pickup / BOPIS missing as a delivery option is local pickup not showing. An inventory transfer that will not receive at destination is transfer order not receiving. This page is only: Shopify order routing / fulfillment order assigned to wrong location (routing rules, inventory, Markets, apps).

Six ordinary reasons routing lands wrong: location priority / “ship from closest” picks a store with leftover qty; expected warehouse shows 0 available (committed / incoming / untracked); Markets or delivery profile shipping origin disagrees with your mental model; a fulfillment / 3PL / multi-location router app overrides Shopify order routing; you are testing a hold, POS sync, pickup UI, or transfer receive bug instead of routing; or you edited an old FO expecting re-route without placing a new order. Walk them in that order. You already pay for Shopify + locations. You do not need another “routing SaaS” to prove which location Shopify actually chose.

Open the problem order → Fulfillment orders → note Assigned location and any split FOs. Screenshot Settings → Shipping and delivery → Order routing (strategy + location order). In Products / Inventory, check available quantity at the location you expected vs the one Shopify chose. Note whether the SKU is stocked at multiple locations and whether “Continue selling when out of stock” is on.

Reproduce with a new test order (same SKU, same ship-to address / Market) after you change routing — reassigning an old FO does not always re-run routing. If the order is On hold and you cannot fulfill anywhere, leave this page and use fulfillment hold stuck. If POS and online qty diverge before any FO exists, open POS inventory not syncing.

Align order routing: put the intended warehouse above retail / overflow locations, or switch strategy if “closest location” keeps stealing from a nearby store that still has units. Restock or free committed inventory at the intended location; turn off continue-selling if it lets Shopify invent availability at a location you do not ship from.

Check Markets / delivery profiles so the shipping origin for that country matches the warehouse you stock. Pause a second fulfillment / 3PL / ShipBob / multi-location router app that rewrites assignment, then place a fresh order. If pickup never appears as an option at checkout while shipping FOs route fine, that is local pickup not showing. If stock is stuck on an inventory transfer between locations, use transfer order not receiving. Related multi-location inventory mismatch without FO mis-assignment: multi-location inventory wrong.

Checklist: (1) screenshot Assigned location on the bad FO, (2) screenshot Order routing strategy + location order, (3) confirm available qty at the intended location, (4) fix Markets / delivery profile shipping origin, (5) pause conflicting fulfillment / 3PL router apps, (6) place a new test order to the same address / Market, (7) confirm FO Assigned location matches intent (and splits only when you configured them), (8) if only hold, POS sync, pickup UI, or transfer receive remains, switch playbooks.

Prove it: new paid order → FO Assigned location is the warehouse you ranked; a second Market still routes as configured; retail locations with leftover qty no longer steal the FO unless you want that. If the FO never creates because the order is held, open fulfillment hold stuck.

Fulfillment hold you cannot release is fulfillment hold stuck. POS vs online inventory not syncing is POS inventory not syncing. Local pickup / BOPIS missing at checkout is local pickup not showing. Inventory transfer not receiving at destination is transfer order not receiving. None of those finish a routing bug where the FO already exists at the wrong Assigned location.

Finish prove wrong location → fix routing / stock / Markets / apps → new-order proof first. Only then open the related playbook that matches the remaining symptom.

Stay DIY if you can spend one afternoon on the list above: prove Assigned location on a live FO, fix order routing priority and stock at location, align Markets / delivery profiles, remove conflicting fulfillment apps, and stop treating hold / POS sync / pickup / transfer receive as the same bug. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: fulfillment hold stuck, POS inventory not syncing, local pickup not showing, transfer order not receiving, multi-location inventory wrong.

Pay for help when the work is not the routing dropdown — it is connecting the stack you already have so lead capture is not dying in DMs, cart / ops exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a 3PL retainer, not a conversion guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or uptime claim.

What it does not buy: more orders, automatic warehouse quotas, a Plus license, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.