The shipping functionality stages items into containers and/or staging areas for shipping to a facility (transfer) or customer address. Items shipped are marked as either In Transit (for items that will be received at the destination) or Shipped (for items where shipping is the final tracking step and they become historical data).

Orders

Transfer Orders

Transfer Orders move items between facilities. Orders define what items to transfer at the item master level. Once an order is created, items are picked using the Order Pick transaction, which reserves specific units (setting their status to Picked). Shipment details can be defined at the same time as the order.

Customer Orders

Customer Orders manage the shipping of customer-owned units being tracked in the system. They direct the shipment of existing units to a specified customer address. The shipment is set up at the same time as the order.

Shipment Templates and Shipment ID

The Shipment ID identifies the group of items being shipped. A Shipment ID can be created with a Transfer or Customer Order, or defined independently as part of a Build Shipment.

Shipment Templates define what additional data is captured as part of the shipment (beyond carrier, expected ship date, and destination details). Different templates support different shipment types. For example:

• A template for shipments requiring a Bill of Lading would capture freight charge terms and special instructions.
• A template for FedEx or UPS shipments might only capture a third-party account number.

Standard Shipment Fields

• Expected Ship Date — Used for printing packing lists and Bill of Lading documents. Should be updated to the actual ship date just prior to completing the shipping transaction.
• Planned Carrier — The planned carrier for the shipment. Can be changed up until the shipment is shipped.

Build Shipment

The Build Shipment transaction finalizes items for shipping by assigning them to containers and/or selecting them for shipment.

• Pending Shipment IDs can be selected, and additional units can be added.
• Picked items from an order can be swept automatically into the shipment build, or users can interact with each unit for a final pack to a container.
• New shipments can be created without an existing order — available units can be added directly. If the destination is associated with a customer team, only customer-owned units can be selected.
• If the shipment is associated with a project, only units allocated to that project (or with no project allocation) can be selected.

Pick Order

The Pick Order transaction is available only on the mobile app. It picks items against pre-defined order lines from a Transfer Order or Customer Order. When items are picked, they are moved to a staging area and updated with a status of Picked.

Shipping

The Shipping transaction completes the final shipment action for units grouped under a Shipment ID. Shipment attributes are reviewed and can be edited before the final Ship step. Once shipped, the Shipment ID and its units are marked as either:

• Shipped — Assigned to shipments associated with Customer Orders. Shipping is the endpoint for tracking these customer-owned units. Internal facility destinations not flagged to receive a transfer are treated the same way.
• In Transit — Assigned when the shipment is between two internal facilities. The carrier takes custody of the shipment. The destination facility completes a Receive Transfer to acknowledge receipt, update the custodian, set the destination location, and change the status back to Available.