Why we built BridgeMail on top of the inbox instead of replacing it

The obvious way to fix messy purchase-order handling is to put everyone on a single system — an ERP where every order, every vessel, every contact lives in one place with one clean data model. That’s a real solution, and it’s the right one for a large chandlery ready to run its whole operation through it. It’s also a much bigger ask than it sounds, and it’s not the problem we set out to solve.

The email address is the interface

Every agent, master, and port contact a chandler works with already has that chandler’s email address. That address is the interface the whole market uses, and it took years to build — nobody wants to send an email introducing a new portal, and no agent is going to change how they send a PO because one supplier asked them to. Replacing the inbox means asking the entire market to change behavior on your behalf. That’s a slow, expensive ask, and it doesn’t scale down to smaller chandlers who don’t have the leverage or the time for it.

Reading is easier than replacing

The inbox already contains everything the business needs: the PO, the vessel, the port, the delivery date. What was missing wasn’t a new channel — it was the step that turns an attachment into structured data without a human re-typing it. That’s a narrower, more tractable problem than rebuilding how a chandlery communicates, and it’s the one we chose to solve. We cover what that looks like end to end in software for ship chandlers.

Where a full ERP still makes sense

None of this is an argument against ERP systems. For a chandler with 50 or more seats, ready to standardize every process into one system and willing to run a multi-month implementation, that’s often the right call. We wrote a fair, line-by-line comparison of that trade-off in our ShipCentric comparison — different tools for different sizes of company.

Built on our own inbox first

We didn’t design this in the abstract. BridgeMail started as the tool A2Z Ship Stores needed for its own mailbox, and it still runs there in production. The numbers from that operation are in the A2Z case study.