B2B Manager 2026 release notes

New native support for generating shipping labels and managing cartonization within NetSuite integrations to streamline fulfillment workflows.

Celigo now persistently stores AS2 MDNs for every transaction, allowing you to view acknowledgment data directly in the EDI activity dashboard without enabling debug mode. This update automatically logs MDN details for all inbound and outbound AS2 transactions, whether synchronous or asynchronous. Previously, MDN data was transient and only visible in debug mode, which made it difficult to provide proof of receipt for compliance-heavy partners. By making this data available via the dashboard and API, you can now efficiently resolve partner disputes and meet enterprise-grade audit requirements. Learn more about AS2 MDN logging

You can now view and download Functional Acknowledgment (FA) files directly from the EDI dashboard to confirm whether trading partners accepted your outbound transactions. Previously, you had no way to confirm receipt without contacting Support or reviewing backend logs. This update provides direct access to acknowledgment files for every outbound transaction, which improves audit readiness and reduces dependency on external assistance. Learn more about acknowledgment file visibility

You can now generate outbound EDI files from source JSON payloads up to 1 GB. This enhancement enables high-volume EDI transactions, such as bulk purchase orders and invoices, by removing the file size constraints that previously caused transformation failures. This update ensures continuous data processing for large enterprise batches without requiring manual file splitting or external infrastructure modifications. Learn more about large outbound file generation

We’ve increased the maximum supported EDI file size from 5 MB to 50 MB, enabling processing of larger, high-volume transactions. Multi-transaction (ST–SE) files that exceed processing limits are now automatically split while preserving full EDI envelope integrity (header & trailer segments). If a single oversized transaction cannot be safely split, it will fail gracefully with clear error messaging. This update eliminates file size–related failures and improves reliability for enterprise EDI workflows.

For inbound EDI files ( X12 and EDIFACT), a new, flexible file-processing capability enables you to choose how to handle multi-transaction files when errors occur. Now, under Process parsed data in EDI exports, you can process complete files only (default) or valid/successful transactions while ignoring the invalid ones. Previously, only complete files with all valid transactions were processed. If a single transaction within an EDI file failed, the entire file was rejected.

This capability provides the following benefits:

EDI X12 trading partners: The table below lists new trading partners with doc types and any existing trading partners with new or enhanced doc types.

EDIFACT trading partners: The table below lists new trading partners with doc types and any existing trading partners with new or enhanced doc types.

We’ve launched a powerful, intuitive interface that allows you to design and update EDI file rule definitions visually in exports & imports. By simplifying how you manage segments, fields, and validation logic, this feature accelerates your setup process and ensures a faster path to Go-Live.

EDI parser helper for exports

We’ve enhanced the /ediTransactions API and added a new endpoint to allow for direct EDI file downloads and full metadata retrieval. This update provides greater autonomy for audits and troubleshooting by eliminating the need for manual backend support.

EDI X12 trading partners: The table below lists new trading partners with doc types and any existing trading partners with new or enhanced doc types.

EDIFACT trading partners: The table below lists new trading partners with doc types and any existing trading partners with new or enhanced doc types.

EDI listeners/imports using the AS2 and VAN connections now include an option to process files without automatic parsing, allowing you to access and work with raw files also. This option, that is, Parse files being transferred in EDI listeners and Generate files from records in EDI imports, provides:

New option in EDI listener

New option in EDI import

The EDI trading partners article provides a comprehensive list of trading partner connectors available for EDI transactions. This article provides an alphabetical listing of trading partners, search functionality, and filters that enable you to find supported document types for trading partners quickly and easily. You can also submit a request for a new trading partner from this page. Check out the article! 

The table below lists new trading partners with doc types and any existing trading partners with new or enhanced doc types.