Transfer orders overview
Audience: Inventory managers and center admins who move stock between centers within the organization. For franchise models, also see Purchase orders overview.
On this page
- Push vs pull
- Before you create a transfer order
- Lifecycle of a transfer order
- Worked example β partial delivery
- Quantity rules
- Who can edit a raised transfer order
- Return transfer orders
- Automatic transfer orders
- Store and floor impact
- When NOT to use transfer orders β franchise model
- Related articles
A transfer order lets you move products between centers in your organization. Instead of purchasing from an external vendor, you use transfer orders to redistribute existing stock from one center to another. Transfer orders support both warehouse-to-center distribution and center-to-center stock balancing.
Push vs pull
Transfer orders involve two centers:
- Source center β The center that sends products.
- Destination center β The center that receives products.
There are two initiation models:
- Push β The source center creates and raises the transfer order on behalf of the destination. Typical for a warehouse distributing to centers.
- Pull β The destination center creates and raises the order to the source. Typical when a center proactively requests stock from another center or from the warehouse.
A transfer order always uses the transfer price and transfer tax of the source center. These are per-product, per-center fields configured on the Product Master screen; they may differ from the sale price and sale tax used at POS (Point of Sale). Contact your admin if the transfer price is unset or shows unexpected values.
Before you create a transfer order
- The product must be associated with both the source and destination centers before a transfer order can include it. "Associated" means the product is active at the center on the Product Master association screen β it does not require non-zero stock at the destination. See Associate vendors and products.
- Your role must have the Add and RAISE_ORDER actions under Inventory at the initiating center (source for push, destination for pull). The receiving center needs at least the Edit action to record the delivery.
- For automatic transfer orders, see Automatic transfer orders and Configure automatic orders.
Lifecycle of a transfer order
A transfer order moves through several stages from creation to full delivery:
| Status | Description |
|---|---|
| Created | The order is saved as a draft. You can edit order details, add products, or remove products. |
| Raised | The order is raised and submitted to the other center. |
| Updated | The order details have been modified after the initial recording β typically through a Modify Delivery action, or when the destination center enters received quantities and saves the draft without marking partial delivery. Current stock is not yet affected at the destination. |
| In transit | The order is dispatched from the source center. The destination center cannot edit the dispatched quantity. |
| Partially delivered | The destination center has received some but not all of the dispatched quantity and committed the delivery. Current stock at the destination increases by the committed quantity. |
| Delivered | The destination center has received the full dispatched quantity (or exercised the over-receive override β see below). The order is closed. |
The Updated and Partially delivered states are both "partial" receptions, but Updated is a saved draft that has not yet posted to stock, while Partially delivered is a committed partial that has. Saving as Updated lets the destination pause receipt without impacting stock; committing as Partially delivered posts the current received quantity and leaves the order open for the remainder.
View in-transit transfer orders. Navigate to Inventory > Orders and apply the Status filter set to In transit. See Manage transfer orders for the full procedure.
Worked example β partial delivery
A warehouse has 100 units of a shampoo product. The sequence:
- Day 1: Warehouse raises a push transfer order to Center A for 40 units. Status: Raised. Warehouse stock: 100 (unaffected until dispatch).
- Day 2: Warehouse dispatches 35 units (3 units short of the raised quantity β see Quantity rules). Status: In transit. Warehouse stock: 65.
- Day 3: Center A receives 30 units, enters the received quantity, and saves as a draft. Status: Updated. Center A stock: unchanged.
- Day 4: Center A commits the partial receipt. Status: Partially delivered. Center A stock: +30.
- Day 6: Center A receives the remaining 5 units and marks the order fully delivered. Status: Delivered. Center A stock: +35 total.
Quantity rules
Two separate rules govern quantities on a transfer order:
- Receive vs dispatch. The destination center's received quantity must equal the dispatched quantity by default. Organizations can configure a setting to allow the destination to enter a received quantity greater than the dispatched quantity (useful when the dispatch count was understated); the destination still cannot enter a received quantity less than dispatched β shortfalls are handled by closing the line with a zero remaining balance.
- Dispatch vs raised. The source center can dispatch a quantity less than or more than the raised quantity, giving the source discretion over what it actually sends. This is the expected behavior and does not require a setting toggle.
Who can edit a raised transfer order
After the source center dispatches an order, the destination center cannot edit product-level fields such as MSRP (or your configured retail price label), Unit Price, Retail / Received, Consumable / Received, Discount, and Taxes. The source center can still edit these fields before the order is marked Partially delivered, Delivered, or closed.
Return transfer orders
Create a return transfer order to send stock back to the source center β for example, when products are damaged, expired, or no longer needed at the destination. A return transfer order is created at the center holding the stock, follows the same lifecycle as a standard transfer order (Created β Raised β In transit β Delivered). It is an independent order: it carries a return flag and, when return reasons are enabled, a return reason β it does not reference the original transfer order. See Manage transfer orders for the procedure.
Automatic transfer orders
Zenoti can generate transfer orders automatically based on reorder levels, analyzing stock across centers to move surplus from one center to a deficit center. When the Consider raised purchase orders/transfer orders for calculating Auto PO/TO quantity organization setting is enabled, raising a transfer order updates the undelivered quantities on inventory alert reports and reduces the recommended reorder level accordingly.
For configuration, see Configure automatic orders.
Store and floor impact
Transfer dispatch decrements the source center's Store quantity. Transfer receipt increments the destination center's Store quantity. Neither operation writes directly to Floor. To move received stock to Floor at the destination, run a stock adjustment after receipt. For the store/floor model and how it affects audits and reports, see Store and floor inventory.
When NOT to use transfer orders β franchise model
Transfer orders assume all participating centers are in the same organization under a single ownership and permission model. In a franchise model where each franchise operates independently, the usual practice is for each franchise to raise a purchase order to another center or to the warehouse, rather than a transfer order. This is an operating convention, not a system restriction: the center-level Enable this center to act as a franchise setting records the designation but does not block transfer orders. The receiving franchise then records the PO delivery as if the sending center were an external vendor.
If your organization combines company-owned and franchise centers, apply this rule per relationship: use transfer orders between company-owned centers and use purchase orders between franchise boundaries. See Purchase orders overview.
Related articles
Required next steps
Optional configuration
Related concepts
Reports and troubleshooting