Your ERP is the system of record. It was never the system of entry.
Nobody is replacing it, and nobody should. The work is at the edges — where orders arrive as email, where a portal holds the status, where someone re-keys the same figure into two systems every morning before anyone else is in.
Read, write, reconcile.
- Read
Get the live state out
Inventory, orders, pricing, credit status — pulled from the screens your staff already use. No report writer, no warehouse project, no new module on the licence.
- Write
Key transactions back in
Receipts, adjustments, order entry, status updates, entered through the same interface a clerk would use and validated the same way. Every keystroke logged and replayable.
- Reconcile
Make the systems agree
Match what the ERP believes against the portal, the carrier, the bank and the inbox. Surface only the rows that disagree, which is usually a handful out of thousands.
Platform matters less than access. If a person can do it on a screen, it can be automated. And if there is a real API already, we will use that instead and tell you so — it is cheaper for both of us.
The honest version
This is not new ground. We put a System/36 reservation system on the web for Hampton Jitney — bidirectional, writing bookings straight back into the midrange — and built contractor order entry against Riverhead Building Supply’s AS/400 ERP, both years before anyone called it “integration.”
AS/400, System/36 · since the 1990s
And when wrapping is not enough, we rebuild. Aging Windows client-server applications — VB, Access, old .NET — re-platformed onto a modern LAMP stack (Linux, Apache, MySQL, PHP) that runs in a browser and carries no per-seat licence cost.
Legacy Windows → LAMP
Tell us what you have been told is impossible.
A couple of sentences about the system and what you need out of it is enough to get a straight answer about whether we can do it.