B2B eCommerce Implementation Checklist

If you have never implemented a new B2B eCommerce interface between two businesses, below is a short checklist on how to setup a B2B eCommerce solution:


How is B2B eCommerce Implemented?



Establish Need. First two businesses need to identify a need to exchange electronic documents. An example of this is where a supplier would need an electronic purchase order from a customer and the customer would need an electronic invoice.

Agree Upon A Solution. Next the businesses would need to evaluate the B2B eCommerce opportunity and identify a solution that is agreeable to both parties. In many cases, one or both of the businesses have set up a similar B2B eCommerce relationship previously either with another supplier or customer. The eCommerce solution defines the type of data (invoice, purchase order, etc.) that will be sent, the data standard that would be used (XML, EDI, non-standard), the communications protocol (FTP, SFTP, etc.), processing frequencies (once a day, event-driven, etc), and any quality checks (functional acknowledgment transactions, batch numbers, etc). In many cases, the businesses will sign a formal trading partner agreement.

Jointly Implement Plan. Once the technical solution is agreed upon, both partners would setup their system to exchange the data.

Test Interface. Next, they would send test data and both would agree that they are ready to send and receive electronic business documents.

Implement. After a successful test, both businesses would start accepting and receiving electronic business documents. As needed, either trading partner may request changes that would require them to go through the implementation process again to effect the change.

Back to B2B Commerce Resources.

Tags: ,



Related Posts:
  • mcislog
    7 Simple Steps of Integration - http://bit.ly/1cvsOF @RoyHayward - another great checklist for B2B eCommerce implementations
  • Or they could just decided to implement billFLO and in 5 minutes be up and running. OK, that was a tongue-in-cheek comment :) My point is that a checklist approach is only needed before embarking on a time and resource consuming implementation of a b2b product.

    We've taken a different approach with billFLO. We've designed a service that can be deployed in minutes, works equally well for buyer and seller and is priced at a point everyone can afford - free.

    Ian Sweeney
    CEO billFLO.com

    P.S. Nice blog, I've already added it to my morning reading list!

  • Ian,

    Wow, looks like I will be out of a job soon. The career of B2B integrations has just been replaced with billFLO!!!

    Seriously, if the only B2B integration challenge someone has is electronic infvoicing, then they should use a product like billFLO, but this product is not a comprehensive B2B integration solution.

    A real B2B solution needs to cover multiple transactions like Orders, Acknowledgments, Ship Notices, Invoicing and Remitance. (And this is just for a good and service transaction flow.) And if you are in healthcare or telecom, we have an addtional set of transactions regarding claims and or service.

    There is a reason that there are almost 1,000 diferent transaction types in current EDI standards. (I know, you could count more if you look at variations)

    I'm sure your product is a good one for business that only have this need. But also know that my job is safe because B2B is more than invoicing. (Much much more.)
  • Roy

    You're absolutely right. If the need is for a full b2b suite, you'll need more than e-invoicing.

    Where we've chosen to focus is on the invoicing component because SMBs need that resolved first and most businesses are small. If they receive paper invoices it costs time and money as well as slowing payment cycles for their (big) suppliers.

    Ian
    P.S. theintegrationengineer.com is also one of my regular reads! keep it up!
  • Ian,

    Sorry if my reply was a bit snarky.

    I know that invoicing and integrations with AP systems are a major challenge in B2B. It doesn't stop being a challenge just because the company is large. Most of my integration career has been spend integrating with big vendors. And we got much more traction integrating the catalog and supply chain aspects of the relationship.

    Invoicing and Remittance work seems to always be more touchy both technically and politically.

    ----

    And thanks, its nice to hear you find value in my blog too.
    :)
  • Looks like it did take my post. I am removing this one as a duplicate of the other.

    Oops
blog comments powered by Disqus