Compare

OrderEase vs ParcelNow vs Joel Transport

The problem, what was built, the stack and the outcome, next to each other.

Clear · Up to 3 at a time

In common

  • Shared stack: none in common
  • Both kinds of work: Web, Platform
  • Order: Joel Transport (Dec 2022 – May 2023) → OrderEase (2025 – 2026) → ParcelNow (2025 – 2026)

Swipe sideways to compare ›

OrderEase ›

Branded online ordering for restaurants and retailers

ParcelNow ›

On-demand parcel delivery with real-time tracking

Joel Transport ›

Online booking platform on AWS

At a glance

Role
Technical lead, Smart Kitchen Co
When
2025 – 2026
Length
1 yr
Status
Live
Type
Web, Platform
Role
Technical lead, Smart Kitchen Co
When
2025 – 2026
Length
1 yr
Status
Delivered
Type
Web, Platform
Role
Lead Engineer
When
Dec 2022 – May 2023
Length
6 mo
Status
Live
Type
Web, Platform

The problem

Direct ordering and order management: menus, orders, payments and fulfilment, with automated order intake and status updates that cut merchants' operational overhead.
Customer and operations dashboards with backend services for parcel lifecycles, tracking events and notifications, built for high-throughput transactional workflows.
Centralised the customer journey and operational data, reduced manual hand-offs and set up a documented AWS foundation.

What was built

—
—
Led architecture and hands-on engineering for an online booking platform: Python APIs and the AWS deployment architecture, integrated with Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ.

Stack

  • Next.js
  • FastAPI
  • PostgreSQL
  • Redis
  • Next.js
  • FastAPI
  • PostgreSQL
  • Redis
  • Docker
  • Python
  • AWS
  • Paystack
  • Sage
  • Zoho

Highlights

  • Fast, responsive ordering on Next.js
  • FastAPI services for menus, orders, payments and fulfilment
  • Next.js dashboards over FastAPI services
  • Live delivery updates through logistics and messaging integrations
  • Python APIs and AWS deployment architecture
  • Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ integrations

Infrastructure choices

—
  • Docker-based development and deployment standards
  • AWS

Outcome

—
—
Centralised the customer journey and key operational data, reduced manual hand-offs and established a documented AWS foundation for future development.