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
- Returns and support
Returns and support
Trace return or exchange events and customer issues back to the originating order.
OverviewCaptured Payment Evidence×
Apparel and Footwear OMS · Returns and support
New
Captured Payment Evidence
Payment evidence
| Evidence no | Apparel customer order | Method | Captured amount USD | Verified | Status | |
|---|---|---|---|---|---|---|
| EN-574 | ACO-36139 | Card | 840 | Captured | ||
| EN-760 | ACO-12662 | ACH | 590 | Captured | ||
| EN-259 | ACO-78398 | Wire | 900 | Captured | ||
| EN-233 | ACO-71145 | Store Credit | 240 | Captured | ||
| EN-178 | ACO-20898 | Check | 50 | Captured |
6 of 6 records
EN-574Payment evidence · PE-86055
CardApparel customer orderACO-36139
Captured amount USD840
Verified✓
StatusCaptured
What you can do
Give each issue an order and an owner
Support Agent starts from the affected apparel order. The exception identifies a type, time raised, detail, support owner and current status. The types cover size or color shortages, ship-to address issues, payment holds, damaged or defective items, late shipments, compliance or labeling and other support follow-up. Each points to the same source order that carries the buyer, line variants, payment evidence and fulfillment history.
A return or exchange is a fulfillment event with its own units, date, location and status. It should not be confused with a new order line or a payment refund. Payment evidence can show Refunded, but the team should check the linked evidence before closing the support issue. Attachments can carry a return authorization or other supporting document and remain linked to the order.
How the work is organized
- Exception intake. Record the affected order, issue type, detail and support owner.
- Event review. Check shipped, delivered and returned or exchanged units by date and location.
- Resolution. Write the resolution note and move the exception through investigation or escalation.
What to agree during setup
Agree who receives issues from shoppers and wholesale accounts, who investigates a stock shortage and who may close an exception. Define what evidence is needed for a damaged item, late shipment or ship-to correction. Keep customer fit and return notes available to the support team while limiting edits to authorized staff. Decide when an escalated order requires a new review decision rather than a support-only resolution.
A received return event describes the operational event. A refund result belongs to payment evidence. If payment processing or warehouse intake is handled elsewhere, connect that system and record its reference in the appropriate evidence. The support owner should never close a case based only on an expected event.
Check the handoff on an actual case
A shopper reports a damaged shoe after shipment. Support Agent opens the order and checks the style, size and color line, the Shipped event and any later Delivered event. They record a damaged item exception and attach the relevant evidence. When a returned or exchanged event is recorded, they compare its units with the original order. They check whether payment evidence reflects any refund before writing a resolution note. If the case affects an already Executed order, the correction path records an escalation decision and receipt for compensation instead of erasing the shipment history.
What your team sees
- Open Order and Support Exceptions — Active issues grouped by type and assigned owner.
- Shipped, Delivered and Returned Events — Operational events to compare with the customer’s report.
Follow the work through
What it keeps track of
Data model- 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.
- 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.
- Payment evidence
- Payment evidence captured against apparel orders, with gateway reference, method, verification state and captured USD amount.
- Record attachments
- Fit sheets, packing lists, return authorizations and other evidence attached to an apparel order.
- Wholesale accounts and shoppers
- Department stores, specialty chains and direct shoppers that place US apparel and footwear orders, with fit, sizing and return notes.
- Order review decisions
- Independent review decisions on apparel orders, recording the decision, rationale and order revision the reviewer acted on.
- Operation receipts
- Receipts recorded for every apparel order operation: alignment, allocation, release, reconciliation, cancel and compensation runs.
Who uses it
Permissions- Support Agent
- Investigates and records resolution.
- Fulfillment Lead
- Confirms movement events.
- Order Reviewer
- Considers escalations.
- Reconciliation Analyst
- Checks payment evidence.
Set up Apparel and Footwear OMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.