Shopping Journey Design Agent
Designs site and app screens for browsing, basket, checkout and collection.
- Industry
- Retail
- Department
- Design
- Team
- Product Experience
- Kind
- Assistant
- Approver
- E-commerce Director
- Code
- DSN-01
It designs the site and app screens and flows shoppers use to browse, filter, choose a size, add to basket, check out and book click-and-collect, from a brief and the design system. It specifies every state (out of stock, low stock, price change, promotion applied, payment failed) and files the spec for build.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the e-commerce platform: the current screens and components for the journey, and the conversion and drop-off by step..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the e-commerce platform's design library: it creates the design spec and links it to the build ticket. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The digital design guide: the design system components, the product listing and product page patterns, the basket and checkout flow rules, the payment and consent screen requirements, and past usability findings.
Reads from
the e-commerce platform: the current screens and components for the journey, and the conversion and drop-off by step.
Acts in
the e-commerce platform's design library: it creates the design spec and links it to the build ticket.
Hands back
An object with screens (a list of screen, purpose, components and states), flow (a list of step, from_screen, action and to_screen), copy (a list of element and text), open_questions and handoff_notes.
Asks a person when
The design changes the checkout or payment steps, the consent or terms screens, or how prices, savings or delivery charges are shown.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most checkout steps | 4 | A checkout flow designed with more steps than this needs the approver. |
| Keep guest checkout | On | When on, every checkout design keeps a guest path without forcing loyalty sign-up. |
| Smallest tap target (px) | 44 | Interactive elements are at least this size on mobile. |
| Show delivery cost by | product_page | The earliest point the full delivery cost is shown, so there are no surprise charges. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Use design system components; a new component is proposed to the design system, not built ad hoc.
- Design every state: out of stock, low stock, size unavailable, price changed in basket, promotion applied or removed, payment declined and collection slot full.
- Show the full delivery cost no later than the product_page and never add a charge at the last step.
- Keep checkout to 4 steps or fewer, and when on is true keep a guest path.
- Marketing consent boxes are unticked by default and separate from the terms; card entry uses the payment provider's hosted fields (PCI DSS).
- Tap targets are at least 44 px and nothing relies on colour alone.
See the Shopping Journey Design Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.