Highly manual processes for disputing in Vendor Central Disputing claims on Amazon Vendor Central is a challenge due to a largely manual-driven process coupled with a non-intuitive interface. Some of the key issues associated with disputing on VC are:

1. Claims download This process involves dispute analysts to log in multiple times in the system throughout the day just to check for claims. Every claim has to be manually downloaded from the portal as it cannot be fetched in bulk.
2. Document upload Documents such as claims, remittance, proof of delivery, bill of lading have to manually collected by analysts from multiple sources and upload individually into the portal for every single claim.
3. Information key-in Information related to each dispute has to be painstakingly keyed into the portal. Given the large claim volumes, this could delay raising disputes significantly.
4. Manual correspondence Every time there is an invalid dispute, analysts have to manually type and send the denial correspondence with relevant documents attached, such as claims, POD, BOL, to Amazon.
5. Non-standardized cross-team collaboration Given that disputes involve teams from multiple departments, including cash allocation, collections (if handled separately), logistics, sales, and supply chain, analysts often end up wasting time in coordination instead of actual dispute research. As a result, dispute resolution:

Turns Highly Manual
• Adds little value
• Turns Time consuming
• Misfires on Metrics

Why not let robots do these menial tasks?