Product that suits modern B2B Tech companies

Book Demo
B
Book demo call-to-action illustration
BACK
B

B2B integration tools: pick the category first, then test how they fail

Integration Strategy
February 6, 2026
Summarise the blog with AI
Open in ChatGPT
Ask questions about this page
Open in Claude
Ask questions about this page

Last verified: 2026-11-17

Key takeaways

  • The direction of the integration decides the tool category. Trading-partner exchange, internal app-to-app and customer-facing product integrations are served by different kinds of tool, and connector count does not tell them apart.
  • EDI, APIs and AS2 are layers, not rival choices. A partner requirement constrains the document standard, the interaction or the transport, and each needs its own gate.
  • Per-partner configuration is an inventory you can check. Identity, agreement, schema, map and certificate are the artifacts to ask a vendor to show, and each fails in its own way.
  • Standards and transport that a partner mandates are pass/fail. Settle them as written requirements before any demo, so demos test fit rather than features.
  • Duplicates happen at three levels, and each level has its own check. The business identifier, the interchange control number and the AS2 message ID are caught by different mechanisms, so test all three.
  • A customer-facing integration needs per-integration coverage in writing. Ask how the tool connects and which models each integration supports before you sign.

If you start a B2B integration tool search with the connector count, you answer the wrong question. The count says nothing about what your partner will accept.

A B2B integration tool exchanges business data with parties outside your company: it receives, validates, transforms and routes it. But the parties differ.

A retailer wants purchase orders as EDI over AS2. Your internal systems want an API. Your customers want your product to read their records. Each of those jobs belongs to a different category of tool.

The costly mistakes are the same purchase order arriving twice and posting twice, or a tool bought for one direction and pressed into another.

The rule is to identify the direction of the integration, treat partner-mandated standards and transport as pass/fail, then compare the shortlisted tools on how they handle failure.

Which kind of integration are you building?

Place the integration in one of three directions before you read a single product page. Trading-partner exchange moves business documents between your company and external parties. Internal app-to-app integration connects systems you own. A customer-facing product integration connects your software product to systems your customers run.

Each direction has a category built for it. The table sorts the categories by the job they do, not by who sells them:

Category Direction it serves What moves Who sits on the other end What to check before relying on it
EDI or B2B gateway Trading-partner exchange Business documents in agreed standards, over transports such as AS2 An external partner with its own requirements Which document standards, versions and transports it implements, against your partners' list
iPaaS with B2B capabilities Internal app-to-app, plus trading-partner exchange where B2B features are present Application data through workflows and connectors, plus partner documents once B2B artifacts are configured Your own systems, and partners Whether B2B artifacts such as agreements, maps and certificates come with the product
Managed file transfer Trading-partner exchange, file-based Files, over transfer protocols such as SFTP A partner or internal system that sends or receives files Whether it only moves files or also validates and maps their contents
Managed B2B or EDI service Trading-partner exchange, run by a provider Documents, as with a gateway, operated by the provider The same external partners Which tasks stay with you and which the provider runs
Unified API Customer-facing product integrations Records from many customers' systems, through one API Your customers' systems. Bindbee's API, for one example, connects to 110+ HRIS, payroll, ATS and benefits systems Whether it covers the systems your customers run, and which of those integrations support the data models you need

The categories overlap. An iPaaS may carry a B2B module, and one company can need three of these at once. If your integration is internal, this comparison of data integration and application integration draws that boundary.

The next four sections follow a trading-partner integration. The customer-facing case returns at the end with the same criteria translated.

Whichever of the first four rows you land on, the tool will be configured in your partner's terms, and those terms arrive as three acronyms that sound like rivals.

How EDI, APIs and AS2 fit together

EDI, APIs and AS2 are layers of one exchange. A document standard defines what the business document looks like, an API defines how two systems converse, and a transport defines how the bytes travel. A partner can fix one of the layers, two or all three.

Take a requirement as it will actually arrive: "purchase orders in EANCOM, over AS2." That sentence pins a document standard and a transport, and says nothing about an API. Another partner may say "POST orders as JSON to our endpoint," which fixes the interaction and the payload format, and mentions neither an EDI standard nor AS2. Reading which layer a requirement constrains is the first skill in scoping this purchase. It also answers the common question of EDI compared to API: one is a document standard, the other an interaction style, so neither replaces the other.

The table separates the layers by what each defines and what it leaves open:

Layer What it defines Examples What it does not define
Document standard Structure and meaning of the business document, including its version X12, UN/EDIFACT, EANCOM (a subset of EDIFACT), GS1 XML How the document travels, or how two systems converse
Interaction How one system asks another to act and receives an answer APIs, typically REST with JSON The business vocabulary of the document
Transport How the bytes move between the two sides, securely AS2, AS4, SFTP What is inside the payload

Document standards come in families, and the family is only half the requirement. GS1 describes GS1 EDI as enabling automatic electronic exchange of business data between trading partners, consisting of GS1 EANCOM, GS1 XML and UN/CEFACT XML. EANCOM is a GS1 subset of UN/EDIFACT. The standard is EANCOM 2002, and the GS1 standards repository lists 2022 as its current edition, published in syntax 3 and syntax 4. UN/EDIFACT itself is published in versioned directories that trading partners agree between them.

So "we use EANCOM" is not a complete requirement. A partner's guide will name the syntax and the subset version carried in the UNH header, such as EAN007, and that pair is the requirement. That is why a version your partner names becomes a gate.

AS2 is the transport with a receipt built in. RFC 4130 (IETF, 2005) defines it as a request/reply interchange that gives secure, reliable, authenticated transport for EDI or other business data, such as XML, over HTTP. Authentication and confidentiality use CMS/S-MIME, and the receiver confirms receipt with a signable message disposition notification (MDN). The MDN is what AS2 adds over a bare file send: the sender holds a receipt it can verify. (It is called AS2 because it followed AS1, RFC 3335.)

AS2 is not the only standard transport. OASIS approved the AS4 profile of ebMS 3.0 in 2013, for secure, payload-agnostic document exchange over web services, written to carry AS2's simplicity into that stack. SFTP, the third transport in the table, is file transfer over SSH. This comparison of SFTP and API integration covers the trade-off between file transport and APIs in depth.

A tool's feature grid is therefore a list of layers it implements, and your job is to match them partner by partner. Each of those matches has to be recorded somewhere, and the record has more parts than a protocol name.

What a platform has to hold for each trading partner

A trading-partner setup breaks down into five artifacts: an identity, an agreement, a schema, a map and a certificate. Treat them as an inventory to check each platform against. Which of them a given partner needs depends on that partner's requirements. Each fails in its own way:

Artifact What it holds What fails when it is wrong
Partner identity The identifier and qualifier for the partner, and for you Messages arrive but match no partner or agreement
Agreement The relationship between the two sides, plus protocol settings such as signing and receipts Receipts or signature checks fail between otherwise valid messages
Schema The document structure for one standard at one version A document that looks right is rejected, or validated against the wrong version
Map The transformation between the partner's format and your internal one Values land in the wrong field, or are dropped without an error
Certificate The certificate stored for a partner, and when it has to be renewed Whatever relies on it; ask what the platform does when one lapses, and who is told first

The identity row is the easiest to picture failing. A new retail partner sends its first file, and the platform cannot say who it is from. The identifier in the envelope is correct.

The qualifier, the code that says which numbering scheme the identifier comes from, is not the one that was registered. Nothing is wrong with the document. The platform simply has no partner record that matches it.

Microsoft's Azure Logic Apps documentation describes the same dependency: message resolution depends on matching sender and receiver qualifiers and identifiers. It also shows one way to organize the artifacts: trading partners, agreements, certificates, maps and schemas are stored in an integration account, a cloud container, and an agreement needs a host partner and a guest partner. That is one product's documented model, and another platform may organize the same things differently. The useful question is where each artifact lives in the tool you are evaluating.

Use the inventory to scope onboarding. For each partner, list which of the five artifacts it needs and who will create and maintain each one. Then ask any vendor to show where each artifact is stored, how it is versioned, who renews a certificate, and how an approaching expiry becomes visible to a person.

Once you know what has to be configured, the next step is to find out what each of your partners has already fixed, and to write it down before the first demo.

Turn partner requirements into pass/fail gates

A shortlist built from vendor feature pages tests what the vendors chose to emphasize. A shortlist built from your partners' requirements tests whether the tool can do your job. Build the second kind in four steps:

  1. Inventory: list every partner, internal system and owner, with each one's document standard and version, transport, security needs, expected volume, connected systems and who will run the integration.
  2. Classify: mark each requirement mandatory if the partner will not onboard without it, and preferred otherwise.
  3. Gate: rewrite every mandatory item as a yes/no question the vendor answers in writing, such as "EANCOM at the version our partner's guide names, over AS2, with signed receipts?"
  4. Compare: read each vendor's stated capability against the gates.

The fourth step is where claims need careful reading. Microsoft's Azure Logic Apps documentation states that its B2B workflows support AS2, X12, EDIFACT and RosettaNet. A statement like that tells you the protocols exist in the product. It does not tell you whether the version your partner fixes, or the receipt and signing options in the agreement, are covered. Turn the list into the question, then ask it.

Ownership belongs in the inventory as a gate. If nobody on your team wants to run certificate renewals and partner onboarding, that points to a managed service in the first table, and no feature comparison would have told you so. Volume works the same way. Write down the number you expect, and ask each vendor to state in writing how its tool behaves at that number.

Keep preferred items out of the gating round. Score them only among the tools that survive. Gates answer whether a tool can connect to your partners, and they say nothing about how it behaves when a connection misbehaves. That is where tools that pass the same gates start to separate.

Which failures to test before you buy

Tools that pass your gates still differ in what happens when a message repeats, fails or slows down. Test seven scenarios. The first three are duplicates, because duplicates occur at three separate levels and each level is caught by a different mechanism. A tool can handle one and miss the others.

Stay with the distributor's purchase order. The retailer's system times out waiting for a response and sends PO 4500123 again. What reaches you depends on what the retailer's system regenerates.

The first level is the business document. The order comes in a fresh envelope with new technical IDs, so only its content repeats. RFC 4130 (IETF, 2005) recommends detecting duplicate messages by Message-Id or by business transaction identifiers. It recommends a check but does not mandate a mechanism, so each product decides how, and the PO number is the identifier that catches this case.

The second level is the interchange. If the retailer's X12 envelope is delivered twice unchanged, both copies carry the same ISA13, the interchange control number in the ISA header. In X12 005010, the TA1 acknowledgment reports on that header, and TA1 note code 025 means Duplicate Interchange Control Number. That is how Wisconsin ForwardHealth's companion guide (June 2011) restates ASC X12 005010 TA1. If your partners use EDIFACT, ask the vendor to name the equivalent check.

The third level is the transport message. Each AS2 message has its own Message-Id, which is what the RFC's first recommendation keys on. A tool can deduplicate on that and still post PO 4500123 twice if the retailer rebuilt the message, which is why the levels are tested separately.

The table lists all seven scenarios, with what to send and what a pass looks like:

Scenario What to send or trigger What a pass looks like Mechanism or standard involved
Duplicate business document Send the same PO number again in a new envelope with new technical IDs The second copy is flagged or held, and nothing posts twice downstream Business transaction identifiers, per RFC 4130's recommendation
Duplicate interchange Resend an X12 005010 interchange with the same ISA13 The repeat is detected and reported, with TA1 note code 025 where the partner expects a TA1 ISA13; TA1 note code 025
Duplicate message Send the same AS2 message twice, same Message-Id The second is recognized as a repeat and not processed again AS2 Message-Id, per RFC 4130
Replay Fail a message mid-flow, fix the cause, then replay it It is processed once, with no second copy downstream The vendor's documented replay behavior
Retry and throttling Take the partner endpoint down, bring it back, then send a burst Observed behavior matches the documented retry policy, with no loss and no duplicate on recovery The vendor's own retry and throttling policy
Business-level tracking Ask an operator to find PO 4500123 by its business reference The document is found with its status at each stage, not only as a log line Business identifiers captured at ingest
Security Work through the five checks listed below the table Each check is documented and shown working, and certificate expiry dates are visible CMS/S-MIME for AS2 (RFC 4130)

One scenario deserves more than a table row: the receipt that never arrives. The sender of an AS2 message is waiting for a signable MDN. Ask the vendor to document what a lost receipt does to its processing, then make it happen during the demo.

Microsoft's Azure Logic Apps documentation says throttling follows the configured retry policy and can be mitigated by batching or splitting workflows. Whichever product you test, ask whether the vendor documents its retry and throttling policy and whether what you observe matches it.

Tracking is tested in business terms because a support rep or the retailer's buyer can ask where PO 4500123 is, and the answer should not depend on knowing which log line to search.

Security is the seventh scenario, and it takes five checks. This guide to vendor security reviews covers what a review involves in depth. For the demo, give each control its own evidence:

  • Ask to see encryption in transit enforced on a live partner connection.
  • Ask where stored documents are encrypted at rest, and who holds the keys.
  • Ask the vendor to show one role that can open a document and one that cannot.
  • Ask for the audit log entry that a configuration change produces, with who made it and when.
  • Ask for a walkthrough of certificate renewal, and where an approaching expiry becomes visible to a person.

These are buyer criteria: the vendor documents what its tool does, and you watch it happen.

A tool that catches the repeat, replays once and shows you the order's status has answered the question connector counts cannot: what happens when something goes wrong. The same question carries over to the third direction, where the integration runs between your product and your customers' systems.

When the integration is customer-facing

If your product connects to your customers' HR, payroll or benefits systems, the first question changes. You are no longer asking which standards a partner mandates, but which systems your customers run and how a tool reaches them. The gates and the failure test still apply, translated. A unified API is the category the first table maps to this direction, and how API aggregators work explains how one differs from gateway aggregation.

Picture a benefits platform that has to read employee records from each customer's HRIS and payroll system. Four questions carry the gates over:

  • Ask how the tool connects to each system, and what credentials the customer has to supply.
  • Ask for published coverage for every integration and every data model you need, not a total.
  • Ask where trading-partner formats re-enter, since benefits data bound for carriers is where EDI comes back.
  • Ask for the security attestation, and who can show it to you.

Bindbee is not a trading-partner EDI tool, an iPaaS or a managed file transfer product. If your problem is partner exchange with a retailer or a supplier, buy an EDI gateway, an iPaaS with B2B capabilities or a managed service, and use the gates and failure script above.

For the customer-facing case, here is how Bindbee answers each question. It connects through each system's own API, authenticated with OAuth, an API key, a token or a certificate, or through an SFTP export the customer runs. It never scrapes screens. Bindbee publishes per-integration model support in its Model Availability Matrix, with each model marked Available, Beta or not available, so coverage varies by integration and you can check yours. Bindbee is SOC 2 Type II compliant.

Carrier feeds are where trading-partner formats re-enter on the benefits side, usually as EDI 834 enrollment files. Bindbee doesn't run carrier feeds today, so ask any vendor in this category how it handles them, and apply the gates and failure tests above to the answer.

The criteria in this guide are the same wherever you apply them: classify the direction, gate on what is mandatory, and test the failures. If you have a list of the systems your customers use, bring it to a conversation with Bindbee and check each against the per-integration coverage.

FAQ

What is a B2B integration tool?

A B2B integration tool exchanges business data with parties outside your company: it receives, validates, transforms and routes it. The category covers EDI or B2B gateways, iPaaS with B2B capabilities, managed file transfer, managed B2B or EDI services, and unified APIs for customer-facing product integrations. Which one you need depends on the direction of the integration.

What is the difference between EDI and an API?

EDI is a document standard, such as X12 or UN/EDIFACT, that defines what a business document looks like. An API defines how two systems converse. Neither replaces the other: one partner may require purchase orders in EANCOM over AS2, while another asks you to POST orders as JSON to its endpoint.

What is AS2 used for?

AS2 is a transport for EDI or other business data over HTTP, defined in RFC 4130. It signs and encrypts messages with CMS/S-MIME, and the receiver confirms receipt with a signable message disposition notification (MDN), so the sender holds a receipt it can verify.

How do I test a B2B integration tool before buying?

Write your partners' mandated standards, versions and transports down as pass/fail gates first. Then test the tools that pass on seven failure scenarios: a duplicate business document, a duplicate interchange, a duplicate AS2 message, replay, retry and throttling, business-level tracking, and security.

Is a unified API a B2B integration tool?

A unified API covers one direction: customer-facing product integrations, where your software reads from and writes to systems your customers run. Bindbee, for example, connects to 110+ HRIS, payroll, ATS and benefits systems through one API. It is not a trading-partner EDI tool, and it doesn't run carrier feeds today.

Aditya
VP, Strategy & Growth
Bindbee
VIEW AUTHOR
BLOG_

Related blogs