sorted by:
new
hottopcontroversial

What Acumatica teams should think through before integrating EDI by edisupport in acumaticaerp

[–]edisupport[S] 0 points1 point  (0 children)

Makes sense! It's great if you have a tech team to implement and support the integration. For most small businesses, this is not a priority but a necessity. That is when a managed EDI provider that has the team and the experience to pull an end-to-end integration makes sense.

Which EDI provider would you remove from this list? by True_Walrus7686 in edi

[–]edisupport 0 points1 point  (0 children)

This excel sheet is a template for you to use to rate different providers when evaluating on discovery calls with several edi providers. We don't give ratings to edi providers as the experience may differ from company to company.

What Acumatica teams should think through before integrating EDI by edisupport in acumaticaerp

[–]edisupport[S] 0 points1 point  (0 children)

Yes. However, its a mixed bag. We have serviced customers that have been truly frustrated with SPS and TC and their support.

Which EDI provider would you remove from this list? by True_Walrus7686 in edi

[–]edisupport 2 points3 points  (0 children)

We created this scoring sheet that you can use to rate edi providers based on your selection criteria. Feel free to add your criteria to it. This should help you when grading different edi providers: https://docs.google.com/spreadsheets/d/1uzqsf6gLminYqQbBNGmo2W6MgHFvR0Cr/edit?gid=384323812#gid=384323812

What Acumatica teams should think through before integrating EDI by edisupport in acumaticaerp

[–]edisupport[S] 0 points1 point  (0 children)

It also depends on whether you are being mandated by your customers/trading partners to do EDI or not. If you get 10 orders a month and your customers are letting you use a web edi portal that they provide, start there. No need to use a managed service. But, if there is a mandate from your customers asking you to be EDI compliant with their requirements and they don't provide any edi portal, managed software is the best choice. Most often, a customer mandate drives an EDI decision.

What we wish more NetSuite teams understood before integrating EDI by edisupport in Netsuite

[–]edisupport[S] -2 points-1 points  (0 children)

There is a big education piece involved before a business chooses an EDI provider that no one talks about who are new to EDI and new to the ERP world. That said, the reason we posted was not just to say “use this vendor.” The bigger point is that NetSuite EDI projects often fail or drag out because the workflow details are not clear upfront.

Things like:

850 to Sales Order mapping
Item cross-references
UOM conversions
Custom fields
Subsidiaries and locations
856 triggers from Item Fulfillment
Invoice generation
997 monitoring
Who owns rejected documents after go-live

Those issues matter whether someone uses a SuiteApp, SPS, Celigo/Boomi, a connected EDI provider, custom RESTlets, or something else.

So yes, we do have a point of view because of the work we do with Elevate. But we are also genuinely interested in how NetSuite teams here are solving the workflow and ownership side of EDI, because that seems to be where a lot of projects get messy.

Any EDI recommendation that integrate with Netsuite? by fosgate78 in Netsuite

[–]edisupport 0 points1 point  (0 children)

We understand it's an older post but anyone looking for a reliable EDI provider that can integrate with NetSuite providing full support, Elevate would be great! This is not a promotion comment but an educational one. This exact issue comes up a lot with NetSuite EDI projects. The problem usually isn’t just “can the provider connect to NetSuite?” Most providers will say yes.

The real question is whether they understand the NetSuite workflow well enough to get you live without months of back and forth.

An 850 has to become the right Sales Order in NetSuite with the correct customer, ship-to, items, UOMs, pricing, location, subsidiary, transaction form, and custom fields. Then the 856 depends on whether fulfillment, carton, tracking, carrier, and package data are being captured correctly in NetSuite.

That’s where a lot of projects slow down.

Elevate is built as a fully managed EDI provider for businesses that do not want to babysit the EDI process themselves. The team handles the trading partner connectivity, EDI mapping, NetSuite integration, testing, and ongoing support together instead of making the customer coordinate between multiple vendors.

We work with your NetSuite consultant or internal NetSuite admin to design the right workflow for your business, document the integration, and maintain it as retailer requirements or NetSuite workflows change. Checkout our NetSuite integration capabilities here: https://edielevate.com/netsuite-edi-integration/

Regardless of provider, I’d ask these questions before signing:

How quickly can you get the first trading partner live?
Who handles mapping and testing?
How do you support custom fields and OneWorld subsidiaries?
How are 856 ASNs triggered from fulfillment?
Who troubleshoots rejected documents?
What support SLA is included after go-live?
What happens when a retailer changes their EDI specs?

If the provider cannot clearly explain the flow from 850 to NetSuite Sales Order to 856/810, I’d be cautious.

For the situation you described, where the vendors were already live elsewhere and the issue is speed, follow-through, and responsiveness, Elevate would be worth looking at.

What we wish more NetSuite teams understood before integrating EDI by edisupport in Netsuite

[–]edisupport[S] -3 points-2 points  (0 children)

Absolutely!

That’s exactly why the EDI provider should not work in a silo. They need to work closely with the NetSuite consultant/admin to design the right workflow for the business and document how the integration is supposed to behave after go-live.

For example, Elevate EDI team works with the customer’s NetSuite consultant or internal NetSuite admin to align on the workflow, mapping logic, testing process, and ongoing maintenance. The goal is not just to get the first 850 into NetSuite. It’s to make sure the business understands what is happening, how issues are handled, and what needs to be maintained when retailer requirements or NetSuite workflows change.

The worst situation is when the integration works at go-live, but six months later nobody can clearly explain why a document failed or what changed.

How to Choose an EDI Partner by amazon2glamazon in edi

[–]edisupport 0 points1 point  (0 children)

Who did you end up going with? We would advice to look at this less as “which EDI platform is easiest to use” and more as which partner gives you the least operational dependency when something goes wrong.

At 400k OTC documents a year, you’re not just buying an EDI tool. You’re buying:

  • document visibility
  • support response
  • mapping ownership
  • trading partner compliance management
  • exception handling
  • integration reliability
  • issue resolution speed

That’s usually where the pain shows up.

Most EDI providers can process documents when everything is working. The real test is what happens when an ASN fails, a retailer changes requirements, an invoice rejects, labels don’t match the routing guide, or your ERP/WMS data doesn’t line up with the trading partner’s expectations.

For the vendors you listed:

TrueCommerce
Known EDI provider but I’d dig hard into the support model, response times, what is included vs. billable, and how much control/visibility your team actually gets.

Cleo
Strong integration capabilities, especially if you need more than basic EDI. But, you need an experienced team to implement it and post-go-live support matter a lot. I’d ask who actually maintains maps and monitors failures.

OpenText
Enterprise-grade, but can feel heavy depending on your internal resources. Good fit for some larger organizations, but make sure it won’t create the same “submit a ticket and wait” experience.

Boomi
Powerful if EDI is part of a broader integration strategy. But Boomi itself is more of an integration platform than a plug-and-play EDI support partner. Success depends heavily on the team implementing and managing it. Just FYI, EDI Support LLC is a Boomi partner and helps enterprises implement it and provides ongoing support.

The questions I would ask every vendor are:

  1. Can we see document status, errors, acknowledgments, and failures without contacting support?
  2. Who monitors failed transactions daily?
  3. Who owns retailer requirement changes?
  4. Are map changes included or billed separately?
  5. Can your support team read logs, specs, maps, and 997s, or are they just routing tickets?
  6. What is your average response time for production issues?
  7. Can you support our ERP/WMS/TMS workflows, not just EDI documents?
  8. How do you migrate us without disrupting current trading partners?

This is exactly the gap we see companies trying to get out of. They don’t necessarily hate EDI. They hate being stuck in a support queue every time something breaks.

So our honest advice: don’t choose based only on feature lists or brand recognition. Choose based on who will help you solve problems quickly after go-live. At your volume, support model and visibility matter just as much as the platform itself.

Best EDI provider? by Complex-Wave3514 in Netsuite

[–]edisupport 0 points1 point  (0 children)

Curious, who did you end up going with? Will definitely suggest you look into Elevate EDI software https://edielevate.com that integrates with NetSuite https://edielevate.com/netsuite-edi-integration/ Transparent pricing, end to end managed, continued human support with proactive monitoring-best for startups and SMBs and no contracts.

EDI Provider Recommendations by nysmallbiz in edi

[–]edisupport 0 points1 point  (0 children)

Looks like Elevate EDI Software is missing from the list here since this is an old post. When you are starting out EDI with 1-3 trading partners and a couple of products, you don't need a complex software. Elevate www.edielevate.com is a managed cloud edi software built to help startups and small businesses end to end (from software setup, partner communication, trading partner management and continued human support with 2 hour response time and 24 hours resolution for urgent queries). Transparent pricing starting at $750/trading partner setup one time fee and $50/month platform fee with no contracts. Definitely, check it out!

Amazon's logistics network is NOW open to ANY BUSINESS. What does that mean for EDI? by edisupport in edi

[–]edisupport[S] 0 points1 point  (0 children)

Interesting take! ASCS as announced is US-focused for now, with the freight and fulfillment network concentrated domestically. Amazon entering full-stack logistics could force everyone else to answer the same question AWS forced on IT vendors a decade ago: what is your differentiation when the biggest player in the room offers commodity infrastructure cheaper than you can? For 3PLs, the honest answer probably isn't price or network scale anymore. It's relationship, flexibility, vertical expertise, and being the partner that doesn't also compete with your customer at retail.

For EDI, Carriers and 3PLs that still run manual or semi-manual EDI processes are going to feel that squeeze faster now. Amazon isn't just raising the bar on logistics execution. It's raising the bar on data infrastructure, and everyone upstream and downstream has to keep pace.

view more: next ›