--- title: "Plastics EDI for blanket PO releases and carton quantities" description: "Keep each blanket PO release as its own line and the carton count beside converted pieces, so a revised week does not overwrite another accepted release." canonical: https://www.stacksync.com/blog/plastics-edi-blanket-orders-release-uom last_modified: 2026-09-18 --- # Plastics manufacturing EDI: distinguish blanket orders, releases and pack quantities > 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 Weekly distributor releases arrive in cartons while NetSuite plans in pieces; EDI intake keeps every release and its original unit intact before planning accepts demand. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Plastics EDI intake should distinguish the customer’s blanket agreement from the individual releases that create actionable demand. Preserve partner, PO, release and line identity, then map the customer’s part and pack unit to the approved internal item. Document receipt is not production acceptance. Use the partner’s agreed 850/860 process where applicable, and keep tooling, sample or forecast information separate from the quantities planning has accepted for a molding run. Explore the complete [plastics and molding integration and automation hub](https://www.stacksync.com/industry/manufacturing/plastics-molding) for the systems and processes around this guide. ![Summary card: Plastics EDI for blanket PO releases and carton quantities](https://www.stacksync.com/images/blog-highlights/icp-plastics-edi-blanket-orders-release-uom.webp) ## What this looks like in plastics and molding A molder supplies a distributor under a blanket PO. The distributor sends weekly releases in cartons, while the ERP plans production in pieces. A revised release reduces one delivery and moves another date. If intake matches only the PO number, it can overwrite prior accepted releases. If it interprets cartons as pieces, it understates demand. The correct process retains each release and original unit, applies the reviewed conversion, and checks whether changed quantities affect work that has already begun. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Blanket agreement | Commercial operations | Retain the customer’s standing reference and commercial context without treating its total as a new production release. | | Release line | Order management | Identify the actual quantity and date request using the partner’s agreed release and line keys. | | Customer pack definition | Product operations | Map cartons, cases or other selling units to a reviewed base quantity for the relevant item. | | Accepted production demand | Planning | Keep approved quantities separate from pending changes and any nonbinding forecast information. | ![Record ownership diagram: Blanket agreement, Release line, Customer pack definition](https://www.stacksync.com/images/blog-diagrams/icp-plastics-edi-blanket-orders-release-uom.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Review the partner’s release examples Obtain representative original, changed and repeated documents. Confirm how releases are identified and which document messages carry them. A familiar transaction-set number does not by itself explain the partner’s business convention. 2. 02 Preserve source quantities before conversion Keep the customer’s quantity and unit on every proposed line. Resolve the pack definition through approved product data, including the relevant customer and effective scope. Show the calculated base quantity so a reviewer can inspect the conversion. 3. 03 Apply changes to the intended release Compare the incoming request with the latest accepted release state. Hold unknown references and changes affecting committed production for review. A change to one week’s demand must not overwrite another week’s accepted quantity under the same blanket PO. 4. 04 Reconcile application and acknowledgment Confirm which lines the ERP accepted and retain their destination references. Prepare the agreed business response from that outcome. Keep transmission failures separate so retrying a response does not recreate the production demand. ![4-step operating sequence: Plastics EDI for blanket PO releases and carton quantities](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-plastics-edi-blanket-orders-release-uom.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The same release is sent with another envelope Use the business release identity and processing history to recognize the replay. ### The carton quantity changes for a new packaging version Require a reviewed effective conversion and preserve earlier orders under the version they accepted. ### The customer sends an annual estimate with releases Represent it as planning context under the agreed meaning, not another firm production order. ## What to verify before expanding - Separate releases under one PO retain distinct quantities and dates. - The original carton quantity remains visible beside the converted piece quantity. - A replay adds no new demand and an accepted revision updates only its target release. - Pending production-impacting changes remain distinct from the current accepted schedule. ## 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 blanket agreement example and the exception your team handles most often, for example the same release is sent with another envelope. - [Plastics manufacturing: connect Salesforce tooling quotes and NetSuite production orders](https://www.stacksync.com/blog/plastics-salesforce-netsuite-tooling-production-order) - [Plastics brands using NetSuite and Shopify: preserve pack sizes and released stock](https://www.stacksync.com/blog/plastics-netsuite-shopify-pack-size-finished-goods) - [Plastics manufacturing: connect Dynamics resin lots to a SQL Server readiness view](https://www.stacksync.com/blog/plastics-dynamics-sql-server-resin-lot-readiness) - [Bi-Directional Sync for Microsoft Dynamics 365 EDI](https://www.stacksync.com/blog/bi-directional-sync-microsoft-dynamics-365-edi) - [Design Reliable Sync: Ditch Exactly-Once Delivery, Embrace Idempotency](https://www.stacksync.com/blog/design-reliable-sync-ditch-exactly-once-delivery-embrace-idempotency) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) - [X12: supply chain transaction flow](https://x12.org/flow/supply-chain) FAQ ## Frequently asked questions Can EDI eliminate all release review? It can automate well-defined checks and handoffs. Ambiguous identities, changed packaging and production-impacting revisions still need the approval path established by the business. Should the blanket quantity be reduced after every release? Follow the customer agreement and ERP model. The integration should not invent a depletion rule without confirming whether the blanket value represents a ceiling, estimate or another commercial concept. What should a test set contain? Include two releases, a carton-to-piece conversion, a replay, a changed date and a packaging-version change. Verify both resulting demand and the partner response. 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 NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [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 Plastics manufacturing resin substitutions: coordinate evidence before changing the run 4 min read read](https://www.stacksync.com/blog/plastics-resin-substitution-approval-workflow) [App tips Resin certificate AI exceptions: handle lot mismatches and corrected documents 4 min read read](https://www.stacksync.com/blog/plastics-genie-certificate-lot-document-exceptions) [App tips AI agents for plastics manufacturers: collect resin certificates for quality review 4 min read read](https://www.stacksync.com/blog/plastics-genie-resin-certificate-collection) ## 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/)