Overview
Understanding Electronic Data Interchange and its role in NetSuite implementations for wholesale, manufacturing, and retail businesses.
What is EDI?
Electronic Data Interchange (EDI) is the computer-to-computer exchange of business documents in a standardized electronic format. For wholesale distributors, manufacturers, and retailers, EDI is often mandatory for doing business with large trading partners like Walmart, Target, Amazon, and Costco.
Why EDI Matters
- Retailer requirements: Major retailers mandate EDI compliance as a condition of doing business
- Efficiency: Eliminates manual data entry, reducing errors and processing time
- Speed: Transactions process in minutes vs. days for paper/email
- Chargebacks: Non-compliance results in costly penalties from retailers
- Visibility: Real-time order and shipment tracking across the supply chain
EDI Transaction Flow
EDI uses standardized document formats (ANSI X12, EDIFACT) transmitted via specialized networks (VAN) or AS2 protocol. Unlike REST APIs, EDI is batch-oriented and follows strict formatting rules. Many trading partners require EDI specifically and don't accept API alternatives.
Key EDI Standards
| Standard | Region | Usage |
|---|---|---|
| ANSI X12 | North America | Dominant standard in US/Canada retail and manufacturing |
| EDIFACT | International | UN standard, common in Europe and global trade |
| TRADACOMS | UK | Legacy UK retail standard, declining |
| XML/JSON EDI | Global | Modern alternatives, limited trading partner adoption |
Document Types (X12)
ANSI X12 transaction sets commonly used in retail and wholesale NetSuite implementations.
Core Transaction Sets
ANSI X12 documents are identified by three-digit transaction set numbers. Here are the most common documents used in retail and wholesale transactions:
| Document | Name | Direction | NetSuite Mapping |
|---|---|---|---|
850 | Purchase Order | Inbound | Creates Sales Order |
855 | PO Acknowledgment | Outbound | Confirms SO acceptance |
856 | Advance Ship Notice (ASN) | Outbound | From Item Fulfillment |
810 | Invoice | Outbound | From Invoice record |
997 | Functional Acknowledgment | Both | Confirms receipt |
Additional Transaction Sets
| Document | Name | Direction | Use Case |
|---|---|---|---|
820 | Payment Order/Remittance | Inbound | Payment details, creates Customer Payment |
846 | Inventory Inquiry/Advice | Outbound | Share inventory levels with partners |
860 | PO Change Request | Inbound | Modify existing orders |
865 | PO Change Acknowledgment | Outbound | Confirm PO changes |
214 | Shipment Status | Inbound | Carrier updates (from 3PL) |
940 | Warehouse Ship Order | Outbound | Instructions to 3PL/warehouse |
945 | Warehouse Ship Advice | Inbound | Confirmation from 3PL |
EDI Document Structure
X12 documents follow a hierarchical structure with segments, elements, and sub-elements. Here's a simplified example of an 850 Purchase Order:
- ISA/IEA: Interchange envelope (routing information)
- GS/GE: Functional group envelope (document type grouping)
- ST/SE: Transaction set envelope (individual document)
- BEG: Beginning segment with PO number and date
- N1/N3/N4: Name and address loops
- PO1: Line item details
NetSuite EDI Architecture
Architectural approaches for connecting EDI with NetSuite, from turnkey SuiteApps to enterprise iPaaS platforms.
NetSuite doesn't have native EDI translation capabilities. You need a middleware layer to translate between EDI formats and NetSuite records. There are three main architectural approaches:
Option 1: EDI SuiteApp (Connector)
Pre-built NetSuite bundles that handle translation and mapping within NetSuite. The SuiteApp connects to your EDI provider or VAN and creates/updates NetSuite records automatically.
Pros
- Lives within NetSuite (single system)
- Pre-built mappings for common scenarios
- Easier for IT teams to manage
- Often includes trading partner management
Cons
- May require SuiteScript customization
- Limited flexibility for complex requirements
- Dependent on SuiteApp vendor updates
- Uses NetSuite governance/processing
Option 2: Standalone EDI Platform
A dedicated EDI platform handles translation, compliance, and trading partner management. It connects to NetSuite via REST/SOAP APIs or CSV imports.
Pros
- Full EDI feature set and compliance tools
- Scales independently of NetSuite
- Dedicated EDI expertise and support
- Can serve multiple systems (not just NetSuite)
Cons
- Additional system to manage
- Integration development required
- Data latency between systems
- Higher total cost for simple setups
Option 3: iPaaS with EDI Capabilities
Use an integration platform that has EDI connectors alongside its other integration capabilities. Good if you have broader integration needs beyond just EDI.
Pros
- Unified platform for all integrations
- Visual mapping tools
- Can handle EDI + API + file-based
- Strong NetSuite connectors available
Cons
- EDI features may be less robust
- Still need VAN connectivity
- Jack-of-all-trades tradeoffs
- Complex pricing models
For most wholesale/distribution clients with 5-20 trading partners, a SuiteApp connector from SPS Commerce or TrueCommerce is the path of least resistance. If you have 50+ trading partners, complex compliance requirements, or need EDI for multiple ERP systems, consider a standalone EDI platform. The architecture decision should be driven by trading partner volume, compliance complexity, and existing integration infrastructure.
Provider Comparison
Major EDI providers that integrate with NetSuite, with strengths, considerations, and ideal use cases.
SPS Commerce
The largest retail EDI network with 115,000+ trading partners. Known for their "Full-Service" model where SPS handles all mapping, compliance, and trading partner onboarding.
Strengths
- Largest retail trading partner network
- Full-service = they do the work
- Native NetSuite SuiteApp (Fulfillment)
- Community trading partner database
- Strong retailer compliance expertise
Considerations
- Premium pricing (full-service model)
- Per-document and per-partner fees
- Less control over mapping details
- Best for retail/wholesale verticals
Best for: Retailers, consumer goods, companies selling to big box stores
TrueCommerce
Full-service EDI provider with strong NetSuite integration. Offers both cloud and on-premise options with a focus on mid-market companies.
Strengths
- Comprehensive NetSuite connector
- Flexible deployment options
- Good mid-market pricing
- Also handles e-commerce integration
- Acquired Datalliance (VMI expertise)
Considerations
- Smaller trading partner network than SPS
- Feature set varies by deployment
- Multiple product lines can be confusing
Best for: Mid-market wholesale, manufacturing, companies with mixed integration needs
Dell Boomi
Enterprise integration platform with B2B/EDI capabilities. Strong choice if you have broader integration needs beyond just EDI.
Strengths
- Unified platform for all integrations
- Enterprise-grade scalability
- Visual mapping and workflow tools
- Strong NetSuite connector
- Good for complex transformation logic
Considerations
- Enterprise pricing (can be expensive)
- Requires integration expertise
- EDI is one feature among many
- VAN connectivity still needed
Best for: Enterprises with complex integration landscapes, multiple ERPs
Cleo
B2B integration platform focused on supply chain connectivity. Strong EDI heritage with modern API and file-based integration capabilities.
Strengths
- Deep EDI expertise and compliance
- Handles complex EDI scenarios well
- Good visibility and monitoring
- Managed services available
Considerations
- NetSuite integration may need development
- Better suited for larger volumes
- Can be complex to configure
Best for: High-volume EDI, complex supply chains, 3PL/logistics
Celigo
NetSuite-centric integration platform with EDI capabilities through partnerships. Strong if you're already using Celigo for other NetSuite integrations.
Strengths
- Deep NetSuite expertise
- Pre-built NetSuite flows
- Modern UI and error handling
- Good for combining EDI + e-commerce
Considerations
- EDI via partners (SPS, etc.)
- Not a native EDI platform
- Additional costs for EDI features
Best for: NetSuite-centric companies with e-commerce + EDI needs
Provider Selection Matrix
| Criteria | SPS | TrueCommerce | Boomi | Cleo |
|---|---|---|---|---|
| NetSuite Integration | Native SuiteApp | Native Connector | Strong Connector | API-based |
| Full-Service Option | Yes (core model) | Yes | Limited | Yes |
| Trading Partner Network | 115,000+ | Large | Via VAN | Via VAN |
| Mid-Market Pricing | Premium | Good | Premium | Mid-range |
| Setup Complexity | Low (they do it) | Low-Medium | Medium-High | Medium-High |
Trading Partner Setup
Configuring trading partner identifiers, document versions, and communication settings for EDI exchange.
Trading Partner Information Needed
Each trading partner (customer or vendor you exchange EDI with) requires specific configuration for identifiers, document versions, and communication settings.
| Data Element | Description | Example |
|---|---|---|
| Qualifier (ISA05/07) | Identifies the type of ID being used | ZZ (mutually defined), 01 (DUNS), 08 (UCC) |
| Sender ID (ISA06) | Your company's EDI identifier | YOURCOMPANY (15 chars) |
| Receiver ID (ISA08) | Trading partner's EDI identifier | WALMART (15 chars) |
| X12 Version | Document standard version | 004010, 005010, 007030 |
| Test/Production | ISA15 indicator | T = Test, P = Production |
| Communication Method | How documents are transmitted | AS2, SFTP, VAN |
NetSuite Customer/Vendor Setup
When using an EDI SuiteApp, you'll typically configure EDI settings on the Customer or Vendor record:
- EDI Trading Partner ID: Link to the EDI provider's partner record
- Ship-To Locations: Map retailer store/DC codes to NetSuite locations
- Item Cross-References: Map partner SKUs/UPCs to NetSuite items
- Default Settings: Shipping method, payment terms, price level
- Compliance Flags: ASN required, specific label requirements, etc.
EDI orders reference items by the trading partner's identifiers (UPC, vendor part number, buyer item number). You must set up Item Cross-References or External IDs in NetSuite to map these to your internal item records. Missing cross-references are the #1 cause of EDI order failures.
Location/Store Code Mapping
Retailers send orders with store or distribution center codes. These must map to Ship-To addresses in NetSuite. Common approaches:
- Customer Locations: Create a location record for each store/DC under the customer
- Custom Records: Maintain a mapping table for complex scenarios
- Address Book: Use the customer's address book with external IDs
Large retailers may have hundreds of store locations. Request their location master file and use CSV Import to bulk-create customer address records. Include the store code as an external ID for EDI mapping.
Document Mapping
How EDI fields translate to NetSuite record fields for common transaction types.
850 Purchase Order → Sales Order
Document mapping defines how EDI fields translate to NetSuite record fields. Here are the key mappings for common transactions:
Item Fulfillment → 856 ASN
Invoice → 810
Document mapping is where most EDI implementations get complex. Each trading partner may have slightly different requirements even for the same document type. The EDI provider typically handles these partner-specific variations, but you need to ensure NetSuite has all the required data fields populated. Common gaps: missing ship-to codes, no UPC on items, incomplete addresses.
Error Handling & 997s
Understanding EDI error types, functional acknowledgments, and business-level failure resolution.
997 Functional Acknowledgment
EDI transactions can fail at multiple points. Understanding error types and acknowledgment flows is critical for maintaining compliant operations.
The 997 confirms receipt and syntactic validity of an EDI document. It doesn't confirm business acceptance -- just that the document was readable.
| AK5 Code | Meaning | Action |
|---|---|---|
| A | Accepted | No action needed |
| E | Accepted with Errors | Review warnings, may still process |
| R | Rejected | Fix and retransmit |
Common Error Codes
| Error Code | Description | Common Cause |
|---|---|---|
| 1 | Unrecognized segment ID | Wrong X12 version or typo |
| 3 | Required segment missing | Missing mandatory data |
| 4 | Loop exceeded max repetitions | Too many line items |
| 5 | Segment count mismatch | Transmission corruption |
| 6 | Required element missing | Blank required field |
| 7 | Invalid element value | Wrong format (date, code, etc.) |
Business-Level Errors
Even if a document passes 997 validation, it can still fail business processing in NetSuite:
- Item not found: UPC/SKU doesn't match any cross-reference
- Customer not found: Trading partner ID not configured
- Ship-to not found: Store code not mapped to address
- Duplicate PO: Order already exists in NetSuite
- Price mismatch: EDI price differs from NetSuite price level
- Inventory unavailable: Can't fulfill requested quantity
EDI errors that aren't addressed quickly lead to chargebacks and strained trading partner relationships. Set up alerts for failed transactions and review the error queue at least twice daily during business hours. Most EDI providers offer dashboards and email notifications for failed documents.
Retailer Compliance
Retailer-specific EDI requirements, chargeback prevention, and GS1-128 labeling standards.
Common Compliance Requirements
Major retailers have specific EDI requirements that go beyond standard X12. Non-compliance results in chargebacks -- deductions from your payments that can significantly impact margins.
- ASN timing: Must be sent before shipment arrives (often within hours of ship)
- Carton labeling: GS1-128 labels with SSCC-18 barcodes
- Routing compliance: Use specified carriers and routing guides
- Must-arrive-by dates: Miss the window, get charged back
- Fill rate requirements: Partial shipments may be penalized
- Invoice matching: 810 must match ASN and PO exactly
Major Retailer Requirements
Walmart
- Retail Link portal access required
- ASN within 24 hours of ship
- SSCC-18 on every carton
- Specific routing guide compliance
- On-time delivery critical
Target
- Partners Online portal
- EDI 856 required for all shipments
- Specific pallet configurations
- Appointment scheduling via EDI
Amazon Vendor Central
- EDI or Vendor Central portal
- Strict packaging requirements
- ASIN matching critical
- Chargeback-heavy for non-compliance
Costco
- EDI required for most vendors
- Strict ship window compliance
- Pallet and case quantity rules
- Label specifications
A single non-compliant shipment can result in chargebacks of $50-500 per violation. Multiply that by dozens of shipments and it becomes a serious profit drain. Common chargeback reasons: late ASN, missing/wrong labels, incorrect quantities, wrong carrier. Track chargebacks by type and address root causes in your NetSuite processes.
SSCC-18 / GS1-128 Labels
Most retailers require GS1-128 (formerly UCC-128) shipping labels with SSCC-18 serial numbers. The SSCC-18 uniquely identifies each shipping container and must be transmitted in the ASN.
- SSCC-18 structure: (00) + Extension Digit + Company Prefix + Serial Number + Check Digit
- NetSuite integration: Generate via SuiteScript or shipping software, store on fulfillment record
- Label printing: Often handled by shipping software (ShipStation, etc.) that syncs with NetSuite
Testing & Certification
EDI testing phases, certification process, and pre-go-live validation checklist.
Testing Phases
Before going live with EDI, you'll need to complete testing with each trading partner. This typically involves exchanging test documents and receiving certification.
| Phase | Description | Duration |
|---|---|---|
| 1. Internal Testing | Test mapping with sample files, verify NetSuite records | 1-2 weeks |
| 2. Connectivity Test | Establish VAN/AS2 connection, exchange test envelopes | 2-5 days |
| 3. Document Testing | Exchange test transactions with partner, verify 997s | 1-3 weeks |
| 4. Certification | Complete partner's certification checklist | 1-2 weeks |
| 5. Pilot | Limited production volume, monitor closely | 2-4 weeks |
| 6. Production | Full volume, ongoing monitoring | Ongoing |
Testing Checklist
- Verify ISA/GS envelope settings match partner requirements
- Test with multiple PO line items (1, 5, 50+ lines)
- Test split shipments and partial fulfillments
- Verify all item cross-references resolve correctly
- Test ship-to location mapping for multiple stores
- Confirm ASN timing meets partner requirements
- Verify 810 invoice totals match ASN and PO
- Test error handling for invalid items/locations
- Validate GS1-128 label generation and SSCC-18 transmission
- Confirm 997 acknowledgments flow both directions
Always use ISA15 = "T" (Test) indicator during testing. This tells the trading partner that documents are test transactions and shouldn't be processed. Switch to "P" (Production) only after certification is complete. Many EDI providers automatically set this based on environment configuration.
Troubleshooting
Common EDI issues, diagnostic steps, and resolution guidance for NetSuite integrations.
Common Issues and Solutions
| Problem | Symptoms | Solution |
|---|---|---|
| Item not found | Order fails to import, "item lookup failed" error | Add UPC/SKU to Item Cross-Reference or External ID field |
| Duplicate PO | "Record already exists" error | Check if PO was already imported; may need duplicate handling logic |
| Ship-to not found | Order imports but wrong address or fails | Map store code to Customer Address record with matching external ID |
| 997 Rejected | Partner returns 997 with "R" status | Review AK4/AK5 error codes, fix mapping or data issues |
| ASN not sent | Chargebacks for missing ASN | Check fulfillment workflow triggers, verify timing requirements |
| Price mismatch | Partner rejects invoice or pays different amount | Verify price level configuration, check for contract pricing |
| Connectivity failure | Documents not transmitting | Check VAN/AS2 credentials, firewall rules, certificates |
| Wrong X12 version | Parsing errors, unrecognized segments | Verify partner's required version (4010, 5010, etc.) |
Diagnostic Steps
- Check the raw EDI file: Most errors are visible in the document itself
- Review 997 details: Error codes point to specific segments/elements
- Check EDI provider logs: Translation and transmission history
- Verify NetSuite data: Items, customers, addresses, cross-references
- Compare to partner specs: Ensure mapping matches their requirements
Most EDI problems fall into three categories: data issues (missing cross-references, wrong IDs), timing issues (ASN sent too late), and format issues (wrong version, missing segments). Build a runbook for common issues and train your operations team to handle tier-1 troubleshooting. Escalate to your EDI provider for mapping and connectivity issues -- that's what you're paying them for.
Resources
EDI standards documentation, provider resources, and related appendices for further reference.
EDI Standards & Documentation
- X12.org: Official ANSI X12 standards body (membership required for full specs)
- GS1 US: Barcode and GTIN standards, SSCC-18 specifications
- EDIFACT: UN/CEFACT international EDI standard
Provider Documentation
- SPS Commerce: University training portal, implementation guides
- TrueCommerce: Knowledge base and support portal
- Cleo: CIC (Cleo Integration Cloud) documentation
NetSuite Resources
- SuiteAnswers: Search for EDI SuiteApp documentation
- SuiteApp Marketplace: Browse EDI connectors and bundles
Related Appendices
- Integration Patterns - General integration architecture
- Inventory Costing - Inventory management context