> 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/admin/route.md).
# Route
### Overview
The **Route** module enables organizations to define delivery schedules that can be assigned to customers and automatically applied during the sales fulfillment process. By configuring delivery days and shipment lead times for each route, XoroERP can automatically determine the appropriate **Ship Date** and **Delivery Date** for Sales Orders, reducing manual planning and ensuring deliveries are scheduled accurately.
A Route represents a predefined delivery schedule for a group of customers or a geographical delivery area. Each Route can include one or more delivery days and a configurable Ship Date Offset, allowing the system to calculate when an order should be shipped in order to meet its scheduled delivery date.
Once a Route is assigned to a customer, it is automatically populated when creating a new Sales Order. XoroERP then uses the Route configuration to determine the next available delivery schedule and calculate the corresponding shipment dates.
The Route module works closely with the **Shipment Delivery** module. After shipment and delivery dates are determined, users can create and manage Shipment Deliveries directly from Sales Orders, ensuring a streamlined and automated delivery workflow.
***
### Fields and Options
### Route Details
The following fields are available when creating or modifying a Route.
| Field | Description |
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** \* | Specifies the name of the Route. Choose a descriptive name that clearly identifies the delivery route or service area. |
| **Code** \* | A unique identifier for the Route. This code can be used to quickly identify and reference the Route throughout the system. |
| **Description** | Provides additional information about the Route, such as delivery region, transportation method, or operational notes. |
| **Delivery Days** \* | Specifies the days on which deliveries are scheduled for this Route. Multiple days can be selected, allowing the same Route to support deliveries throughout the week. |
| **Ship Date Offset (Calendar Days)** | Specifies how many calendar days before the Delivery Date an order should be shipped. For example, a value of **-4** indicates that the shipment should be dispatched four calendar days before the scheduled delivery date. If left blank, the system automatically considers the value as **0**. |
***
#### Header Options
The following Header Options are available in the Route module.
| Option | Description |
| ---------- | --------------------------------------------------------------------------------------------------------- |
| **Save** | Saves the Route configuration and makes it available for assignment to customers and Sales Orders. |
| **Delete** | Deletes the selected Route, provided it is not restricted by system validations or existing dependencies. |
***
### Use Cases
#### Configure Delivery Schedules
Organizations can create Routes with one or more delivery days to establish recurring delivery schedules for different delivery regions, transportation methods, or customer groups.
***
#### Automate Ship and Delivery Date Calculation
Once a Route is assigned to a customer, XoroERP automatically calculates the appropriate **Ship Date** and **Delivery Date** whenever a Sales Order is created. The calculation is based on:
* Sales Order Date
* Configured Delivery Day(s)
* Ship Date Offset
This eliminates manual scheduling and ensures deliveries are planned according to predefined business rules.
***
#### Standardize Customer Deliveries
Assigning a default Route to customers ensures every new Sales Order follows a consistent delivery schedule without requiring users to manually select a Route for each order.
***
#### Support Multiple Weekly Deliveries
A single Route can contain multiple Delivery Days, enabling organizations to schedule deliveries several times a week while allowing the system to automatically determine the next available delivery date.
***
#### Improve Delivery Planning
Using the Ship Date Offset, warehouse and logistics teams can accurately determine when orders need to be shipped to meet their scheduled delivery dates, improving fulfillment planning and operational efficiency.
***
#### Simplify Logistics Management
By centralizing delivery schedules within the Route module, organizations can easily maintain, update, and reuse delivery configurations across multiple customers and Sales Orders.
***
#### Route Scheduling Example
The following example demonstrates how XoroERP automatically determines the appropriate **Ship Date** and **Delivery Date** based on the configured Route, Delivery Days, Ship Date Offset, and the Sales Order Date.
**Scenario**
* **Sales Order Date:** Wednesday, **07/22/2026**
* **Assigned Route:** AIR 6
* **Configured Delivery Days:** Monday, Tuesday, and Friday
* **Ship Date Offset:** **-2 Days**
Based on the configured route, the system first calculates the possible shipment dates for each available delivery day:
| Delivery Day | Ship Date (Delivery Day - 2 Days) |
| ------------ | --------------------------------- |
| Monday | Saturday |
| Tuesday | Sunday |
| Friday | Wednesday (**07/22/2026**) |
When the Sales Order is created on **Wednesday, 07/22/2026**, the shipment dates for the Monday and Tuesday delivery schedules have already passed. Therefore, those delivery windows are no longer eligible.
The system automatically selects the **next available delivery schedule** that can still be fulfilled based on the Sales Order date. In this case:
* The earliest valid **Ship Date** is **Wednesday, 07/22/2026**.
* The corresponding **Delivery Date** is **Friday, 07/24/2026**.
As a result, the order is scheduled to:
* **Ship On:** Wednesday, **07/22/2026**
* **Deliver On:** Friday, **07/24/2026**
This automatic scheduling ensures that every Sales Order is assigned the earliest possible delivery date that satisfies the configured route schedule and ship date offset, eliminating manual date calculations and helping deliveries remain on schedule.
### Relationship with Shipment Delivery
The **Route** and **Shipment Delivery** modules work together to automate the delivery planning and fulfillment process.
The typical workflow is as follows:
1. Create and configure a Route by defining its Delivery Day(s) and Ship Date Offset.
2. Assign the Route as the default Route for one or more customers.
3. Create a Sales Order.
4. XoroERP automatically assigns the customer's Route and calculates the appropriate Ship Date and Delivery Date.
5. Create a **Shipment Delivery** directly from the Sales Order.
6. Process and manage the Shipment Delivery through the Delivery Manager until the order is delivered.
By combining Route Scheduling with Shipment Delivery, organizations can automate delivery planning, reduce manual scheduling, improve shipment accuracy, and maintain complete visibility throughout the order fulfillment lifecycle.
{% hint style="info" %}
**Related Module:** **Shipment Delivery** — The Shipment Delivery module uses the delivery schedule generated by the Route module to create, manage, and process deliveries from Sales Orders.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.xorosoft.com/xoroerp-1/admin/route.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.