--- title: "Amazon–NetSuite Integration for Beauty Marketplace…" description: "Bring beauty marketplace order evidence into ERP reconciliation at the exact sellable-offer level." canonical: https://www.stacksync.com/use-case/amazon-netsuite-integration-for-beauty-marketplace-operations last_modified: 2026-09-21 --- Personal care # Amazon–NetSuite Integration for Beauty Marketplace Operations > 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 ![Personal care systems connected through Stacksync two-way sync: Shopify, NetSuite, Amazon Seller Central, HubSpot, Acumatica, Zendesk](https://www.stacksync.com/images/industry-heroes/icp-personal-care-800.webp) Bring beauty marketplace order evidence into ERP reconciliation at the exact sellable-offer level. This fits brands whose variation families contain many shades, sizes, or packs that must remain distinct in finance and operations. The documented Amazon sync access is read-only and supports downstream evidence gathering. A parent variation or familiar product name gets treated as the identity of every child offer. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. When this fits ## Built for this operating problem Personal-care and beauty brands combining product manufacturing, ecommerce, salons, and retail distribution. ### Keep variations distinct Use the actual sellable identity and approved item crosswalk while retaining family context as supporting evidence. ### Preserve historical order context Connect returns and finance events to the original line and mapping revision after the catalog changes. ### Amazon Seller Central stays read-only Stacksync reads Amazon Seller Central with read-only access: seller offers and order lines flow into NetSuite as evidence, scoped by seller account and marketplace. Nothing is written back to Amazon. Listing changes, order cancellations, and marketplace refunds happen inside Amazon under separate authorization. Product operations owns the ERP crosswalk that ties each child offer to the exact shade and size. The process, end to end ## Follow the work across systems A beauty brand groups several shades and bottle sizes under one marketplace family. Finance receives sales evidence while support investigates a return. The evaluation should demonstrate that each original order line retains the seller-scoped offer and exact ERP item rather than collapsing into one family-level record. [Amazon Seller Central connector](https://www.stacksync.com/connectors/amazon-seller-central) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [Review the integration details ↗](https://www.stacksync.com/integrations/amazon-seller-central-and-netsuite) Scope your implementation ## Bring these details to the demo - A variation family with several shades or sizes. - Seller and marketplace identifiers. - The approved ERP crosswalk for each sellable offer. - Examples of historical returns or catalog revisions. Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. From foundation to action ## One connected operating process 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Go deeper ## Implementation guides for your team - [Shopify–NetSuite Sync for Personal Care Brands: Align Shades, Sizes, and Gift Sets](https://www.stacksync.com/blog/shopify-netsuite-sync-for-personal-care-brands-align-shades-sizes-and-gift-sets) Travel sizes, full sizes and seasonal sets stay separate NetSuite items, so a Shopify order or a partial set return still resolves to what the customer bought. - [Amazon–NetSuite Sync for Beauty Brands: Match Variation Families to ERP Products](https://www.stacksync.com/blog/amazon-netsuite-sync-for-beauty-brands-match-variation-families-to-erp-products) 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. - [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) Sales works salon groups and stylists in HubSpot while finance keeps the billing identity and terms in Acumatica, so no tester contact turns into a duplicate customer. [Explore all personal care integration and automation guides ↗](https://www.stacksync.com/industry/cpg/personal-care) ## Common evaluation questions ### Can this reorganize Amazon variation families? The sync connector imports Amazon evidence. Listing or variation mutations require a separately verified action and authorization. ### How do we match a return that names only the variation family? Hold it until the original order line is found. The sync keeps each Amazon order line with its seller-scoped child offer and quantity, so support can retrieve the exact shade, size, and pack that shipped instead of guessing from the family title. A return that cannot be tied to a line stays unmatched and goes to review. Because Amazon access is read-only, the refund itself is issued in Seller Central by whoever holds that authority, and finance reconciles it against the original line in NetSuite. ### Which Stacksync product comes first for Amazon and NetSuite reconciliation? Begin with two-way sync, connecting Amazon Seller Central read-only, so order lines and seller offers land in NetSuite against the approved ERP crosswalk. Workflows follow when a child offer disappears from the catalog and new unmatched orders need routing to product operations. Genies help when a return names only a family and someone must gather the original line, offer, and mapping revision before a person decides. EDI is separate from marketplace sales; it enters when retailers send purchase orders for the same shades.