Background Schedulers
A handful of jobs run on their own every night and morning, on a fixed timetable. You don't open a screen and press "start" — you mostly see and act on the records they leave behind.
Nothing on this page corresponds to a page under /staff that you click into. Each job is a scheduled command that runs unattended on the server. Your involvement is upstream (setting the kill-switches in System Configuration) and downstream (working the sale orders, picking waves and bank statements the jobs produce or touch).
The daily timetable
The despatch jobs run in this order every night. Despatch-item creation runs first, at 01:00, so reservation an hour later has every newly owed part to work on; wave creation follows reservation so it only ever groups items that are already reserved. At 04:00 packages that have been on the road longer than their carrier's delivery window are marked delivered; the despatch safety net then checks that nothing was missed, and at 06:00 finished waves are closed.
Releasing a printed part (Release for despatch on Products) only marks it ready; the 01:00 run is what turns it into despatch items for every order that is owed it. See the callout below the timetable for how they connect.
The chain that starts with an approved order and ends with a despatched package runs all the way through: Release for despatch (a Products row action, stock_move.create — see Products) marks a printed part ready → air:create-despatch-moves creates Confirmed delivery stock moves for every order owed it → air:auto-reserve reserves them → air:auto-wave groups them into picking waves and packs them → waves go out for despatch → air:close-waves closes them once every package has reached the end of its road. Release is a manual console action; the jobs on this page carry a released part the rest of the way automatically. HO can pull one order forward with Create despatch items now.
Despatch-item creation Built
Command air:create-despatch-moves, runs daily at approximately 01:00.
For every sale order that is Approved for despatch or In despatch, it creates a despatch item (a Confirmed delivery stock move) for each part the order is still owed: the book itself on a book line, and every released part on a subscription line — skipping future editions, parts at or after the line's stop point, and parts that already have a live item. An order approved mid-year catches up on all parts already released. Items ship from the order warehouse's default location and are left for the 02:00 reservation run. Copies handed over at booking are issued at the same time. The order moves to In despatch with its first items.
Orders are processed in batches (despatch.batch_size, 500). An order that fails — no source location, or no longer paid — is recorded and skipped; the others go ahead. Each run is logged with how many items were created and which orders were skipped or failed, and the super administrator the run is attributed to gets an in-app summary. Controlled by despatch.creation_enabled in System Configuration.
Auto-reservation Built
Command air:auto-reserve, runs daily at approximately 02:00.
It first re-checks items held by a hold that clears itself, and releases those whose cause has gone. It then scans confirmed delivery stock-moves product by product — products with a higher delivery priority first, then a lower despatch sort order — and within a product, urgent orders first, then the smallest quantity first. An item a manager has overridden is picked up even if it carries a hold. For each move it does one of two things: reserve the available stock (moving quantity from available to reserved), or — if the move fails one of the credit-control checks below — hold it under a suspend reason instead of reserving it. A warehouse or carrier can opt out of this entirely; any move at a location or carrier whose allow_autoreservation flag is off is skipped and left for manual handling.
The checks run strictest first, and only the first one that fails is recorded — so the hold reason you see on a move is the thing you actually have to fix. See Stock Moves → Why a move is held for what each reason means and what to do about it.
- Carrier can't deliver there
The order's delivery pincode is marked as not serviceable by the carrier on the move → held as Delivery pincode not serviceable by the assigned carrier. If there is no serviceability record for that pincode and carrier at all, the move passes — a missing record is never treated as "unserviceable".
- A return is still open on this order line
An earlier part of the same order line came back in a return that isn't reconciled or cancelled yet → held as A pending return on this order line holds its further parts.
- Too much uncollected COD cash is already out
On a cash-on-delivery order, the customer has more than 5 (reservation.cod_in_transit_limit) despatched or delivered COD packages whose money has not come back yet → held as Too many unremitted COD packages already out for this customer. The same check with a limit of 1 (reservation.rbp_in_transit_limit) applies to items on carriers marked RBP / OLP carrier → Too many RBP/OLP packages already out for this customer.
- The full set isn't paid
The product is flagged withhold until paid in full and the cleared payments against that order line don't yet cover the whole line → held as Full set not yet paid. No part of the set goes out until it is paid. Cash-on-delivery orders are not held.
- The minimum payment isn't in
The product (or the order type) has a minimum payment allocation % and the payments against the order line, or against the whole order, are below it → held as Minimum payment allocation not reached. Clears itself once the payment reaches the percentage.
- The order line has run out of credit
The line's credit — cleared payments, post-approval discounts, its parts-on-credit allowance and its share of credit HO approved — less the value of its parts already reserved or sent, no longer covers this part. Parts go in despatch order while the credit lasts (₹1 tolerance) → held as Not enough credit left on the order line for this part. Cash-on-delivery orders, free-supply and re-send order types, and items already packed are not checked.
- The customer is over their credit limit
Credit-limit checking is on for the customer and what they would owe with this item exceeds the ceiling → held as Credit limit exceeded.
- The order's payment hasn't settled
The last catch-all: the order is not settled for head office, and no payment override is in force → held as Payment not received/allocated.
A part's value is the one fixed on its despatch item when it was created — for a set, the line's value shared across its parts by each part's price weight. Only payments that have cleared count. A customer marked send first parts on credit gets the first 3 parts of a subscription line (reservation.first_parts_on_credit) past every payment check; the credit limit still applies.
An item a manager has overridden (Override holds on Stock Moves) skips every check above and reserves regardless.
Running out of stock is not a hold: a move with insufficient stock simply stays Confirmed and is tried again on the next night's run.
Controlled by the reservation.enabled switch in System Configuration. Turn it off and the job still runs but does nothing.
Open Stock Moves the morning after a run: reserved moves show as Reserved, and anything the credit-control checks stopped shows as Suspended with its Hold reason filled in. You can also watch it indirectly — the qty_reserved column on Stock on hand rises for the products it touched, and an hour later the reserved moves start appearing grouped into new picking waves (below).
Auto-wave creation Built
Command air:auto-wave, runs daily at approximately 03:00, after reservation.
It groups reserved delivery moves that aren't yet part of a wave by location, carrier, product category, product timeline and the product's wave group # (plus delivery route for hand delivery), and turns each group into a picking wave — batches of up to 500 moves per wave, with a solo wave carved out for any single large-quantity move (more than 50 units). A move with no carrier assigned is skipped rather than forced into a wave. It also leaves out items whose customer asked for delivery more than wave.expects_on_window_days (5) days away, items from stock locations switched out of the wave scheduler, and items whose product is no longer released for despatch — they wait for a later night.
Controlled by the wave.enabled switch in System Configuration.
The waves it creates land in Picking Waves at Items Identified, ready for despatch staff to print labels, pack and send them on. Since November 2026 it also generates each new wave's packages — one per customer and shipping address, boxes chosen automatically (see Packages). If building the packages fails for a wave — for example its carrier has no active box types — the wave is still kept and the reason recorded; fix the cause and use Generate packages on the wave's page to build them. Books left unpacked because their product has no weight or size are recorded on the run the same way, naming the products.
Package auto-delivery Built
Command air:auto-deliver-packages, runs daily at approximately 04:00.
Most carriers never tell us a parcel arrived. For a carrier with Auto-deliver after (days) set (see Delivery Carriers), this job marks a package Delivered once it has been Despatched for that many days — no news within the window means it arrived. It is exactly like recording the delivery by hand: the books' stock moves finish and the order completes when its last package is delivered.
- A package on an open carrier complaint (draft, submitted or acknowledged) or on a return shipment that is not cancelled is left alone. Once the complaint is resolved or closed, the next run delivers it.
- Hand-delivery carriers are never auto-delivered — they still need the delivery person's GPS check-in and the signed delivery challan.
- Packages of stock transfers and purchase orders are not touched; they are settled when the receiving warehouse receives them.
- A carrier with the field blank is never auto-delivered. HO can always record a delivery, return or loss by hand before the window ends.
A package that cannot be delivered is listed as a dropped record on the run, which then shows Warning; the rest still go through.
Despatch safety net Built
Command air:despatch-safety-net, runs daily at approximately 05:00, after auto-wave and before the health check.
This job is a safety net, not a producer — it never creates a stock move itself. After the 01:00 run it looks for anything still owed: for every order that is Approved for despatch or In despatch, each released part a line should have an item for and doesn't (checked part by part, so a subscription missing just one month is caught). Each one it finds is logged as a dropped record naming the line and the part, and the scheduler run is marked Warning if it found anything, Success if it found nothing.
Normally the 01:00 run leaves nothing behind. What this catches is an order the run skipped — usually one whose warehouse has no single source location, or that is no longer fully paid — so it doesn't sit unnoticed for days.
Finding an orphan line here does not create the missing item. Fix the cause (give the warehouse a single source location — see System Configuration — or settle the payment), then either wait for the next 01:00 run or use Create despatch items now on the order — both only ever create what is still missing.
Closing finished waves Built
Command air:close-waves, runs daily at approximately 06:00.
Marks Done every picking wave that is Despatched and whose packages are all delivered, returned, lost or cancelled. A despatched wave with no packages is left to be closed by hand. Controlled by wave.auto_close_enabled in System Configuration.
Gateway settlement bifurcation Built
Command air:bifurcate-settlements, runs daily at approximately 07:00.
Online-gateway settlements (Razorpay, CCAvenue) arrive as one lump sum covering many customer payments. This job splits a bank statement's gateway settlement lines back into the individual payment vouchers they represent, so each customer's payment can be reconciled on its own. See Bank Reconciliation for the statement screen this feeds.
Health check Built
Command air:health-check, runs daily at approximately 06:00.
Records a snapshot of overall system health. Review it in Administration › Diagnostics › Health Check Results — see Diagnostics below.
Wallet balance check Built
Command wallets:verify, runs daily at approximately 06:15.
Checks that every customer wallet's balance equals the total of its ledger. Any wallet that differs is written to the application error log ("Wallet balance drift detected") with both figures. This run is not listed under Scheduler Runs. See Customer wallet.
Reviewing what the schedulers did
Every run above is recorded and can be reviewed in the console. The Administration → Diagnostics screens (gated diagnostics.view) show Scheduler Runs (each run's status + processed/skipped/failed counts), Dropped Records (exactly what each run skipped and why — e.g. the despatch safety net's orphan-line log or a credit-held reservation), and Health Check Results (the latest health-check output). See the Diagnostics page.