Pickwave Generation Rules
Pickwave Generation Rules help automate the creation of pickwaves for a warehouse. Instead of manually creating pickwaves throughout the day, you can configure rule sets and schedules so StoreFeeder creates them at the right time for the right operational process.
This feature is currently in early access and should be live soon.
You can find this page under:
V2 - Settings - > Warehouse Management > Pickwave Generation rules
New pages - Settings > Warehouse > Pickwave Generation Rules
What is a pickwave generation rule?
A pickwave generation rule defines which orders should be considered for a pickwave and how that pickwave should be created.
A rule set can support processes such as:
- Priority order picking
- Courier-specific picking
- Next-day or Prime order picking
- Single-line or multi-line picking
- Warehouse or zone-based picking
- End-of-day catch-up picking
Creating a rule set
When creating a rule set, start with the warehouse process you want to support.
A good rule set should answer:
- Which orders should this rule find?
- What should happen once those orders are found?
- Should the pickwave only be created once enough orders are available?
- Should the rule run automatically on a schedule?
Use clear names, such as DPD Next Day Orders, Prime Orders, Zone A Picking, or End-of-Day Catch-Up.
Available options
Pickwave Generation Rules include two broad types of options:
| Type | What it does |
|---|---|
| Order filtering options | Decide which orders are eligible for the pickwave |
| Pickwave creation options | Control how StoreFeeder creates the pickwave once matching orders have been found |
This distinction matters. A courier option filters the orders. A picker, minimum size, or split-by-courier option controls what happens when the pickwave is created.
Order filtering options
These options are used to find the orders that should be included.
| Option | What it is used for |
|---|---|
| Priority | Includes or excludes priority orders |
| Courier | Finds orders assigned to a selected courier |
| Shipping Method | Finds orders using a selected shipping service |
| Warehouse | Finds orders for a selected warehouse |
| Warehouse Zone | Finds orders allocated to selected warehouse zones |
| Priority Warehouse Zone | Uses priority zone logic when selecting eligible orders |
| Country | Finds orders by delivery country |
| Channel | Finds orders from a selected sales channel |
| Tag | Finds orders with selected order tags |
| Amazon Prime | Finds Amazon Prime orders |
| Amazon Business | Finds Amazon Business orders |
| Amazon Easy Ship | Finds Amazon Easy Ship orders |
| Business Order | Finds business orders |
| Attention Required | Includes or excludes orders that need attention |
| Product SKU | Finds orders containing selected products |
| Products in Bulk Only | Finds orders where products are held or picked from bulk-only locations |
| Multiple Lines | Separates single-line and multi-line orders |
Pickwave creation options
These options control what happens after matching orders have been found.
| Option | What it is used for |
|---|---|
| Picker | Assigns or controls the picker used when the pickwave is created |
| Minimum Order Quantity | Only creates a pickwave when enough matching orders exist |
| Minimum Pickwave Size | Sets the minimum number of orders required before a pickwave is generated |
| Maximum Pickwave Size Override | Overrides the usual maximum pickwave size for this rule set |
| Split by Courier Override | Controls whether matching orders should be split into separate pickwaves by courier |
| Consolidated Tote Size | Controls grouping based on tote size requirements |
How rules work together
When multiple filtering options are added to a rule set, StoreFeeder uses them together to decide which orders qualify.
For example:
Courier = DPD
Priority = Yes
Country = United Kingdom
This would target priority UK orders assigned to DPD.
Pickwave creation options are applied after the matching orders have been found. For example, a rule set might find matching DPD orders, then assign the pickwave to a selected picker, only create the pickwave once the minimum size has been met, or split the orders by courier depending on the selected options.
Avoid making rules too strict. If the conditions are too narrow, no orders may match and no pickwave will be created.
Scheduling a rule
A rule set can be scheduled so StoreFeeder runs it automatically at selected times.
When scheduling a rule, users can configure:
| Option | What it does |
|---|---|
| Enabled / disabled | Turns the schedule on or off without deleting it |
| Warehouse | Selects the warehouse the schedule applies to |
| Run this rule on | Selects the days of the week the rule should run |
| Every week day | Quickly selects Monday to Friday |
| Every day | Quickly selects every day of the week |
| At | Sets the time the rule should run |
| Add time | Adds additional run times for the same selected days |
For example, a rule can be scheduled to run for a selected warehouse on Tuesday and Wednesday at 10:15 and 10:30.
Running a rule manually
Rules can also be run manually when you need to create a pickwave outside of the normal schedule.
When running a rule manually, make sure you select the correct warehouse before starting the process. The selected warehouse controls where the pickwave will be created, so choosing the wrong warehouse may create the pickwave in the wrong operational area.
Manual runs are useful for:
- Creating an extra pickwave during busy periods
- Re-running a rule after new orders become eligible
- Testing a rule before relying on a schedule
- Running an end-of-day catch-up pickwave
Scheduling best practices
Schedule rules around real warehouse activity, such as shift starts, courier cut-offs, packing deadlines, and final dispatch checks.
Use multiple run times when the same rule needs to run more than once during the day.
Avoid scheduling several similar rules at the exact same time, especially if they may target the same orders.
Leave enough time after each scheduled run for orders to be picked, packed, and dispatched.
Disable schedules that are no longer needed rather than leaving old automation running unnoticed.
End-of-day catch-up process
It is good practice to have a final end-of-day process to catch orders that were not included in earlier pickwaves.
This could be:
- A manual review of remaining eligible orders
- A broader, less restrictive rule set
- A final scheduled run near the end of dispatch
This is especially useful if stricter rules are used throughout the day for specific couriers, services, zones, or order types. A catch-up process helps reduce the chance of eligible orders being missed before dispatch cut-off.
Use it as a safety net, not as a replacement for well-configured rules during the day.
Best practice recommendations
Keep rule sets focused and easy to understand.
Use clear names that describe the purpose of the rule set.
Start with simple filtering options, then refine once you have checked the results.
Separate filtering logic from pickwave creation logic. Ask: which orders should this rule find? and what should happen once those orders are found?
Use minimum quantities and pickwave size options carefully. If thresholds are too high, orders may sit waiting unnecessarily.
Review generated pickwaves regularly to make sure the rules and schedules still match the warehouse process.
Troubleshooting
If no pickwave is created, check that:
- The schedule is enabled
- The correct warehouse is selected
- The correct days and times are selected
- Matching orders exist
- Any minimum quantity or minimum pickwave size has been reached
If the wrong orders are included, the filtering options may be too broad.
If expected orders are missing, they may not match the filtering conditions, may already be in another pickwave, may not meet the pickwave creation options, or may not yet be eligible for picking.
Comments
0 comments
Article is closed for comments.