The line-item property is blank—or never arrives.

This page is for a value attached to one product line that is blank, missing, or attached to the wrong line in cart, checkout, or the order. A buyer-entered message for the whole order is a cart/order note. A value stored on a draft itself is a draft-order custom attribute. Do not fix the wrong field.

Write down the product handle, variant ID, exact property key, expected value shape, market, channel, and the step where it disappears. Use a non-sensitive marker; never paste customer data, payment details, or tokens into a ticket.

Add one controlled product and enter a marker such as LATCH-PROP-TEST-01. Capture the product form payload, browser Network request, cart JSON, checkout line details, and the resulting Admin order. Compare the same line by variant ID, not only by product title.

• Marker absent from the form request: the input name, disabled state, or serializer is wrong.
• Request contains it but cart does not: inspect properties[...], AJAX add-to-cart, and a second cart writer.
• Cart contains it but order does not: check checkout handoff, hidden/private properties, and the app or channel creating the order.
• It appears then disappears: find a theme script, app, Flow, import, or full line replacement that overwrites the item.

Remove the marker after retesting and keep a before/after record with a rollback step.

Common causes include an input with a display label but no usable name, a form serializer dropping unchecked or disabled fields, an AJAX request using the wrong property shape, a cart drawer replacing the line without properties, an app mapping properties into a different field, or an order view hiding private properties.

• Use properties for data that belongs to one line; use cart attributes or a note for one value belonging to the whole order.
• Check raw cart and order representations as well as the Admin presentation; labels can differ.
• If the product form works but draft orders are blank, use the draft-order attribute playbook instead of rewriting theme code.
• Keep privacy, consent, payment, fraud, and staff-access controls unchanged while diagnosing.

Fix only the smallest confirmed gate: restore the documented property key, serialize the form, preserve properties in the AJAX cart path, correct the supported app mapping, publish the right theme, or stop the proven overwriter. Do not broaden permissions, duplicate automations, or replace an entire line item without a documented reason.

Retest with two positive controls and one negative control. Confirm the marker lands on the intended variant, survives the expected checkout handoff, does not land on the negative control, and is visible in the actual downstream field. Test the market and channel where the issue occurred, then remove test data and record the run ID, timestamp, result, and rollback.

Stay DIY if one property has one confirmed input, serializer, mapping, 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 a line-item-property guarantee.