Delivery Hub Structure and Data Flow

An order is a request to fulfill goods at a specific address. It includes all information needed to complete it, such as the requested service or goods, the customer’s contact information, and the time window. Order properties determine the services required to fulfill the order. For example, fragile goods may require special packaging. 

One order can have several fulfillments or destinations, for example, if goods are located at several stores.

Inside the Bringg database and payloads, an order is sometimes referred to as a task.

One order can include several fulfillments that Delivery Hub displays only in the shipping location where a packer will fulfill one part of the order. Fulfillments include the list of inventory for that location and requested service levels.

Packers start their workflow in the Fulfillment screen, where they can view and select from the relevant fulfillments.

Each fulfillment contains at least one shipment, which is created using the Shipments API or when a user packs fulfillment inventory and makes at least one attempt to book a carrier.

Fulfillments can be split into multiple shipments. For example, if some of the inventory is unavailable for the first shipment, it can be sent in a subsequent shipment. A single shipment can contain several packages.

Shipments may be referred to as *consignments* outside of Bringg.

Each shipment can contain multiple packages. A package refers to the physical goods that are shipped, including packaging and inventory. You might hear packages referred to as parcels outside of Bringg.