These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Apparel and Footwear OMS
- Features
- Payment and reconciliation
Payment and reconciliation
Compare order lines, fulfillment events, payment evidence and receipts before a matched close.
OverviewOpen Apparel Orders×
Apparel and Footwear OMS · Payment and reconciliation
New
Open Apparel Orders
Apparel customer orders
Draft2
WAA-110MAS-1683
10 Oct
WAA-120MAS-2004
09 Oct
Add
Review2
WAA-110MAS-2068
03 Oct
WAA-120MAS-9014
10 Oct
Add
Approved2
WAA-110MAS-2567
03 Oct
WAA-110MAS-4512
09 Oct
Add
What you can do
Reconcile the order that actually moved
Payment evidence belongs to a specific apparel order. It carries the method, status, captured USD amount, verification flag, optional gateway reference and capture date. Reconciliation Analyst checks that evidence alongside line units, fulfillment events and operation receipts. A captured amount alone is not a proof that every line shipped, and a Shipped event alone is not a payment result. Each record answers a different question.
The reconciliation action reads a selected order and those linked records. When the records match, it writes a Verified receipt and may advance an Approved order to Executed. When they disagree, it writes a Failed receipt and raises an order and support exception. The receipt and exception keep the discrepancy visible for a named owner rather than burying it in a final status.
How the work is organized
- Payment evidence. Compare method, captured amount, verification state and gateway reference.
- Operational evidence. Match line units with fulfillment and return events and operation receipts.
- Reconciliation outcome. Inspect the Verified or Failed receipt and the associated exception.
What to agree during setup
Set the expected payment methods and how the team receives gateway references from a connected payment system. Decide who may mark evidence verified and who investigates a failed reconciliation. Agree how returned or exchanged units and refunded evidence are compared. Use consistent order numbers so the payment team, fulfillment team and support team can identify the same transaction. Keep an owner on every discrepancy.
The reconciliation action is record initiated. Before using it in an operating cycle, test which lines and events it considers and compare its receipt with the actual order. The team should review a discrepancy before rerunning or correcting data, so the reason for a changed outcome remains traceable.
Check the handoff on an actual case
Take an Approved order with two size lines. Check its captured payment evidence, its Allocated and Shipped events and the receipts from prior operations. Run reconciliation and inspect the resulting receipt. If the second line lacks the expected event, a Failed receipt and exception should identify the problem. Support Agent investigates the missing movement; Fulfillment Lead confirms the event history. Once the records match, Reconciliation Analyst can rerun the check and inspect the Verified receipt. A close should follow the matched evidence, not a manual change to the order label.
What your team sees
- Captured Payment Evidence — Captured amounts and verification state by source order.
- Failed or Corrected Receipts — Reconciliation and operation runs needing attention.
- Executed Apparel Orders — Orders that reached execution after release or a matched check.
Follow the work through
Read payment reconciliation and returns and support.
What it keeps track of
Data model- Payment evidence
- Payment evidence captured against apparel orders, with gateway reference, method, verification state and captured USD amount.
- Apparel customer orders
- US apparel and footwear customer orders with order channel, primary style, seasonal promotion code and net order value in USD.
- Order lines size and color
- Order lines by style variant, carrying the ordered units, wholesale unit price and size or color substitution allowance.
- Fulfillment and returns events
- Allocation, pick, pack, shipment, delivery and return or exchange events against apparel orders at a DC or store location.
- Operation receipts
- Receipts recorded for every apparel order operation: alignment, allocation, release, reconciliation, cancel and compensation runs.
- Order and support exceptions
- Size and color stock shortages, ship-to address issues, payment holds, damaged or defective items, late shipments and customer support follow-ups on US apparel orders.
Who uses it
Permissions- Reconciliation Analyst
- Compares the records and owns the check.
- Support Agent
- Investigates the exception.
- Fulfillment Lead
- Confirms movement.
- Admin
- Oversees corrections.
Set up Apparel and Footwear OMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.