--- title: "NetSuite Shopify sync for component variants and pack sizes" description: "Map Shopify variants to NetSuite items and selling packs so near-identical connectors, pack quantities and accepted orders keep the right item and unit." canonical: https://www.stacksync.com/blog/electrical-components-netsuite-shopify-pack-variant-orders last_modified: 2026-09-18 --- # Electrical components on Shopify: map NetSuite variants, packs and order 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 Similar connector descriptions and a new pack size are where storefront orders go wrong; hold variant identity, item reference and conversion version per accepted order. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision Electrical and electronic component sellers using NetSuite and Shopify need a precise mapping between storefront variants, internal items and selling packs. Preserve manufacturer references, relevant configuration attributes and the reviewed unit conversion. Two-way sync should align selected records without implying that every similarly named component is interchangeable. Confirm the exact order and inventory operations required, and keep availability separate from technical suitability for a buyer’s intended application. Explore the complete [electrical and electronic components integration and automation hub](https://www.stacksync.com/industry/manufacturing/electrical-electronic-components) for the systems and processes around this guide. ![Summary card: NetSuite Shopify sync for component variants and pack sizes](https://www.stacksync.com/images/blog-highlights/icp-electrical-components-netsuite-shopify-pack-variant-orders.webp) ## What this looks like in electrical and electronic components A manufacturer sells connectors individually to service accounts and in packs through Shopify. Several variants differ in an attribute customers must select, while their short descriptions look almost identical. A new pack size is introduced after earlier orders were accepted. An integration that joins by description and uses the current pack count for every order can select the wrong variant and distort historical quantities. The correct handoff retains the storefront variant identity, approved item reference and conversion version used for that specific accepted order. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Storefront variant | Product operations | Preserve Shopify variant identity and the exact approved product attributes represented by it. | | Internal component | Product operations | Map the relevant internal and manufacturer references without using similar descriptions as proof of equivalence. | | Selling-pack definition | Product data owner | Keep the reviewed quantity per pack and its effective scope. | | Commerce order line | Order management | Retain source quantity and unit, accepted conversion and ERP order relationship. | ![Record ownership diagram: Storefront variant, Internal component, Selling-pack definition](https://www.stacksync.com/images/blog-diagrams/icp-electrical-components-netsuite-shopify-pack-variant-orders.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Review the variant cross-reference Select a product family with closely related variants and inspect the mapping with product operations. Ensure that the attributes needed to distinguish the customer’s selection survive the handoff. A title change should not reassign an existing variant to another component. 2. 02 Define the pack and inventory policy Record the conversion between the storefront selling unit and the ERP quantity. Identify which stock locations and statuses contribute to the channel offer. Technical suitability remains a product decision even when a variant has available quantity. 3. 03 Preserve the accepted order interpretation Store the original pack quantity, converted quantity and mapping version. Resolve customer and ship-to independently. Keep the external order and line references so edits and repeated messages can be reconciled against the same transaction. 4. 04 Prove the required operations Test product updates, order preparation and any intended stock publication with the actual app permissions. Scope fulfillment, cancellation and refund behavior separately. A working product sync should not be presented as proof of every commerce action. 5. 05 Exercise catalog changes and delayed events Change the pack definition for future sales, then inspect an earlier order. Deliver a stale order update and verify that it cannot undo a newer accepted state. Reconcile authoritative records after interruption rather than relying on message arrival order. ![5-step operating sequence: NetSuite Shopify sync for component variants and pack sizes](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-electrical-components-netsuite-shopify-pack-variant-orders.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### A variant description is shortened Keep its stable identity and approved mapping; do not rematch it to another product based on the new text. ### An order requests a component not approved for the application Route the customer’s technical question through the appropriate process. Inventory availability does not establish compatibility. ### A pack is partially fulfilled Reconcile the remaining obligation using the agreed commercial and base units without losing the original order quantity. ## What to verify before expanding - Closely related variants retain distinct approved item mappings. - Accepted orders keep their original pack conversion after catalog changes. - Repeated order events retain one destination reference. - Available stock is not represented as an engineering compatibility decision. ## 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 storefront variant example and the exception your team handles most often, for example A variant description is shortened. - [Salesforce and Acumatica two-way sync for electrical manufacturers](https://www.stacksync.com/use-case/electrical-salesforce-acumatica-two-way-sync) - [NetSuite and Postgres two-way sync for electronic-component operations](https://www.stacksync.com/use-case/electronics-netsuite-postgres-two-way-sync) - [Electrical manufacturers: connect Salesforce assembly quotes to Acumatica orders](https://www.stacksync.com/blog/electrical-manufacturers-salesforce-acumatica-configured-assemblies) - [Electronic component substitutions: route evidence to engineering before changing supply](https://www.stacksync.com/blog/electronics-component-substitution-engineering-workflow) - [Electronic-component returns: reconcile distributor quantities, lots and credit decisions](https://www.stacksync.com/blog/electronics-distributor-returns-lot-credit-workflow) - [Field-Level Change Detection: The Key to Efficient Real-Time Bidirectional CRM Sync](https://www.stacksync.com/blog/field-level-change-detection-the-key-to-efficient-real-time-bidirectional-crm-sync) - [Source of Truth: Should Your Warehouse or Your CRM Own Customer Data?](https://www.stacksync.com/blog/data-warehouse-vs-crm-source-of-truth) 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 customers buy a technically unsuitable component online? Product information and the company’s sales process govern suitability. The integration should accurately preserve the selected variant and route any explicit compatibility question rather than inventing an answer. Should the SKU alone control every match? Only if the approved model guarantees the required uniqueness and meaning. Preserve native variant and item identifiers even when SKU is part of the cross-reference. What should the pilot focus on? Use similar-looking variants, two pack sizes and a later catalog change. Inspect actual quantities and item references rather than judging only whether an order appeared. 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 NetSuite and Shopify for manufacturers: publish saleable finished goods 4 min read read](https://www.stacksync.com/blog/manufacturing-netsuite-shopify-finished-goods-availability) [Data engineering Plastics brands using NetSuite and Shopify: preserve pack sizes and released stock 4 min read read](https://www.stacksync.com/blog/plastics-netsuite-shopify-pack-size-finished-goods) ## 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/)