EPADS — National E-Procurement Platform with Real-Time Government API Integration

The problem

Government procurement in most countries runs on paper, email, and trust. The system I worked on was being built to replace all three with a transparent, auditable, real-time digital platform.

The challenge: a government-scale procurement system has unforgiving requirements:

• Every action must be auditable for years
• Vendor identity must be verified against national databases (NADRA)
• Tax compliance must be checked in real-time (FBR)
• Multiple stakeholders need different views of the same data
• Bidding must happen in real-time with cryptographic proof of timestamp

What I built

I was a core contributor on the development team for EPADS — a nationwide e-procurement system used by government departments and verified vendors.

Modules I worked on:

1. Automated workflow routing Procurement requests follow different approval chains depending on amount, department, and category. I built the rules engine that routes each request through the correct approval path automatically — eliminating manual handoffs that previously took 3-7 days per request.

2. NADRA + FBR API integration Vendor onboarding requires verifying CNIC against NADRA (national identity) and tax status against FBR. I built the integration layer that handles these calls with proper error handling, retries, and graceful degradation when external services are slow.

3. Real-time bidding Vendors submit bids during open windows. I built the WebSocket layer that updates every connected user instantly when bids come in — with cryptographic timestamps so disputes can be resolved fairly.

The stack and why

React frontend for stakeholder dashboards (different views for procurement officers, vendors, auditors).

PHP backend because the team already had deep PHP expertise and government deployment infrastructure was PHP-friendly.

MySQL with careful indexing — procurement systems have read-heavy patterns that are perfect for relational databases.

WebSockets for real-time bidding (Pusher in production for reliability).

Outcome

The platform handles requests across multiple government departments. The biggest impact wasn't a single feature — it was the time savings: requests that previously took weeks of paperwork now route automatically in minutes.

What I learned

Working on a government-scale project taught me lessons that small projects never could:

1. Boring stacks win in production. Government IT teams maintain code for 10+ years. Choose stacks they can hire for.
2. APIs fail. Build for it. External services like NADRA go down. Your system should degrade gracefully, not crash.
3. Audit trails are not optional. Every action needs a who/what/when log. Build it from day one.
4. Real-time is hard. WebSocket connections drop. Reconnection logic is harder than the initial connection.