SaaS · Thrive IT Solutions
OrderBuddy
Multi-Tenant Courier Dispatch & Tracking Platform Unifying Pathao, RedX and More Behind One Dashboard
- Couriers
- Pathao, RedX
- Secrets
- AES-256
- Queue
- BullMQ
The problem
One shop, many couriers, many dashboards
Online shops in Bangladesh work with several couriers at once. Each courier has its own dashboard, its own API and its own data format. Staff copy the same order into multiple portals, tracking is scattered, and API keys often sit in plain text.
The build
One payload in, the right courier call out
Built a Turborepo + pnpm monorepo: a Next.js web app for the landing page, merchant dashboard and public tracking pages; a Node.js worker that processes BullMQ jobs from Redis; a courier package using the strategy pattern so each courier is one adapter; and a crypto package that encrypts credentials with AES-256-GCM. Prisma runs on PostgreSQL with a multi-tenant client extension. A companion Expo mobile app is in progress.
Each courier is a small adapter behind one shared interface. Adding a new courier means writing one adapter, not changing the dashboard. Slow courier API calls run in a background worker, so the merchant never waits on them.
Unified Dispatch Engine
Strategy-pattern courier adapters turn one payload into the right Pathao or RedX API call.
Background Queue
BullMQ + Redis worker takes slow courier calls off the request path and retries failures.
Encrypted Credential Vault
AES-256-GCM encryption for every merchant's courier API keys and secrets.
Results
What shipped
- One order payload dispatches to Pathao or RedX. A new courier needs only one new adapter.
- Courier API calls run in a BullMQ background worker, so the merchant dashboard never waits on slow courier APIs.
- Courier secrets are encrypted at rest with AES-256-GCM, and every merchant's data is isolated at the database client layer.