How RackSort works
RackSort reviews a proposed warehouse operation and returns a verdict, the next step to take, and the facts behind the decision.
A scanner, agent, or integration can submit an operation for review before carrying it out. The same decision format covers receiving, reservations, picking waves, serial scans, packing, inventory counts, carrier actions, and handover.
1. Describe the operation
Choose a decision type and provide the proposed action together with its relevant records. A reservation decision uses stock and reservation quantities; a carrier decision uses request keys, connector capabilities, and the outcome of earlier requests.
Each of the ten decision types has a schema, worked examples, and the specification clauses it applies. The API reference describes the shared request and response format.
2. Check structured facts and text evidence
Rules settle facts that can be established directly: quantities, reservations, lock versions, request keys and digests, and pickup scan times.
SmallDecide answers typed questions about text such as carrier replies, tender evidence, unit wording, counter notes, and order-change messages. An answer settles a fact only when it clears a threshold qualified for that model and question. Otherwise the question abstains and the specification determines the next step.
3. Read the verdict
Every response returns one of five verdicts:
- Allow: proceed with the operation under the conditions stated.
- Replay: reuse an existing result instead of repeating the operation.
- Reject: stop an operation that breaks a rule.
- Review: route the decision to the responsible person.
- Reconcile: establish the missing facts before proceeding.
The response identifies the next action, the role responsible, the facts used, and the specification clauses applied. A verdict reviews the proposed operation; your application carries out and records the resulting work.
A carrier reply goes missing
A label request reaches the carrier, but its reply never arrives. Retrying as a new purchase can buy a second label. RackSort checks the connector's idempotency and lookup capabilities before deciding whether to retry the same request, reuse a known result, or reconcile the outcome.
The model overview includes the complete request and response. The carrier decision reference explains the rules and evidence questions.
Run a decision
Use the quickstart to run an example, inspect a request in the console, or read the evaluation report for measured coverage and error bounds.