Prepare the reorder.
Keep the issue open.
We connected the trade account's purchase history to a repeat draft and a receiving reconciliation.
The product rows make the order recognisable, while the separate records explain what is being purchased and what arrived.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Trade wholesale reorder and delivery issues
- DESIGN FOCUS
- Keeping a repeat order separate from a delivery issue
A new draft does not replace the old delivery.
The delivery correspondence remains attached to the original issue. We kept that conversation out of the repeat-order state so a new purchase would not obscure an unresolved delivery. An anchored document reader completes the record without claiming live order processing.
The pages we designed.
The build brings trade order desk, repeat purchase draft, receiving reconciliation, delivery correspondence and order document reader into one workspace.
Repeat purchase draft
View the screen ↓Receiving reconciliation
View the screen ↓Delivery correspondence
View the screen ↓Order document reader
View the screen ↓Project scope.
We designed and built 5 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.
The gallery shows our rendered pages with identifying details masked.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
5 views Select any view to exploreHave a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.




