Styxis
Company
Knowledge

Shopify shipment webhooks: preserve transfer IDs and verify the reference scope

An explicit transfer ID reduces inferred joins, but reference existence and correct linkage still need separate checks.

Do not substitute a nearby movement for the source reference

Preserve the transfer identifier supplied by the source before trying to match shipments by similar quantities or timestamps. A logistics handoff needs the relationship so receipt work and discrepancy investigation can follow the same movement. Forcing unrelated shipments onto a transfer may improve the displayed match rate while weakening its evidence. [1, 2, 3]

What the new field communicates

Shopify's 2026-10-01 announcement adds inventory_transfer_id to several inventory_shipments webhooks in 2026-10. It lists creation, deletion, item and quantity changes, in-transit marking, receiving and tracking updates. The purpose is to identify which transfer, if any, is related to a shipment. It does not establish that every shipment must have such a relationship. [1]

Check collection scope before calling a reference invalid

The receipt owner should preserve the webhook's transfer identifier in the collection table. If a populated reference is absent from the collected transfer ledger, verify the ledger's scope before reconsidering the link. Keep store boundaries separate and inspect permissions, collection time and missing pages. Calling an incomplete ledger's reference failure a source-shipment error starts the investigation in the wrong place. [1, 3]

An existing key is not necessarily the correct key

Suppose the illustrative source transfer ID is MOVE-A and the approved complete ledger contains MOVE-A. Expected reference state is present; an actual present satisfies existence. A received MOVE-X missing from the ledger produces absent and requires source and collection-scope checks. Conversely, replacing the reference with another existing transfer, MOVE-B, can pass existence. Preserve separate checks for source-ID fidelity and ledger membership. [1, 3]

Keep the two Truthound responsibilities distinct

ForeignKeyValidator in Truthound Core 3.3.2 accepts prepared child and parent tables and key columns to identify missing references. State the null policy for unrelated shipments explicitly. This does not detect replacement with a different existing ID, so source comparison remains separate. Truthound also does not recover missing webhooks or query Shopify transfers. Investigate suspicious references through ledger refresh and documented lookup paths; do not invent a link from similar time and quantity alone. [1, 2, 3]

Application conditions

Use the listed inventory_shipments events in 2026-10 or later. Prepare a transfer ledger for the same store and a verifiable collection scope. Distinguish an unrelated shipment from a missing ledger record.

Alternatives

Verify ledger refresh and access permissions, then investigate suspicious references through the official API. Do not force joins using only timestamps and quantities.

Limitations

  • An absent reference alone does not establish that a shipment is invalid. Truthound does not recover missing webhooks or query the existence of source transfers.

Evidence

Event checked
Subject checked
Modified