> 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/complex-routing-with-combinatorics/routing-simulation-test-orders.md).

# 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
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/complex-routing-with-combinatorics/routing-simulation-test-orders.md?ask=<question>&goal=<user_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.