Frequently Asked Questions

EDI is an open data standard / technology. No different than physical mail, EDI is a digital mail standard that businesses use. You do not need to use a specific EDI Vendor to do EDI with your Customers.

All of these are Communication Protocols for how you send and receive EDI Files (like an inbox / outbox). An experienced EDI Vendor provides Communication services and can support any protocol. Your Retail Customer will either dictate a specific protocol or provide you the flexibility to use any one you want.

‍

Edisoft has integrated to over 100+ ERPs in its 30-year history. We can integrate to on-premise or cloud ERPs whether they use API, file Import/Export or the database to receive and share data. If we have not seen your ERP before, it takes us 30 days to build a new integration that supports all of our Integration Workflows.

‍

Edisoft has integrated to over 100 ERPs and it is highly likely that we have integrated to your systems before. Be wary of other solutions that promise pre-built connectors to your ERP. Your company, customer, inventory and other data is unique to you. It is not possible to make a pre-built connector that takes into account all of your unique ERP data and configurations. Without Edisoft's Integration Workflows, custom field mapping and ERP customization is always required.

Connecting to a customer typically requires multiple connections - one for each EDI document. With traditional solutions, every EDI document is a unique integration to your ERP and these integrations are not sequenced, leaving you with limited automation and the risk of human error. Edisoft's Integration Workflows sequence all of your EDI and internal data together for end-to-end automation.

Traditional EDI Integrations are just moving EDI data from point A to point B. For example, when an EDI Order lands in the ERP, someone typically has to check the Header and Line Level details to validate items, prices and quantities. These types of manual decisions or edits are why organizations with EDI Integration are still manual. This is why we design all of our Integration Workflows with logic that does more for you than just move data.

ERPs are not designed to account for EDI Documents which means any integration and automation requires customization of your ERP with optional fields and scripts. Over-customization of your ERP can put you in digital handcuffs where making changes to, upgrading or swapping your ERP becomes too complex of a task to undertake. We designed our Integration Workflows to eliminate almost any need to customize your ERP.

The ERP is a Hub for your company, inventory, customer, and vendor data. ERPs are not designed to be integration hubs.