Shopify pickup point metafield missing? Prove the owner, value, API path, and one carrier selection.

Use this page when the value itself never lands: a definition never receives the carrier point ID, an app shows blank data, or ops tools never see the selected point. If carrier pickup points (UPS Access Point, FedEx Hold at Location, DHL Service Point, and similar) never appear as options, use the pickup points not showing playbook instead. Local delivery zones and BOPIS in-store pickup are separate paths.

Do not add a second metafield or install another shipping app yet. Capture the shop, carrier, destination, cart, and exact surface where the selected pickup point should be stored.

Open Settings → Custom data and confirm the definition is owned by the resource your implementation writes — often an Order, Shipping line, Delivery method, or custom app-owned resource. Record the exact namespace and key, for example shipping.pickup_point_id, the type, validations, and whether it is a plain value, list, reference, or JSON value.

Complete one checkout that selects a pickup point (or simulate the write with Admin API). Refresh the order or resource and confirm the value survives. A filled definition with no write, a value on a draft order, or a label that only looks right is not proof.

Compare the saved definition with the checkout UI extension, carrier app, or Admin API mutation that should write the field, and with the read query used by ops or fulfillment. The write and read must use the same namespace.key on the same resource, and the app must have the intended access scope. A successful checkout can still omit metafields, write another owner, or serialize a carrier payload differently than the code expects.

Verify the published checkout profile and the active carrier / pickup-point app version. Log field presence without logging customer PII or secrets. If a plain text test arrives but the intended structured carrier payload does not, fix type-specific parsing rather than changing shipping rates.

Pickup points are context-sensitive. Record the market, currency, destination, carrier, cart contents, shipping profile, and whether pickup points are enabled for that method. Confirm the metafield belongs to that delivery context and that the current checkout profile is the one published to buyers.

Keep the diagnosis distinct from the local delivery metafield and delivery customization metafield paths. They can affect the same checkout while reading different resources and fields.

Use one cart and one destination that should offer pickup points. Record the resource ID, namespace.key, type, saved test value, app/checkout version, write success, read presence, and the selected pickup-point label/ID. Repeat logged out if the result is customer-facing, then test a second carrier only after the first path is proven.

If the field is still missing, classify it as definition/value, access/write, resource context, unpublished checkout/app, or type parsing. Do not call a “points not showing” failure until a selection exists and the write path is demonstrably attempted.

Stay DIY when one definition, write path, read query, or published-version check explains the missing field. Keep the proof packet so future carrier changes are reversible.

Pay for the $997 one-time install when several Shopify surfaces, carriers, 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.