Alluvia supports the full range of EDI documents your trading partners require, and each one is mapped to the matching Acumatica record rather than landing as raw EDI. An inbound 850 purchase order creates a Sales Order in Acumatica. The 855 acknowledgment goes back to your partner from that order. The 856 advance ship notice is generated off the Shipment, and the 810 invoice off the Acumatica Invoice. An 820 remittance advice posts back as a Payment. The 940, 944, and 945 warehouse documents keep your 3PL in sync with Acumatica, and GS1-128 labels are produced to each partner’s spec. Every document is validated against your trading partner’s requirements before it reaches Acumatica.

Both. Every trading partner starts from the same master template library, which is what makes onboarding fast and repeatable. From there, any individual partner can be customized to meet their specific requirements without affecting the mapping for any other partner. You get the speed of shared templates with the flexibility to handle a partner whose spec does not follow the rules.

Yes. Alluvia maps to Acumatica custom fields, attributes, classes, warehouses, locations, units of measure, and pricing, so your existing configuration stays as it is. Non-standard label formats, custom packaging details, and unique workflow requirements are handled without code changes inside Acumatica.

No. Alluvia’s team builds and maintains every trading partner map. There is no custom development, no workflow rewrites, and no ongoing developer involvement. When a trading partner changes a spec, Alluvia handles it directly with them rather than sending you a ticket.

Most Acumatica EDI implementations go live in three to four weeks. Alluvia’s team handles the mapping and the trading partner onboarding, drawing on 1,600+ master templates, so your team is never pulled into development work.

Yes. Alluvia is an ERP integration platform, not an EDI-only tool. Your eCommerce channels and your EDI trading partners each connect independently to Acumatica, so the two run in parallel without depending on each other. One platform handles both, which is usually what replaces a stack of separate point tools.