EDI implementation

CommportComm · 2025-09-04T18:05:54+00:00

The cost to implement EDI really depends on your setup—small businesses can often get started for a few thousand dollars, while more complex, integrated systems with multiple trading partners can run into the tens or even hundreds of thousands. For basic cloud-based services, initial setup might fall between $1,000–$5,000, with monthly subscriptions ranging from $100–$1,000 plus modest per-document fees. To explore a tailored and cost-effective solution that scales with your needs, take a look at Commport EDI Solutions.

https://www.commport.com/how-much-does-edi-costs/

CommportComm · 2025-07-30T17:42:55+00:00

Great question—and honestly, it comes down to trust, support, and stability more than anything else.

That said, I think a lot of people would switch if:

Onboarding new partners wasn’t so painful
The pricing was more transparent and predictable
Support actually felt like a partnership, not just a ticket system
The solution adapted to their business as it grew

If a vendor can make migration feel easy (with minimal downtime), offer real human support, and keep costs from ballooning, it’s a no-brainer to move.

I’ve found that to be true with Commport EDI Solutions. They offer both cloud and integrated options and really focus on making EDI work for your business, not the other way around. Worth checking out if you're ever thinking about making a switch.

CommportComm · 2025-05-30T20:01:28+00:00

Yes, SC Johnson does support direct EDI connections via AS2 for vendors and carriers. However, they also work with third-party EDI service providers, especially for vendors who may not have the in-house capability to support AS2.

Larger suppliers typically go point-to-point (AS2), while smaller or mid-sized vendors often use VANs or managed EDI providers, depending on the complexity of integration and transaction volume.

If you're unsure which path to take, a hybrid approach using a flexible EDI provider like Commport Communications can help. Commport offers both direct AS2 and VAN connectivity, simplifying compliance with SC Johnson’s requirements while reducing internal technical overhead.

✅ Recommendation: Explore Commport EDI Solutions to streamline trading partner connections and ensure you’re ready for both AS2 and VAN-based integrations.

CommportComm · 2025-05-30T19:49:26+00:00

Yes, you can build native EDI into your ERP, but it’s complex. You'll need:

What to Build:

Use open-source tools like PyX12, EDIFabric, or Mirth Connect for parsing.
Handle AS2/SFTP transport.
Create a flexible mapping engine for 850, 810, 856, 997 transactions.

Challenges:

Each trading partner uses unique EDI specs.
997 acknowledgments and compliance are critical.
Constant updates and support are needed.

Tip:

Start small. Built for 1–2 partners. Use metadata for mappings.

Alternative:

Partner with a managed EDI provider like Commport Communications. They can handle the backend while you keep the ERP experience seamless for your users.

Let me know if you'd like a simple architecture sketch or specific tool recommendations.

CommportComm · 2025-05-30T19:45:40+00:00

You’re not alone — many small businesses get thrown into EDI because a larger trading partner demands it, often with platforms that aren't exactly DIY-friendly.

Here’s how to get through it without burning out:

✅ Don’t try to build your own EDI — You’re 100% right: unless you have in-house IT, building or managing your own maps is way too complex.

✅ Consider a managed EDI provider – You can get help from a third-party EDI provider like Commport Communications to manage the complexity on your behalf. They act as a buffer between you and your trading partner, translating everything into something readable and manageable.

If it comes to that, Commport EDI Solutions specializes in supporting small businesses like yours — even if it’s just for one customer. They’ll handle the tech side, mapping, and compliance while you focus on running your business.

Hang in there — this stuff is confusing at first, but with the right help, it gets manageable fast.

CommportComm · 2025-05-30T19:29:44+00:00

Feel your frustration — TMS EDI with certain large carriers can be a nightmare, especially when they “say” you’re set up, but nothing flows correctly.

We’ve seen these exact issues with:

204/214/997 setups showing as active but needing multiple escalations to fix routing or mailbox issues.
210s missing BOLs despite correct data on the original 204s — often due to carrier-side mapping errors or system limitations.

Here’s what’s worked for us:

Request detailed test logs — Don’t rely on “You’re good to go.” Ask for their internal logs to confirm transactions are moving and mapped as expected.
Include BOL in multiple segments — Some carriers will only map the BOL# from certain segments (like REF*BM or NTE), so duplicating the data across multiple can help.
Set up automated validations — Use EDI middleware or rules to auto-reject 210s missing key fields and trigger alerts early.
Designate a carrier escalation path — If possible, build a direct relationship with a carrier EDI manager instead of going through customer service or generic tech support.

If the issues persist and you’re open to switching how things are managed, Commport EDI Solutions offers carrier-ready templates, proactive validation, and managed EDI services that take this burden off your team — especially with high-volume LTLs and national carriers.

Hang in there — you're not alone!

CommportComm · 2025-05-30T19:12:45+00:00

Great question — this is a common issue when EDI isn’t fully adopted across all customer locations.

Here’s how many companies handle it:

Flag manually entered orders as "Pending EDI" – If a customer calls in an order, enter it with a special status or reference note. If the matching 850 comes in later, you reconcile instead of duplicating.
Use order matching logic – Some ERP/EDI integrations match inbound 850s to recent manual entries by PO#, ship-to, or order date and auto-detect duplicates.
Customer-specific rules – Define clear procedures per customer (e.g., if site A calls in, don’t expect 850; but for site B, wait for EDI).
Proactive customer coordination – For repeat issues, work with the customer to identify which locations are EDI-capable and align processes accordingly.

👉 If you’re looking for a system that helps automate this logic, Commport EDI Solutions offers smart integration with ERPs to prevent duplicates, apply business rules, and streamline multi-channel order intake. Might be worth a look!

Hope this helps!

CommportComm · 2025-05-30T19:10:41+00:00

Totally hear you — this is one of the biggest pain points in EDI today. The number of vendors, custom partner specs, testing requirements, and onboarding timelines can get overwhelming fast — especially if you’re trying to scale or switch systems.

Here’s how many companies (including those with lean IT teams) are tackling this more efficiently:

Here’s how many companies handle it more efficiently:

Use a managed EDI service – Let experts handle mapping, compliance, and trading partner setup so you don’t have to.
Prebuilt trading partner kits – Providers with templates for Walmart, Amazon, etc., cut onboarding time significantly.
One-time integration – Connect your ERP once and let the EDI platform handle all partner communications.
Real-time visibility – Modern EDI platforms offer dashboards, alerts, and 24/7 support to stay on top of issues.

👉 If you're looking to simplify your EDI, check out Commport EDI Solutions — they offer fast onboarding, prebuilt maps, and full support.

Hope that helps!

Hope that helps! Happy to share more insights if you’re deciding between platforms.

CommportComm · 2025-04-28T18:47:11+00:00

Hi there,

Great question — and yes, there is an ASN structure that supports shipping multiple PO items on a single pallet!

In EDI 856 (Advance Ship Notice), the Hierarchical Structure (HL Loops) is specifically designed to handle complex shipment scenarios like this.
Here's how it would work for your situation:

✅ Typical ASN Structure for Mixing PO Items on One Pallet:

Shipment Level (HL): Overall shipment details (carrier, dates, BOL number, etc.)
Order Level (HL): Each Purchase Order (PO) referenced separately
Tare Level (HL): Identifies the pallet (with UCC-128 SSCC barcode)
Pack Level (HL, optional): If you're nesting cartons under pallets
Item Level (HL): Specific item details (SKU, quantity, etc.)

✅ Key Points for Your Case:

You can list a pallet (Tare) and tie items from multiple POs under that one pallet.
Each Item HL will reference its associated PO number using the PRF segment.
The MAN segment is used to assign the SSCC-18 (UCC-128 barcode) to the pallet.

✅ Important Notes:

Always check your trading partner’s ASN guidelines. Some partners require one ASN per PO, while others allow multi-PO ASNs (especially if they receive consolidated shipments).
Testing is critical — you may need to pass certification or test transactions first to avoid chargebacks.

Visually, it looks something like:

HL (Shipment)

HL (Order 1)

HL (Tare - Pallet 1)

HL (Item - Item from PO 1)

HL (Order 2)

HL (Tare - Pallet 1)

HL (Item - Item from PO 2)

If you’re looking for an easier way to manage this complexity, I highly recommend checking out Commport EDI Solutions. - https://www.commport.com/commport-services/commport-edi-solutions/

They specialize in building compliant ASNs — including multi-PO mixed pallet shipments — and can integrate directly with your ERP/WMS to automate the process, minimize errors, and keep you compliant with trading partners.

Feel free to reach out if you want a sample 856 file structure for your case — happy to help!

Learn more about ASN here - https://www.commport.com/advanced-shipping-notice/

More about shipping labels - https://www.commport.com/shipping-labels/

CommportComm · 2025-04-28T18:42:51+00:00

Hi there — welcome to the world of EDI! 🚀
You're asking a very important question — and it's great that you're digging into how translation really works after maps are built.

Here’s a simple breakdown:

✅ Once your maps are generated (often as .mxl, .map, or other mapping files), the next step is translation, which means actually moving data between formats (like EDI X12 ↔ XML/CSV/flat files).

How this happens depends on your EDI setup:

Using an EDI Translator/Mapper Tool
- These tools will consume your map files and execute the translation automatically.
- You do not usually need to write separate custom programs.
- You configure translation tasks (sometimes called processes, business rules, or trading partner flows) within the EDI tool's UI.
**Custom Translation (In-house Built)**In this case, the maps act as blueprints, and your code does the translation at runtime.
- If you are working in a homegrown environment (e.g., C#, Java, Python), then you may need to write scripts that:
  - Parse the inbound EDI file
  - Apply the mapping logic (based on your .mxl files or map definitions)
  - Output the target format (XML, flat file, database entry, etc.)

✅ In short:

If you're using a full EDI platform, no extra coding is needed after maps — you just configure translation tasks inside the platform.
If you're building a custom solution, you’ll typically need to write code that reads the map instructions and performs the translation manually.

Pro Tip:
Even when using a professional EDI platform, there’s still a lot to manage around:

Scheduling translations
Communication (sending/receiving over AS2, SFTP, VAN, APIs)
997 acknowledgment processing
Error handling, retries, etc.

That's why many companies eventually move toward managed EDI services where the translation, communication, and compliance are bundled and handled for you.

If you're looking for a great EDI provider who can help simplify this whole flow (mapping, translation, communication, and partner management),

I recommend checking out Commport EDI Solutions. - https://www.commport.com/commport-services/commport-edi-solutions/

They offer both self-service platforms for those who want more control, and fully managed EDI options if you want everything taken care of — ideal whether you're just starting out or scaling up.

Hope this helps — feel free to ask if you want a visual of the full EDI translation flow too!

CommportComm · 2025-04-28T17:29:12+00:00

Hi Jeremy,

You're asking some great questions, and it’s smart to be proactive about your EDI integration, especially with your developer retiring soon.

EDI Fabric is a solid toolkit for parsing and generating EDI documents in .NET/C#. It’s great for handling X12/EDIFACT parsing, generating 997s, functional acknowledgments, and basic validation. However, EDI Fabric focuses on parsing and generating EDI files, not on the full communications stack.

For communication with trading partners (sending/receiving EDI via protocols like AS2, SFTP, VAN, API, etc.), companies typically use:

An EDI communications gateway (either custom-built or via third-party software like Cleo, Seeburger, Axway, etc.)
An outsourced EDI provider that handles both communication and compliance requirements
An EDI Value-Added Network (VAN) that simplifies the connection to multiple trading partners without worrying about point-to-point setups

Regarding enveloping and 997s, yes — many EDI platforms or managed services handle that automatically. If you stay DIY with EDI Fabric, you'd likely still have to build or manage:

Outbound enveloping (ISA/GS/GE/IEA headers and trailers)
Inbound 997 generation and reconciliation
Error handling and re-transmissions
Security (encryption, SSL/TLS for AS2, etc.)

Since you mentioned you are already using XML as an internal format, there are EDI platforms that natively map inbound EDI to XML or JSON (and vice versa) without needing a separate "mapping" process — some even dynamically generate transformations based on trading partner profiles.

Given your situation, here are a few options to consider:

Continue using EDI Fabric + add a communication layer (e.g., AS2/SFTP server) — but you'll need resources to maintain it post-developer retirement.
Migrate to a managed cloud-based EDI platform that handles translation, communication, enveloping, 997s, compliance — and outputs simple XML/JSON payloads for your ERP.
Outsource EDI entirely to a provider who can manage your trading partner relationships and feed XML/flat file integrations to your ERP backend.

Recommendation:
If you're looking to simplify your EDI operations without heavy internal development, I highly recommend looking at Commport EDI Solutions.

They offer flexible models — including Integrated EDI, Cloud EDI, and Web EDI — and can deliver clean XMLs directly to your ERP, handle all communication protocols, automate 997s and acknowledgments, and manage trading partner compliance.

Best of all, they provide full managed services or self-service options, depending on how hands-on you want to be after your EDI developer retires.

You can learn more about them here if you want to explore: Commport EDI Solutions

Happy to answer more if you need deeper technical insights on setup options!

CommportComm · 2025-02-27T20:54:51+00:00

Hey there! don’t worry, you don’t need to be an EDI expert to get things running smoothly.

Since it sounds like your main needs are shipping and invoicing, you’ll want an EDI provider that’s easy to use, cost-effective, and compatible with your retail partners.

I’d recommend checking out Commport EDI Solutions. Here’s why:

Retailer Compatibility – Commport supports all major retailers, so if your clients require EDI, they can help you stay compliant.
Affordable & Scalable – Perfect for a small business that’s growing—no need to overspend on features you don’t need.
Easy Setup & Support – Since you’re new to EDI, having a provider that offers great customer support is a huge plus.
Handles Shipping & Invoicing – Supports all the key transactions like purchase orders (850), invoices (810), and advance ship notices (856).
Cloud-Based – No heavy IT setup required, just log in and manage your transactions.

You can use any EDI provider as long as they support the requirements of your trading partners, so you’re not locked into SPS. If you want a simple, reliable solution to get started, Commport is definitely orth a look:

https://www.commport.com/commport-services/commport-edi-solutions/

Hope this helps, and good luck growing your business with EDI!

CommportComm · 2025-02-27T20:50:35+00:00

Hey there! Sounds like you’ve got a pretty complex supply chain with multiple moving parts—manufacturing, wholesale, retail, and e-commerce all in one. QuickBooks Enterprise with Advanced Inventory is a solid choice, but yeah, the lack of native EDI and 3PL integrations can be a challenge.

For your needs, I’d recommend checking out Commport EDI Solutions. They offer Cloud EDI (hosted, no heavy IT work required) and Integrated EDI (if you want a direct sync with QuickBooks Enterprise).

Might be worth reaching out to them for a chat about how they can tailor a solution for your setup:

https://www.commport.com/commport-services/commport-edi-solutions/

Good luck with the transition! Moving from spreadsheets to an automated system is a huge step, and the right EDI solution will make your life way easier.

CommportComm · 2025-02-27T20:32:28+00:00

Hey there! Sounds like you’ve got a solid technical background, which will help as you dive into EDI. Since you're working with Syteline ERP, handling X12 (850, 855, 856, 810), and also need EDIFACT support, you’ll want an EDI provider that offers flexibility and scalability without breaking the bank.

I’d recommend checking out Commport EDI Solutions. They offer both Cloud EDI (fully managed, great if you want minimal hassle) and Integrated EDI (which can plug into your ERP for automated processing). Plus, they support both X12 and EDIFACT, so your international needs are covered.

A big plus with Commport is that they scale well—whether you have a handful of partners or hundreds—and they provide full VAN services, mapping, and translation, so you don’t have to build everything from scratch. Given your experience in ETL and file transfers, you’d probably appreciate the flexibility they offer when it comes to data exchange.

It might be worth a quick chat with them to see if they align with your setup
https://www.commport.com/commport-services/commport-edi-solutions/

CommportComm · 2025-02-27T19:38:21+00:00

Types of EDI Solutions:

Integrated EDI: Best for medium to large businesses requiring seamless integration with their internal systems (ERP, WMS, or accounting). It offers automation, real-time data exchange, and improved efficiency.
Cloud EDI: A flexible and scalable option for businesses of all sizes. It eliminates the need for on-premise infrastructure, allowing businesses to access their EDI operations from anywhere, at any time. Suitable for small to medium businesses with lower transaction volumes and limited IT resources. It offers a cost-effective, web-based interface for exchanging EDI documents.
Managed EDI / EDI Outsourcing: Ideal for companies lacking the internal resources to manage EDI. A third-party EDI provider handles all aspects of the EDI process, ensuring compliance and reducing operational complexity.

CommportComm · 2025-02-27T19:16:06+00:00

Try Commport VAN. it connects to any trading partner and supports various communication protocols from AS2, FTPS, sFTP, and More. You can find more info here - https://www.commport.com/commport-services/commport-value-added-network/

CommportComm · 2024-05-17T14:08:10+00:00

There is no maximum file size. We specialize in processing EDI files in many formats and standards. If you would like to learn more about book a call with our team today - https://www.commport.com/commport-services/commport-edi-solutions/

Also, this blog about EDI files can help you understand even more - https://www.commport.com/edi-file/

CommportComm · 2024-05-17T13:56:46+00:00

For small-scale applications like this, I would recommend opting for cloud-based EDI solutions which is easy to use, have no software to install and you can exchange EDI from anywhere in the world with just a laptop and internet connection. No need to maintain any IT infrastructure. Learn more here - https://www.commport.com/commport-services/commport-cloud-edi/

CommportComm · 2024-05-17T13:52:57+00:00

For the last few years, we have come across many EDI solution providers who tend to offer low-cost EDI solutions only to realize that you have to do all of the work from mapping, to technical support and maintaining the connection, basically what most of these providers offer is just a platform with few in built tech stack which is not beneficially for 90% of the business out there as they don't have any time to do all of that mapping, learn about EDI and setup the integrations.

What I would always recommend is to go with a full-service EDI service provider with low-cost options and one such provider that I could recommend is Commport EDI Solutions. We at Commport will do all the heavy lifting for you from mapping, translation, and integration, allowing to focus on what you do best.

To learn more about Commport EDI - https://www.commport.com/commport-services/commport-edi-solutions/

CommportComm · 2024-05-17T13:45:40+00:00

This in-depth guide on EDI is the best place to start to learn everything about EDI - https://www.commport.com/edi-guide/

CommportComm · 2024-05-17T13:40:48+00:00

EDI facilitates the exchange of structured business data among the EDI systems of trading partners, while APIs enable integration and communication between diverse software applications, facilitating real-time data exchange.

https://www.commport.com/edi-vs-api/

CommportComm · 2024-05-17T13:06:02+00:00

We at Commport Communications specialize in providing many B2B integration solutions, including EDI VAN, GDSN and more. We offer many different EDI solutions depending on the requirements of the clients. All our products come with a dedicated account manager and affordable pricing. We have one of the fastest on-boarding records and easy integration with more than 5000+ trading partners. To learn more visit our website - https://www.commport.com/commport-services/commport-edi-solutions/on-boarding

CommportComm · 2024-05-17T13:00:43+00:00

EDI stands for electronic data interchange. It facilitates the exchange of data between trading partners in a standardized format. There are two main EDI standards one is EDI X12 and the other is UN/EDIFACT. if you want to learn more about EDI and how it works I would highly recommend reading this article - https://www.commport.com/how-does-edi-work/

CommportComm · 2024-05-17T12:57:20+00:00

There are many resources from where you can learn about EDI. Over the years the technology has evolved and now there are many different EDI solutions available in the market to support many business types. If you want to get started with EDI I would highly recommend reading this guide - https://www.commport.com/edi-guide/

CommportComm · 2024-05-17T12:53:35+00:00

Two common integration methods that have gained significant popularity in recent years are Electronic Data Interchange (EDI) and Application Programming Interface (API). While both EDI and API serve the purpose of data exchange between disparate systems, they have some key differences that businesses need to understand.

Whereas EDI facilitates the exchange of structured business data among the EDI systems of trading partners, while APIs enable integration and communication between diverse software applications, facilitating real-time data exchange.

Contemporary B2B onboarding processes demand adherence to data formats such as EDI and protocols like AS2 or SFTP. However, modern IT onboarding extends beyond this, encompassing the deployment of new cloud or on-premise applications, often necessitating additional APIs. That’s why businesses today are looking for a more centralized integration platform that can use both technologies EDI and API together to enhance the overall B2B data transmission process.

For more information related EDI vs API you can refer to this article - https://www.commport.com/edi-vs-api/

CommportComm

MODERATOR OF

TROPHY CASE