--- title: "Google EDI Integration | Stacksync" description: "Google EDI: 10 listed document types, channel comparison, record mapping and validation guidance for your integration." canonical: https://www.stacksync.com/edi/google last_modified: 2026-09-15 --- # *Google* 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 Google EDI integration using 10 listed document types across 1 channel. 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 | 10 | Partner document references | | Listed channels | 1 | Google | | 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 ## Google: EDI implementation plan Build a reliable EDI workflow for Google. Use 10 document types across 1 channel 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 850 Purchase Order](https://www.stacksync.com/edi/google/google/x12-850-purchase-order) Listed on 1 channel: Google | **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 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/google/google/x12-855-purchase-order-acknowledgment) Listed on 1 channel: Google | **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. | | [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/google/google/x12-860-purchase-order-change-request-buyer-initiated) Listed on 1 channel: Google | **buyer order-change request** original purchase order, change revision and affected line | Apply a quantity reduction to the existing order instead of creating another order. Test a cancellation arriving after allocation or shipment and route it to an exception owner. | | [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/google/google/x12-856-ship-notice-manifest) Listed on 1 channel: Google | **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 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/google/google/x12-846-inventory-inquiry-advice) Listed on 1 channel: Google | **inventory availability record** item, location, quantity type and snapshot time | Distinguish on-hand, available and reserved quantities before publishing availability. Deliver an old snapshot after a new one and prevent stale stock from replacing current values. | | [X12 865 Purchase Order Change Acknowledgment Request Seller Initiated](https://www.stacksync.com/edi/google/google/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) Listed on 1 channel: Google | **seller order-change response or request** original purchase order, change reference and affected line | Distinguish a seller-proposed change from acceptance of a buyer-requested change. Reject an outdated revision that would overwrite a later agreed quantity. | | [X12 861 Receiving Advice Acceptance Certificate](https://www.stacksync.com/edi/google/google/x12-861-receiving-advice-acceptance-certificate) Listed on 1 channel: Google | **goods receipt or acceptance record** receipt, shipment, order and inspected item | Separate received quantity from accepted quantity when damaged goods are reported. Reconcile two partial receipts against one shipment without closing the order early. | | [X12 940 Warehouse Shipping Order](https://www.stacksync.com/edi/google/google/x12-940-warehouse-shipping-order) Listed on 1 channel: Google | **warehouse fulfillment order** warehouse order, owner, ship-to and item | Test a cancellation after picking and define who approves any warehouse reversal. Validate owner-specific SKU and unit mappings before allocating stock. | | [X12 945 Warehouse Shipping Advice](https://www.stacksync.com/edi/google/google/x12-945-warehouse-shipping-advice) Listed on 1 channel: Google | **warehouse shipment confirmation** warehouse order, shipment and shipped line | Test partial fulfillment and leave the unshipped order quantity open. Reconcile shipped units and tracking references before preparing a customer-facing shipment notice. | | [X12 947 Warehouse Inventory Adjustment Advice](https://www.stacksync.com/edi/google/google/x12-947-warehouse-inventory-adjustment-advice) Listed on 1 channel: Google | **warehouse inventory adjustment** adjustment, item, location and reason | Test a negative adjustment without converting it into a positive stock receipt. Preserve adjustment reasons and prevent a duplicate message from moving stock twice. | ### Implementation steps 1. #### Choose the trading account and channel Choose among Google. Confirm the business unit and account before copying a mapping from another channel. 2. #### Map records and assign owners Start with purchase order or sales order, purchase-order response, buyer order-change request. 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 Google production handoff and save the results of each approved test. 4. #### Check results after launch Match records between systems using buyer purchase order, order line and trading-party identifiers. 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/) - [Google document reference](https://www.orderful.com/network/google) Document catalog ## EDI documents listed for Google 10 transactions across 1 channel. ### [Google](https://www.stacksync.com/edi/google/google) 10 docs - [X12 850 Purchase Order](https://www.stacksync.com/edi/google/google/x12-850-purchase-order) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/google/google/x12-855-purchase-order-acknowledgment) - [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/google/google/x12-860-purchase-order-change-request-buyer-initiated) - [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/google/google/x12-856-ship-notice-manifest) - [X12 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/google/google/x12-846-inventory-inquiry-advice) - [X12 865 Purchase Order Change Acknowledgment Request Seller Initiated](https://www.stacksync.com/edi/google/google/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [X12 861 Receiving Advice Acceptance Certificate](https://www.stacksync.com/edi/google/google/x12-861-receiving-advice-acceptance-certificate) - [X12 940 Warehouse Shipping Order](https://www.stacksync.com/edi/google/google/x12-940-warehouse-shipping-order) - [X12 945 Warehouse Shipping Advice](https://www.stacksync.com/edi/google/google/x12-945-warehouse-shipping-advice) - [X12 947 Warehouse Inventory Adjustment Advice](https://www.stacksync.com/edi/google/google/x12-947-warehouse-inventory-adjustment-advice) Document flow ## Example document relationships for Google Where each document sits in its trading cycle, based on the 10 document types listed for Google across 1 channel. These are example relationships; the trading agreement determines the required sequence. ### Order-to-cash Some example steps listed 1. [850 Purchase Order](https://www.stacksync.com/edi/google/google/x12-850-purchase-order) 2. [855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/google/google/x12-855-purchase-order-acknowledgment) 3. [856 Ship Notice Manifest](https://www.stacksync.com/edi/google/google/x12-856-ship-notice-manifest) 4. 810 Invoice not listed for Google ### Warehouse fulfillment All example steps listed 1. [940 Warehouse Shipping Order](https://www.stacksync.com/edi/google/google/x12-940-warehouse-shipping-order) 2. [945 Warehouse Shipping Advice](https://www.stacksync.com/edi/google/google/x12-945-warehouse-shipping-advice) ### Catalog & inventory Some example steps listed 1. 832 Price / Sales Catalog not listed for Google 2. [846 Inventory Inquiry Advice](https://www.stacksync.com/edi/google/google/x12-846-inventory-inquiry-advice) 3. 852 Product Activity Data not listed for Google 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. [Target 23 docs · 4 channels](https://www.stacksync.com/edi/target) [Wayfair LLC 9 docs · 1 channel](https://www.stacksync.com/edi/wayfair-llc) [Bealls Inc. 11 docs · 2 channels](https://www.stacksync.com/edi/bealls-inc) [Dow Inc. 10 docs · 1 channel](https://www.stacksync.com/edi/dow-inc) [Williams Sonoma 10 docs · 2 channels](https://www.stacksync.com/edi/williams-sonoma) [ASUSTeK Computer Inc. (dba ASUS) 8 docs · 1 channel](https://www.stacksync.com/edi/asus) [MSC Industrial Supply Co. 8 docs · 1 channel](https://www.stacksync.com/edi/msc-industrial-supply) [MidwayUSA 7 docs · 1 channel](https://www.stacksync.com/edi/midwayusa) [Sportsman's Guide 7 docs · 1 channel](https://www.stacksync.com/edi/sportsmans-guide) [QVC Group (dba Cornerstone Brands Inc) 7 docs · 1 channel](https://www.stacksync.com/edi/garnet-hill) [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) [Nordstrom 28 docs · 8 channels](https://www.stacksync.com/edi/nordstrom) [JCPenney 25 docs · 20 channels](https://www.stacksync.com/edi/jcpenney) [Macy's 17 docs · 5 channels](https://www.stacksync.com/edi/macys) [AAFES (Army and Air Force Exchange Service) 15 docs · 3 channels](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service) [Dot Foods, Inc. 14 docs · 2 channels](https://www.stacksync.com/edi/dot-foods-inc) [Lowe's 13 docs · 2 channels](https://www.stacksync.com/edi/lowes) [Mountain High Outfitters 12 docs · 2 channels](https://www.stacksync.com/edi/mountain-high-outfitters) [PetSmart 11 docs · 2 channels](https://www.stacksync.com/edi/petsmart) [Evereve.com 10 docs · 2 channels](https://www.stacksync.com/edi/everevecom-evereve) [Browse the full directory](https://www.stacksync.com/edi) FAQ ## Google EDI questions ### Which EDI documents are listed for Google? X12 850 Purchase Order; X12 855 Purchase Order Acknowledgment; X12 860 Purchase Order Change Request Buyer Initiated; X12 856 Ship Notice Manifest; X12 846 Inventory Inquiry Advice; X12 865 Purchase Order Change Acknowledgment Request Seller Initiated; X12 861 Receiving Advice Acceptance Certificate; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account. ### How should I choose the Google EDI channel? The directory lists 1 channels for Google, including Google. Match the channel to your actual trading relationship and compare its document list before reusing a mapping. ### Which identifiers should the Google mapping preserve? For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 855 Purchase Order Acknowledgment, use original purchase order, response revision and order line. Use the partner guide to locate these values and check their allowed formats. ### Does a successful EDI receipt mean Google 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 Google EDI? 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. 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/)