When I first joined the Tradz project, most of the team’s discussions were heavily focused on the seller side: dashboards, card management, and transaction flows. But from a product perspective, I saw something more fundamental, buyer experience will never be healthy if the system behind it is messy.
A marketplace is a two-sided product. What buyers see on the front end is entirely shaped by how sellers manage data, inventory, and listings on the back end. If the seller system is unclear, buyers will feel it through inaccurate data, confusing listings, and inconsistent purchasing experiences.
This project was never just about building a seller dashboard. It was about creating a reliable foundation for buyers.
Tradz aimed to build a collectibles marketplace for serious buyers—not casual window shoppers, but collectors who care deeply about card condition, authenticity, and detail.
However, when I joined, the product was still in an early and fluid stage. There were big ideas and ambitious goals, but no solid system yet to ensure that the information reaching buyers would be accurate and trustworthy.
The seller dashboard became the most critical starting point—not because sellers were more important than buyers, but because every buyer experience begins there.
Instead of jumping directly into screens and UI, I started with one simple question:
“If I were the buyer, what information must always be correct, clear, and consistent?”
The answer always came back to the same things:
Clean product structure
Accurate card data
Clear listing status
No misleading information
None of these problems could be solved only from the buyer-facing interface.
The issue had to be fixed at the source.
One of the earliest decisions I made was separating the seller’s operational dashboard from analytics. At first glance, this looked like an internal design decision, but the impact was directly tied to buyer experience.
If sellers were forced to process every metric in one overloaded screen, they would likely:
Lose focus
Manage listings more slowly
Overlook important product details
By making the dashboard focused on daily operational tasks and keeping analytics as a separate reflection space, sellers could work faster and with more accuracy. The final outcome was better-maintained listings, which directly improved buyer trust.
In the collectibles industry, one small mistake can break buyer trust instantly. A single card with a different condition can mean a completely different market value.
When I started working on card management, the feature still existed mostly as a concept. If left ambiguous, buyers would eventually face the consequences through:
Mixed product listings
Unclear card details
Confusing order experiences
I designed the card management flow with one principle:
One card should always represent one clear truth.
From data input to listing management and status visibility, the system had to guarantee that what buyers saw on the front end could be trusted without hesitation.
One important decision came from transaction tables. Initially, one order was represented as one product. In the collectibles space, this was risky.
A buyer could place one order containing multiple cards with different conditions, values, and details. If this was simplified into one generic product label, it would create confusion and potential disputes.
I pushed for better data structure and clearer labeling so that what sellers managed internally would remain accurate for buyers during checkout and order history.
This was not a flashy UI improvement, but buyer trust is built on details like this.
Toward the final phase of the project, the team needed multiple designs within an extremely short timeline. I completed more than ten end-to-end mockup pages in a single night.
This speed was important not just for internal presentations, but for protecting buyer experience from becoming fragmented due to delayed design decisions.
Because the structural foundation had already been built, I could move quickly without sacrificing consistency.
Design, in this moment, became a tool for maintaining momentum.
I also approached the “Coming Soon” landing page from a buyer-first perspective, even though its main target was attracting large sellers.
A marketplace that wants buyer trust must also show that the sellers joining the ecosystem are serious and credible.
The messaging and copy I created focused on positioning Tradz not as an open marketplace with no standards, but as a curated ecosystem designed for high-quality sellers.
Buyers may never directly read this page—but they would feel the impact through the quality of sellers who eventually joined the platform.
By the end of the project, Tradz was no longer just a collection of ideas. It had a clearer structure, stronger system logic, and a product direction the development team could confidently continue building.
Sellers could manage products with more clarity. Developers had a reliable design reference. Product managers had stronger alignment. And most importantly, buyers were protected from confusing and inconsistent marketplace experiences.
The biggest impact of my work was not a single screen, it was the quality of buyer experience created through the invisible system behind it.
As a Senior Product Designer, I learned that buyer experience is often shaped by decisions users never directly see.
Designing seller systems correctly is one of the most effective ways to protect trust in a two-sided marketplace.
At Tradz, my role was to ensure that everything reaching buyers was supported by a structured, consistent, and trustworthy system.
That is where design truly works.