Case Studies
Five Times Faster Fulfilment on a Legacy ERP
We built a web and Android platform for LEE Distributors in New York that bridges their webshop and a legacy ERP, then runs packing, carrier selection and label printing automatically across the warehouse, with zero downtime under a demanding threat environment.
Client Snapshot
The Challenge
LEE Distributors ran on a legacy ERP that could not keep up with modern order management. The webshop and the ERP lived in separate worlds, so orders had to be moved and reconciled by hand, and the warehouse work of packing and shipping was manual and paper-heavy.
That created the usual costs of a paper process at scale: slow throughput, room for picking and packing mistakes, and no clean record of what shipped to whom. Replacing the ERP outright was not the goal. It held data and logic the business still relied on. The job was to make it work like a modern system without ripping it out.
There was a second, harder constraint. As a high-value distributor, LEE treats uptime and security as non-negotiable. Any new system had to be faster and easier to use, and also harder to take down. It had to keep running through a demanding threat environment, not just on a quiet day.
The Approach
We built a web application and an Android app that sit between the webshop and the legacy ERP and automate the full fulfilment path, without replacing the ERP underneath.
Orders flow in from the webshop and are bridged to the ERP automatically, so the two systems stay in step without manual re-keying. From there the platform takes over the warehouse work. It picks the best carrier and service for each order, and prints every shipping label automatically to Zebra printers across the floor. Staff scan each item into a box on Zebra handhelds and mark it packed, so what goes into the box is verified rather than assumed. Customers get their own portal where they can track shipments and see the full packing specification, every box and every item it contains.
Because uptime and security were core requirements, we hardened the platform with specific security techniques and a resilient hosting setup, so it stays online under load and under attack.
Phases
Phase 1 - Bridge the Webshop and the ERP
Built the Laravel web application that connects the webshop to the legacy ERP and keeps orders in sync automatically.
Phase 2 - Automate the Warehouse
Added automatic carrier selection, automatic Zebra label printing, and the React Native Android scanning app for box-by-box packing on Zebra handhelds.
Phase 3 - Customer Portal and Hardening
Shipped the customer tracking and packing-specification portal, and hardened the platform and infrastructure for zero downtime under a demanding threat environment.
What We Shipped
- A web app linking the webshop to the legacy ERP
- An automated order, packing and shipment workflow
- Automatic carrier selection and Zebra label printing
- An Android scanning app running on Zebra handhelds
- A customer portal for tracking and box-by-box packing specs
- Security hardening for zero downtime
Results
Paperwork dropped to a third of what it was, and order processing became five times faster. Because every item is scanned into its box before the order is marked packed, pick-and-pack errors were eliminated.
Just as important for a high-value distributor, the platform has run with zero downtime to date, including through attempted attacks. The security hardening was not a checkbox; it is why the system stays up when it is targeted. The platform is in daily use across the warehouse, and we continue to maintain and extend it.
Tech Stack
- Laravel - web application bridging the webshop and the legacy ERP
- React Native - Android scanning app on Zebra handhelds
- MySQL - order and fulfilment data
- Laravel Forge + DigitalOcean - deployment and hosting
- Cloudflare - security and resilience layer
- Zebra - label printers and handheld scanners
Lessons Learned
The instinct with a struggling legacy ERP is to replace it. Often the better move is to leave it in place and build around it.
LEE's ERP still held logic and data the business depended on. Wrapping it with a modern web layer, instead of migrating off it, removed the risk of a big-bang cutover and got the warehouse a faster process much sooner. The hard engineering was in the seams: keeping two systems in sync reliably, and hardening the new layer enough that adding it did not add an attack surface. If we did it again, the approach would be the same. Modernize at the edges first, and only touch the core system if and when there is a clear reason to.
Stuck With a Legacy ERP That Can't Keep Up?
If an older system is holding back fulfilment, integration or customer experience, you usually do not have to replace it to fix it. We connect legacy systems to modern, automated workflows, and harden them to stay up under real-world conditions.
Talk to us about your project →