ReturnLoom
A post-purchase orchestration service that normalizes return, exchange, tracking, refund, dispute, and carrier exceptions while preserving merchant policy, buyer authorization, payment state, and human escalation.
Agent purchasing infrastructure increasingly covers checkout, while post-purchase work fragments across commerce, carrier, tracking, returns, and payment systems. The input incorrectly says Zinc omits returns entirely; its current API already creates return requests and retrieves dispute cases. The remaining opportunity is narrower and harder: multi-provider orchestration, exchanges, fee exceptions, authorization evidence, and reconciled refund state. ReturnLoom should coordinate those systems without letting an agent invent merchant policy, negotiate away fees, or release preview settlement as production money movement.
The product or post-purchase operations leader at an agent-shopping platform, ecommerce infrastructure provider, or merchant serving automated buyers.
Agent-friendly actions must remain bound to merchant policy, human authority, and financial finality.
Current agent volume and return pressure make the workflow timely.
The input has several references and inbound links but moderate grounded convergence.
High return volume, validated agent purchasing, six available capabilities, and a real multi-provider post-purchase gap support the orchestration layer.
The buyer is broad, a major platform already covers basic returns, one capability and the authorization token remain unresolved, settlement is preview, and provider semantics are complex.
Discussion
No comments yet — be the first to weigh in.