> For the complete documentation index, see [llms.txt](https://docs.fulfillmenttools.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fulfillmenttools.com/documentation/backoffice/network-view/orders.md). # Order overview The network order overview provides an overview of all orders across the fulfillment network. What actions you can perform and what you can see, will depend on your user role and permission. Below is what a role with full permissions will see:

The search bar can be used to find orders. You can search by tenant order ID, consumer, address, stickers and labels, article name and ID, order custom attributes, facilities, carrier track-and-trace ID, and custom service names. You can also use filters to find relevant orders: * **Order date:** Filters orders by order date. * **Creation date**: Filters orders by the date they were created in fulfillmenttools. * **Facilities:** Filters orders by the facility where fulfillment occurs. * **Facility countries:** Filters orders by the country where fulfillment occurs. * **Delivery countries:** Filters orders by the country of the delivery address. * **Type:** Filters orders by [order type](/documentation/by-pillar/order-management.md#delivery-preferences-and-order-types). * **Carrier**: Filter orders by the carrier. * **Process status:** Filters by the aggregated status of the process. Note: `Finished` can represent any state marking the process as complete, such as `Delivered`, `Picked up`, or `Pickup canceled`. * **Completion by:** Filters by the time when the pick job should be completed. * **Brands:** Filters orders containing items from specific brands. * **Routing:** Filters orders by their routed status, whether routed to a facility or unroutable. * **Lock:** Filters orders by their locked or unlocked status. * **Delivery progress:** Filters orders by their delivery status sent from the carrier. * **Article:** Filters orders by their included article. By default, orders are shown from the last 12 months. They are sorted by order date in ascending order. To change the sorting, click the arrow on any column to sort the table by that column. Use the customize icon at the end of the table to change which columns are shown in the table and in which order. Alternatively, use the more icon on each column to change it's position. Click anywhere on the order row to open the [Order details view](/documentation/backoffice/network-view/orders/order-details-view.md). Click on the Order ID to open the [fulfillment status quick view](#fulfillment-status-quick-view). ## Order table: Field definitions Below are all the fields that could be included in the orders table. These are listed in the default order within the table.

Field name	Type	Definition
Type	Enum	Supply: The order is intended to supply a facility (for example, replenishment or internal stock movement). Shipping: The order is shipped to a consumer or external recipient. Pickup: The consumer collects the order at a designated facility.
Order ID	String	A unique identifier assigned to each order. Used for tracking, referencing, and linking the order across systems.
Status	Enum	An order's status depends on its current processing stage. The complete process encompasses picking, packing, handover, and delivery. The order process status integrates these stages to show the overall progress. See the order process status section for more details.
Alert	Enum	Provides visibility into operational conditions that may require attention. Alert messages are displayed in the format `{Affected area}: {Alert type}`. The affected area indicates where the issue occurred. Alert colors indicate the current status and urgency. Gray alerts indicate that operational intervention in the fulfillment process is no longer possible. The relevant process step has already been completed or passed, although follow-up actions outside the fulfillment workflow may still be required. `Stuck`: A process step is blocked and can't proceed. `Mismatch detected`: An inconsistency or discrepancy has been detected. `Delay detected`: The committed promise can likely no longer be met or has already been missed.
Order date	Date	The timestamp indicates when the order was originally created in the system.
Preferred date	Date	The consumer's preferred delivery date, if provided.
Target time	Date	Indicates when a shipping provider should pick up an order for delivery. A value of `–` means that no target time is defined or available for this order.
Info	Enum	Displays an informational icon. See the info icons section for more details.
Ordered	Number	Indicates the total quantity of items included in the order.
Picked	Number	Indicates the quantity of items that have been successfully picked. This value is updated only after all pick jobs for the order are closed.
Consumer	String	Represents the recipient of the delivery. May contain a last name or company name, depending on the consumer data in the order.
Delivery street	String	The street address of the delivery destination.
Delivery city	String	The street address of the delivery destination.
Delivery country	String	The destination country for the delivery.
Carrier	Enum	The logistics provider responsible for transporting and delivering the order or transfers.
Facility	Enum	The operational location(s) responsible for processing or fulfilling the order.
Label		Represents the set of stickers automatically assigned to the order during order creation.
Bundles	Number	The number of bundles included in the order. A bundle represents a grouped set of items packaged together.
Splits	Number	Indicates whether the order is split across multiple facilities. A value greater than 1 means the order is fulfilled from multiple facilities.
Payment method	Enum	The payment method (for example, credit card, invoice, digital wallet).
Payment currency	Enum	The currency in which the consumer paid for the order.
Last edited on	Date	The date and time of the most recent modification to the order.
Last edited by	String	The person responsible for the most recent modification to the order.
Creation date	Date	The date on which the order was created in fulfillmenttools.

### Order process states The order process status represents the current stage of an order within its lifecycle. It's automatically determined based on the statuses of the underlying processes and modules, such as routing, fulfillment operations, shipping, and returns. The following table outlines the criteria used to assign each order status.

Status	Status color	Description	Type
`Open`	gray	No operational processes have started yet. If it's locked, it will show a lock symbol.	Shipping and Pickup
`In progress`	orange	A routing process is running, or at least one operational process (picking, packing, services, shipping label creation, or handover) has been started. Or a return process has been initiated.	Shipping and Pickup
`Pickup pending`	orange	The order is ready for consumer pickup.	Pickup
`In transit`	orange	At least one parcel is in transit. The carrier has confirmed the handover.	Shipping
`Delivered`	green	The carrier has confirmed the delivery.	Shipping
`Finished`	green	All fulfilled parcels have been handed over to the carrier, and fulfillmenttools has no further delivery information. The status may also include orders that were partially canceled during processing, while all remaining fulfillable items were completed and handed over.	Shipping
`Picked up`	green	The consumer has picked up the order.	Pickup
`Error`	red	An error occurred, which could be operational (for example, a failed label request), shipping-related (for example, a carrier reports a delivery delay), or technical.	Shipping and Pickup
`Canceled`	red	The order was canceled manually or automatically, depending on the configuration.	Shipping
`Pick up canceled`	red	A handover didn't occur, for example, if the consumer didn't pick up the order.	Pickup

### Info icon The information icon column displays order details.

Icon	Description
	The order is locked. You can manually unlock it using the three-dot menu.
	Comments have been added to the order process. To view and add new comments, open the order details page.
	The order is a preorder or backorder and is awaiting new stock. For more information, see the Preorders and backorders article.

## Fulfillment status quick view When you click the order ID, a modal opens. This is the fulfillment status quick view. It provides detailed insight into the operational status of order fulfillment. You can see whether an order is currently being picked or packed, or if labels have been created. Any recorded attributes added to an item during the operational process are shown here, such as serial numbers, country of origin, and so on.

### Operational status {% tabs %} {% tab title="Picking" %}

Status	Color	Description
`Open`	gray	No related order-picking tasks have started in the facility yet.
`In progress`	orange	The facility has started at least one picking task related to the order.
`Done`	green	All picking tasks were completed, and all items were picked.
`Incomplete`	half-green	All picking tasks were completed, but not all items could be picked.
`No items picked`	red	All picking tasks were completed, but no items were picked.
`Canceled`	red	The order, or just the picking task, has been canceled.
-	-	No picking tasks exist.

{% endtab %} {% tab title="Packing" %}

Status	Color	Description
`Open`	gray	No related order-packing tasks have started in the facility yet.
`In progress`	orange	The facility has started at least one related order-packing task.
`Done`	green	All packing tasks were completed.
`Canceled`	red	The order has been canceled.
-	-	No packing tasks exist.

{% endtab %} {% tab title="Services" %}

Status	Color	Description
`Open`	gray	No related order-service tasks have started in the facility yet.
`In progress`	orange	The facility has started at least one service task related to the order.
`Done`	green	All service tasks were completed.
`Canceled`	red	All related services were canceled.
-	-	No services exist.

{% endtab %} {% tab title="Label" %}

Status	Color	Description
`Open`	gray	At least one order-related package has been packed at the facility, but no shipping label has been ordered yet.
`In progress`	orange	At least one shipping label has been requested.
`Retryable`	orange	Creating at least one shipping label has failed and can be retried, for example, through the Store Operations app.
`Done`	green	Order-related shipping labels have been successfully generated.
`Error`	red	The delivery label couldn't be created.
-	-	No parcel or shipping label exists.

{% endtab %} {% tab title="Delivery" %}

Status	Color	Description
`Open`	gray	No handover to the carrier or consumer has been reported yet.
`In transit`	orange	The carrier has accepted at least one package, and it's on its way to the consumer.
`Picked up`	green	A handover to the consumer has been reported.
`Delivered`	green	The carrier reports that it successfully delivered to the consumer.
`Error`	red	The carrier reports an incident during delivery.
-	-	No parcel, shipping label, or handover task exists.

{% endtab %} {% endtabs %} ### Customization You can edit the view of the fulfillment status quick view: * Table columns can be rearranged or stuck to either side. This action is available via the three-dot menu in each column header. * Table columns can be shown or hidden using the edit button located at the right end of the table. * The table can be sorted by the data of a column using the arrow icon in the header. * The reset button restores the visibility of all columns and reverts the table to its original sorting order. ## Operational actions The below actions can be found in the 3-dot menu on the order table or in the fulfillment status quick view.

Action	Description	Requirements
Cancel order	Cancels all entities of an order.	All pick jobs are open No items have been picked The necessary permission `ORDER_CANCEL` is set
Force cancel order	Sets all entities to canceled, regardless of processing status. Releases reserved stock. If items are already picked, you must manually return them to storage and align physical inventory with system records.	Must be enabled via REST API The necessary permission `ORDER_FORCE_CANCEL` is set
Unlock order	Unlocks the order and operational processes. Operational entities change their status to open.	Order is in status locked The necessary permission `ORDER_UNLOCK` is set
Edit address	Allows users to correct typographical errors or incorrect address entries.	The necessary permission `ORDER_CONSUMER_WRITE` is set
Change carrier	Change the carrier for the picking task. A new label must be generated.	Ship‑from‑store orders only Handover job is open The necessary permission `SHIPMENT_WRITE` is set
Assign order	Assigns the order to a new facility and creates a new pick job there. Deletes existing pick jobs.	Ship‑from‑store orders only All pick jobs are open No items have been picked The necessary permission `PROCESS_WRITE` is set
Reroute order	Performs new routing if the current routing isn't optimal. Deletes existing pick jobs.	All pick jobs are open No items have been picked The necessary permission `PROCESS_REROUTE` and is set
Reroute unroutable order	Evaluates the order again against routing rules to find the optimal routing option. Can be executed in bulk to process multiple unroutable orders simultaneously.	Order or articles within the order aren't routable The necessary permission `ROUTING_WRITE` is set
Reroute task	Enables manual rerouting of tasks. Blocklists the facility that previously processed the order (if activated in the settings).	Pick job is open The necessary permission `ROUTING_WRITE` is set Feature is enabled in the settings
Restart task	The picking task remains in progress, and the number of already picked items stays the same, but the shipping labels will be removed.	Task hasn't yet handed over to a carrier or consumer Restart configuration is active The necessary permission `PICKJOB_WRITE` is set
Reset task	Resets the task status to open, resets already picked items to 0, and removes already created service jobs, pack jobs, parcels, handover jobs, and shipping labels. This is useful if a mistake was made during the picking process in the facility.	Pick job is in progress The necessary permission `PICKJOB_WRITE` is set
Cancel task	Cancels the picking task and updates the order status to canceled in Backoffice. Note: The order isn't automatically canceled, and the `ORDER_CANCELED` event isn't triggered. You must cancel the order separately if required.	Picking has not started yet or ended with the status `ABORTED` The necessary permission `PICKJOB_WRITE` is set
Confirm pickup	Confirms the pickup by the carrier or consumer.	Collect orders only Handover job is open The necessary permission `HANDOVERJOB_WRITE` is set
Cancel pickup	Cancels the pickup by the consumer.	Collect orders only Handover job is open, handed over, or waiting for input The necessary permission `HANDOVERJOB_WRITE` is set
Edit order	Allows you to edit certain order details, including the preferred delivery date and the ability to add or remove items. Any line item change triggers a reroute.	Pick job is open Editable fields are dependent on order status The necessary permission `ORDER_CONSUMER_WRITE` and `ORDER_LINEITEM_WRITE` is set

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.fulfillmenttools.com/documentation/backoffice/network-view/orders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.