An order can be configured to ship from a single stock location (i.e. primary). In this scenario the number of shipments is minimized by creating one or more stock transfers from the stock location where the items are available to the primary one. Shipping categories are still honored, by creating different shipments. Stock transfers can also be created outside of the order scope, in such case they have no relationships with shipments and line items.
A stock transfer object is returned as part of the response body of each successful list, retrieve, create or update API call.
The stock transfer unique identifier
The stock transfer endpoint URL
The code of the associated sku.
The stock transfer status, one of 'draft', 'upcoming', 'picking', 'in_transit', 'completed', or 'cancelled'
The stock quantity to be transferred from the origin stock location to destination one
Time at which the stock transfer was completed.
Time at which the stock transfer was cancelled.
Send this attribute if you want to mark this stock transfer as upcoming.
Send this attribute if you want to start picking this stock transfer.
Send this attribute if you want to mark this stock transfer as in transit.
Send this attribute if you want to complete this stock transfer.
Send this attribute if you want to cancel this stock transfer.
Time at which the resource was created.
Time at which the resource was last updated.
A string that you can use to add any external identifier to the resource. This can be useful for integrating the resource to an external system, like an ERP, a marketing tool, a CRM, or whatever.
Any identifier of the third party system that defines the reference code
Set of key-value pairs that you can attach to the resource. This can be useful for storing additional information about the resource in a structured format.
The associated sku.
The origin stock location.
The destination stock location.
The associated shipment.
The associated line_item.
The resource environment (can be one of