Less repeated work. More control over what ships.

Seller Dashboard is Ezze’s web workspace for sellers to prepare products and fulfill orders. As the business expanded from Live Sales to Marketplace, sellers needed to manage both channels without repeating setup or losing control of individual items and parcels.

In 2023, listing was manual and orders shipped separately. Marketplace, on-demand AI, and automatic order grouping followed in 2024. The 2025 redesign addressed what those additions exposed: long forms, repeated inputs, and bundles that did not always fit one package.

I led workflow and interaction design across the three releases. Interviews and feedback meetings with three experienced sellers highlighted repeated listing and shipping work. I combined that input with workflow reviews and feedback from live use to decide what to automate and what sellers needed to control.

One product. Shared inventory. Channel-specific prices.

Reviewing the 2023 and 2024 forms showed that AI assistance addressed writing effort while the editing surface remained long. I separated shared product information from channel decisions: photos, details, variants, and stock stay together, with channel settings and shipping alongside them.

Live Sales reserves inventory for Buy It Now or Auction; Marketplace uses the remainder. Sellers can price only the variants they want in each channel. Unpriced variants stay out of that channel, without removing them from the product.

I accepted an extra opening step for pricing dialogs because channel configuration did not need to dominate every product edit. Sellers can prepare the product first, then choose variants and prices for each channel.

A photo starts the draft. Sellers make it accurate.

In 2024, sellers requested AI for each listing. Photos were already required and supplied the draft’s input. In 2025, I connected generation to photo upload, removing the repeated request without adding another preparation task.

Vintage sellers still needed to verify item-specific details. I kept the generated draft editable, with the review prompt beside the photo and seller review before creation. Recently used categories handle recurring selections separately, keeping AI assistance focused on the individual item.

Find matching orders. Let sellers choose the parcel.

After automatic grouping launched in 2024, feedback from live use showed that same-buyer orders could need separate packages, especially for bulky items such as sneakers. A buyer match established relevance, but not package fit. I proposed keeping automated discovery and adding seller confirmation.

In 2025, selecting a confirmed order surfaces other eligible orders for the same customer and address. Sellers choose which to include. This adds a confirmation step, but lets the person handling the items decide what belongs in each parcel.

Connect seller operations to business performance.

Admin Dashboard is Ezze’s internal workspace for managing sellers, products, orders, content, and payouts. In 2021–2022, I redesigned seller pages, analytics views, and shared UI components with product management, engineering, and operations.

The earlier dashboard centered on community activity. As commerce operations expanded, seller information remained scattered across overlays and long pages that mixed account details, transactions, and payouts. Finding a record and understanding its business context had become separate tasks.

I reviewed existing screens and operations requests, grouped related information, and designed the revised layouts. I then connected dashboard summaries to detail views and documented recurring table, card, and field patterns.

Give each task a home. Keep the seller in view.

I reorganized seller details into six task tabs, separating profile context, products, orders, content, and payouts. Identity, account status, and Stripe connection stay in the shared header; Activity provides a consistent entry for history and notes.

The tradeoff was an extra navigation step for a more focused working area. Overview brings performance and profile context together. Record-heavy tabs give their tables room, and purchased orders sit within Orders instead of a separate destination.

For wider tables, I fixed record identity and status while supporting fields scroll horizontally. This preserves the relationship between a row and its details. I applied the pattern selectively, rather than forcing every list into the same layout.

Follow a business signal through to its detail.

Operations needed to move from a high-level number to the records behind it. I designed summary cards for scanning and detail pages for closer inspection. View more connects the two while preserving the selected metric and reporting period.

For Total Sales, I paired a period summary with a comparison chart and Daily Breakdown. Exact values appear on hover or tap, keeping the chart readable without labeling every point. Ranked tables identify the sellers, products, and livestreams behind business performance.

A shared date range establishes the starting window; local ranges let operations investigate one card independently. That flexibility can produce different reporting periods on the same dashboard. I kept each range visible beside View more and carried it into the detail view, making the scope of each comparison explicit.

Make shared patterns carry across the workspace.

I collected recurring buttons, fields, filters, status tags, cards, and table cells from the redesigned pages and organized them into a shared component library. Typography, semantic colors, spacing, corners, and strokes give those components a common visual base.

I documented empty, filled, and focused fields; default and applied filters; selected navigation; and feedback for success, information, warnings, and restrictions. These states show how each component responds during an operation.

I also documented how the parts combine in complete examples: an Orders table, an analytics card, and empty, writing, and saved notes. These examples connect the library to the same screens shown earlier.

Make structure, data, and interaction work together.

The delivered pages give seller information a clear location, connect dashboard summaries to supporting records, and use consistent controls. The component library documents the states and patterns used across those pages.

Stakeholders responded positively. Following the redesign, internal records showed:

Sales and average order value increased during the same period; these figures reflect broader platform performance.

The project taught me to settle information groups before polishing individual screens. Checking headers, tab names, metric labels, and states across related pages was essential to keeping the work coherent.

Seller operations, beyond the desktop.

Seller Hub brings Ezze’s seller operations to mobile across Live Sales and Marketplace. In 2026, I owned its 0–1 product design, building on Seller Dashboard’s 2023–2025 web foundation. The product is now live.

Seller work extends beyond a desk, from preparing stock to handing purchases to buyers. The mobile product needed to support complete tasks while preserving the inventory, payment, and order rules established on the web.

I defined the mobile task hierarchy, focused editing model, and fulfillment checkpoints with product and engineering. The work connected product preparation, order decisions, and verified pickup in one seller workspace.

Keep the rules. Rethink the task.

I organized the experience around preparing a product, configuring its channels, finding an actionable order, and completing fulfillment. Each task needed a clear entry, its required information, and a visible saved or completed result. The criterion was whether sellers could finish and verify the task, rather than how many desktop controls could fit on the screen.

On mobile, product summaries lead to focused sheets for variants, prices, and shipping. Order cards prioritize recognition and action; identifiers and financial breakdowns sit in Order Details. I accepted extra openings for individual edits in exchange for a clearer main surface and a predictable return point. Simplification changed the information hierarchy while keeping business rules intact.

Focused edits. A reviewable product.

A photo starts an AI-assisted draft for seller review. I carried that capability from SDB into a mobile capture-and-review task, keeping generated details editable before product creation. Save Draft preserves unfinished preparation.

Variant stock remains the source of inventory. Live Sales reserves quantities for Buy It Now and Auction; Marketplace uses the remainder. Sellers configure only the variants intended for each channel. Unused rows stay out of saved summaries. This separates creating a product from deciding where each variant sells, without suggesting the same stock is available everywhere. Live Sales validates quantity-and-price pairs; Marketplace shows remaining inventory as read-only and validates prices only for variants the seller chooses to list.

Clear next steps. A verified handoff.

I grouped Orders by fulfillment progress, retaining detailed statuses on each card. To Fulfill includes Confirmed, Pre-Transit, and Ready for Pickup, helping sellers find unfinished work without a tab for every status.

Related orders remain suggestions: sellers review the buyer, address, and selected items before continuing. They can purchase a label, add tracking, or arrange pickup. Label purchase and tracking produce Pre-Transit; preparation is distinct from delivery. Before label purchase, a final review keeps selected orders, destination, service, and total cost together at the point of commitment.