Carsparency Back Office — the operator console behind the marketplace

Carsparency Back Office — the operator console behind the marketplace | Sina Oshaghi

01Context

The marketplace is run by people, and this is their desk

Carsparency was not self-service classifieds. Between a seller entering a car and a dealer winning it sat a staff-run pipeline: requests were qualified, cars inspected and priced, dealers invited, auctions run and payments confirmed. The back office is where that work happens.

It is the largest desktop surface in the set: 68 frames at 1,440 px behind a seven-section sidebar (Requests, Trade, Cars, Car Price, Users, Finance and Setting), plus the inspection report the operation hands to buyers.

Carsparency Back Office — the requests table beside a seven-section sidebar, with filter, search, group operation and create-request controls — Figure 02The requests table, the console's landing view.

02Problem

Four prices, two conversations and a queue that never empties

A car has several prices at once: what the business is aiming for, what the seller wants, what the valuation says and what dealers bid. Someone has to see all of them to close the gap.

The reasons a price moved live in conversations: some with the dealer, some internal. And requests arrive faster than they can be opened one page at a time, so the console has to let staff act from the list.

03Flow

From request to settled trade

The sidebar follows the order in which a car moves. A request enters under Requests, becomes a car under Cars, gets priced under Car Price, is sold under Trade (auctions, inventory and listings) and is paid for under Finance. Users holds the three kinds of people involved: dealers, sellers and employees.

A request's status can be changed from the list itself, to Auction, Cancel auction or Review inspection, so moving a car forward does not mean leaving the queue.

The operator's pipeline, as the sidebar orders it

01
RequestA seller's request is listed, filtered, commented on and qualified.
02
InspectThe inspection is reviewed before the car moves on.

Carsparency Back Office — the quick view up close: request details, comment history, price history and valuations by condition — Figure 03The quick view up close. Dealer comments and internal notes run as separate threads, the price history records each change with its author, and the valuation column prices the car for four condition grades.

04Key decisions

Four decisions that make the console workable

Read from the frames; the file shows what was built, not the debate behind it.

01
A quick view instead of a page
An operator working a queue loses their place every time a row opens a new page. The quick view shows everything about a request over the list and lets its status change there.
Trade-off
The dialog is dense, with four panels in one view.
02
Show every price at once
Target, seller, fair and dealer prices usually disagree. Showing all four, with a history of who changed what, makes the negotiation visible and gives the operator the gap they are closing.
Alternatives
A single price field, which hides the operator's judgement.
03
Separate what the dealer can see from what staff say to each other
Dealer comments and internal communication are kept as distinct threads. One can be shared; the other can be candid, which matters for a business that sells on transparency.
04

05Solution

Act from the list, open the page only when you must

The quick view is the centre of the console. From any row, one dialog shows the request strip (contact, phone, car, status, reason, last editor, city, created), the comment history, the price history and a valuation for each condition grade: Like New, Good, Poor condition and Very poor.

Around it, the tables are built to be shaped by the people using them: filter and sort chips that stay visible, a column manager to show or hide columns, group operations for bulk changes, and a suggested-dealer list for each car with a live countdown to the auction's end.

Requests: list, filter, quick view, inline status change, comments
Trade: auctions, inventories and car listings, each with bids and suggested dealers
Cars and Car Price: make, model, trim, year and options; four-way pricing with history
Users and Finance: dealers, sellers and employees; payments and wallet histories

Carsparency Back Office — the auctions table with last, first, target and fair prices, bids and views for each car — Figure 04Auctions as a table rather than cards: each row carries last, first, target and fair prices next to bid and view counts, so an operator can compare cars at a glance.

Carsparency Back Office — the suggested-dealer dialog listing dealers to invite for a BMW X4

Carsparency Back Office — the column manager dialog with a toggle for each table column

Carsparency Back Office — the employee list with role and name filters and active sort chips

06Ecosystem

The console turns an inspection into something a dealer can trust

The back office sits in the middle of the chain. It receives what the seller declared on the web and what the inspector recorded in the field, and it sends priced cars out to dealers in Pro. Its Fair price is the same figure dealers see as Fair Market Value.

The same file holds the Advanced Inspection Report, a printable record of the car: exterior, general and interior details with verification marks, then a defects page drawn on the exploded car map that also appears in the Pro file, with signature fields for dealer and buyer.

Carsparency inspection report — page two, exterior and general details of the car

Carsparency inspection report — page three, interior details

07My role

Sina's part

Listed from the Back Office file. The files do not record team size or who decided what, and one version of the report is labelled with another person's name, so authorship there is shared.

Owned

Information architecture: the seven-section sidebar and its sub-sections
The request list, quick view and inline status changes
Pricing, auction, bid and suggested-dealer screens
User, employee, payment and wallet screens
The Advanced Inspection Report layout

Co-owned

Collaborated

A colleague credited on one version of the inspection report
Operations and engineering colleagues, not named in the files

The side menu is the one component set built locally in this file; the dialogs, inputs, pagination and icons in the console frames come from the shared Carsparency library.

08Outcomes

What the file delivers

Counts of designed work, not results. The console names four metrics (view-to-bid rate, bid-to-win rate, cancel rate and discount rate) but no file records a reading.

console frames: 68; At 1,440 px, across requests, trade, cars, pricing, users and finance; Delivered output
sidebar sections: 7; Ordered the way a car moves through the business; Delivered output
prices per car: 4; Target, seller, fair and dealer, shown side by side; Delivered output

What was delivered

Requests list and quick view
Inline status changes and comment threads
Four-way pricing with history
Auctions, inventories, bids and suggested dealers
Dealer, seller and employee records
Payments, wallets and the inspection report

09What I learned

What this work taught

01
Internal tools deserve the same design attention as the product
The console is where the business's real definition of success lives: its only metrics labels are here, not on the consumer site.
02
Showing four prices is a product decision
Most tools pick one number and hide the rest, which makes the operator's judgement invisible. Putting all four on screen turns pricing into a conversation with a record.
03
Test dense screens with data that disagrees
Every row in the file shows the same request and every price the same figure, so a console built to resolve disagreement was never drawn with any.

Language

Carsparency Back Office — the operator console behind the marketplace

The marketplace is run by people, and this is their desk

Four prices, two conversations and a queue that never empties

From request to settled trade

The operator's pipeline, as the sidebar orders it

Four decisions that make the console workable

A quick view instead of a page

Show every price at once

Separate what the dealer can see from what staff say to each other