> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/sales/sales-order/backorders.md).

# Backorders

Backorder quantity is the number of units that are left unshipped or unfulfilled on a sales order. This normally happens if the item(s) is currently not in stock or ready for immediate delivery. When this happens, the seller may partially fulfill the order with the available inventory and place the remaining quantity on backorder.

The backorder procedure allows you to ascertain the quantity that is currently unavailable, and when the inventory is restocked, you can dispatch the necessary quantity to your customers.

### How do backorders work?

You can define the backorder quantity on the sales order, indicating how much should be waved or fulfilled and how much should be kept on backorder. You can then proceed to fulfill the available quantity.

To handle the backorders, two new app configs, "**Enable Backorder Qty on SO**" and "**Block Operations for Back Order Qty**" have been added.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FxQp8GDT6A93zWf7BoEGA%2Fimage.png?alt=media&amp;token=8aced6d8-6483-478d-91f8-f16746c7cc26" alt=""><figcaption></figcaption></figure>

**a. Enable BackOrder Qty on SO:** If this setting is on the User can block the item qty to be waved/shipped.

**b. Block Operations on the item to be waved/shipped for BackOrder Qty:** Block Operations on the item to be waved/shipped for BackOrder Qty.

This config has two options i.e. **Create Wave, Ship.**

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FaPiiopY2LQKIlS1ddsvV%2Fimage.png?alt=media&amp;token=38048ffa-f273-4283-8b15-830c177b857f" alt=""><figcaption></figcaption></figure>

* **Create Wave:** If the user selected this option then the user can only allocate the remaining qty (qty-backorder) qty.

  For Example, OrderQty=10, BackOrderQty= 6, Output (10 – 6) = 4 (User can allocate 4 units).

  Eg2: OrderQty= 10, BackOrderQty= 6, QtyShipped= 3, Output (10 – 6 – 3) = 1 (User can allocate 1 unit).\
  \
  If this option is selected and backorder quantity has been defined, this is how wave creation will work:

  * **Manual Wave** – Wave can only be created for the remaining qty(order qty – qty backorder
  * **Full Order Only** – User cannot create wave if backorder qty > 0
  * **Allocate full lines**  – User cannot create wave if backorder qty > 0
  * **Allocate what’s available lines**  – Allocate (remaining qty – backorder qty)<br>
* &#x20;**Ship:** If the user selected this option then the User can allocate full qty but **can only ship/pick the remaining (qty-backorder) qty.**

  \
  For Example, OrderQty=10, BackOrderQty= 6, QtyAllocated=10, Output: 4 (User can ship/pick 4 units.

  \
  In case **both options are selected in the app config i.e. Create Wave & Ship:**&#x20;

  For Example, OrderQty=10, BackOrderQty= 6, QtyAllocated= (10 – 6= 4), Output= 4 User can ship/pick 4 units.

### How to handle backorders in Sales Order?

To handle the backorders, you begin by defining the backorder quantity on the sales order. Then, depending on the option selected in the app config, the order will be processed. Let's see how this works.

* In the Sales Order, when adding the items, define the "BackOrder Qty" and add the item to the order.

  <figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2F3mkZ3bv3z7mlX48LOyE4%2Fimage.png?alt=media&amp;token=1efd550d-59e9-4730-94d7-fb4b6febecb6" alt=""><figcaption></figcaption></figure>
* Save and Release the order.

  <figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2Fe2sOkgbbIrS1tMrmCzI9%2Fimage.png?alt=media&amp;token=f2a73ee3-cb3c-4071-8d80-45c210cfcf65" alt=""><figcaption></figcaption></figure>
* If you try to allocate or ship the entire order, the system will throw an error depending on the app config.

  <div align="left"><figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FifBsiW5VX17aprGvyBpI%2Fimage.png?alt=media&amp;token=0b76a0b4-f21b-48b3-80ef-b19c6a8e506b" alt=""><figcaption></figcaption></figure></div>
* You can ship the available quantity. When the remaining units are available, you can update the backorder quantity and process the order.

#### Can I Create a Sales Order Before Receiving the Goods and Fulfill It Later?

Yes. XoroERP allows you to create and release a Sales Order before the ordered goods are physically received. This lets you record customer demand in advance and fulfill the order once the inventory becomes available.

However, creating an advance Sales Order does not add unreceived goods to your physical inventory. Incoming supply and customer demand are tracked separately.

**How does the process work?**

1\. Record the incoming stock through a Purchase Order (PO).

* An Open Purchase Order appears under On PO (Draft) in the Item Inventory Snapshot.
* Once the PO is released, its outstanding quantities appear under On PO.
* This allows you to track expected inventory without recording it as received stock.

2\. Create the advance Sales Order (SO).

* Navigate to Menu > Sales > Sales Order.
* Select the customer, Sale Store, and Ship Store.
* Add the required items and quantities.
* Enter the To Be Shipped date or a line-level Ship Date, as applicable.
* Save the order. It starts with Open status unless the Auto Release Sales Order configuration applies. You can release it before the goods arrive.

Note: Creating a Sales Order does not post an accounting sale or increase inventory.

3\. Track incoming supply and sales demand.

The Item Inventory Snapshot provides visibility into both:

* On SO (Draft): Quantities on open Sales Orders.
* On SO: Quantities on released but unshipped Sales Orders.
* ATS: Available stock after accounting for released Sales Order demand.
* ATS (Inc PO): Available stock after also including quantities from released Purchase Orders.

ATS (Inc PO) is a planning figure. It does not mean the incoming goods are physically available for fulfillment.

4\. Optionally track quantities pending fulfillment.

Enable the Enable Backorder Qty on SO App Config to use the BackOrder Qty field on Sales Order lines. This field helps identify quantities that are not yet ready to be fulfilled.

This configuration is optional and is not required simply to create an advance Sales Order.

5\. Receive the goods and fulfill the Sales Order.

* Once the goods arrive, complete the receiving process through Item Receipt.
* If warehouse processing is enabled, the receipt can be generated when the ASN is received and closed.
* The receipt increases the on-hand inventory.
* Reduce or clear the applicable BackOrder Qty, if used.
* Allocate the available stock using Options > Create Wave - Manual or Options > Create Wave - Auto.
* Complete picking and shipping.

You can fulfill the Sales Order partially while the remaining quantity stays pending. If warehouse processing is enabled, shipping generates the invoice.

In summary: You can accept customer orders before inventory arrives by creating and releasing Sales Orders against incoming Purchase Orders. XoroERP tracks the expected supply and committed demand separately, allowing you to plan fulfillment without treating unreceived goods as available physical stock.

**Settings, permissions and limitations**

* **Keep the preorder from being cancelled automatically.** If **Auto-Cancel Sales Order on Inventory Shortage** is enabled, selecting **Auto Update Cancel Qty On SO?** in the **Other** tab cancels unfulfillable quantities when the order is saved. Leave that order option off when the intention is to retain the shortage for later fulfillment.
* **Backorder controls affect fulfillment.** The backorder restriction options **Create Wave** and **Ship** can prevent allocation and/or picking/shipping of the held quantity. **BackOrder Qty** cannot be negative or exceed the remaining unshipped quantity; other committed quantities can further limit it. Update it when those units are ready to fulfill rather than assuming receipt clears the hold automatically.
* **Order acceptance is not a stock reservation.** Normal wave allocation requires available inventory. An order for incoming stock does not, by itself, reserve physical stock. **Minimum Fill Rate %** can also affect order processing where specified.
* **Access still applies.** Users need the appropriate rights through **Access Manager** and store access through **User Store Mapping**. **Restrict Released Sales Order Modifications**, when enabled, requires authorized approval for changes to released orders.
* **Do not use stock adjustment as a substitute for a preorder.** **Auto Inventory Adjustment** can add a stock shortage to inventory records during eligible automatic wave creation. That changes recorded stock; it is not the same as keeping goods pending receipt. Direct invoicing also reduces inventory and is not simply advance-order booking.


---

# 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.xorosoft.com/xoroerp-1/sales/sales-order/backorders.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.
