SPS - Amazon’s App Design
*designs shown do not include information from real Amazon retailers
Since becoming the designer for Amazon suppliers at SPS in 2025, I’ve focused on bringing clarity to dense data and complex revenue-recovery workflows. I lead the design end to end, creating experiences that help users understand deductions, identify recovery opportunities, and act with confidence.
Amazon’s Overage Invoices
-
The Challenge
Users needed a clear and reliable way to create and submit overage invoices. Users also needed to confirm the correct VAT ID or tax rate and understand when SPS had corrected an overage amount before submitting.
-
My Approach
I designed a dedicated Overages experience where users can create overage invoices and review all related details in one place. I added a required confirmation step for VAT and tax selections, along with notifications explaining when SPS corrected an overage amount.
-
The Outcome
The experience gives suppliers greater clarity and confidence when managing overage invoices. Users can verify tax details, stay informed about corrected amounts, and access everything connected to their overages in one place.
Amazon’s Vendor Returns
-
The Challenge
Amazon suppliers needed a clearer way to review and dispute vendor returns. Important details, including VRET numbers, related returns, warehouses, vendor codes, invoice numbers, processing dates, and return amounts needed to be brought together in one connected experience.
-
My Approach
I designed an end-to-end Vendor Returns experience using the familiar structure of Amazon CoOps while adapting it for return-specific workflows. I reorganized the list view around key return data, created a details card for processing information and amounts, and designed a dispute flow that groups related returns by VRET number and allows users to apply or customize dispute reasons.
-
The Outcome
Users can move from identifying a return to reviewing its full context and creating a dispute within one consistent experience. The design makes return amounts and related records easier to understand while giving users more control over how each return is disputed.
CoOp Disputing & Readiness
-
The Challenge
CoOp disputing depends heavily on timing. Users lacked a clear view of previous disputes and needed to know whether an invoice was ready to be included in a new batched dispute, especially when related cases were still unresolved.
-
My Approach
This became my first project after taking ownership of Amazon design in 2025. I added a detailed dispute history with direct access to individual cases, then designed a readiness timeline and warning system showing when an invoice is not ready, ready, nearing expiration, or expired.
-
The Outcome
The updated experience helps users understand what has already been disputed and identify the best time to take further action. It provides greater context when building batched disputes and helps prevent CoOp invoices from being submitted prematurely.
Designing in Motion
-
Amazon rarely stays still and neither has my first year leading design for SPS’s Amazon product. Its complexity and constant change have pushed me to research deeply, ask better questions, and collaborate closely with product and engineering to turn evolving information into clear experiences. It keeps me on my toes, and it’s helping me become a more adaptable and collaborative designer.