Warehance has two distinct priority fields that control when and how orders move through fulfillment. Understanding the difference helps you route urgent orders ahead and manage inventory allocation when stock is limited.
Overview
| Field | Type | Default | Where It Affects Order Flow |
|---|---|---|---|
| Priority | Yes/No (boolean) | No | Batch shipping, picking |
| Allocation Priority | Number (1–100) | 1 | Inventory allocation |
Priority (Order Flag)
Priority is a simple Yes/No flag. When set to Yes, the order is treated as higher priority in batch creation and picking.
Where It Applies
- Batch Shipping: When creating a batch, orders with Priority = Yes are added first. Sort order: Priority DESC → Order Date ASC → Required Ship Date ASC.
- Picking: When getting the next order to pick, Priority = Yes orders are chosen before others. Sort order: Priority DESC → Shipping Method Priority DESC → Order Date ASC → Required Ship Date ASC.
How to Set It
- Open the order, go to Settings → Common Settings, and check Priority.
- Use Bulk Update on the Orders table to set Priority on multiple orders.
- Use an automation rule with the Set Priority action (Yes or No).
Priority is a binary flag. Use it when you need a clear “rush” vs. “normal” split.
Allocation Priority
Allocation Priority is a numeric value (1–100). Higher numbers mean higher priority. It controls which orders receive inventory first when there is not enough stock for everyone.
Where It Applies
- Inventory Allocation: When allocating inventory to orders, Warehance sorts by Allocation Priority (highest first), then Required Ship Date (earliest first), then Order Date (earliest first). Orders with higher allocation priority get stock before lower-priority orders.
How to Set It
- Open the order, go to Settings → Common Settings, and set Allocation Priority (if your org has this field enabled).
- Use Bulk Update to change allocation priority on multiple orders.
- Use an automation rule with the Set Allocation Priority on Order action (1–100).
Allocation Priority is only shown if your organization has enabled it (or if you are an org admin). Client users may not see it depending on org settings.
How They Interact
- Priority affects which orders get into batches and which order is picked next.
- Allocation Priority affects which orders get inventory first when stock is limited.
They do not override each other. A high Allocation Priority does not change batch or picking order, and a high Priority does not change allocation order.
Example
- Order A: Priority = Yes, Allocation Priority = 1
- Order B: Priority = No, Allocation Priority = 10
- Batch creation / picking: Order A is chosen before Order B.
- Allocation: Order B gets inventory before Order A when stock is limited.
Other Fields That Affect Order Position
Required Ship Date
- Earlier dates are favored in allocation and picking.
- Used as a tiebreaker after Priority and Allocation Priority.
Order Date
- Earlier dates are favored when Required Ship Date is the same.
- Used as a tiebreaker in allocation and picking.
Hold Until Date
- Orders with holds are not ready to ship until the hold date passes.
- They are excluded from batch creation and picking until the hold is released.
Exclude From Batch Shipping / Exclude From Picking
- These flags remove the order from batch creation or picking entirely.
- Use them to keep orders out of automated flows without cancelling them.
Shipping Method Priority
- In picking, after Order Priority, orders are sorted by Shipping Method Priority (higher first).
- Configure this on the shipping method, not on the order.
When to Use What
| Goal | Use |
|---|---|
| Rush an order through batch creation and picking | Set Priority = Yes |
| Give an order first access to limited inventory | Increase Allocation Priority (e.g., 50 or 100) |
| Both rush and ensure it gets stock first | Set Priority = Yes and Allocation Priority high |
| Push an order behind others in allocation | Lower Allocation Priority (e.g., 1) |
| Push an order behind others in batches/picking | Set Priority = No |
| Keep an order out of batches or picking | Use Exclude From Batch Shipping or Exclude From Picking |
| Delay an order until a date | Set Hold Until Date |
Step 1: Set Priority on a Single Order
- Go to Orders and open the order.
- In the order details panel, open Settings → Common Settings.
- Check Priority to mark it as high priority, or uncheck to mark it as normal.
Step 2: Set Allocation Priority on a Single Order
- Open the order and go to Settings → Common Settings.
- If Allocation Priority is visible, enter a number (1–100). Higher = higher priority.
- Save.
Step 3: Bulk Update Priority or Allocation Priority
- Go to Orders.
- Select the orders you want to change.
- Click Bulk Update.
- Set Priority and/or Allocation Priority as needed.
- Apply the update.
Step 4: Use Automation Rules
- Create an automation rule with a trigger (e.g., order imported, tag added).
- Add an action: Set Priority or Set Allocation Priority on Order.
- Configure the value and save.
Automation rules let you set priority based on store, shipping method, tags, or other conditions without manual edits.
Troubleshooting
- Allocation Priority not visible: Your organization may have it disabled, or client users may not have access. Check org settings.
- Order still behind others in allocation: Confirm Allocation Priority is higher than competing orders. Check Required Ship Date and Order Date as tiebreakers.
- Order not in batch: Verify Priority = Yes if you expect it to be picked first. Ensure it is not excluded (Exclude From Batch Shipping) and that it is Ready to Ship.
- Order not getting inventory: Check Allocation Priority and any allocation holds. Orders with allocation hold are allocated but do not consume inventory until the hold is released.