Picking Waves

A picking wave groups the reserved stock for one carrier and one despatch location so it can be picked, labelled, packed and despatched together as a single unit of work.

What a wave is

Once a sale order is approved for despatch, its lines become stock moves reserved against a warehouse location. Rather than handling each order individually, the despatch team works in waves: a wave bundles together every reserved move that shares the same carrier and location, so one physical batch of picking, packing and despatch covers many orders at once.

Waves are not created from this screen

Waves are not built by hand. They are assembled automatically — by the daily auto-wave scheduler, the API, or, since November 2026, the Create waves now button at the top of this list (wave.create), which runs that same wave run on the spot and reports how many items it waved, skipped (for example an item with no carrier — give it one with Set carrier) and failed — which groups eligible reserved stock moves by carrier and location and creates the wave already in the Draft state. See Schedulers for how and when this runs. Since November 2026 the same run also builds each new wave's packages, so a wave normally arrives with its parcels ready. A move only joins a wave if it is reserved, ships from the wave's location and uses the wave's carrier (or has none). The nightly run also leaves out an item whose customer asked for delivery more than a few days away (wave.expects_on_window_days, 5 by default, in System Configuration), an item from a stock location switched out of the wave scheduler (the location's "Wave" setting, on by default — see Warehouses), and an item whose product is no longer released for despatch. They wait for a later night. Everything on this page is about what your team does after a wave exists.

Where to find it & who can see it

Open Despatch › Picking Waves in the left navigation. The list is visible to anyone holding wave.view (or a super administrator). The page is index-only for create/edit — there is no create or edit form — but each row can also be opened to a read-only detail view (see below); every column and every action described below appears on the list itself.

The wave lifecycle

A wave moves through eight states. Six of the forward steps are driven by buttons on this list; the step from Draft to ItemsIdentified happens automatically (outside the console) once the scheduler has finished allocating items to the wave.

Columns

ColumnShows
nameThe wave's identifying name/number, shown as a badge. Searchable and sortable.
Carriercarrier.name — the delivery carrier every package in this wave will use.
Routeroute.name — the delivery route the wave was grouped onto, or a dash when it has none. Only hand-delivery waves get a route. Hidden by default; switch it on from the Columns menu.
Locationlocation.location_name — the single warehouse stock location the wave was built from.
wave_typeBadge showing the wave's type (no special colour mapping — rendered in the console's default badge style).
StateA coloured badge — see the diagram above for the colour key.
created_atDate and time the wave was created. Sortable.

Filter

Select Filters to open a State drop-down covering all eight WaveState values (Draft, Items Identified, Label Printing, Packing, At Branch, Despatched, Done, Cancelled). Combine it with the search box, which matches the wave's name only — not the carrier or the location, so searching for a carrier name here returns nothing.

Screenshot placeholderThe Picking Waves list: Name, Carrier, Location, Wave Type and State columns, the State filter panel open, and row action buttons on the right of a wave in the "At Branch" state (Despatch, Send to branch already used).

Viewing a wave Built

Use the View row action to open a wave's detail page — read-only, gated by the same wave.view permission as the list. It has two info panels and two child tables:

The top of the detail page has three buttons: Generate packages, Enter tracking numbers and Print labels — all described under Actions below.

Everything else here is read-only — a wave is driven through its lifecycle by the row actions below (Print labels, Complete packing, Send to branch, Despatch, Mark done, Cancel), not edited on this page.

Every wave step is now recorded, with who did it

Alongside the date_… stamps shown on the detail page, each of the transitions below — Print labels, Complete packing, Send to branch, Despatch, Mark done and Cancel — writes a permanent entry recording the state it came from, the state it went to, and the user who did it. The same is true of a package being sealed, marked labelled, or given a delivery outcome. The timestamps tell you when a step happened; these entries tell you who. There is no screen for them yet — they are queried directly when a wave or package has to be investigated.

Screenshot placeholderThe Picking Wave detail page: "Wave" and "Despatch" info panels (name, state badge, wave type, carrier, location, operator, created date; SMS/email sent flags, despatch date), with "Moves" and "Packages" tables below.

Actions

Permissions

Every action on this page needs wave.manage in addition to wave.view to see the list at all — except Enter tracking numbers, which needs package.track instead (the same permission as editing a package). There is no finer-grained split between the other actions — if you can drive one, you can drive all of them.

  1. Print labels New 2026-11-07

    A Print labels button (on the row and at the top of the wave's detail page) opens the barcode address labels for every package in the wave, in package-number order, in a new tab ready to print. Pick the stationery from its menu: Carrier default, Continuous 4×5 in (dot-matrix), Thermal 4×6 in or A4 sheet, 6 per page (laser) — the carrier default is set on the carrier (see Warehouses › Delivery carriers) and is thermal 4×6 unless changed. Cancelled packages are left out. Generate the wave's packages first; a wave with none shows an empty page.

    Opening the labels while the wave is Items Identified moves it to Label Printing and stamps date_labels_generated — exactly like Mark labels printed below. Reprinting later never moves the wave back. Shown on any wave except Draft and Cancelled.

    What a label shows: the carrier, weight and number of items; the package number as a Code 128 barcode with the number underneath; COD ₹ amount in a heavy box when the package is cash-on-delivery; the recipient's name, address, PIN code and phone; the tracking number as a second barcode once one has been entered; AIR's name and the despatching warehouse's address as the return address; and what is inside, order by order (since November 2026) — each order number followed by its books and how many of each are in this package, so the label doubles as the packing slip when one parcel carries several orders of the same customer. Labels are pure black on white so they print cleanly on a dot-matrix ribbon.

    Printing tips. In the browser's print dialog set margins to None and scale to 100%, and choose the paper size matching the layout (4×5 in, 4×6 in or A4). For continuous stationery on a dot-matrix printer, create a 4×5 in custom paper size in the printer driver so each label starts at the top of the next form.

  2. Generate packages New 2026-11-07

    A button at the top of the wave's detail page, shown while the wave is Items Identified, Label Printing or Packing. It packs every move on the wave that is not in a package yet: one customer and one shipping address per parcel, cut to the carrier's maximum quantity per package, in the smallest box that fits (see Packages). Parcels are made in the old packing order: urgent orders first, then by state, district, town and PIN code, then customer name. Books whose product has no weight, height, width or length are not packed: the rest of the wave is, and a warning names those products — fill in their measurements on the product and press the button again. Packing is refused — with a message, and nothing built — when the wave has no items, when none of its books has full measurements, or when its carrier has no active box types (link one to the carrier first). The nightly run records the same refusal and leaves that wave unpacked. The nightly run already does this for the waves it creates, so you normally only need it after something changed — for example after suspended moves were taken out and resumed. Pressing it again is safe: moves already packed are left alone, and "No unpacked moves — nothing to generate" means there was nothing to do.

  3. Enter tracking numbers New 2026-11-07

    A button at the top of the wave's detail page, shown once the wave has packages that are not yet delivered, returned, lost or cancelled (and the wave is not Done or Cancelled). It opens one tracking-number box per package, labelled with the package number and customer, pre-filled with any number already entered. Scan or type each AWB: pressing Enter (as most barcode scanners do) jumps to the next box instead of submitting. Submit saves them all together. Leaving a box empty removes that package's number.

    Carriers that require tracking. When a carrier is set to require a tracking number, the wave cannot be despatched until every package has one — Despatch is refused and lists the packages still missing it.

    Items that were not packed. An item left out of the packages (its product has no weight or dimensions) is not despatched: Despatch takes it out of the wave — noted on the stock move's history — and it is put on a later wave once the product is measured. A wave with nothing packed at all cannot be despatched. Added 11 Nov 2026.

  4. Mark labels printed — Items Identified → Label Printing

    Moves the wave on without opening the labels — for when they were printed some other way. Selecting it stamps date_labels_generated and moves the wave into Label Printing.

  5. Complete packing — Label Printing → Packing

    Use this once labels are printed and the team is ready to physically pack the wave's packages. It stamps date_packing_complete.

  6. Send to branch — Packing → At Branch

    Hand-delivery waves only. Use this when a packed hand-delivery wave is sent to the branch that will deliver it. It stamps date_sent_to_branch and tells the branch: the location's responsible person gets an in-app notice, or, when the location has none, every user assigned to that location. Post and courier waves don't go via a branch — the button is not shown for them and the API refuses it; they are despatched straight from Packing.

  7. Despatch — Packing or At Branch → Despatched Confirmation required

    Despatch is refused while any move on the wave is Suspended (use Remove suspended moves below, or resume the move), or while a package has no tracking number on a carrier that requires one. The message lists the moves or packages to fix.

    This is the point at which the whole wave physically leaves. Customers get the despatch notice (SMS / email, as the carrier is set up) once per wave — despatching never sends it a second time. A confirmation dialog asks you to confirm before it proceeds — there is no undo button, so check the wave is genuinely ready. On confirming, the wave's date_despatched is stamped and a cascade runs in one transaction:

    What the Despatch cascade actually does

    Every package on the wave that is not already in a terminal state becomes Despatched. Every stock move on the wave that is not already Done or Cancelled is shipped — this is the moment physical stock is actually decremented from the warehouse location, via the stock-move service's ship step. In other words, Despatch on one wave silently finalises the state of every package and every stock move it contains; you do not need to (and cannot) despatch packages individually from this screen — see Packages.

    Labelling is not a precondition. A package that was sealed but never marked labelled is swept up by this cascade exactly like a labelled one — the cascade skips only packages already delivered, returned, lost or cancelled. If you want to check nothing is going out unlabelled, filter the Packages list on Sealed before despatching.

    Each move is shipped by the quantity this wave's packages actually carry, not necessarily its whole quantity — see Packages for how a move can be split across parcels. A move that ended up in no package at all still ships in full, exactly as it always has. A move only earns the Shipped badge once all of it has left; a move that has only partly gone keeps the state it already had, and whatever has not shipped stays reserved for it.

  8. Remove suspended moves New 2026-11-07 Confirmation required

    Shown only when a move on the wave has been put on hold after it was waved (for example a payment hold, or a manual hold), and only before despatch. It takes every suspended move off the wave and out of its package so the rest of the wave can go. A package left with nothing in it is cancelled; a package that still holds other books stays, with its weight and value recalculated.

    Take the book out of the parcel. The portal can't unpack a sealed box — check each removed move's history on Stock Moves, which names the package it was unpacked from, and pull the item out physically. When the hold clears, the move is reserved again and goes on a later wave.

  9. Mark done — Despatched → Done

    Use this once every package on the wave has reached the end of its journey. It is refused until each package is Delivered, Returned or Lost (cancelled ones don't count) — the message lists the packages still open; record their outcomes on Packages first. It stamps date_all_done and is the wave's final, successful state.

    Done by itself every morning. At 06:00 the portal marks done every despatched wave whose packages are all delivered, returned, lost or cancelled, so you rarely need this button. A despatched wave with no packages at all is left for you to close by hand. Switch the run off with wave.auto_close_enabled in System Configuration.

  10. Cancel — Draft or Items Identified → Cancelled Confirmation required

    Shown in danger red. Only available before any packing work has begun — once labels have started printing, a wave can no longer be cancelled from this screen, only carried forward or, exceptionally, corrected through another process

    Cancelling releases the wave's stock moves: every move that is not already Done or Cancelled is taken off the wave, removed from any package generated for it, and becomes available again — the next auto-wave run can put it on a new wave. Any package already generated for the cancelled wave becomes Cancelled. Each released move's history records which wave it left and which package it was unpacked from.

Why you only ever see one or two buttons

Each action's button is only shown when the wave is in the exact state that action requires — for example Despatch only appears on waves that are Packing or At Branch. If a colleague acted on the same wave a moment before you, the buttons you see will already have moved on; the underlying service re-checks the state again regardless, so an out-of-turn click is always refused safely rather than corrupting the wave.

Bulk actions and forms

There are no bulk actions on this list — every wave is progressed one at a time. Only Enter tracking numbers opens a form; Print labels opens the labels in a new tab, and the rest are a single confirmation (or, for Mark labels printed, Complete packing and Send to branch, an immediate one-click transition).

Related pages

See Sale Orders for how an order's stock is reserved before it ever reaches a wave, Packages for what happens to each individual package inside a wave (including after despatch), and Schedulers for how waves are created in the first place.