Promos surge. Cut-offs loom. Requirements vary by customer. Order Management in Clarus turns all that noise into a clear plan. Orders are ranked by your rules. Fragile, hazmat, and value controls apply automatically. Picking flows by the best method. Packing is guided and verified. Labels print. Carriers are chosen against cost and service. Your team focuses on flow, not firefighting.
Sequence by cut-off, SLA, customer tier, value, delivery method, or backlog age. Clarus updates priorities in real time as conditions change, so the right work always happens first.
Flag SKUs once and let the system enforce handling—separate totes, “do not stack”, weight/height limits, extra scans at pack, or photo evidence where needed. Quality becomes predictable, not a hope.
From each-pick D2C to wholesale cartons and pallets, the same engine allocates tasks, validates barcodes, and keeps status accurate across waves, zones, and benches.
Select services by rules… cost, speed, promise date, destination, or customer preference. Manifests, labels, and tracking references generate at the right time and place to keep benches moving.
With Order Management orchestrating priorities, methods, and carriers in the background, every role works with confidence… not guesswork.
Set the rulebook. Clarus applies it in the flow of work so the right orders move first, fragile handling is enforced, and cut-offs hold… even on peak days.
Tasks arrive in the right order. Exceptions are clear and actionable. Teams move from queue to queue without radio chatter, keeping throughput high and errors low.
Answer confidently. See release, pick, pack, and despatch milestones plus tracking in one place. Calls get shorter. Trust climbs.
Orders land via API, EDI, marketplace, or manual entry and are normalised with customer and channel rules. Clarus evaluates each order against priorities (cut-off, SLA, tier, age, value) and chooses a picking method based on live queues, SKU velocity, and layout. Tasks are generated to handhelds: pick ? replenish (if needed) ? pack ? ship.
At pack, workflows verify item, quantity, and (if relevant) batch/lot or serial. Fragile logic adds checks, inserts fillers or “ship alone” rules, and captures photos where configured. Carrier selection applies your cost/speed rules and creates labels and tracking. Status moves to despatch, manifests close, and confirmations publish back to your systems and clients. Everything is timestamped with user, device, and location for a clear audit trail.
How does Clarus decide which orders to do first?
A rules engine scores orders by cut-off, SLA, age, value, customer tier, and channel. As conditions change (late inbound, carrier cut-off shifts) the scores update and queues re-sequence automatically, keeping work aligned to what matters most.
How are fragile items protected?
Flag SKUs with handling attributes (fragile, do-not-stack, temperature-sensitive). Clarus enforces separate totes, pack checks, filler prompts, and “ship alone” where needed. Optional photo capture at pack provides proof for claims.
Can we mix different picking methods?
Yes. Clarus can run tote for singles, batch for common lines, and zone for large orders simultaneously. The system assigns the most efficient method per order/SKU and keeps status coherent across flows.
What carriers are supported?
You can configure your chosen carriers/services and apply routing rules for cost and speed. Labels, manifests, and tracking references are produced in the right sequence at despatch. (Specific integrations depend on your setup.)
How do we handle exceptions without stalling?
Exceptions surface with context and a next action. Short pick, substitution rule, reprint label, re-route service. Supervisors get an override path where permitted, so queues keep moving.
Will Order Management slow us down during rollout?
No. Start with guidance and safe overrides. As confidence grows, tighten rules. Most sites see immediate gains from prioritisation and barcode checks, with further improvements as method and carrier rules are tuned.
