← All projects

Merchant Console · Order detail

The whole story of an order on one screen

At Lidia I designed order management and the cancel, return and refund flows from zero. This is the Merchant Console order detail, redrawn with sample data; it aims to let sellers answer any question about an order without leaving the screen.

Role
Product design
Type
Lidia Commerce · representative screen
Platform
Web · B2B & B2C
Product & B2B
Order detail

Lidia's real screens are confidential. Screens on this page are representative work, redrawn with sample data based on my experience on these products.

Problem

To understand one order, sellers moved between shipping, payment, campaign and customer screens. In split shipments, which item was in which package, the effect of discounts and the net payout all lived in different places.

Solution

A package-based item list, a payment summary with campaign and coupon breakdown, the seller payout, customer and risk cards, and one order history that includes the AI agent's activity.

Intended impact

Sellers answer order questions on one screen, and the next task is always the primary action.

Final design

Order detail: shipping, payment, customer and history together

Order detail
  1. 1

    The next task is the primary button

    Depending on the order's state, the next action, here shipping the second package, is the primary button.

  2. 2

    Package-based view

    In a split shipment each package is its own card with status, warehouse and tracking number.

  3. 3

    From discount to payout

    Campaign and coupon breakdown, VAT and the net payout after commission share one card.

  4. 4

    One timeline

    Team notes, system events and the AI agent's messages to the customer share one history.

Outcomes

Intended impact and what I learned

One screen

shipping, payment, customer and risk

Per package

tracking for split shipments

Net payout

after discounts and commission, on the order itself

  • Don't make users guess the next step.

    A primary action that follows the order's state removes the guesswork.

  • People and AI in one history.

    Seeing everything the agent did next to the team's notes makes it easy to audit.

Next steps: partial return flow · merging packages · creating order notes from customer messages