# Routing simulation test orders

{% hint style="info" %}
If you would like to use these functionalities, [contact our Support team](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1) for more information and activation support.
{% endhint %}

The order simulation API evaluates an order without creating operational records or triggering fulfillment processes. The simulation uses the same routing, sourcing, and rule-evaluation logic that fulfillmenttools uses for production orders. It enables validation of configuration changes, routing behavior, and business rules without affecting stock, suppliers, or downstream systems.

The simulation runs on a dedicated resource and doesn't interact with reservations, stock movements, eventing, and so on.

### Purpose

Order simulations support the following use cases:

* Validation of routing behavior.
* Verification of rule configurations, such as fences, ratings, and facility connections.
* Quality assurance for changes to listing, facility, and facility connection data.
* Testing of order scenarios without creating productive orders.

{% hint style="info" %}
More sourcing options API information can be found in the [REST API documentation – Simulation orders](https://fulfillmenttools.github.io/fulfillmenttools-api-reference-ui/#post-/api/routing/sourcingoptions).
{% endhint %}


---

# 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/by-pillar/advanced-order-routing/complex-routing-with-combinatorics/routing-simulation-test-orders.md?ask=<question>
```

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.