--- title: "NetSuite Shopify sync for plastics packs and released stock" description: "Map Shopify variants to NetSuite items with a reviewed pack conversion and publish only released stock, so a six-pack order creates six pieces of demand." canonical: https://www.stacksync.com/blog/plastics-netsuite-shopify-pack-size-finished-goods last_modified: 2026-09-18 --- # Plastics brands using NetSuite and Shopify: preserve pack sizes and released stock > 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 A direct store that sells packs while NetSuite counts pieces needs a variant cross-reference, a versioned pack definition and a channel stock rule that excludes held lots. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision A plastics manufacturer selling through Shopify should map each sellable variant to the correct NetSuite item and reviewed pack definition. Publish stock that is eligible for the channel, keeping production output, quality-held quantity and available finished goods distinct. Two-way sync should preserve the original order quantity and its selling unit. The team must verify the specific inventory and order operations it needs rather than assuming a product connection includes every fulfillment action. 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: NetSuite Shopify sync for plastics packs and released stock](https://www.stacksync.com/images/blog-highlights/icp-plastics-netsuite-shopify-pack-size-finished-goods.webp) ## What this looks like in plastics and molding A plastics business sells storage components in single units to distributors and packs of six through its direct store. A new color is molded in a trial run, but most of that lot remains on hold pending inspection. If the store receives the gross piece count as the pack quantity, it can accept more orders than the company can fulfill. The integration needs a product-variant cross-reference, an approved pack conversion and a channel availability rule that uses released stock instead of treating every completed molding cycle as saleable inventory. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Store variant | Product operations | Link color and pack configuration to the intended ERP item without relying on a mutable product title. | | Pack definition | Product operations | Store pieces per selling pack and the effective version used for each accepted order. | | Quality eligibility | Quality and inventory | Distinguish released finished goods from trial output, held lots and quantities already committed elsewhere. | | Channel order line | Order management | Preserve shop, order, line, quantity and selling unit alongside the ERP reference. | ![Record ownership diagram: Store variant, Pack definition, Quality eligibility](https://www.stacksync.com/images/blog-diagrams/icp-plastics-netsuite-shopify-pack-size-finished-goods.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Review the assortment at variant level Select products with clear color, size and pack definitions. Identify variants that share a base molded part but have different packaging. Resolve their relationships before enabling order transfer so a common SKU description does not conceal a different unit of sale. 2. 02 Define released channel stock Agree which locations and statuses can contribute to the store’s available quantity. Include existing commitments and the stock policy for distributor accounts. Record when the underlying availability was measured so a stale projection can be distinguished from a current shortage. 3. 03 Retain both quantity representations Store the customer’s pack quantity and the calculated piece quantity. Use the reviewed conversion applicable to that order. Reconcile partial fulfillment and cancellations at the same grain rather than subtracting pieces from a field that represents packs. 4. 04 Test changes and recovery Exercise an order, a pack-definition change and a quality hold on a contributing lot. Reconcile authoritative order state after delayed or repeated messages. Confirm the exact destination operations and permissions used to publish quantity and accept the order. ![4-step operating sequence: NetSuite Shopify sync for plastics packs and released stock](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-plastics-netsuite-shopify-pack-size-finished-goods.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### A pack definition changes after an order Keep the accepted order’s original conversion. Apply the new definition only to the approved scope and future orders. ### A color variant is held for inspection Remove only the ineligible quantity from the relevant variant’s offer and route existing affected commitments to review. ### A cancellation follows partial shipment Reconcile the remaining accepted quantity through the approved process. Do not treat a whole-order cancellation message as proof that shipped units returned to stock. ## What to verify before expanding - One six-pack produces six pieces of demand under the approved mapping. - Held trial output does not increase the offered stock. - Historical orders retain their original pack definition after a catalog change. - Replayed messages cannot create another order or restore cancelled demand. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real store variant example and the exception your team handles most often, for example A pack definition changes after an order. - [Salesforce and NetSuite two-way sync for plastics manufacturers](https://www.stacksync.com/use-case/plastics-salesforce-netsuite-two-way-sync) - [NetSuite and Shopify two-way sync for plastics brands](https://www.stacksync.com/use-case/plastics-netsuite-shopify-two-way-sync) - [Plastics manufacturing: connect Dynamics resin lots to a SQL Server readiness view](https://www.stacksync.com/blog/plastics-dynamics-sql-server-resin-lot-readiness) - [Plastics manufacturing resin substitutions: coordinate evidence before changing the run](https://www.stacksync.com/blog/plastics-resin-substitution-approval-workflow) - [Plastics quality holds: update customer promises when a color lot is blocked](https://www.stacksync.com/blog/plastics-color-quality-hold-order-promise-workflow) - [Optimize NetSuite Shopify Integration and HubSpot Sync with Stacksync](https://www.stacksync.com/blog/optimize-netsuite-shopify-integration-and-hubspot-sync-with-stacksync) - [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) - [Shopify: webhook ordering and reconciliation](https://shopify.dev/docs/apps/build/webhooks) FAQ ## Frequently asked questions Can the store share stock with wholesale accounts? Yes, if inventory control defines how commitments and channel reservations affect the published quantity. A shared warehouse does not mean every unit can be offered independently to every channel. What if the ERP uses a different unit than Shopify? Preserve both units and use a reviewed conversion. Do not overwrite the source quantity with the converted total because reviewers need to see the customer’s actual order. What should the demonstration emphasize? Show a pack-based order and a quality hold occurring after publication. Buyers should see how the mapping preserves quantity and how affected commitments are identified. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) 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 - [integration NetSuite and Shopify integration](https://www.stacksync.com/integrations/netsuite-and-shopify) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Shopify integrations](https://www.stacksync.com/connectors/shopify) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Building products on Shopify: sync NetSuite bundles, pieces and saleable stock 4 min read read](https://www.stacksync.com/blog/building-products-netsuite-shopify-bundle-unit-sync) [Data engineering Electrical components on Shopify: map NetSuite variants, packs and order quantities 4 min read read](https://www.stacksync.com/blog/electrical-components-netsuite-shopify-pack-variant-orders) [Data engineering NetSuite and Shopify for manufacturers: publish saleable finished goods 4 min read read](https://www.stacksync.com/blog/manufacturing-netsuite-shopify-finished-goods-availability) ## 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/)