Review and evidence

A draft becomes review work when Order Coordinator confirms it. Confirmation calculates the order amount from the lines, increments its revision, writes an operation receipt and opens a review decision. Order Reviewer can then examine the order, lines, exceptions and attached evidence before recording a decision and reason. The source revision matters: a decision on an earlier version should not be confused with the current order.

For a skincare promotion, the reviewer might find an exception marked Promotion Misapplied. The order record shows the promotion code and net amount; the line records show the price used. The reviewer can record an approved, rejected, returned or escalated decision, with a reason tied to the version examined.

• Submitted scope. Confirmation moves the order from draft to review and gives the reviewer a revision and computed amount.
• Decision trail. Review decisions carry outcome, reason, reviewer, date and source revision.
• Operating proof. Receipts and attachments remain linked to the order so later corrections can be read in context.

Agree which order changes require renewed review, which reviewer can approve a particular organization and how rejected or returned work reaches the coordinator. Keep the approving person separate from the person who prepared the order. Define the evidence expected for promotion disputes, high value orders and batch questions. An attachment can carry a document URL and evidence type; the team should agree naming and access rules for that document source.

Decide how to interpret an escalated decision. The outcome should identify who owns the next action and should not be treated as a shipment approval. The approved customer order state is the starting condition for release. Reviewers need to understand that a decision record and an order state are related, distinct pieces of the operating trail.

Confirm a draft with two lines and an exception. Ask Order Reviewer to inspect the current revision, attachments and exception, then record a returned decision with a reason. Correct the line and confirm the revised scope. Check that the first receipt and decision are still visible and that the new decision references the new revision. Repeat with approval. Before Fulfillment Operator releases shipment, check that the order itself is in the Approved state.

The case should reveal who can see the reason and who can correct the order. A reviewer should have enough context to decide without editing the coordinator’s original line silently.

• Orders in review — Order records waiting for a decision, with revision and amount visible.
• Returns and Rejections — Recorded decision outcomes requiring follow-up.

See order confirmation and review and see correction handling.