Introduction
Acenda supports seamless electronic data interchange (EDI) to facilitate automated order management and inventory synchronization. While we maintain a robust set of standard specifications, Acenda is highly flexible. We can easily adapt our EDI configurations to match your specific file formats or unique business requirements.
Communication and Connectivity
If your organization requires AS2 or other specific EDI documents not covered in our standard specs, Acenda integrates seamlessly with the following providers for more traditional EDI integrations:
SPS Commerce
Orderful
EDI Gateway
Supported Transaction Sets
Our standard baseline utilizes X12 Version 4010 for the following documents:
EDI 850: Purchase Order (Inbound to Vendor) Used by Acenda to place orders. Mandatory segments include BEG (PO Number), DTM (Requested Delivery Date), and PO1 (Item/Quantity).
EDI 856: Advance Ship Notice (Outbound from Vendor) Used by the vendor to provide shipping and tracking info. Requires a Pick/Pack (SOPI) hierarchy including BSN (Shipment ID) and TD5 (Carrier SCAC).
EDI 846: Inventory Advice (Outbound from Vendor) Used by the vendor to provide stock level snapshots. Mandatory segments include BIA (Report Type) and QTY (Quantity Available to Sell).
Flexibility and Customization
The specifications outlined in our documentation represent our default implementation. However, Acenda is designed for maximum compatibility:
Mapping Flexibility: We can map to your existing EDI format to minimize development work on your end.
Custom Segments: We can include custom segments or specialized qualifiers to align with your internal ERP or warehouse management systems.
Format Support: If you require variations in versioning or delimiters, our team can configure the connection to meet those needs with ease.
Detailed Specifications
You can view our full element-level technical requirements and sample files here: https://www.acenda.com/acenda_edi_specs.html