Review and approval

Confirmation puts a Draft order into Review and opens a decision for that revision. Order Reviewer reads the customer request, product lines and current exceptions before approving or returning the order. The decision has a reviewer, date, reason and revision. A later order change can therefore be distinguished from the request that was actually reviewed.

Approval is a human decision. The review workflow writes a decision record and a processing receipt, then changes the order to Approved when the checks pass. It skips a duplicate decision for the same order revision. That protects the record from a repeated review action appearing to be a second independent approval.

• Queue. Reviewers use the confirmed order queue to choose work at the Review status.
• Evidence. Each decision identifies the order revision, reviewer and reason, with attached order material available for inspection.
• Outcome. Approved orders proceed to fulfillment; returned or rejected decisions remain visible for follow-up.

Agree who may act as Order Reviewer and what checks that person must complete. The customer address, credit and eligibility note, line quantities, prices, order amount and open exceptions are useful review context. Document which findings require a return for correction and which require an exception owner. Keep the decision reason specific enough that Order Desk Agent knows what to change.

Choose how the team handles a returned order. The order’s status choices include Draft, Review, Approved, Executed, Rejected and Cancelled, while decision outcomes include Approved, Rejected, Returned and Escalated. The decision outcome and the order status are distinct records. Train the team to read both before deciding what action comes next.

Confirm an order containing two lines and an attachment. Order Reviewer opens it from Orders Awaiting Review, compares the lines to the customer request, and records a reasoned decision. Check that the decision names the same revision the reviewer saw. Approve it, then verify the order is Approved and a processing receipt shows the operation.

Repeat with a stock shortage exception. Return the order and write a reason that identifies the affected line and expected correction. Verify that Returned or Rejected Review Decisions gives the order desk a clear follow-up path. A second attempt to review the same revision should not create another decision. Review any corrected revision separately.

• Orders Awaiting Review — Reviewers find confirmed orders awaiting a decision.
• Returned or Rejected Review Decisions — The order desk reads decisions that need correction or follow-up.
• Order Status Board — Operations can see the boundary between Review and Approved work.

See order preparation and review through allocation.