The organisation needed one industrial dealer platform for customers, dealers, sales teams, and operations managers. The existing journey divided technical catalogues, dealer pricing, stock visibility, quotes, orders, approvals, fulfilment, warranty requests, documents, and sales reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete industrial dealer platform shaped around customers, dealers, sales teams, and operations managers
The organisation needed one industrial dealer platform for customers, dealers, sales teams, and operations managers. The existing journey divided technical catalogues, dealer pricing, stock visibility, quotes, orders, approvals, fulfilment, warranty requests, documents, and sales reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between dealer commerce, order management, and after-sales service, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole industrial dealer platform.
- Separate firm industrial distribution rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined dealer commerce, order management, and after-sales service without blurring roles
Share catalogue and order rules across customer, dealer, and administration experiences while keeping commercial access role-specific.
In the industrial dealer platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Angular, Flutter, .NET formed one supportable industrial dealer platform
The architecture follows business ownership rather than the navigation menu. Angular, Flutter, .NET share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind order management.
In the industrial dealer platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Angular supports the primary product surface.
- Flutter owns a bounded part of the product journey.
- .NET keeps operational data and handoffs reviewable.
The release had to prove the whole industrial dealer platform, not one polished screen
Customers and dealers can complete routine business directly and operations retains one view of orders, stock, and service commitments. The release plan therefore followed representative work across every audience and the complete path through dealer commerce, order management, and after-sales service.
Acceptance for the industrial dealer platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Customers and dealers can complete routine business directly and operations retains one view of orders, stock, and service commitments.
- 01
The industrial dealer platform now gives customers, dealers, sales teams, and operations managers one shared operating record.
- 02
Dealer commerce, order management, and after-sales service follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.