🚫 Sales order rejection
Updated
Rejection is the reversible manager decision before approval. It sends a submitted order back to Draft with a reason; it does not cancel the sale and does not post numbers.
User path: rejecting a sales order. Related process: sales order.
How the process works#
A SalesOrder can be rejected only from Submitted. The manager fills
Reject reason and presses Reject order. The document returns to
Draft, where the agent can edit lines and submit it again.
Rejection is not cancellation:
| Action | From | Result | Numbers |
|---|---|---|---|
| Reject order | Submitted | Draft, reason kept | none |
| Cancel order | Submitted or Approved | Cancelled, no further editing | linked not-yet-released realization is cancelled |
Settings#
There is no setting for rejection. The command is available by state. The only mandatory value is Reject reason on the order card.
Example with numbers#
An order for 5 pieces at 100 is submitted. The manager rejects it because the outlet asked for another delivery date.
| Step | State | Register effect |
|---|---|---|
| Submit | Submitted | none |
| Reject | Draft | none |
| Agent edits and submits again | Submitted | none |
| Approve later | Approved, realization Reserved | ReservedStock +5 on the realization |
Boundaries and edge cases#
- Empty Reject reason is refused.
- The reason remains on the card after the order returns to Draft.
- If a realization already exists, use cancellation rules instead; rejection belongs before approval.
What is posted#
Nothing. Rejection changes only the order state and text reason.
What's not there yet#
- There is no rejection-reason dictionary and no rejection statistics screen.
- There is no notification from manager to agent beyond the changed state and reason field.
Same topic for other readers: User