Hundreds of Connectors

Application & Data Connectors


Best-in-Class Connectivity. Drag & Drop Interface. Configure and Use in Minutes.


Core   |   MFT   |   EDI   |   Database   |   Integration


Try It Now
illustration

EDI Connectors

Frictionless EDI with unmatched flexibility. Arc EDI Connectors simplify the process of mapping, transforming, and integrating EDI with databases and other back-office systems.

Sample Flows

A Library of Pre-Packaged Integration Flows Connecting Your Apps and Trading Partners.


Logistics & Supply Chain Flows

The following flows demonstrate EDI integration for logistics documents like Load Tenders, Shipment Status Updates, and more.

EDI 210 (Load Tender Invoice) to CSV

Receive 210s from your trading partner and convert the data into a CSV flat file format for further processing.

SQL Server to EDI 204 (Load Tender)

Generate outbound 204s from data contained in a SQL Server back-end system.

SQL Server to EDI 214 (Shipment Status Update)

Generate outbound 214s from data contained in a SQL Server back-end system.

SQL Server to EDI 856 (Advanced Shipment Notice)

Generate outbound 856s from data contained in a SQL Server back-end system.

EDI 210 (Load Tender Invoice) to MySQL

Receive 210s from your trading partner and integrate the data into a MySQL back-end.

EDI 210 (Load Tender Invoice) to SQL Server

Receive 210s from your trading partner and integrate the data into a SQL Server back-end.

CSV to EDI 204 (Load Tender)

Generate outbound 204s from data contained in CSV flat files.

MySQL to EDI 204 (Load Tender)

Generate outbound 204s from data contained in a MySQL back-end system.

MySQL to EDI 214 (Shipment Status Update)

Generate outbound 214s from data contained in a MySQL back-end system.

CSV to EDI 214 (Shipment Status Update)

Generate outbound 214s from data contained in CSV flat files.



Suppliers & Manufacturers Flows

The following flows demonstrate EDI integration for suppliers & manufacturers, using documents like inbound Purchase Orders, outbound Invoices, and more.

Oracle to EDI 810 (Invoice)

Generate outbound 810s from data contained in a Oracle back-end system.

SQL Server to EDI 810 (Invoice)

Generate outbound 810s from data contained in a SQL Server back-end system.

SQL Server to EDI 855 (Purchase Order Acknowledgment)

Generate outbound 855s from data contained in a SQL Server back-end system.

NetSuite to EDI 810 (Invoice)

Generate outbound 810s using data pulled from your NetSuite back-end.

MySQL to EDI 855 (Purchase Order Acknowledgment)

Generate outbound 855s from data contained in a MySQL back-end system.

EDI 850 (Purchase Order) to MySQL

Receive 850s from your trading partner and integrate the data into a MySQL back-end.

EDI 850 (Purchase Order) to NetSuite

Receive 850s from your trading partner and integrate the data into a NetSuite back-end.

EDI 850 (Purchase Order) to Oracle

Receive 850s from your trading partner and integrate the data into a Oracle back-end.

EDI 850 (Purchase Order) to SQL Server

Receive 850s from your trading partner and integrate the data into a SQL Server back-end.

MySQL to EDI 810 (Invoice)

Generate outbound 810s from data contained in a MySQL back-end system.



Retail & E-Commerce Flows

The following flows demonstrate EDI integration for retail documents and order integrations for e-commerce platforms.

Oracle to EDI 856 (Advance Shipment Notice)

Generate outbound 856s from data contained in a Oracle back-end system.

Shopify to CSV

Retrieve order data from Shopify's web storefront and store that data as a CSV file.

Shopify to MySQL

Retrieve order data from Shopify's web storefront and store that data in a MySQL back-end system.

Shopify to SQL Server

Retrieve order data from Shopify's web storefront and store that data in a SQL Server back-end system.

SQL Server to EDI 846 (Inventory Inquiry)

Generate outbound 846s from data contained in a SQL Server back-end.

NetSuite to EDI 846 (Inventory Inquiry)

Generate outbound 846s using data pulled from your NetSuite back-end.

MySQL to EDI 856 (Advanced Shipment Notice)

Generate outbound 856s from data contained in a MySQL back-end system.

MySQL to EDI 846 (Inventory Inquiry)

Generate outbound 846s from data contained in a MySQL back-end system.



Complex EDI Flows

The following flows demonstrate sophisticated sets of EDI document exchanges based around common retail partners like Amazon, Target, and Walmart.

Overstock EDI to MySQL

Communicate with Overstock using a range of EDI documents generated from a backend MySQL database.

Overstock EDI to SQL Server

Communicate with Overstock using a range of EDI documents generated from a backend SQL Server database.

Target EDI to MySQL

Communicate with Target using a range of EDI documents generated from a backend MySQL database.

Target EDI to Oracle

Communicate with Target using a range of EDI documents generated from a backend Oracle database.

Target EDI to SQL Server

Communicate with Target using a range of EDI documents generated from a backend SQL Server database.

Walmart EDI to MySQL

Communicate with Walmart using a range of EDI documents generated from a backend MySQL database.

Walmart EDI to Oracle

Communicate with Walmart using a range of EDI documents generated from a backend Oracle database.

Amazon Direct Fulfillment EDI to MySQL

Receive 850s from Amazon and map information to a MySQL database. Query it to generate outgoing EDI documents.

Walmart EDI to SQL Server

Communicate with Walmart using a range of EDI documents generated from a backend SQL Server database.

Amazon Direct Fulfillment EDI to SQL Server

Send 810s, 846s, 855s, and 856s to Amazon Fulfillment and integrate incoming order information into SQL Server.

Amazon Direct Fulfillment EDI to Oracle

This sample flow showcases end-to-end integration from an Oracle database to EDI communication with Amazon.

Amazon Direct Fulfillment EDI to NetSuite

Integrate incoming 850s directly into NetSuite, and query data from the application to generate 810s and 846s.

Amazon Direct Fulfillment EDI to QuickBooks Online

Receive 850s and automatically push them into QuickBooks. Poll the application for data to generate invoices and more.



Healthcare Flows

The following flows demonstrate EDI integration for healthcare documents like Healthcare Claims, Benefit Enrollments, and more.

SQL Server to EDI 834 (Benefit Enrollment)

Generate outbound 834s from data contained in a SQL Server back-end.

SQL Server to EDI 837 (Healthcare Claim)

Generate outbound 837s from data contained in a SQL Server back-end.

CSV to EDI 834 (Benefit Enrollment)

Generate outbound 834s from data contained in CSV flat files.

CSV to EDI 837 (Healthcare Claim)

Generate outbound 837s from data contained in CSV flat files.

MySQL to EDI 837 (Healthcare Claim)

Generate outbound 837s from data contained in a MySQL back-end system.



Other Flows

The following flows demonstrate aspects of Arc that are not covered in the previous categories.

Bulk Import Opportunities to Salesforce

Translate incoming CSV files into a readable XML format, and insert each record into the Leads table in Salesforce.

Upload Attachments to Salesforce

Receive files from an SFTP Server and upload them into Salesforce as attachments.



Sample Flows

A Library of Pre-Packaged Integration Flows Connecting Your Apps and Trading Partners.


Logistics & Supply Chain Flows

The following flows demonstrate EDI integration for logistics documents like Load Tenders, Shipment Status Updates, and more.

EDI 210 (Load Tender Invoice) to CSV

Receive 210s from your trading partner and convert the data into a CSV flat file format for further processing.

SQL Server to EDI 204 (Load Tender)

Generate outbound 204s from data contained in a SQL Server back-end system.

SQL Server to EDI 214 (Shipment Status Update)

Generate outbound 214s from data contained in a SQL Server back-end system.

SQL Server to EDI 856 (Advanced Shipment Notice)

Generate outbound 856s from data contained in a SQL Server back-end system.

EDI 210 (Load Tender Invoice) to MySQL

Receive 210s from your trading partner and integrate the data into a MySQL back-end.

EDI 210 (Load Tender Invoice) to SQL Server

Receive 210s from your trading partner and integrate the data into a SQL Server back-end.

CSV to EDI 204 (Load Tender)

Generate outbound 204s from data contained in CSV flat files.

MySQL to EDI 204 (Load Tender)

Generate outbound 204s from data contained in a MySQL back-end system.

MySQL to EDI 214 (Shipment Status Update)

Generate outbound 214s from data contained in a MySQL back-end system.

CSV to EDI 214 (Shipment Status Update)

Generate outbound 214s from data contained in CSV flat files.



Suppliers & Manufacturers Flows

The following flows demonstrate EDI integration for suppliers & manufacturers, using documents like inbound Purchase Orders, outbound Invoices, and more.

Oracle to EDI 810 (Invoice)

Generate outbound 810s from data contained in a Oracle back-end system.

SQL Server to EDI 810 (Invoice)

Generate outbound 810s from data contained in a SQL Server back-end system.

SQL Server to EDI 855 (Purchase Order Acknowledgment)

Generate outbound 855s from data contained in a SQL Server back-end system.

NetSuite to EDI 810 (Invoice)

Generate outbound 810s using data pulled from your NetSuite back-end.

MySQL to EDI 855 (Purchase Order Acknowledgment)

Generate outbound 855s from data contained in a MySQL back-end system.

EDI 850 (Purchase Order) to MySQL

Receive 850s from your trading partner and integrate the data into a MySQL back-end.

EDI 850 (Purchase Order) to NetSuite

Receive 850s from your trading partner and integrate the data into a NetSuite back-end.

EDI 850 (Purchase Order) to Oracle

Receive 850s from your trading partner and integrate the data into a Oracle back-end.

EDI 850 (Purchase Order) to SQL Server

Receive 850s from your trading partner and integrate the data into a SQL Server back-end.

MySQL to EDI 810 (Invoice)

Generate outbound 810s from data contained in a MySQL back-end system.



Retail & E-Commerce Flows

The following flows demonstrate EDI integration for retail documents and order integrations for e-commerce platforms.

Oracle to EDI 856 (Advance Shipment Notice)

Generate outbound 856s from data contained in a Oracle back-end system.

Shopify to CSV

Retrieve order data from Shopify's web storefront and store that data as a CSV file.

Shopify to MySQL

Retrieve order data from Shopify's web storefront and store that data in a MySQL back-end system.

Shopify to SQL Server

Retrieve order data from Shopify's web storefront and store that data in a SQL Server back-end system.

SQL Server to EDI 846 (Inventory Inquiry)

Generate outbound 846s from data contained in a SQL Server back-end.

NetSuite to EDI 846 (Inventory Inquiry)

Generate outbound 846s using data pulled from your NetSuite back-end.

MySQL to EDI 856 (Advanced Shipment Notice)

Generate outbound 856s from data contained in a MySQL back-end system.

MySQL to EDI 846 (Inventory Inquiry)

Generate outbound 846s from data contained in a MySQL back-end system.



Complex EDI Flows

The following flows demonstrate sophisticated sets of EDI document exchanges based around common retail partners like Amazon, Target, and Walmart.

Overstock EDI to MySQL

Communicate with Overstock using a range of EDI documents generated from a backend MySQL database.

Overstock EDI to SQL Server

Communicate with Overstock using a range of EDI documents generated from a backend SQL Server database.

Target EDI to MySQL

Communicate with Target using a range of EDI documents generated from a backend MySQL database.

Target EDI to Oracle

Communicate with Target using a range of EDI documents generated from a backend Oracle database.

Target EDI to SQL Server

Communicate with Target using a range of EDI documents generated from a backend SQL Server database.

Walmart EDI to MySQL

Communicate with Walmart using a range of EDI documents generated from a backend MySQL database.

Walmart EDI to Oracle

Communicate with Walmart using a range of EDI documents generated from a backend Oracle database.

Amazon Direct Fulfillment EDI to MySQL

Receive 850s from Amazon and map information to a MySQL database. Query it to generate outgoing EDI documents.

Walmart EDI to SQL Server

Communicate with Walmart using a range of EDI documents generated from a backend SQL Server database.

Amazon Direct Fulfillment EDI to SQL Server

Send 810s, 846s, 855s, and 856s to Amazon Fulfillment and integrate incoming order information into SQL Server.

Amazon Direct Fulfillment EDI to Oracle

This sample flow showcases end-to-end integration from an Oracle database to EDI communication with Amazon.

Amazon Direct Fulfillment EDI to NetSuite

Integrate incoming 850s directly into NetSuite, and query data from the application to generate 810s and 846s.

Amazon Direct Fulfillment EDI to QuickBooks Online

Receive 850s and automatically push them into QuickBooks. Poll the application for data to generate invoices and more.



Healthcare Flows

The following flows demonstrate EDI integration for healthcare documents like Healthcare Claims, Benefit Enrollments, and more.

SQL Server to EDI 834 (Benefit Enrollment)

Generate outbound 834s from data contained in a SQL Server back-end.

SQL Server to EDI 837 (Healthcare Claim)

Generate outbound 837s from data contained in a SQL Server back-end.

CSV to EDI 834 (Benefit Enrollment)

Generate outbound 834s from data contained in CSV flat files.

CSV to EDI 837 (Healthcare Claim)

Generate outbound 837s from data contained in CSV flat files.

MySQL to EDI 837 (Healthcare Claim)

Generate outbound 837s from data contained in a MySQL back-end system.



Other Flows

The following flows demonstrate aspects of Arc that are not covered in the previous categories.

Bulk Import Opportunities to Salesforce

Translate incoming CSV files into a readable XML format, and insert each record into the Leads table in Salesforce.

Upload Attachments to Salesforce

Receive files from an SFTP Server and upload them into Salesforce as attachments.



Don't see your application listed here?

We can develop custom connectors for any application, protocol, or data source.


Submit Request