--- title: "Grainger EDI Integration | Stacksync" description: "Grainger EDI: 5 listed document types, channel comparison, record mapping and validation guidance for your integration." canonical: https://www.stacksync.com/edi/grainger last_modified: 2026-09-15 --- # *Grainger* EDI integration guide. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Plan your Grainger EDI integration using 5 listed document types across 3 channels. Compare channels, map business records and test the operational handoff. [Book an EDI demo](https://www.stacksync.com/book-a-demo) Explore EDI documents | | | | | --- | --- | --- | | Listed documents | 5 | Partner document references | | Listed channels | 3 | Grainger 210 Only → Grainger Sourcing | | Implementation | Plan | Map, validate and reconcile | ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Implementation guide ## Grainger: EDI implementation plan Build a reliable EDI workflow for Grainger. Use 5 document types across 3 channels to plan record mapping, prevent duplicate processing and reconcile results in your business systems. The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | [X12 210 Motor Carrier Freight Details And Invoice](https://www.stacksync.com/edi/grainger/grainger-210-only/x12-210-motor-carrier-freight-details-and-invoice) Listed on 1 channel: Grainger 210 Only | **freight invoice** carrier invoice, shipment reference and charge line | Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate. Test a second invoice for the same shipment and distinguish a revision from a duplicate. | | [X12 810 Invoice](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-810-invoice) Listed on 2 channels: Grainger Industrial Supply, Grainger Sourcing | **accounts-receivable or accounts-payable invoice** invoice number, purchase order and invoice line | Reconcile line amounts, allowances, charges and tax to the invoice total. Submit the same invoice twice and verify that it cannot create a second payable. | | [X12 850 Purchase Order](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-850-purchase-order) Listed on 2 channels: Grainger Industrial Supply, Grainger Sourcing | **purchase order or sales order** buyer purchase order, order line and trading-party identifiers | Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. | | [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-856-ship-notice-manifest) Listed on 1 channel: Grainger Industrial Supply | **shipment notice (ASN)** shipment, order, package and item references | Reconcile item quantities through shipment, order and packaging levels against the physical shipment. Test split shipments for one purchase order and prevent the second ASN from replacing the first. | | [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-855-purchase-order-acknowledgment) Listed on 2 channels: Grainger Industrial Supply, Grainger Sourcing | **purchase-order response** original purchase order, response revision and order line | Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. | ### Implementation steps 1. #### Choose the trading account and channel Choose among Grainger 210 Only, Grainger Industrial Supply, Grainger Sourcing. Confirm the business unit and account before copying a mapping from another channel. 2. #### Map records and assign owners Start with freight invoice, accounts-receivable or accounts-payable invoice, purchase order or sales order. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event. 3. #### Test a complete exchange Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Grainger production handoff and save the results of each approved test. 4. #### Check results after launch Match records between systems using carrier invoice, shipment reference and charge line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries. ### Go-live checklist - The required X12 documents, versions and sample files are agreed. - Sender and receiver IDs, test connections and production connections are agreed with the channel owner. - Delivery receipts, document validation and business responses have monitoring and a named owner. - Tests cover duplicates, partial processing and reconciliation with realistic business records. ### Related documents and resources - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [Evaluate your integration requirements](https://www.stacksync.com/blog/integration-evaluation-worksheet) **Sources.** Directory data as of 2026-05-07. Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) - [Grainger document reference](https://www.orderful.com/network/grainger) Document catalog ## EDI documents listed for Grainger 8 transactions across 3 channels. ### [Grainger 210 Only](https://www.stacksync.com/edi/grainger/grainger-210-only) 1 doc - [X12 210 Motor Carrier Freight Details And Invoice](https://www.stacksync.com/edi/grainger/grainger-210-only/x12-210-motor-carrier-freight-details-and-invoice) ### [Grainger Industrial Supply](https://www.stacksync.com/edi/grainger/grainger-industrial-supply) 4 docs - [X12 810 Invoice](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-810-invoice) - [X12 850 Purchase Order](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-850-purchase-order) - [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-856-ship-notice-manifest) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-855-purchase-order-acknowledgment) ### [Grainger Sourcing](https://www.stacksync.com/edi/grainger/grainger-sourcing) 3 docs - [X12 810 Invoice](https://www.stacksync.com/edi/grainger/grainger-sourcing/x12-810-invoice) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/grainger/grainger-sourcing/x12-855-purchase-order-acknowledgment) - [X12 850 Purchase Order](https://www.stacksync.com/edi/grainger/grainger-sourcing/x12-850-purchase-order) Document flow ## Example document relationships for Grainger Where each document sits in its trading cycle, based on the 5 document types listed for Grainger across 3 channels. These are example relationships; the trading agreement determines the required sequence. ### Order-to-cash All example steps listed 1. [850 Purchase Order](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-850-purchase-order) 2. [855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-855-purchase-order-acknowledgment) 3. [856 Ship Notice Manifest](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-856-ship-notice-manifest) 4. [810 Invoice](https://www.stacksync.com/edi/grainger/grainger-industrial-supply/x12-810-invoice) ### Logistics Some example steps listed 1. 204 Motor Carrier Load Tender not listed for Grainger 2. 990 Response to a Load Tender not listed for Grainger 3. 214 Transportation Carrier Shipment Status not listed for Grainger 4. [210 Motor Carrier Freight Details And Invoice](https://www.stacksync.com/edi/grainger/grainger-210-only/x12-210-motor-carrier-freight-details-and-invoice) - 210 Motor Carrier Freight Details And Invoice — is listed on 1 of Grainger's 3 channels - 810 Invoice — is listed on 2 of Grainger's 3 channels - 850 Purchase Order — is listed on 2 of Grainger's 3 channels - 855 Purchase Order Acknowledgment — is listed on 2 of Grainger's 3 channels - 856 Ship Notice Manifest — is listed on 1 of Grainger's 3 channels LEGACY EDI MIGRATION FUND ## Still with a legacy EDI vendor? Ask about a contract buyout. Stacksync can buy out your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. Eligibility and terms are confirmed on a call. [Check your eligibility for the EDI migration fund](https://www.stacksync.com/book-a-demo) | | | | --- | --- | | | [Migrate from SPS Commerce](https://www.stacksync.com/sps-commerce-alternative) | | | Migrate from Cleo | | | Migrate from TrueCommerce | | | Migrate from OpenText | SECURITY ## Security teams trust Stacksync As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### SSO & SCIM Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more. ### Alerts Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more Related references ## Partners with related document listings Compare document requirements for similar business processes. [The Home Depot 48 docs · 11 channels](https://www.stacksync.com/edi/the-home-depot) [Walmart 32 docs · 8 channels](https://www.stacksync.com/edi/walmart) [Target 23 docs · 4 channels](https://www.stacksync.com/edi/target) [United Natural Foods, Inc. (UNFI) 17 docs · 4 channels](https://www.stacksync.com/edi/united-natural-foods-inc-unfi) [Boscov's Department Stores 13 docs · 2 channels](https://www.stacksync.com/edi/boscovs-department-stores) [Rivian Automotive, Inc 11 docs · 1 channel](https://www.stacksync.com/edi/rivian-automotive-inc) [Quebec Health Ministry 85 docs · 17 channels](https://www.stacksync.com/edi/quebec-health-ministry) [Costco 55 docs · 12 channels](https://www.stacksync.com/edi/costco) [Nordstrom 28 docs · 8 channels](https://www.stacksync.com/edi/nordstrom) [JCPenney 25 docs · 20 channels](https://www.stacksync.com/edi/jcpenney) [Amazon 24 docs · 4 channels](https://www.stacksync.com/edi/amazon) [NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) [Sprouts Farmers Market 19 docs · 2 channels](https://www.stacksync.com/edi/sprouts-farmers-market) [Ulta Beauty 18 docs · 3 channels](https://www.stacksync.com/edi/ulta-beauty) [KeHE Distributors 18 docs · 5 channels](https://www.stacksync.com/edi/kehe-distributors) [Macy's 17 docs · 5 channels](https://www.stacksync.com/edi/macys) [Aldi 16 docs · 2 channels](https://www.stacksync.com/edi/aldi) [GovX Inc. 15 docs · 3 channels](https://www.stacksync.com/edi/govx) [AAFES (Army and Air Force Exchange Service) 15 docs · 3 channels](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service) [AT&T Inc. 14 docs · 2 channels](https://www.stacksync.com/edi/att) [Dot Foods, Inc. 14 docs · 2 channels](https://www.stacksync.com/edi/dot-foods-inc) [Browse the full directory](https://www.stacksync.com/edi) FAQ ## Grainger EDI questions ### Which EDI documents are listed for Grainger? X12 210 Motor Carrier Freight Details And Invoice; X12 810 Invoice; X12 850 Purchase Order; X12 856 Ship Notice Manifest; X12 855 Purchase Order Acknowledgment. Confirm which documents, directions and versions apply to your account. ### How should I choose the Grainger EDI channel? The directory lists 3 channels for Grainger, including Grainger 210 Only, Grainger Industrial Supply, Grainger Sourcing. Match the channel to your actual trading relationship and compare its document list before reusing a mapping. ### Which identifiers should the Grainger mapping preserve? For X12 210 Motor Carrier Freight Details And Invoice, plan around carrier invoice, shipment reference and charge line. For X12 810 Invoice, use invoice number, purchase order and invoice line. Use the partner guide to locate these values and check their allowed formats. ### Does a successful EDI receipt mean Grainger accepted the business document? Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed. ### What should be tested before launching Grainger EDI? Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate. Test a second invoice for the same shipment and distinguish a revision from a duplicate. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch. ## Your last integration took months. Your next one takes a prompt. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)