--- title: "Amazon NetSuite sync for beauty variation families" description: "Amazon Seller Central order lines land in NetSuite at the child offer, so a variation family never merges several shades or sizes into one ERP item." canonical: https://www.stacksync.com/blog/amazon-netsuite-sync-for-beauty-brands-match-variation-families-to-erp-products last_modified: 2026-09-21 --- # Amazon–NetSuite Sync for Beauty Brands: Match Variation Families to ERP Products > 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 Read-only Amazon order evidence keeps seller SKU, marketplace and child offer intact, so finance and support can identify the exact shade and size a shopper bought. Author Ruben Burdin · Founder & CEO Published September 21, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Import beauty marketplace evidence at the sellable offer and order-line level, retaining variation-family context without using it as the ERP product key. A parent catalog grouping can contain many shades and sizes. The NetSuite relationship must identify the exact purchased item and preserve seller and marketplace scope. Explore the complete [personal care integration and automation hub](https://www.stacksync.com/industry/cpg/personal-care) for the systems and processes around this guide. ![Summary card: Amazon NetSuite sync for beauty variation families](https://www.stacksync.com/images/blog-highlights/icp-amazon-netsuite-sync-for-beauty-brands-match-variation-families-to-erp-products.webp) ## What this looks like in personal care A beauty listing groups several shades and two bottle sizes. Finance needs order evidence and support needs to identify a returned item. Mapping the entire family to one ERP SKU would make the data look consistent while losing the very attributes that distinguish what the customer bought. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Variation context | Marketplace catalog owner | Preserve the available family and child references as catalog evidence. | | Seller offer | Marketplace operations | Scope seller SKU by account and marketplace and map the actual sellable configuration. | | Order line | Operations | Retain the purchased offer, quantity, and stable original line reference. | | ERP crosswalk | Product operations | Approve the exact shade and size relationship with effective dates. | ![Record ownership diagram: Variation context, Seller offer, Order line](https://www.stacksync.com/images/blog-diagrams/icp-amazon-netsuite-sync-for-beauty-brands-match-variation-families-to-erp-products.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Select the correct grain Use the sellable offer or child-level identity available in the source, not a parent variation title. Inspect representative records before choosing the keys used by the integration. 2. 02 Validate product attributes Check shade, size, and pack against the approved ERP item. Conflicting attributes should stop the match even when a catalog family or name appears familiar. 3. 03 Preserve marketplace scope Retain seller account and marketplace so similar SKUs in another channel cannot collide. Keep the original line reference for later returns and finance reconciliation. 4. 04 Review catalog revisions Version changes to offers and product mappings. Historical order evidence must continue to resolve to the sold item after a listing family is reorganized. 5. 05 Trace one variation family through NetSuite line by line Pick a live Amazon listing family with at least two shades and two pack sizes. Import one day of its orders, then query the resulting NetSuite records grouped by ERP item. You should see one item per child offer sold. A single item absorbing the whole family, or a two-pack showing as two units of the single, means the crosswalk is keyed too high and the rollout stops there. Then take a return from that batch and walk it back from the NetSuite line to the Amazon order-line ID and seller SKU. If any step requires guessing the shade from a title, fix the mapping before importing further history. ![5-step operating sequence: Amazon NetSuite sync for beauty variation families](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-amazon-netsuite-sync-for-beauty-brands-match-variation-families-to-erp-products.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Family contains several pack sizes Map each sellable configuration independently rather than applying one shared quantity factor. ### Child offer disappears Keep historical mapping evidence and route new unmatched orders for review. ### Return names only the family Request or retrieve the original order-line relationship before choosing the affected item. ## What to verify before expanding - A variation family cannot collapse several ERP items into one. - Each returned line can resolve to the originally sold shade and size. - A return naming only a variation family remains unmatched until the original sellable child offer and order line are resolved. - Removing a child offer from the current catalog leaves the historical shade, size, and pack mapping available for earlier sales. ## 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 variation context example and the exception your team handles most often, for example family contains several pack sizes. - [Shopify–NetSuite Integration for Personal Care and Beauty Brands](https://www.stacksync.com/use-case/shopify-netsuite-integration-for-personal-care-and-beauty-brands) - [Amazon–NetSuite Integration for Beauty Marketplace Operations](https://www.stacksync.com/use-case/amazon-netsuite-integration-for-beauty-marketplace-operations) - [HubSpot–Acumatica Sync for Personal Care Brands Selling to Salons and Retailers](https://www.stacksync.com/blog/hubspot-acumatica-sync-for-personal-care-brands-selling-to-salons-and-retailers) - [Personal Care Sample and Tester Workflows: Track Requests Through Warehouse Fulfillment](https://www.stacksync.com/blog/personal-care-sample-and-tester-workflows-track-requests-through-warehouse-fulfillment) - [Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv](https://www.stacksync.com/blog/personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv) - [Product Exchange Checks: Refunds, Stock, and Customer Choice](https://www.stacksync.com/blog/product-exchange-checks-refunds-stock-and-customer-choice) - [EDI Compliance Issues with Retail Trading Partners (2026 Guide)](https://www.stacksync.com/blog/edi-compliance-retail-partners-trading) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync two-way sync quick start](https://docs.stacksync.com/start-here/quick-start) - [Stacksync Amazon Seller Central access](https://docs.stacksync.com/two-way-sync/connectors/amazon-seller-central) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Can this sync reorganize Amazon variation listings? No. The documented sync access is read-only. Marketplace listing changes require separately confirmed actions and authorization. How far back should the first Amazon import reach? Start with the period your open returns window covers, since those are the orders support will need to trace first. Older history can follow once the crosswalk has been checked against live sales. Before any backfill, have product operations date each ERP relationship: a child offer whose pack count changed last year needs two mapping rows, and an undated crosswalk cannot tell them apart. Where does a finance reviewer see the marketplace scope on an order? On the NetSuite transaction itself. Seller account and marketplace identifiers arrive as fields on each imported line instead of being folded into the item name, so a reviewer opening a sales record can tell two marketplaces apart for the same seller SKU without leaving the ERP. Keep those fields read-only in NetSuite; the sync carries them from Amazon, and editing them by hand breaks the trace. 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 Amazon Seller Central integration](https://www.stacksync.com/integrations/amazon-seller-central-and-netsuite) - [connector Amazon Seller Central integrations](https://www.stacksync.com/connectors/amazon-seller-central) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [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 Amazon–NetSuite Sync for Household Consumables: Reconcile Marketplace Order Quantities 5 min read read](https://www.stacksync.com/blog/amazon-netsuite-sync-for-household-consumables-reconcile-marketplace-order-quantities) [Data engineering Amazon–NetSuite Sync for Packaged Food Brands: Separate FBA and Merchant-Fulfilled Orders 5 min read read](https://www.stacksync.com/blog/amazon-netsuite-sync-for-packaged-food-brands-separate-fba-and-merchant-fulfilled-orders) [Data engineering Amazon–NetSuite Sync for Pet Brands: Reconcile Marketplace Returns and Original Orders 5 min read read](https://www.stacksync.com/blog/amazon-netsuite-sync-for-pet-brands-reconcile-marketplace-returns-and-original-orders) ## 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/)