Hi all,
I’m testing Order Orchestration in Acumatica 26R1 using Destination Priority with multiple warehouses and wanted to confirm the expected behavior when total available inventory across all eligible warehouses is insufficient.
Current setup:
- Fulfillment Strategy: Destination Priority
- Shipping Zone: EAST
- Warehouse priority:
- EAST
- CENTRAL
- WEST
- Order type is configured for Order Orchestration
- Will Call is cleared and the order is otherwise eligible for orchestration
I’ve confirmed the following behavior:
- If one warehouse can fulfill the full quantity, Acumatica may select that single warehouse.
- If no single warehouse can fulfill the quantity, but multiple warehouses can collectively cover it, Acumatica successfully splits fulfillment across those warehouses.
- If the total available quantity across all eligible warehouses is less than the sales order quantity, orchestration fails with:
“The order cannot be orchestrated due to insufficient stock across all available warehouses.”

The client requirement is slightly different. They want Acumatica to:
- Fulfill as much as possible from the prioritized internal warehouses.
- Split quantities across warehouses where necessary.
- If there is still remaining demand after all eligible warehouse inventory is exhausted, automatically convert the remaining quantity to drop ship from a vendor.
Example:
- Order Qty: 130
- EAST Available: 40
- CENTRAL Available: 30
- WEST Available: 20
- Total internal availability: 90
Desired result:
- 90 units fulfilled from internal warehouses
- Remaining 40 units converted to drop ship
Instead, standard orchestration currently appears to fail because total internal availability is less than the order quantity.
My questions are:
- Is there any standard configuration that allows orchestration to partially fulfill the available quantity and leave the remainder for another fulfillment method?
- Can the unfulfilled quantity be automatically converted to a drop-ship line or linked to a drop-ship PO using standard functionality?
- If not, has anyone implemented a customization extending Order Orchestration to support this type of warehouse-first / drop-ship-fallback logic?
- Is there a recommended extension point or event in the orchestration process for identifying the unsuccessful remainder and creating the drop-ship demand?
Any guidance or examples would be appreciated.