> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fire.rest/llms.txt
> Use this file to discover all available pages before exploring further.
# Introduction
> FUEL is the internal testing and simulation workbench for the FIRE restaurant OS ecosystem.
FUEL (FIRE Unified Event Loader) is an internal tool used by QA, development, and operations teams to validate the full FIRE platform without depending on real clients, stores, or third-party providers. It works in two directions: loading test events into FIRE, and simulating the external systems that surround it.
## Two directions of operation
| Direction | What it does | Examples |
| ------------------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------- |
| **Loading into FIRE** | Sends events to FIRE endpoints as if they came from a real channel | Injecting orders via `POST /v1/orders`, cancelling via `POST /v1/orders/:id/cancel` |
| **Simulating external systems** | Acts as the external services FIRE talks to | KDS webhooks, fiscal callbacks (PlugNotas, country-specific), mock HTTP endpoints |
This lets you exercise end-to-end flows — across 7 countries and multiple environments — without touching production integrations.
## The 7 operational tabs
* **Single order** — Build and inject one order with full control over every field.
* **Batch** — Generate and send multiple orders at once with configurable distributions for channel, status, and processor.
* **Load sim** — Replay a realistic traffic pattern based on historical production data, compressed into a target duration.
* **Raw replay** — Search for production orders in FIRE (or pull from FUEL's stored samples) and re-inject them, optionally regenerating IDs.
* **Comparison** — Send the same order set to multiple scenarios side by side and compare results.
* **Cancel order** — Cancel an existing order by external order ID or order code.
* **Webhooks** — Send KDS events (`order.preparing`, `order.ready`, `order.dispatched`, `order.cancelled`), fiscal callbacks, and PlugNotas events; manage mock HTTP endpoints; and inspect the incoming events log.
## Operating context
Before using any tab, you must select your **operating context** in the sidebar. The context has five levels:
The FIRE environment (e.g., staging, production). Each environment is configured by a superadmin with a base URL and API key.
The account (brand or operator group) within that environment.
The country that governs tax rules, fiscal formats, and currency.
The vendor (restaurant concept) under the account.
The specific store location to target.
All five levels must be selected before FUEL can send any request. Tabs that require a test menu also need one configured for the selected vendor.
## Where to go next
Configure environments, accounts, and test menus.
Inject a single order with full field control.
Send multiple orders with configurable distributions.
Simulate peak traffic from historical patterns.
Search and re-inject production orders.
Cancel an order by ID or code.
Send webhook events and manage mock endpoints.
Compare injection results across environments.