> 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/by-pillar/advanced-order-routing/fences.md). # Fences A fence can be part of the routing rules and is required for a routing decision. If a facility can't meet the requirements of an order, the facility is excluded from the routing decision. This can lead to a situation in which no facility can meet the order's requirements. If this is the case, the order is returned to the pool and either included in upcoming routing decisions or deemed [unroutable](/documentation/by-pillar/advanced-order-routing/unroutable-orders.md). {% hint style="info" %} See the [Routing strategy API documentation](/documentation/apis/api-reference/routing-strategies.md). {% endhint %} A fence can be static or reactive. A static fence has no event trigger. If an order becomes [unroutable](/documentation/by-pillar/advanced-order-routing/unroutable-orders.md) because of a static fence, this order will remain in the unroutable order section. A reactive fence has an event trigger. This means fulfillmenttools constantly checks for events that might dissolve this fence so the order becomes routable. For now, only the complete stock fence can be set as a reactive fence. If an order becomes unroutable due to an out-of-stock situation and the items are [preorderable or backorderable](/documentation/by-pillar/advanced-order-routing/pre-and-backorders.md), the order gets routed automatically if stock becomes available. To determine which reactive fences would have made an order unroutable, fulfillmenttools sorts fences from static to reactive and ensures all reactive fences are processed with all entities. ## Standard fences fulfillmenttools provides predefined fences. See the table below.

Fence	Description	Notes	Fence type
Complete stock	Checks if all ordered items are available in the facility. This check already accounts for reservations and other stock that is unavailable for certain reasons.	The complete stock fence can't be combined with an order split.	Reactive
Service type	Checks whether the facility can fulfill the order's service type (ship-from-store standard, ship-from-store same day, or click-and-collect).		Static
Preselected facilities	Reduces the facility candidates considered from all facilities in the network to only the specified ones. This list must include at least one facility and applies only to ship-from-store orders.		Static
Carrier availability	Checks whether the consumer's chosen carrier is enabled at a given facility and can fulfill the order.		Static
Same-day delivery possible	Checks if there is a facility that has the service type ship-from-store and at least one active same-day carrier, and whether there is enough time for the facility to perform a same-day delivery.		Static
Country	Checks whether the facility's address is in the same country as the consumer's address. Only those facilities are considered.		Static
Facility capacity	Checks if there are any free fulfillment capacity slots available for a facility within a predefined future timeframe.		Static
Ensure minimum picking	Checks that at least one ordered item is in stock. If not, the facility is excluded from order routing.	Items bundled so they are not split during routing (see the custom services article) are treated as one in this fence. Meaning that if one item is missing in such a bundle, all items within this bundle are seen as missing.	Static

--- # 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/by-pillar/advanced-order-routing/fences.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.