Shopify discount metafield missing — prove the owner, value, access, and render path.

The symptom here is a field attached to a discount that is blank or invisible in Admin, an app, an API response, a theme surface, or an extension. A discount code failing to combine is a rules problem; use the code stacking playbook. A Discount Function not applying is execution logic; use the Function stacking playbook.

Do not create a second field or install an app yet. First identify the owner, the exact resource, the key, and the destination where the value should render.

Go to Settings → Custom data → Discounts. Confirm the definition exists, note its type and validations, and copy the exact namespace.key. Then open one discount that is actually active or otherwise available to the surface you are testing. Confirm the value is filled and saved on that discount, not only on a draft, duplicate, or different discount.

Owner matters. A discount field is not a product, order, collection, or shop metafield. If a template or app expects campaign.badge but the definition is marketing.badge_text, a blank is expected until both sides agree.

If an app or Admin API reads the field, verify the app has the intended access and is reading the Discount resource rather than a code, price rule, cart line, or order. Check the API version and the returned namespace/key. An app can successfully fetch a discount while omitting metafields because its query, scope, or resource path is incomplete.

Check the type too: plain text, number, rich text, reference, list, and file values do not serialize or render alike. Remove ambiguity by testing one simple text value first, then restore the intended type only after the read path is proven.

A discount metafield does not automatically appear on a storefront. Identify the intended destination: Admin list/detail, an app screen, a theme section, a cart or checkout extension, or a customer-facing landing path generated by your app. Confirm that the current theme or extension is published and that the block is connected to the Discount resource.

For Liquid or a custom app, compare the expression and the resource context. Do not paste a product accessor into a discount context. Inspect the rendered DOM or API response, not only the editor preview, and check whether empty values are intentionally hidden.

Use one discount with a short, unmistakable test value. Save it, wait for the relevant cache or sync window, then check the exact surface where it should appear. Test logged out when the destination is customer-facing. Record the discount ID or handle, namespace.key, type, theme or extension version, and timestamp.

If it is visible, stop. If it is still blank, the evidence should identify whether the break is definition, value, access, resource context, publication, or empty-value handling. Do not conflate this with discount combination rules.

Stay DIY if the work is confirming the Discount owner, saving one value, fixing namespace.key or access, and wiring the current render path. This page is the checklist.

Pay for the Latch AI Ops install when you want Nico to connect the stack you already use so lead capture, ops alerts, and a checkout-ready workflow are handled together. $997 USD one-time buys that install for one live Shopify store, with a 72-hour delivery window after collaborator access. It does not buy more orders, recovered revenue, a conversion guarantee, or a theme rebuild. Checkout is on Whop; owner passwords are not requested.