Shipments processed by your system for Jet orders can be entered in bulk using a csv spreadsheet.
You can download an example csv here: Example Import Shipments CSV
|1||Order Id||The Jet defined Order Id. If you have broken an order into multiple shipments, you may repeat the Order Id (and Alt Order Id) in a different row.|
|2||Alt Order Id||The Order Id from your system.|
|3||Alt Shipment Id||This is an optional custom shipment Id that can be assigned by your system.|
|4||Tracking Number||Packaging tracking number that the carrier is using. If this shipment represents a cancellation, and no items are shipped for the given order, then a tracking number must not be included.|
|5||Shipment Date||The date when your shipment will be picked up by the carrier. Jet wants the date to be formatted using the ISO 8601 standard, which
includes a date, time and time zone offset from GMT. If you choose not to supply a compliant date and time, Aerodrome will automatically set the time and offset to your local zone.
If you would like to precisely set this field, please use the following format:
|6||Shipment Method||Shipping method used for the given shipment. Must be one of the following values:
|7||Expected Delivery Date||The date and time the carrier expects the shipment to be delivered. This value must use the ISO 8601 format:
|8||Ships from Zip Code||The zip code where the shipment departed.|
|9||Carrier||The carrier that will complete the delivery. Please omit this value if the order does not contain any shipped items. Must be one of the following values:
|10||Carrier pick up date||The date the carrier picked up the shipment. This value must use the ISO 8601 format:
|11||Redirect Node||If this shipment was shipped from a different fulfillment node than the one specified in the initial order, then include the configured fulfillment node value here.|
|12||Zero Inventory||If this order was redirected to a new fulfillment node because of Jet having bad inventory data, or for a similar reason you can set this column to true. Doing so will effective zero the inventory at the specified fulfillment node.|
|13||Item Id||The Jet-supplied item id. This is a unique id that represents a given item within an order. This must be listed for each item within the bulk import spreadsheet.|
|14||Alt Item Id||A custom id representing this item from your system.|
|15||SKU||The product sku from your system. This must match the SKU supplied by Jet in the initial order.|
|16||Quantity Shipped||The quantity of the current SKU contained within the specified shipment.|
|17||Quantity Cancelled||The quantity of the current SKU that were not shipped.|
|18||RMA Number||You may supply a custom RMA number for the shipment|
|19||Address 1||Optional return location address line 1|
|20||Address 2||Optional return location address line 2|
|21||City||Optional return location city|
|22||State||Optional return location state|
|23||Zip code||Optional return location zip code|
A note about shipment quantities. The total quantity of a given sku that is shipped, and the cancelled quantity for that sku, must equal the total quantity ordered.
When entering shipments, it's important to note that we must represent each product within a shipment individually. This means you may have to duplicate data within your spreadsheet. Please see the Example Import Shipments CSV for a detailed example.
Main Window & Dashboard