Retail · Case Study
Thanks for Visiting
Reach out
Overview
Dealership side · ~9 min read
The Track
Featured projects from Tekion Retail.
A dealership runs its whole day on one piece of software. Retail is the half of it the dealership itself touches: the deal a salesperson builds at a desk, the money the cashier takes at the counter, the paperwork the customer leaves holding.
Four of these 5 shipped for Inchcape and Renault Retail Group on ARC; the fifth is a 3D pack that went out across the whole platform. Each began as a flow nobody had written down, and ended as a system you configure rather than rebuild for the next market.
What it was made of
- Design system
- Logs 2.0 gave components back to the system, for everyone after it
- Web and mobile
- ARC and DRP. Every frame below is the desktop half
- Systems, not screens
- Templates, field sources and setup, rather than one-off screens
- 3D and illustration
- The vehicle pack, and the plugin that renders it live
- Cross team
- Design, product, engineering, QA, finance and the business
- Ownership
- A live 3 month project taken over mid flight, run from design
- 01Cashiering at Invoice LevelInchcape · ARC
- 02Order Forms & InvoiceInchcape · ARC
- 03Contract Management ModuleRRG · ARC
- 04Activity & Audit Logs 2.0Inchcape · ARC
- 053D PlaceholderTekion · Platform
- Under NDAA live product for real dealerships, so not all of it can be public. What is here is what I can show.
Cashiering at Invoice Level
01Inchcape · ARC
The problem was the unit. A dealership was paid one amount against one deal total, which is not how a customer actually pays: one invoice now, another later, part in cash and part on a card.
The solution made the invoice the unit, each one payable on its own, in part, by any method, with all 23 payment paths drawn in 3 groups before a screen was designed. The outcome, as reported on the project's own brief, is 97% of cashiering use cases covered, satisfaction up 23% and a 93% overall score. The output is a framework running at 15+ UK dealerships and built to take the next market's rules.
Screens

Cashiering, invoice by invoice
- 23 flows
- Every payment path drawn, in 3 groups
- 97%
- Of cashiering use cases covered, from the project brief
- 15+
- UK dealerships on the rebuilt flow
Order Forms & Invoice
02Inchcape · ARC
The problem was that every market wanted its own paperwork. A country's finance rules and its legal requirements each landed as another order form to build, and another form meant a developer, a release and a wait.
The solution was a single template a dealership's own finance manager configures: any field renamed, given a sample value or switched off, against a live preview of the document the customer will receive. The outcome is that a new market is set up rather than rebuilt, by an admin rather than by engineering. The output is one order form and invoice system, built for Bravo Auto and integrated across the company and its clients.
Screens

Where the document starts
- 1 template
- Configured per market instead of rebuilt per market
- Live preview
- Every change shown on the document the customer receives
- Admin, not dev
- A finance manager reshapes the form; nobody ships code
Contract Management Module
03RRG · ARC
The problem is written on the brief itself. Provision normally sits with the bank that owns the leased vehicle. At Renault Retail Group the bank and the dealership are subsidiaries of the same parent, so regulation puts the provision on the dealership instead.
The solution is a module the dealership manages provision from, its 85 fields each given a source, RCI or ARC, and its error reporting drawn 6 ways before one was chosen. The outcome is provision held and tracked where the regulation puts it, by the party that answers for it. The output names its own next step: lease activity, active and inactive users, equity mining.
Screens

Every contract, and what is set aside against it
- 85 fields
- Each given its source, RCI or ARC, by the dealership
- 6 explorations
- Error reporting drawn 6 ways before one was chosen
- Dealer held
- Provision tracked by the dealership, not by the bank
Activity & Audit Logs 2.0
04Inchcape · ARC
The problem was that a log said something had happened without saying where. Reading one meant rebuilding the record it belonged to from memory, and the old system was deep enough that owning it took calls with senior designers, managers, product managers and developers before a line could be drawn.
The solution, built with a senior designer, borrows a shape every user already has: the folder path from a desktop file browser, run across the top of the panel, with every entry coloured by the kind of change it records. The outcome is a log read at a glance, across 4 record types and 10 use cases. The output went back into the design system as new components and a new process for the teams after this one.
Screens

Where the record lives
- 4 record types
- Order forms, sales orders, reservations and invoices
- 10 use cases
- Each one drawn with the entry its action writes
- 3 colours
- The kind of change reads before the sentence does
3D Placeholder
05Tekion · Platform
The problem was an empty slot. Every list, card and deal screen keeps room for a picture of the car, and with no photograph on file that room printed text. The design system had no standard thing to put there.
The solution was to model the car nobody sells and render it from 6 angles, one for every slot the platform has. The outcome is a placeholder used across the whole platform, for GM, Ford, Aurora, Honda, RRG and Inchcape among others. The output is the pack itself, and the internal plugin built with a staff designer that renders the model live into the frame that needs it.
Screens

Three quarter front
- 6 angles
- One car, rendered for every slot the platform has
- 6 brands
- GM, Ford, Aurora, Honda, RRG and Inchcape
- 1 plugin
- Built with a staff designer, renders the model live
What it taught me
The spark
The lesson was not a method. On all 5 of these files a decision had to earn its place against something real: a market's law, a cashier's afternoon, a table row 40 pixels wide. It is why none of them ended in a finished screen and all of them ended in something configurable.
I was already working that way before I noticed I was. What my manager and the staff designers around me gave me was the noticing: watch first, ask the question nobody has asked yet, and most of the design falls out of the answer. That habit is what eventually took me to a masters in the UK.

