I think you've identified the two reasons why EDI does not penetrate the SMB space – there are no user-friendly EDI clients AND even if there were, the small biz has to map it correctly for each of their trading partners.

Our approach is to provide a free, user-friendly client for the SMB to send or receive electronic invoices. We do the leg work of mapping that into a format digestable by their trading partners EDI, Accounting or ERP system. This becomes a one-size-fits all solution for the small business and for the large trading partner.

Ian

I always appreciate your comments. I may be an optimist, but I do believe that EDI client software can be developed that could be used by the small “Ma and Pop” suppliers and manufacturers.

I would think that most small suppliers are computer-literate to use QuickBooks and online banking to schedule payments. Why does an EDI client communications software application need to be any more challenging?

The challenge is to get large manufacturers, large retailers, and large service providers to map or provide a map with lookup tables that can link to the same group of data elements. The EDI map can be transparent to the small suppliers where they either enter the data or provide a standard .csv or Excel file as input.

On the surface this seems easy. But when you get down to it, there is always a snag. (or at least there seems to be.) The Order, Ship, Invoice set in itself has a variety of data issues that if unplanned will turn your b2b setup into anything but simple or helpful.

Even if the software for EDI and B2B is free, the Mom and Pop will need a supply chain consultant to help them set up or they will end up with a very error prone relationship. (Or should I say, “Exceptional” with the emphasis on “Exception”)