Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated VAN hyperlink

On this page

Table of Contents

Articles in this section


Children Display


SnapLogic's B2B solution allows you to integrate the EDI gateway of 1 EDI Source with another EDI gateway or B2B solution to send and receive B2B data. You can integrate with multiple applications supported by SnapLogic, such as NetSuite, SAP, Oracle, etc.

The following workflow explains the lifecycle of the B2B integrated solution:

Supported B2B Gateway Protocols

  • File Transfer Protocol (FTP)
  • SSH File Transfer Protocol (SFTP)
  • File Transfer Protocol secure (FTPs) 
  • Applicability Statement 2 (AS2)
  • HTTPS Web Service

In addition to the above protocols, you can leverage a Value Added Network (VAN) through 1 EDI Source to support all common B2B protocol requirements.  


  • Working knowledge of the SnapLogic Intelligent Integration Platform (IIP).
  • Appropriate level of access to the target endpoints to integrate.

  • Access to the 1 EDI Source web visibility portal. 

Implementing a B2B Solution

To implement SnapLogic's B2B solution you must first integrate the B2B gateway with SnapLogic. While each gateway has its specifications and requirements, the general procedure to integrate it with SnapLogic is per the following:

  1. Establish B2B requirements. Enter your requirements in the SnapLogic Discovery Questionnaire. This establishes your requirements from the SnapLogic B2B solution such as the trading partners to integrate and the transaction types. 

  2. Setup and configure the B2B platform. Make a note of the account attributes (such as tenant URLs, passkeys, client IDs) and the file paths that you may need while configuring the accounts in SnapLogic. File Reader/Writer Snaps that read from or write to the B2B platform's account, require these account attributes and file paths. Additional requirements may come up based upon the specific account, available Snaps, and client solution implementation. Typically, such requirements become clear during the implementation phase with 1 EDI Source. 

  3. Design and develop the SnapLogic Pipelines per your requirements. Use the account attributes that you stored earlier during this step. You need to build one Pipeline each for outbound and inbound transactions with the B2B platform per the following:
    1. Handling outbound transactions from the B2B Trading Partner to the Backend Application (Endpoint):

    2. Handling outbound transactions from the Backend Application (Endpoint) to the B2B Trading Partner: 

  4. Monitor the B2B system to ensure that the associated processes are running as expected and status reports are created and sent. The 1 EDI Source Managed Services team is notified of any errors or data exceptions from either the client's trading partner or backend application. Error resolution by either 1 EDI Source, the trading partner, or the customer is based on the error type.

The configuration of the B2B platform is performed by 1 EDI Source using the Discovery Questionnaire and follow up conversations through the implementation process. At the end of this process, you can expect the following three components to be configured:

  • B2B Gateway
  • B2B transformation engine
  • Customer-facing visibility and data insights web portal

When building Pipelines to write data into the B2B platform, ensure that you structure the data per the platform's expected schema.

SnapLogic EDI Use Cases

The following use cases demonstrate how SnapLogic's Pipelines can handle transactions between the B2B gateway and an ERP:

See Also