# Routing simulation Routing simulation enables the creation and evaluation of test orders directly in Backoffice. It allows administrators to validate routing behavior without affecting live operations. Test orders are processed using the currently active routing strategy, and the resulting metrics provide insights into assignment quality, delivery performance, and cost implications. Routing simulation provides several advantages for configuration management and operational transparency: * Routing strategies can be validated for correctness, ensuring that changes behave as intended. * The impact of strategy adjustments becomes immediately visible, enabling rapid iteration and controlled experimentation.
To access the routing simulation, click the **Routing simulation** button on the top right of the Routing screen. ## Creating a test order To create a new test order, click the **Create test order button** at the bottom of the **Routing simulation** table. This opens the create panel.
Backoffice provides two ways to create a test order: * [Form-based input](#form-based-input) * [Advanced mode](#advanced-mode) Both are created in the same panel. Once created, you can edit the test order at any time by hovering on the test order, clicking the more icon (3 dots), and selecting **Edit test order**. To delete the test order, select **Delete test order**. ### Form-based input The form-based input mask covers the majority of routing‑relevant order attributes. This includes customer information, items, quantities, delivery preferences, and other parameters that influence routing decisions. Input the relevant fields you'd like to use for your test order, then click **Continue**.
### Advanced mode The advanced mode allows users to create or edit a test order directly in a JSON editor. This mode provides full flexibility and supports all fields available in the `order` schema. Input your JSON, then click **Continue**.
## Running the simulation After a test order is created, the simulation can be started from Backoffice. Hover on the test order you want to run the simulation for, click the more icon (3 dots), and select **Run test order**. This will run the simulation, and the **Simulation results** screen will open.
The system routes the test order using the currently configured routing strategy. All routing rules, constraints, and prioritization logic are applied exactly as they would be for a live order. {% hint style="warning" %} If you change the routing strategy to get a different test result, this will affect live orders. {% endhint %} ### Simulation results The simulation result consists of several sections that summarize the routing outcome and highlight key performance indicators.
To return to the test order list, click **Routing simulation** in the breadcrumb navigation at the top of the screen. #### Key metrics The **Key metrics** section provides an overview of the most relevant metrics for evaluating the routing result. **Assignment rate** The assignment rate indicates the percentage of ordered items that were successfully assigned to a facility. If not all items could be assigned, an overlay displays which items were assigned and which items couldn't be fulfilled. **Calculated total costs** The calculated total costs represent the cost of fulfilling the order. These costs are only available if all required data for cost calculation is present (see the [Cost calculation in routing article](broken://spaces/wxw7CUWGaTQdU5nY8tU0/pages/HUUsioKlkiOGURVuGqfr)). Also, the total cost rating must be enabled with at least one cost factor. **Number of partial deliveries** This metric shows how many separate deliveries the recipient receives. The recipient can be either the consumer or a facility placing an internal replenishment order. **Calculated delivery date** The calculated delivery date represents the expected delivery day based on the routing result. The calculation logic is described in the [delivery date calculation section](broken://spaces/wxw7CUWGaTQdU5nY8tU0/pages/bx3q0EH6fghKZ48LMogY). #### Routing details The **Routing details** section provides two perspectives on how the routing result was generated. **Routing decision** The **Routing decision** view displays the complete sourcing path determined by the routing engine. It includes all participating facilities as well as the item transfers between them. For each transfer, detailed operational information can be reviewed, including target times, used packaging units, and intermediate handling steps. This view helps illustrate the end‑to‑end flow of items and highlights how the system combines facility capabilities, stock availability, and transfer options to construct the final routing solution. **Routing strategy** The **Routing strategy** view lists all fences and rating factors that were applied during the simulation. This includes active constraints, prioritization rules, and rating weights that influenced the decision. The **Rating** tab provides statistical insights into each routing factor, enabling a comparison between the selected routing result and alternative feasible solutions. This supports deeper analysis of why a specific routing path was chosen and how it performed relative to other potential outcomes. #### Routing configuration The Routing configuration section shows which ruleset was applied when routing the test order. It visualizes the decision path through the strategy tree and highlights which nodes and conditions were activated during evaluation. This allows users to trace exactly which strategy branch led to the final routing result. By reviewing the selected path, you can verify whether the intended logic was applied, understand why routing rules were triggered, and identify potential misalignments between routing strategy and operational expectations. --- # Agent Instructions: 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: ``` GET https://docs.fulfillmenttools.com/documentation/backoffice/network-view/orders/routing/routing-simulation.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.