
Idealite contributed web engineering to a Post Office operations project to help staff answer item queries and keep postal supplies in view.
{ Project Overview }
About the Project
Post Office Limited is the UK's state-owned post office company, independent of Royal Mail since 2012. It describes itself as Europe's largest retail franchise network: more than 11,500 branches, most run by independent postmasters, offering over 170 products and services across mail, banking, bill payments, travel money and government services. Branches handle sending, returns and collections for several carriers, including Royal Mail, Parcelforce, DPD and Evri, and 99.7% of the population lives within three miles of a Post Office. Running a network this size depends on teams being able to answer questions about items, keep postal supplies stocked and resolve customer queries quickly, without disrupting the systems branches already rely on. Idealite's role: contributing web development to a Post Office operations project covering item status lookups, postal supplies and customer-query tools for staff.
- Industry
- Govt
- Services
Web App Development • API Development • System Integration
{ The Challenge }
Visibility Gaps Across a Busy Network
Key Challenges
- Slow answers to customer item queries
- Postal supplies running short unnoticed
- Manual checks across separate systems
- Change cannot interrupt daily service
{ Our Solution }
Information Staff Can Act On
- One view of items
- Supplies levels in sight
- Joined-up query handling
- Less manual cross-checking
{ How We Built It }
Development Process
How the UK Post Office engagement came together, step by step.
- 01
Understand the Operation
Mapped the questions staff most need answered: where an item is, which postal supplies are running low, and what a customer needs.
- 02
Design Around Staff
Shaped each view around one of those questions, so staff reach an answer without hunting across separate tools.
- 03
Bring Information Together
Joined item status, supplies levels and customer-query details, so one lookup can replace several manual checks.
- 04
Protect and Hand Over
Built protection for customer data into the tools and handed them over to the Post Office team.
{ Results & Impact }
Delivering Business Value
Item Queries Answered
Staff can check an item's status when a customer asks about it.
Supplies Stay Stocked
Teams can spot low postal supplies before they run out.
Easier Customer Help
Staff resolve customer queries in one place instead of several.
Service Kept Steady
New staff tools sit alongside the systems the network already depends on.
Technical details
Requirements, architecture, development, testing and deployment notes.
Technical details
Requirements, architecture, development, testing and deployment notes.
Objectives
- Clear Item Status: Give staff a clearer view of the status of parcels and mail items.
- Supplies in View: Help teams see postal supplies levels so shortages are spotted early.
- Easier Query Handling: Let staff resolve customer queries without checking several separate tools.
Requirements
- Item status: lookups of parcel and mail item status for staff.
- Postal supplies: a record of supplies on hand and those running low.
- Customer service: a staff interface for handling customer queries and transactions.
- Integration: connections to existing Post Office systems and third-party services.
- Data security: protection for customer information.
Architecture
- A web front end calling REST APIs, which connect to existing Post Office systems and third-party services.
Technology stack
- Front end: React, with Redux for state management.
- Back end: Node.js with Express.js REST APIs.
- Authentication: OAuth 2.0 with JWT-based sessions.
Front end
- Reusable React components for the item status, supplies and customer-service screens.
- Responsive layouts for different screen sizes.
Back end
- Node.js and Express.js REST APIs for item status, supplies and customer-service requests.
- OAuth 2.0 and JWT-based access control.
- Integrations with existing systems and third-party services.
Challenges & solutions
- Legacy integration: new tools had to work alongside existing systems without disrupting service.
- Data protection: customer information had to stay secure as work moved into web tools.
- Staff adoption: the tools had to fit the way teams already work, so change did not slow service down.
Outcomes
- Staff have a single view of parcel and mail item status to draw on when customers ask.
- Postal supplies levels are visible to teams, so restocking can be planned before items run short.
- Customer queries and transactions are handled through one staff interface rather than several tools.

Next case study
Qritive: Faster, More Consistent Cancer Diagnosis for Labs
{ Let's Build Together }
Let's build what's next
We partner with ambitious businesses to design, build and scale digital products that create lasting value.
Contact Us