Orders
Overview
Orders represent purchase orders, sales orders, or other inventory in your facility. The benefits of uploading orders to Conduit include:
- PO#/SO# validation for incoming appointments
- Auto-filled shipper, carrier, item, or load types on appointments
- Alerts on orders with a "need-by" or "deliver-by" date and preventing scheduling before these dates
Orders are a key concept when integrating your existing systems (such as your TMS or WMS) with Conduit, and because of this, we support multiple ways to integrate your system's orders into our platform.
Fields
Orders in Conduit support the following fields regardless of the method orders are delivered into the system:
| Field | Description | Required |
|---|---|---|
| Reference ID | Primary value of an order that uniquely identifies it | Yes |
| Facility ID | The Conduit UUID of the facility that the order belongs to | Yes |
| Direction | "Inbound" or "Outbound" | No |
| Load Type | The type of order | No |
| Earliest Scheduled Start Time | ISO 8601 timestamp of the pick up, delivery, or ready by date for the order. Any linked appointments to this order will not be able to be booked externally before this time. | No |
| Item IDs | The contents of the order | No |
| Shipper Receiver | Shipper or receiver of the order depending on if the appointment is outbound or inbound | No |
| Carrier | The carrier for the order | No |
| Carriers Emails | The emails associated with the carrier | No |
| Customer | The customer of the order (commonly used by 3PLs) | No |
| Notes | Relevant notes for the order that you want to show in Conduit | No |
Example
An example CSV upload might look like the following snippet:
reference id,item ids,direction,load type,shipper receiver,facility id,carrier,notes, external reference id
reference-id-1,item-id-1,Inbound,,Shipper Name 1,0db07caf-5005-4144-a983-e210c96cd451,carrier 1,Inbound Pallet Notes,external-reference-id-1
reference-id-2,item-id-2,Outbound,,Receiver Name 1,0db07caf-5005-4144-a983-e210c96cd451,carrier 1,,
Integration Connections
We categorize our connection types for integrations into two buckets. Standard integrations are ones that work out of the box with no additional work required.
Custom integrations are enabled by Conduit's integration layer that allows any type of data to be connected into Conduit. This is the type of integration if the method of integration is not supported by the standard integration connections.
Standard
The standard integration methods supported are:
Custom
If you would like to integrate orders in a different way than those listed in the Standard integration types, we can also support techniques such as:
- Direct vendor integrations
- CSV upload via SFTP
- EDI