Inventory Shipment
read_inventory_shipments access scope.read_inventory_shipments access scope.:Subscribe to field-level changes on the InventoryShipment GraphQL Admin API object. You can subscribe to create, delete, and update events, as well as changes to specific fields.
Each topic corresponds to a commerce resource (for example, an inventory shipment) that can exist independently within its domain. Child entities that depend on a parent within the same domain don't have their own topic. Instead, changes to child entities trigger a delivery on the parent topic. Calculated fields, derived fields, auto-updated timestamps, and cross-domain fields aren't available as triggers.
shopify.app.toml
Anchor to Supported triggersSupported triggers
Field-level triggers for InventoryShipment subscriptions.
All triggers require the read_inventory_shipments access scope, and those triggers that require additional scopes are documented where relevant. Deprecated triggers are listed last.
Subscriptions can include multiple triggers. Use the shopify-webhook-id header for deduplication when handling duplicate deliveries.
Custom queries aren't limited to InventoryShipment. They can query the full GraphQL Admin API.
Anchor to list-of-topics-inventoryShipment.*inventoryShipment .*
Fires when events involve the object.
The "create" and "delete" actions are only relevant within the context of this parent topic. Use to follow or replicate impacted data after a delete event. Define a custom query to retrieve specific fields from create events.
is a parent trigger. Subscribing with the "update" action receives events for all supported triggers under , including nested triggers. Use a more specific trigger to limit events to the fields you need.
Variables:
Anchor to list-of-topics-inventoryShipment.statusinventoryShipment .status
Fires when the status field on the object changes.
Subscribe to this trigger with the "update" action and include the field in a custom query to retrieve updated data from the payload.
You can trace the field in subsequent requests using .
The status field represents the current status of the shipment.
Variables:
Anchor to list-of-topics-inventoryShipment.tracking.*inventoryShipment .tracking .*
Fires when the tracking field on the object changes.
is a parent trigger. Subscribing with the "update" action receives events for all supported triggers under , including nested triggers. Use a more specific trigger to limit events to the fields you need.
Include the field in a custom query to retrieve updated data from the payload.
You can trace the field in subsequent requests using .
The tracking field represents the tracking information for the shipment.
Variables:
Anchor to list-of-topics-inventoryShipment.tracking.arrivesAtinventoryShipment .tracking .arrivesAt
Fires when the field on the object changes.
Subscribe to this trigger with the "update" action and include the field in a custom query to retrieve updated data from the payload.
You can trace the field in subsequent requests using .
The field represents the estimated date and time that the shipment will arrive.
Variables:
Anchor to list-of-topics-inventoryShipment.tracking.companyinventoryShipment .tracking .company
Fires when the company field on the object changes.
Subscribe to this trigger with the "update" action and include the field in a custom query to retrieve updated data from the payload.
You can trace the field in subsequent requests using .
The company field represents the name of the shipping carrier company.
Variables:
Anchor to list-of-topics-inventoryShipment.tracking.trackingNumberinventoryShipment .tracking .trackingNumber
Fires when the field on the object changes.
Subscribe to this trigger with the "update" action and include the field in a custom query to retrieve updated data from the payload.
You can trace the field in subsequent requests using .
The field represents the tracking number used by the carrier to identify the shipment.
Variables: