> 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.md).
# Network view
The Network view allows you to manage the fulfillment network. It's designed for network, store, and warehouse managers requiring a general overview of orders, facilities, and inventory at the network level.
{% hint style="info" %}
You'll only see this view if you have the role and permission to select this view. See the [Backoffice permissions article](/documentation/backoffice/network-view/users-roles-and-permissions/backoffice-permissions.md) for more information.
{% endhint %}
## Home
On the homepage, you'll see an operational overview and a facility map. You can use the **Customize** button to change this layout.
### Operation overview
The operation overview gives you a quick look at what's happening across your fulfillment network. It can highlight up to three KPIs, so you can easily access important data for your facilities.
The three default KPIs are:
* Open orders: Number of orders in status `OPEN`
* Unroutable orders: Number of orders in status `UNROUTABLE`
* Order errors: Number of orders in status `ERROR`
Selecting a number opens the **Orders** overview with the corresponding filter applied.
The other KPIs available are shown in the table below.
| KPI | Description | Underlying data |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| High-performing facilities (revenue/facility) | This KPI reflects the revenue generated by the highest‑performing facilities within the last 7 days. |
Total revenue per facility for the last 7 days.
Revenue based on articles successfully delivered to the customer.
No costs are subtracted.
Returns aren't considered.
Data is updated once a day.
|
| Low-performing facilities (revenue/facility) | This KPI reflects the revenue generated by the lowest‑performing facilities within the last 7 days. |
Total revenue per facility for the last 7 days.
Revenue based on articles successfully delivered to the customer.
No costs are subtracted.
Returns aren't considered.
Data is updated once a day.
|
| Short pick reasons | This KPI reflects the number of short pick reasons per reason and per facility recorded within the last 7 days. |
A pick job line wasn't fully picked, and a reason was provided.
Each recorded reason includes the associated short picked quantity.
Short picks without a recorded reason are excluded.
If multiple lines in a pick job were short picked at different times, the timestamp of the first recorded short pick reason is used.
Data is updated once a day.
|
| Processed pick jobs | This KPI reflects the distribution of pick jobs created per facility within the last 7 days. |
Total number of pick jobs generated per facility for the last 7 days.
The visualization displays the five facilities with the highest operational workload.
Data is updated once a day.
|
|
Most sold products (top products)
| This KPI reflects the products with the highest fulfillment volume within the last 7 days. |
Top 20 articles successfully fulfilled and handed over to the customer.
Later returns aren't considered.
Each product is counted based on completed fulfillment events only.
Data is updated once a day.
|
| Most returned products | This KPI reflects the products with the highest number of completed returns within the last 7 days. |
Top 20 articles included in a return process that reached the final return state.
Only returns that were fully processed and completed are considered.
Each product is counted based on finalized return transactions.
Data is updated once a day.
|
### Facility map
The facility map shows you the facilities across your fulfillment network. Selecting a facility displays basic facility information and, if you have the required permissions, provides a link to the order overview for that facility.
## Sidebar
The sidebar navigation allows you to access different sections of Backoffice.
Depending on your [user role and permissions](/documentation/backoffice/network-view/users-roles-and-permissions.md), and what's been applied in the [remote configuration](/documentation/by-pillar/store-operations/remote-configuration.md), you can see different sections in the sidebar navigation.
Clicking on the name of the section or the expand arrow will show all sub-sections within the section that you can navigate to.
Below is the list of sections in Backoffice in the default order, assuming you have full access and all features added.
* Order management
* [Order overview](/documentation/backoffice/network-view/orders.md): Monitor and manage orders and order status across the network.
* [Returns](/documentation/backoffice/network-view/orders/returns.md): Monitor and manage returns across the network.
* Order routing
* [Routing strategy](/documentation/backoffice/network-view/routing.md): Define routing configurations to select the ideal facility for fulfillment.
* [Routing simulation](/documentation/backoffice/network-view/routing/routing-simulation.md): Simulate routing in Backoffice to validate routing behavior and analyze performance.
* Inventory management
* [Inventory overview](/documentation/backoffice/network-view/inventory.md): Monitor and manage inventory across the network.
* Store operations
* [Facilities overview](/documentation/backoffice/network-view/facilities.md): View and edit facility settings at the network level.
* [Facility groups](/documentation/backoffice/network-view/facilities/facility-groups.md): View and edit facility group settings at the network level.
* [Suppliers](/documentation/backoffice/network-view/facilities/suppliers.md): View and edit supplier settings at the network level.
* Users
* [User overview](/documentation/backoffice/network-view/users-roles-and-permissions.md): Add, delete, edit, or view users.
* [Roles](/documentation/backoffice/network-view/users-roles-and-permissions.md#roles-and-permissions): Add, delete, edit, or view roles.
* [Analytics](/documentation/backoffice/network-view/analytics.md)
At the bottom of the sidebar, you'll find three more options:
* [Settings](/documentation/backoffice/network-view/settings.md): Manage network-wide settings.
* Customize sidebar: Remove sections from the sidebar and reorder the sections based on how often you use them. You can reset these changes at any time.
* Help: Access our documentation.
## Topbar
The topbar is the same across all Backoffice sections.
* fulfillmenttools icon: Takes you to the homepage of the Network view.
* App icon: Role-dependent. Choose between the Network view and the Facility view (if you have access).
* Breadcrumb information: Tells you which view and the section you're in. For example, **Network view - Inventory**.
* AI Sidekick: On click, it opens our [AI Sidekick](/documentation/backoffice/ai-sidekick.md) where you can ask questions about fulfillmenttools and using Backoffice.
* Bell icon: On click, it shows you all notifications relevant to the network and facilities you have access to. See the [Notification center article](/documentation/backoffice/network-view/notification-center.md) for more details.
* Profile icon: Shows your name and role.
* Account settings: Access your account settings.
* Log out: End your session.
## Bottom bar
The bottom bar shows in certain sections.
* fulfillmenttools logo: Takes you to our website.
* Version number: Shows the version number of Backoffice you're using. Share this with the Support team if you're having any issues.
* Apps and connections: Quickly access the setup for connecting your tenant with the fulfillmenttools apps.
* Privacy: Access our [privacy policy](https://fulfillmenttools.com/privacy-policy/).
* Imprint: Access our [imprint](https://fulfillmenttools.com/imprint/).
* Contact: Access our [contact information](https://fulfillmenttools.com/contact-us/). If you're having any issues while using Backoffice, use [our support portal](/documentation/about-fulfillmenttools/incident-management.md) instead.
## Changing the language of Backoffice
The default language of Backoffice is English. To change the language, follow the steps below.
{% stepper %}
{% step %}
**Click the profile icon**
You'll find this in the top-right corner of all screens.
{% endstep %}
{% step %}
**Click Account settings**
This is the second option in the dropdown.
{% endstep %}
{% step %}
**Click the Language dropdown and select the desired language**
There are currently 17 languages available to choose from. If we're missing your language, let us know using [our feedback form](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1/group/13/create/47).
{% endstep %}
{% step %}
**Click Save**
Backoffice will refresh, and all fields will update to the selected language.
{% endstep %}
{% endstepper %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.fulfillmenttools.com/documentation/backoffice/network-view.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.