Replace a legacy mailbox and parcel operation with one platform, without stopping the mail.
The challenge
A mail-forwarding operation ran members, parcels, scanning and shipments across systems that had grown apart over years. The replacement had to be designed and migrated while the existing operation kept receiving and forwarding mail every day.
What we built
Outcomes
How we shipped it
Design the data first
Before any feature work, the member, parcel, scan and shipment models were redesigned as one schema. The legacy behaviour was captured as an explicit API mapping document so nothing in the old system could quietly disappear during the cut-over.
Shipments as their own module
Forwarding is where the operation makes and loses money, so shipments were built as a module of their own — carrier handling, per-parcel state and billing-relevant events — rather than as a field on a parcel record.
Migrating a live operation
The plan was written in phases with a documented flow per phase, because the warehouse could not stop scanning while the platform changed underneath it.
Stack
Aprojectlikethis?
One-page brief, two-week sprint, real exit ramps.
next kickoff · week 34