1. Size & Fit Recommendation
  2. Features
  3. Reviews and Reconciliation
Feature · Reviews and Reconciliation

Reviews and Reconciliation

Keep independent decisions and completed effects tied to the order scope before retrying or correcting an action.

OverviewReceipt Exceptions
Size & Fit Recommendation · Reviews and Reconciliation

Receipt Exceptions

Operation receipts

New
IdParentOperation keyActionExpected revisionResult state
IDD-711SO-78794OK-927ACT-102440Pending
IDD-271SO-60505OK-649ACT-61080Failed
IDD-894SO-64382OK-369ACT-791750Needs review
IDD-694SO-84679OK-163ACT-111360Pending
IDD-335SO-51499OK-218ACT-193590Failed
6 of 6 records
IDD-711Operation receipts · OR-44652
Pending
ParentSO-78794
Operation keyOK-927
ActionACT-102
Expected revision440
Occurred at21 Oct
Example screen with sample data

What you can do

Establish what was approved and what happened

Commerce Reviewer records the decision against the submitted source version, with the reviewing person, date and reason. The order reference keeps the decision within the customer transaction. The action identity distinguishes the fit, refund or correction scope that the decision concerns.

Operation receipts retain the expected version and result state together with external and effect references. Pending, Failed and Needs review identify work that needs investigation. Reconciliation reads the existing order, payment, fulfillment and attachment evidence before deciding whether the requested outcome is established.

How the work is organized

  • Independent decisions. Fit and refund requests receive review from a person independent of the preparer. Keep the reason with the exact submitted scope so a changed request cannot quietly rely on an earlier approval.
  • Result checks. Read the retained receipt and linked effects when completion is unclear. Match the recorded external identity to the same order and requested action before interpreting the provider result.
  • Corrections. Unexecuted draft scope can be cancelled through its responsible path. Executed scope needs a reviewed corrective action that preserves the original identity and evidence. External effects are not reversed automatically by changing a local label.

What to agree during setup

Agree how the team assigns an independent reviewer and handles reviewer absence. Check the authenticated account links used to identify the preparing and deciding people. A role label alone must not make the same person independent of their own request.

Set the evidence needed to establish completion for each action. The reviewer should know which provider or stock-owner reference is authoritative and how to investigate a mismatch. Agree the correction process before accepting live sales, especially where a payment or product movement has already occurred. Keep the original decision and result available during that review.

Check the handoff on an actual case

A fit assessment is approved, but the operator cannot establish whether its completion action finished. Commerce Reviewer opens the retained result and checks the expected effects for that recommendation. The team resolves the existing outcome before another attempt is made.

Next, use an uncertain refund response. The reviewer compares the receipt with the locally recorded provider reference and verified evidence. A reference to another order or a different amount needs a discrepancy explanation; its mere existence cannot establish the requested refund.

Finally, ask to cancel an order after external execution has occurred. Review the prior payment and fulfillment evidence before choosing the corrective action. Preserve the original records and seek the required independent approval for the correction. Do not delete executed history or assume that a local cancellation has returned merchandise or reversed the provider transaction.

What your team sees

  • Receipt Exceptions — Pending, failed and review-needed results identify actions requiring investigation.
  • Decision History — Decisions retain the submitted version, reason and named reviewer.
  • Order Evidence — Supporting files remain attached to the order for the review discussion.

Follow the work through

What it keeps track of

Data model
Review decisions
Independent review decisions on submitted revisions
Operation receipts
Stable operation keys and persisted effect results
Sales orders
Priced sales orders carrying fit recommendation scope
Fit assessments
Consented fit assessments and product size recommendations
Payment evidence
Verified provider authorization, capture, refund and void events
Fulfillment events
Allocated, picked, shipped, delivered and returned events
Record attachments
Evidence files attached to operational records
Team members
Authenticated platform identities with operational role scope
Users
Users

Who uses it

Permissions
Commerce Reviewer
Makes independent decisions and reconciles outcomes.
Commerce Operator
Prepares the scope and supplies context.
Auditor
Follows authorized evidence.
Admin
Maintains authenticated identities.

Set up Size & Fit Recommendation your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started