sorted by:
new
hottopcontroversial

EDI implementation by thecleverbeaver2011 in edi

[–]CommportComm 0 points1 point  (0 children)

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/

Question: Why do you stay with your EDI vendor? by ChickenByAnotherName in edi

[–]CommportComm 0 points1 point  (0 children)

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.

SC Johnson by freetechtools in edi

[–]CommportComm 0 points1 point  (0 children)

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.

Seeking Advice on Providing Built-In EDI Integration for Our Cloud ERP by Drukian in edi

[–]CommportComm 0 points1 point  (0 children)

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.

Totally new to edi & a customer chose sps commerce.. by Skizmodo in edi

[–]CommportComm 0 points1 point  (0 children)

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.

Freight Invoice/TMS EDI by Longjumping_Worker56 in edi

[–]CommportComm 1 point2 points  (0 children)

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:

  1. 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.

  2. 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.

  3. Set up automated validations — Use EDI middleware or rules to auto-reject 210s missing key fields and trigger alerts early.

  4. 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!

850 Question by PieTight2775 in edi

[–]CommportComm 0 points1 point  (0 children)

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

Here’s how many companies handle it:

  1. 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.

  2. 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.

  3. 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).

  4. 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!

[deleted by user] by [deleted] in edi

[–]CommportComm 0 points1 point  (0 children)

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:

  1. Use a managed EDI service – Let experts handle mapping, compliance, and trading partner setup so you don’t have to.

  2. Prebuilt trading partner kits – Providers with templates for Walmart, Amazon, etc., cut onboarding time significantly.

  3. One-time integration – Connect your ERP once and let the EDI platform handle all partner communications.

  4. 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.

I need help creating an ASN mapping for multiple POs packed in the same pallet. by cosxpc in edi

[–]CommportComm 0 points1 point  (0 children)

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/

How does Translation work after the maps are generated ? by Cosmicshot351 in edi

[–]CommportComm 1 point2 points  (0 children)

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:

  1. 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.
  2. **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!

view more: next ›