Customers · Success stories

Every partner on EDI. Here's how they did it.

Our customers run on EDI. Many of the companies they trade with don't. These stories show how we closed that gap from both sides: suppliers receiving orders from buyers without EDI, and buyers working with small vendors who could never send an EDI document.

Supplier stories Vendor stories →
two sides · one platform live
Client side · Supplier
Buyer without EDI→Supplier on EDI

Buyers order in a web portal. The supplier receives standard EDI purchase orders.

850, 997, 855, 856, 810
Vendor side · Buying from partners
Vendor without EDI→Client on EDI

Vendors acknowledge, ship and invoice in the portal. The client receives standard EDI.

855, 856, 810
The client side · Suppliers

Orders from buyers
who don't have EDI.

Our clients' systems are built to process EDI. Their smaller buyers sent orders by email, phone and spreadsheet, and someone had to type each one in.
Specialty food supplier

Independent stores on the same order pipeline as the national chains

Documents: 850, 997, 855, 856, 810
The challenge

The supplier received EDI orders from its large retail accounts. Its independent grocers ordered by email and phone, so those orders were keyed in by hand, often with the wrong item number or ship-to.

What we did

We invited each grocer to the Trading Partner portal. They build orders from the supplier's own item catalog and send them with one click. The platform translates each order into a standard 850 with the supplier's IDs and settings.

The result

Every order now reaches the supplier the same way, whether it comes from a national chain or a single-store grocer. Acknowledgments, ship notices and invoices go back to the grocer's portal automatically.

Consumer products manufacturer

A new distributor live without an EDI project on either side

Documents: 850, 810
The challenge

The manufacturer won a regional distributor that had no EDI capability. The distributor wasn't going to buy translation software or a VAN, and the manufacturer wasn't going to set up a manual order desk.

What we did

We set up the relationship in test mode first. The distributor placed test orders through the portal, and the manufacturer confirmed they loaded correctly before we switched to production.

The result

The distributor needed only a browser and a login. Invoices are checked against the original order in the portal, so pricing disputes surface right away instead of at month-end.

The vendor side · Buying from partners

Vendors who can't send EDI.
Clients who need it.

When our clients buy, the roles reverse. Their small vendors had to acknowledge, ship and invoice in EDI, and they couldn't.
Wholesale distributor

Small vendors acknowledge, ship and invoice from a web page

Documents: 855, 856, 810
The challenge

The distributor's purchasing system expected EDI acknowledgments, ship notices and invoices. Its smaller vendors replied by email, so buyers chased confirmations and receiving had no notice of what was arriving.

What we did

Vendors receive purchase orders in the portal. They accept, change or reject each line, record full or partial shipments, and turn the shipped order into an invoice. Each step produces a standard EDI document for the distributor.

The result

The distributor gets the same 855, 856 and 810 from a five-person vendor as from its largest supplier. Partial shipments are tracked, so open quantities are always clear.

Multi-location retailer

Orders created in the portal, delivered straight into the ERP

Documents: 850, ERP connector
The challenge

The retailer placed orders through the portal with suppliers that require EDI, but its own team then re-entered each order in its ERP to track receiving and payables.

What we did

We added an ERP connector. Orders are delivered to the retailer's ERP over a secure connection, mapped to its import format. Each delivery is logged, and redeliveries need explicit confirmation to prevent duplicates.

The result

One order, entered once. The supplier receives EDI, the retailer's ERP receives the same order, and nobody types it twice.

What these stories share

The same approach,
every time.

NO NEW SOFTWARE

A browser is enough

Partners without EDI never install anything. They get an invitation, a login and a portal built for their side of the trade.

STANDARD EDI

Nothing changes for the EDI side

The EDI side receives standard X12 or EDIFACT documents with the IDs, version and settings it already uses.

WE RUN IT

Our team sets it up

We configure the relationship, test it with real orders, then switch to production and keep watching every transmission.

Have a partner who can't do EDI?

Whether they buy from you or sell to you, tell us who they are. We'll show you how the connection would work and run test orders before anything goes live.

Talk to us See the non-EDI flow →