Choose returns management software by following a request across the customer, support, warehouse and finance teams. Before comparing suppliers, agree what each team must know and which decisions remain its responsibility. Use the same return cases for every evaluation, and keep proposal claims separate from demonstrated results and unresolved dependencies.
Returns management supplier scorecard
Use the same policy and cases for each supplier. Record the evidence observed and the owner of every unanswered question before deciding on a pilot.
| Criterion | Evidence to request | Pilot test |
|---|---|---|
| Item-level request | Order, item, quantity and reason kept together through review. | Return one item while leaving the rest of the order unchanged. |
| Policy decisions | Decision inputs, exclusions and the route for a human review. | Explain an out-of-policy request and name its approver. |
| Damage review | Evidence requirements and the team responsible for assessment. | Submit the damaged-item case and locate the next review owner. |
| Physical return | Written responsibility for instructions, labels and receipt evidence. | Check an expected quantity against a different warehouse receipt. |
| Financial resolution | A distinct resolution event, source record and responsible team. | Keep goods received visible while the financial outcome is pending. |
| Scope and handover | Included work, provider dependencies, data access and charging unit. | Compare the proposal with each handoff in the four test cases. |
Set the boundary of the purchase
List the work you want the supplier to cover: collecting a request, reviewing eligibility, providing instructions, recording receipt or sharing a resolution update. Name the system and team that owns each step today. Ask where the proposed service starts and ends. Keep label arrangements, warehouse handling and financial actions as explicit items in the discussion.
Evaluate how policy becomes a decision
Bring your published policy and redacted examples from relevant markets. Ask the supplier to explain which fields support each decision, including item, quantity, reason and reference date. Examine an excluded item or a request needing human review. Record who approves policy changes and how support explains a decision when a customer asks for an exception.
Use four cases to compare suppliers
Give every supplier the same case brief and expected evidence. Follow each request from the customer view into the responsible team’s view. Record the result at each handoff, including any step that needs a separate system or agreement.
- Standard eligible request: identify the item and show the next review step.
- Partial return: select one item and preserve the remaining order context.
- Damaged item: gather the agreed evidence and assign a review owner.
- Goods received, resolution pending: show receipt while the financial decision remains open.
Check what each status actually establishes
Ask what event supports request submitted, approved, received and financially resolved. Inspect who can record or correct each event and how the change reaches support. Test a mismatch between the expected and received quantity. The person answering a customer should see the last confirmed fact, the outstanding decision and the owner who can explain the next step.
Compare the operating agreement
Ask for written responsibilities for return instructions, shipping documents, label provision, inspection and payment updates. Confirm the charging unit and any separate provider costs in the proposal. Review data access, export arrangements and the process for unresolved cases. For JetonTrack, use the sample return journey to clarify the desired experience, then agree which production activities are included.
Close evaluation gaps before choosing
Use the scorecard below with extra columns for supplier statement, demonstrated evidence, gap, owner and decision date. Attach the sample record or agreed document to each result. Ask support, warehouse and finance to review the same findings. Approve a pilot only when its scope, open dependencies and acceptance decisions are clear to the teams who will operate it.
Common questions
Does a return portal include labels and refunds?
Ask each supplier to document those responsibilities. A request interface alone does not establish who provides a label, receives the goods or approves and records a financial outcome.
Can we compare suppliers with sample data?
Sample cases help compare the proposed journey. Record their limits and agree which data, connections and responsible teams need further verification before a production decision.