Electronic Data Interchange (EDI)

EDI Integration Diagram

Who Typically Uses EDI Integration?

Companies that use EDI integration typically have a higher volume of sales through large-scale retailers. This type of integration best fits medium to large-sized vendors for retailers. EDI integration is often required of vendors by their retail trading partners. Generally, companies that use EDI also use an ERP, which collects and organizes key business information.

What We Need from Our Client for EDI Integration

  1. Information regarding inbounds and outbounds — full SKU list, quantities/unit of measures, and destination/carrier
  2. EDI service provider information
  3. Established communication pathways:
    • Names of customers in ERP
    • Fields mapped for EDI
  4. Customer requirements — routing and vendor guides for each customer

Application Programming Interface (API)

API Integration Diagram

Who Typically Uses API Integration?

Companies that use API integration typically utilize an online shopping cart, such as Shopify or ShipStation. This type of integration is ideal for companies looking for a cost-effective way to aggregate orders from multiple channels. Companies may also use API to access potential shipping advantages (ex: shipping through Shopify’s UPS account).

What We Need from Our Client for API Integration

  1. Established communication pathways and preferences
  2. Information regarding inbounds and outbounds — full SKU list, unit of measures, set up of customers
  3. Access to shopping cart/API Key
  4. Customer requirements if applicable

Manual / Email / Flat File

Manual Integration Diagram

Who Typically Uses Manual Order Entry?

Companies that use manual integration typically have sales that don’t involve a lot of large scale e-commerce, sell in more pallet quantities, and have lower order volumes. This type of integration best fits manufacturers and domestic producers/sellers.

What We Need from Our Client for Manual Order Entry

  1. Established communication requirements/preferences for inbounds, outbounds, and inventory
  2. Base level information regarding inbounds and outbounds — SKU data, quantities/unit of measures, and destination/carrier
  3. Customer requirements if applicable

Want to hear from us?

Subscribe to receive Beyond Warehousing newsletters and other valuable content.

Questions?

If you have any questions about our services or capabilities, please reach out to our team!

Recent Blog Posts

Beyond Warehousing Logistics Park Kansas City Location
Outsourcing

Public Warehousing vs. Contract Warehousing: Understanding the Key Differences

With the intricate landscape of logistics and supply chain management, businesses often have no interest in managing their own private warehouse operations. Alternatively, these businesses look for efficient and cost-effective third-party logistics (3PL) warehousing solutions to meet their unique needs.When evaluating potential 3PL providers, there

Read More »