> 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/facilities.md). # Facilities {% hint style="info" %} This article focuses on using Backoffice. For information on APIs and customizations, see the [Facilities](/documentation/getting-started/facilities.md) section. {% endhint %} A facility is a fulfillment location in the network. A facility could be a store, warehouse, dark store, and so on. Upon opening **Facilities** in the sidebar, you'll see a table of all the facilities that have been created in your network. To create a new facility, click the **Add facility** button at the bottom of the table, input the required information, and click **Save**.
To view details for an existing facility, click the facility anywhere in the table row to open the details screen.
You can manage facility data and configurations for each facility, such as fulfillment times or available shipping providers (carriers). These configurations can influence the routing decision and the data displayed in the Store Operations app and Backoffice. {% 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 %} ## Facility data Facility data contains the main information about a facility. This includes the name, address, contact information, and certain characteristics. All of this can be edited using Backoffice. Once you've made any changes, ensure you click the **Save** button for them to take effect.
### Facility name A facility has both an external name and an internal name. The external name is used, for example, as the sender address on a shipping label and should feature the company name itself. The internal name can be used within your team to differentiate between different facilities. ### Facility address The facility address is the country, street, ZIP code, and city. This also includes the geo-coordinates of the facility's location. ### Facility contact information You can add a specific person to contact for a facility. This is usually the facility manager. You can also add phone numbers and email addresses.
### Facility location characteristics There are 4 location characteristics: * [Location type](#location-type) * [Status](#facility-status) * [Service type](#service-type) * [Tags](#facility-tags)
#### Location type A facility can be one of three types: * Store * Warehouse * External (usually a [supplier](/documentation/getting-started/facilities/supplier-facilities.md)) You can use the dropdown to change the type if needed. #### Facility status A facility can have one of three statuses with different implications for views and routing: * Online * The facility is considered for order routing * The facility is accessible in Backoffice * Suspended * The facility is not considered for order routing * The facility is accessible in Backoffice * Offline * The facility is not considered for order routing * The facility is not accessible in Backoffice If a facility is no longer used for order fulfillment, it's recommended to set its status to **Suspended**. As a consequence, no new orders are assigned to this facility. After all operational processes have been completed (and no more returns are expected for this facility), the facility can be set to **Offline**. This should be done only if there is no longer any need to access the facility from an operational perspective. #### Service type A facility can have the service type of **Shipping, Pickup**, or both. The service type affects the routing decision and the views and settings in the Store Operations app.
Service typeStore Operations appRouting decision impact
Pickup (click-and-collect)
  • The click-and-collect handover section is shown.
Facilities aren't considered in routing decisions, as the facility the customer wants to pick up the click-and-collect order from is already determined in the web shop.
Shipping (ship-from-store)
  • The label section is shown.
  • The ship-from-store handover section is shown.
  • A switch offering to order a label or pick another task when reaching the end of picking is shown.
Only facilities with the shipping type are considered in the routing decision in a ship-from-store order.
#### Facility tags If [tags](/documentation/getting-started/tags.md) have been created, these are available in the dropdown to add to the facility. ## Fulfillment times and capacity Fulfillment times are the days and times on which fulfillment is performed for a facility. They might not match a facility's opening times. Fulfillment times can be configured individually for each day. Fulfillment times are considered within fulfillmenttools, for example, when a [target time](/documentation/by-pillar/store-operations/picking/pick-job-target-time.md) is generated or when a [time-triggered reroute](/documentation/by-pillar/advanced-order-routing/reroute.md#time-triggered-reroute-for-started-pick-jobs) takes place. The fulfillment capacity can be defined for each time slot within the facility settings. It reflects the number of orders, and therefore pick jobs, that can be fulfilled in the time slot. When an order is routed to a facility with capacity information, the facility's capacity is reduced by the order's quantity for the next available [capacity slot](/documentation/by-pillar/advanced-order-routing/ratings.md#ratings-nextfreecapacity-2). To ensure that fulfillment capacities are considered in routing, the capacity [fence](/documentation/by-pillar/advanced-order-routing/fences.md#facility-capacity) or [rating](/documentation/by-pillar/advanced-order-routing/ratings.md) must be activated.
{% hint style="info" %} If fulfillment times are not configured, a tenant-level fallback is used. By default, fulfillment times are Monday to Saturday, from 09:00 to 17:00. {% endhint %} For more information on how the target time of an order is calculated considering capacities, see the [Order target time calculation section](/documentation/by-pillar/store-operations/picking/pick-job-target-time.md). ## Non-fulfillment days Non-fulfillment days are days on which no fulfillment occurs, such as public holidays. You can set a specific date that will occur only once, or set an annual occurrence. To add a new non-fulfillment day, click the **Add day** button. Use the **X** button to delete an existing non-fulfillment day. {% hint style="warning" %} Fulfillment closing days can also be configured in the [network settings](/documentation/backoffice/network-view/settings.md) for multiple facilities. Saving a bulk update for fulfillment times and closing days overwrites any previously submitted times for the selected facilities. {% endhint %}
## Average fulfillment duration Average fulfillment duration is the lead time or buffer time required for an order to be ready for handover to the shipping provider or the consumer. This corresponds to the time from the creation of the pick job to the completion of the handover. It's used in fulfillmenttools to calculate whether successful order completion can be ensured at a facility. {% hint style="info" %} The default fulfillment duration when creating a new facility is 240 minutes. This can be a tenant-wide setting or only the selected facility. {% endhint %}
## Carrier You can assign different carriers to a facility. With this information, a [fence](/documentation/by-pillar/advanced-order-routing/fences.md#carrier-availability) can be implemented where orders that need to be shipped by a chosen carrier are routed to a facility where this carrier is active. Carriers enabled at the tenant level must also be enabled for the facilities where the carrier is available. Pickup times can be configured for each carrier at each facility using the more icon. This time represents when a carrier usually comes to the facility to collect parcels for shipping. This is also known as the cutoff time.
## Short pick A short pick describes a case where an order could not be fully picked. This can happen when some ordered items are too low in stock or out of stock. By enabling this configuration, stock for an item in a facility is set to zero if nothing or not enough can be picked for that item. {% hint style="warning" %} It's strongly recommended to activate the `confirmationOnShortPick` in the [picking configuration](/documentation/by-pillar/store-operations/picking.md#picking-configuration) simultaneously. Otherwise, fulfillmenttools can't differentiate between cases where the user tried to pick an item and failed due to no stock available, and cases where the pick job was rerouted before the user tried to pick all ordered items. {% endhint %}
## Storage principles Storage principles for stock properties (such as best-before date) can be defined for each facility. The unmixed storage principle means that the same item with different properties (for example, best-before date) must not be stored in the same storage location. Enabling unmixed storage has the following effects: * If a user tries to stow the same items with different properties in the same storage location, a user prompt is shown. * For storage location recommendations, only locations that meet the unmixed storage principle are shown. The unmixed storage configuration should be deactivated if stock properties aren't relevant while stowing or relocating items.
## Discounts Facility discounts determine the value by which the [sales price](/documentation/getting-started/facilities/prices.md#sales-price) of the facility's listings is reduced for a specific group. It's configured on the facility that supplies the listing to other facilities. Discounts can be defined for a facility, a [group of facilities](/documentation/getting-started/facilities/facility-groups.md), or a group of articles ([category](/documentation/by-pillar/global-inventory-hub/categories.md)). In Backoffice, you can only view existing facility discounts. To create a new discount, it needs to be done via the API. {% hint style="info" %} More information can be found in the [Facility discounts article](/documentation/getting-started/facilities/facility-discounts.md). To enable facility discounts in Backoffice, [contact our Support team](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1/group/13/create/47). {% endhint %} --- # 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/facilities.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.