PickItUp Platform

The problem

A logistics request needs to move between the customer, driver, dispatch team and payment process without losing operational context.

What was built

A logistics platform spanning customer, driver, dispatch and payment architecture. This case study distinguishes the software work from the PickItUp transport venture.

What works now

The recorded scope includes the customer, driver, dispatch and payment architecture. Which flows are deployed and validated end to end has not yet been confirmed for this public record.

Demo & integration boundaries

Live payment processing, routing connections and operational dispatch readiness require confirmation. Architecture scope is not evidence that these integrations are running in production.

Role & context

Included in Amrish Seunarain’s product-development portfolio. The individual and team contributions have not yet been documented in this public case study.

Software associated with the PickItUp private transport venture, distinct from the municipal Pikitup waste service.

Architecture in plain language

Separate customer and driver experiences connect with dispatch and payment responsibilities. This describes the architecture scope, not a production service guarantee.

• Customer
• Driver
• Dispatch
• Payments

The project brief proposes React, Node.js, Maps and Paystack. Their implemented or live status is not verified here.