Playbook · Order Routing metafield missing
Shopify Order Routing metafield missing? Prove owners, locations, and the active version.
Written for a Shopify owner whose Order Routing / Function input omits a metafield the location-assignment rule expects. Start with the Order Routing owner, exact namespace.key, location candidates, and one active Function version. This is distinct from Order Routing wrong location (field present but wrong warehouse wins) and from Fulfillment Order metafield missing (fulfillment-order Custom data absent).
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
01
An API-missing Order Routing field is not automatically a blank Admin value or a wrong-location bug.
Use this page when Order Routing / Function input does not include the metafield node at all—absent from the payload—while locations otherwise load. If Admin Custom data shows the definition but the saved value is empty on a related owner, diagnose value first. If the field is present in the input but the wrong warehouse is chosen, use wrong location first.
Do not add a second definition or rewrite routing priority yet. Capture order, SKU, location IDs, market or company context, owner ID, namespace.key, and the exact API / input shape where the field should appear.
02
Prove the Order Routing owner and exact namespace.key.
Open Settings → Custom data and confirm whether the definition is owned by Shop, Location, Product, Variant, Inventory Item, Company, or another resource the Function documents. Copy the exact namespace.key, type, validations, and access. Save one unmistakable, reversible test value on that owner.
A shop key will not appear because the input query asks for a location or inventory-item key. Cart or checkout metafields will not appear in Order Routing input unless the query explicitly selects them.
03
Check location candidates before blaming one metafield.
Record which locations qualify for one test order: inventory levels, shipping zones, pickup, markets, B2B company context, and any app-managed warehouses. Compare location IDs with the routing input query and confirm each expected location is returned.
A missing field on a location that never entered the routing candidates is a candidate-selection issue. Keep this separate from a valid location set where the owner simply lacks the metafield the API expects.
04
Trace access, scopes, and the active Function version.
Compare the deployed input query with the definition and confirm the app has the intended access. Verify the active Function version, generated schema, and selected Order Routing configuration. A draft query, stale schema, inactive version, or wrong owner can omit the field from the API while Admin still shows a value.
Inspect field presence in the input separately from assigned-location results. Do not conflate Order Routing API misses with Fulfillment Constraint Rules, Delivery Customization, or inventory transfers.
05
Retest one order path and preserve a small proof packet.
Use one known-eligible SKU, one short synthetic value, and the locations you intend to compare. Record owner ID, namespace.key, type, Admin value, input-field presence, location candidates, active version, and final assigned location. Repeat only after the first trace is captured.
Classify the miss as owner, definition/value, access, location eligibility, query, inactive version, or routing logic. Keep customer data, tokens, and passwords out of screenshots and logs.
06
When to stay DIY vs pay $997.
Stay DIY when one owner, value, location, access, query, or active-version check explains the missing API field. Keep the proof packet so later routing-app changes are reversible.
Pay for the Latch AI Ops install when several Shopify surfaces, apps, markets, and ops alerts need to be wired and documented on one live store. Nico connects the agreed workflow in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.