Playbook · Fulfillment Constraint Rule metafield blank
Shopify Fulfillment Constraint Rule metafield blank? Prove the owner, rule payload, and Admin value.
Written for a Shopify DTC owner whose Fulfillment Constraint Rule / Function input returns a metafield as blank, null, or empty even when Admin Custom data may show a value. Start with owner, namespace.key, the raw rule payload, and one active Function version—not with a second location app. This is distinct from Fulfillment Constraint metafield blank (Admin Custom data empty on the constraint owner) and from Fulfillment Constraint Rule blocking (value present but every location is blocked).
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
01
A blank Constraint Rule field is not the same bug as Admin-missing or a rule that blocks every location.
Use this page when Fulfillment Constraint Rule / Function input returns the metafield node as blank, null, empty string, or empty list while the rule otherwise runs. If Admin Custom data has no definition or no saved value on the constraint owner, use the constraint metafield blank playbook. If the value is present in the input but every location is blocked, use rule blocking first.
Capture shop, fulfillment order, location candidates, product or variant, owner ID, namespace.key, Admin value, and the exact Constraint Rule / input response field before changing the Function or adding another app.
02
Prove owner, fulfillment order path, and exact namespace.key the rule expects.
Confirm whether the Constraint Rule reads a Product, Variant, Location, Fulfillment Order, Shop, or app-owned metafield. A correct value on the wrong owner looks blank in the rule input. Record the fulfillment path (Admin fulfill, API fulfill, Order Routing handoff) and any market or company context.
Copy the exact namespace.key, including case. Do not create a duplicate definition because its Admin label looks identical. A product key will not appear because the input query asks for a location or fulfillment-order key.
03
Compare the Admin saved value with the Constraint Rule payload.
Save one unmistakable, reversible test value on the exact owner in Admin. Refresh Admin and confirm it persists. Then inspect Constraint Rule input / API nodes for that fulfillment order and record whether the metafield is absent, null, empty, type-mismatched, or present under a different alias.
Separate: Admin blank + rule blank (definition/value), Admin present + rule blank (query, access, wrong owner, stale version), rule present + every location blocked (parse / constraint logic). Keep tokens and customer data out of screenshots.
04
Check type, access, input query, and the active Function version.
Record definition type, list/reference shape, and Admin / Storefront / Function access flags the rule needs. Confirm the input query selects the same namespace.key on the same owner. Verify the deployed Function version is Active and the app is installed and selected on the live shop.
A draft query, stale generated schema, inactive version, or unselected constraint can make a correct Admin value look blank in the rule while Liquid or Admin still show the field.
05
Retest one fulfillment path and preserve the proof.
Use one known product or variant, one short synthetic value, and one fulfillment path. Record owner ID, namespace.key, type, Admin value, rule payload excerpt, access flags, active version, and a screenshot of allowed vs blocked locations. Hard-refresh only after the first trace is captured.
Classify the miss as owner, definition/value, access, rule query, type mismatch, inactive version, or constraint parse. Keep it separate from Order Routing, Delivery Customization, and inventory transfers.
06
When to stay DIY vs pay $997.
Stay DIY when one owner, access, query, version, or rule-payload check explains the blank field. Keep the proof packet so future Constraint Rule or location-app changes are reversible.
Pay for the $997 one-time install when several Shopify surfaces, apps, and ops alerts need to be wired and documented on one live store. Nico at Latch AI Ops can connect 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.