Contents x
    Waveflow
    • 08 May 2025
    • 2 Minutes to read
    • Print
    Contents

    Waveflow

    • Updated on 08 May 2025
    • 2 Minutes to read
    • Print
    Article summary

    Understanding Waveflow

    What is Waveflow?


    A Waveflow is a predefined sequence of processes that are executed automatically after a Wave is run in Shipment Planner. These processes occur in chonological order and define how shipments are treated post-wave.

    For example, a common Waveflow step in Canary7 is "Reject Part Allocated Shipment", where:

    • After the Allocation step, the system checks if Shipments have been fully allocated.
    • If not, these Shipments are rejected and returned to the pool for future processing. Typically, a Replenishment plan would then be ran, allowing these Shipments to be allocated upon the next wave run.

    Another example would be "Split Shipment by Job Zone", where shipments allocated across multiple picking zones are split into separate sub-shipments for more efficient picking. Please find a full list of Waveflow details below.


    Accessing Waveflow

    To access Waveflow:

    1. Use the Navigation menu and type "Waveflow" into the search bar.

    2. Click on the Waveflow result.

    3. Alternatively, navigate to Configuration > Shipment Profile Setup > Waveflow.

    Creating a New Waveflow

    Click on the Red Action Buttonred action button, this will bring up a drop-down menu, and select "Add"

    add uom

    To add a new Waveflow:

    1. Click on Add.

    2. Enter a Name for the Waveflow.

    3. Optionally, add a Description for additional context.

    enter name of wave flow

    Description is an optional field

    Add to the Wave Detail list

    Within the details tab, click on the red action buttonred action button and click on "add".add wave detail list

    Select the Detail Option

    detail option select

    Wave Detail Options

    1. Allocation*
      Allocates items to the shipment based on the Allocation Rules assigned to that Shipment.

    2. Carrier Firewall
      Validates if the selected carrier is appropriate (e.g., postcode compatibility or weight constraints).

    3. Split Detail Children
      Breaks down consolidated shipment detail children into individual quantities.

    4. Add Consignment Pieces
      Marks allocated items as consignment pieces, useful for large or heavy items that will require individual labelling.

    5. Add Batch Number
      Assigns batch numbers to allocated items.

    6. Create Job Instruction Groups
      Groups picking instructions from multiple shipments ideal for reducing repetitive picking. Note: This must also be enabled on the picking profile.

    7. Split Shipment
      Splits a shipment into sub-shipments based on the job zones they are allocated from.

    8. Shipment Picking Job Creation*
      Creates picking jobs using the assigned Shipment Picking Job Creation configuration.

    9. Load Assignment*
      Automatically assigns a load to the shipment(s). There are three options for Load Assignment: Assign to Oldest Load, Assign to Oldest Load of the Same Day, or Assign a Load Per Shipment.

    10. Reject Part Allocation
      Rejects partially allocated shipments and returns them to the pool.

    11. Reject Shipments Not Suitable for Consigning
      Filters out shipments that don’t meet consignment criteria and returns them to the pool (e.g., weight, postcode range).

    12. Consign to Carrier
      Automatically consigns the shipment to the selected carrier, using Carrier Assignment Master.

    13. Print Consignment Paperwork
      Prints shipping labels, packing slips, and other documentation. Occurs after consigning.

    14. Consolidate Detail Child
      Consolidates similar items (different locations, batches, UoMs) into one pick line.

    15. Dispatch Held
      Holds the shipment from dispatching until manually released.


    Note: Options marked with * are essential for Waveflow to function correctly.


    Click on the Apply Buttonapply to add your detail option, and add as many of them that are needed for your specific use case.

    Was this article helpful?
    What's Next