--- title: "EDI for Flooring Suppliers and Installation Contractors" description: "Connect purchase, shipment and invoice documents with consistent product and unit references." canonical: https://www.stacksync.com/use-case/edi-flooring-suppliers-installers last_modified: 2026-09-21 --- Commercial flooring and interior installation # EDI for Flooring Suppliers and Installation Contractors > 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 ![Commercial flooring and interior installation systems connected through Stacksync two-way sync: HubSpot, NetSuite, Supabase, Salesforce, Acumatica](https://www.stacksync.com/images/industry-heroes/icp-commercial-flooring-interiors-800.webp) Use EDI to connect flooring supplier documents to project purchase lines while preserving boxes, rolls, pallets and area units. Stacksync can support the document-to-system design with partner-specific mapping and controlled workflow handoffs. Receiving and finance still verify physical quantities, condition and commercial differences. Supplier packaging and invoice units differ from the takeoff, causing avoidable quantity and price disputes. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. When this fits ## Built for this operating problem US flooring and interior contractors with 100–1,000 employees that supply materials and install commercial projects. ### Preserve the original units Keep supplier quantities and approved conversions available so receiving and finance can reproduce the comparison. ### Handle split packages and deliveries Retain purchase-line and shipment references when one order arrives in several phases or partial packages. ### Separate document and business acceptance Technical processing does not prove material was accepted at the site or that an invoice is approved. The process, end to end ## Follow the work across systems a supplier ships a mixture of full and partial pallets while invoicing by area. The contractor needs line-level conversions and receipt evidence so purchasing, warehouse and accounts payable agree on the actual quantity. [NetSuite connector](https://www.stacksync.com/connectors/netsuite) Scope your implementation ## Bring these details to the demo - Trading-partner implementation guide - Item and unit mappings - Sample partial shipments and invoices - Receiving and matching rules Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. From foundation to action ## One connected operating process 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Go deeper ## Implementation guides for your team - [Flooring Supplier EDI: Keep Roll, Box, and Pallet Quantities Consistent From PO to Invoice](https://www.stacksync.com/blog/flooring-supplier-edi-keep-roll-box-and-pallet-quantities-consistent-from-po-to-invoice) Map flooring supplier EDI with explicit product units, package hierarchy and partial-delivery references. [Explore all commercial flooring and interior installation integration and automation guides ↗](https://www.stacksync.com/industry/construction/commercial-flooring-interiors) ## Common evaluation questions ### Does EDI choose the correct conversion? The buyer and supplier must agree the product-specific rule. The mapping preserves and applies that approved meaning. ### Can it handle damaged deliveries? Keep damage and usable quantity in receiving evidence and route the resulting commercial exception. ### What is the right first supplier? Choose recurring volume with clear partner documentation and a manageable set of products and units. ### Should EDI be the first Stacksync product we adopt, or the last? Usually the last. Two-way sync comes first when NetSuite purchase lines, product conversions and receiving records must match what your project and finance teams see elsewhere. Workflows follow, routing supplier quantity, price and substitution changes to the buyer and accounts payable. Genies come next when a receipt disagrees with the takeoff and the difference needs an explanation with sources. EDI arrives once the trading-partner implementation guide and item and unit mappings are agreed. If supplier documents are the only open problem, begin with EDI.