--- title: "Fabrication EDI blanket PO releases and drawing revisions" description: "Map each release under a blanket PO to its own accepted Acumatica line with the approved drawing revision attached, so a replayed document adds no demand." canonical: https://www.stacksync.com/blog/metal-fabrication-edi-purchase-order-drawing-revision last_modified: 2026-09-18 --- # Metal fabrication EDI orders: preserve drawing revision and release identity > 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 Repeat orders for a machined housing arrive as releases against one blanket PO; intake must tell releases, changes and retransmissions apart before any line reaches the ERP. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Metal-fabrication EDI order intake should connect the customer’s line reference to the approved part, drawing revision, selling unit and release. A syntactically valid order can still be incomplete for manufacturing. Use the trading partner’s agreed document rules to distinguish a new order, a release and a change. Keep engineering and planning decisions separate from document receipt so an automated intake does not turn an ambiguous part description into released shop work. Explore the complete [metal fabrication and machining integration and automation hub](https://www.stacksync.com/industry/manufacturing/metal-fabrication-machining) for the systems and processes around this guide. ![Summary card: Fabrication EDI blanket PO releases and drawing revisions](https://www.stacksync.com/images/blog-highlights/icp-metal-fabrication-edi-purchase-order-drawing-revision.webp) ## What this looks like in metal fabrication and machining A fabricator receives repeat orders for a machined housing. The customer reuses a blanket PO and sends releases with different dates, while an engineering change introduces a new drawing revision. If intake uses only the blanket PO and internal item number, it can either reject legitimate demand as a duplicate or overwrite the earlier release with the new specification. The mapping needs the partner’s release identity and the applicable revision, plus an exception path when the incoming document does not supply enough information to choose them. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Partner purchase-order line | Order management | Preserve customer, PO and line references before translating them into ERP identifiers. | | Release identity | Customer operations | Use the agreed release or schedule reference to distinguish separate demand under a blanket order. | | Approved part revision | Engineering | Resolve the customer part and drawing reference against approved manufacturing records. | | Intake decision | Order management and planning | Record accepted, rejected or review-required outcomes for each line and revision. | ![Record ownership diagram: Partner purchase-order line, Release identity, Approved part revision](https://www.stacksync.com/images/blog-diagrams/icp-metal-fabrication-edi-purchase-order-drawing-revision.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Document the repeat-order convention Confirm how the partner represents blanket orders, releases and changes in its implementation guide. Include examples with reused PO numbers. The mapping must follow that convention rather than assuming one PO number always means exactly one executable order. 2. 02 Resolve the manufacturing reference Match the customer part to the internal item and applicable drawing revision. Keep the incoming reference alongside the resolved one. If the document lacks a required revision, route the line to the agreed review process instead of substituting the latest revision automatically. 3. 03 Validate quantity and timing meaning Check selling units and whether the incoming dates are requested shipment, delivery or another agreed milestone. Preserve source values and approved conversions. Planning should see the actual demand meaning before accepting its effect on capacity or committed material. 4. 04 Track application and response separately Apply approved lines through the verified ERP route, retaining external references for replay checks. Record pending exceptions and prepare the partner response required by the agreement. A response retry must not create another release or repeat the accepted order update. ![4-step operating sequence: Fabrication EDI blanket PO releases and drawing revisions](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-metal-fabrication-edi-purchase-order-drawing-revision.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### A repeat transmission uses another envelope identifier Compare the business release and application history before creating demand. A new transport wrapper does not automatically make the order new. ### The customer omits a drawing revision Use only the documented partner rule or explicit approval to resolve it. Otherwise keep the manufacturing reference pending. ### A change moves demand to a new date after work starts Send the revision to planning for impact review and preserve the existing accepted release until the decision is made. ## What to verify before expanding - Two legitimate releases under one blanket PO remain separately identifiable. - A replay of either release produces no additional demand. - The approved drawing revision remains attached to the accepted line. - A changed date is visible as a request until its operational effect is approved. ## Connect this process to the rest of your operation [Explore Stacksync EDI](https://www.stacksync.com/edi) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real partner purchase-order line example and the exception your team handles most often, for example A repeat transmission uses another envelope identifier. - [Metal fabrication: connect Salesforce quotes to Acumatica job-ready orders](https://www.stacksync.com/blog/metal-fabrication-salesforce-acumatica-quote-job-handoff) - [Machine shops: connect NetSuite and Postgres outside-processing status](https://www.stacksync.com/blog/metal-machining-netsuite-postgres-outside-processing-status) - [Metal fabrication: link Dynamics order demand and material certificates in SQL Server](https://www.stacksync.com/blog/metal-fabrication-dynamics-sql-server-material-certificate-links) - [How to Parse EDI Files Into a SQL Database](https://www.stacksync.com/blog/parse-edi-files-sql-database) - [Real-Time NetSuite to Database Sync: Implementation Guide and Best Practices](https://www.stacksync.com/blog/real-time-netsuite-database-sync-implementation-guide) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Acumatica: endpoints and contracts](https://help-2025r2.acumatica.com/%28W%285%29%29/Wiki/ShowWiki.aspx?PageID=1a9d6f7e-8546-426b-b1ff-d712fbcfbc7b&wikiname=HelpRoot_Dev_Integration) - [X12: supply chain transaction flow](https://x12.org/flow/supply-chain) FAQ ## Frequently asked questions Can the most recent drawing be used by default? Only if the customer agreement and internal approval process explicitly define that behavior. For revision-sensitive work, a newer drawing may apply only to future releases. Is EDI intake the same as a native two-way connector? No. EDI transport, document mapping, business validation and ERP operations are separate parts of the process and need their own scope checks. Which test is essential for repeat manufacturing customers? Use two releases under one PO, then replay one and change the other. Confirm that identity, quantity and revision remain correct across all three actions. About the author Alexis Favre Co-Founder & CTO Alexis Favre is the Co-Founder and CTO of Stacksync (YC W24), the first real-time and two-way sync for enterprise data at scale. Alexis is a Y Combinator alumni with expertise in large scale data engineering. [All posts by Alexis Favre](https://www.stacksync.com/blog/author/alexis-favre) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Acumatica integrations](https://www.stacksync.com/connectors/acumatica) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Metal fabrication outside-processing delays: route late returns to the right job owner 4 min read read](https://www.stacksync.com/blog/metal-fabrication-outside-processing-late-return-workflow) [App tips Machining drawing revisions: review a change against work already released 4 min read read](https://www.stacksync.com/blog/metal-machining-drawing-revision-released-job-workflow) [App tips AI RFQ intake for metal fabricators: prepare a complete estimating packet 4 min read read](https://www.stacksync.com/blog/metal-fabrication-genie-rfq-drawing-intake) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)