The draft-order attribute is blank—or never arrives.

This page is for a value that belongs to the draft order's custom attributes / additional details but is blank, missing, or attached to the wrong draft. A readable draft with a blank invoice body is the invoice-blank playbook. A product option that belongs to one line is a line-item property. A buyer-entered cart note is cart-note-not-saving. Do not “fix” the wrong field.

Write down the draft ID, exact attribute key and value shape, source system, intended destination, market, staff/app owner, and the moment it should be written. Use a non-sensitive test value; never paste customer data, payment details, or access tokens into a ticket.

Create or use one controlled draft and add a marker such as LATCH-ATTR-TEST-01. Capture the source form or API request, the response, the draft's Admin view, the draft JSON or supported app log, and the final order after checkout if the field should persist. Search by draft ID, not a customer name.

• Marker absent from the request: the form, mapping, or app never collected it.
• Request contains it but draft does not: inspect the supported field name, API version, permission, validation, and response error.
• Draft contains it but order does not: verify the documented handoff and whether checkout intentionally drops draft metadata.
• It appears then disappears: find a second Flow, app, import, or full-list replacement writer.

Remove the test marker after the retest. Keep a before/after record and a rollback step.

Common causes are a field label that looks like an attribute but writes to line-item properties[], an app that only supports cart attributes, a draft API payload using the wrong namespace or shape, a staff role that can view but not write, a draft created by a different channel, or a second writer replacing the complete attribute list.

• Check whether the value is meant to repeat per line, once per order, or only on the draft; the destination determines the field.
• Compare the draft's raw supported representation with the Admin presentation; a UI panel can be stale or label the same value differently.
• If the draft has the value but the invoice is white, do not rewrite attributes—use the distinct invoice-render playbook.
• If the value is a buyer note, do not call it a draft custom attribute; trace cart note / checkout attributes instead.

Keep privacy, consent, payment, fraud, and staff-access controls unchanged while diagnosing. A custom attribute is operational data, not proof of identity, consent, eligibility, or payment.

Fix the first confirmed gate: map the source to the documented draft field, use the supported API shape and permission, reconnect the app, publish the correct Flow, or stop the proven overwriter. Do not broaden scopes, duplicate automations, or replace the entire attribute list unless that is the documented intended behavior.

Retest with two positive controls and one negative control. Confirm the marker lands on the intended draft, survives the expected handoff, does not land on the negative control, and is visible in the actual downstream field. Check one real market/channel if that is where the failure occurs. Remove test data and record the run ID, timestamp, exact key, result, and rollback.

Stay DIY if one attribute has one confirmed mapping, permission, or overwriter to repair. Keep the change narrow and reversible. No agency is required and no order, revenue, or data-completeness guarantee is implied.

Pay $997 one-time when the work is wiring the Shopify stack you already use: lead capture, ops alerts, and a checkout-ready workflow. Nico at Latch AI Ops installs it on one live store in 72 hours after collaborator access is in. You are buying the install, not more orders, recovered revenue, or an attribute guarantee.