--- title: "Sample and Tester Fulfillment Automation for Personal Care…" description: "Coordinate personal-care sample and tester requests through approved allocation and actual warehouse fulfillment." canonical: https://www.stacksync.com/use-case/sample-and-tester-fulfillment-automation-for-personal-care-brands last_modified: 2026-09-21 --- Personal care # Sample and Tester Fulfillment Automation for Personal Care Brands > 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) Coordinate personal-care sample and tester requests through approved allocation and actual warehouse fulfillment. This fits brands whose sales teams serve salons or retailers and need to know what was authorized, substituted, and shipped. Keep tester items and commercial sales distinct throughout the process. Reps request retail shades while operations stocks separate tester items, and nobody sees the accepted assortment in one place. [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. ### Approve the right goods Resolve tester and sample equivalents and route unusual quantities or substitutions to the responsible owner. ### Close the sales-to-warehouse handoff Store the accepted warehouse reference and communicate actual shipment evidence, including remaining items. ### A request is not a shipment HubSpot holds the tester request that sales writes, NetSuite holds the tester and retail items that product operations maps, and the commercial owner authorizes the allocation. Only the approved list is submitted to Extensiv through a verified warehouse action, and the workflow reads back the accepted reference. The workflow does not substitute retail stock for a missing tester unless the responsible owner approves that specific swap. The process, end to end ## Follow the work across systems A salon requests a tester display for a new line. The account owner proposes shades, product operations resolves tester equivalents, and a manager approves the allocation. A demo should show the final authorized list, a partial shipment, and the actual result returned to sales for follow-up. [HubSpot connector](https://www.stacksync.com/connectors/hubspot) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [Extensiv (3PL Central) connector](https://www.stacksync.com/connectors/extensiv-3pl-central) Scope your implementation ## Bring these details to the demo - A representative salon tester or sample request. - Approved tester-to-retail product relationships. - Quantity limits and substitution authority. - Verified warehouse actions and receiving-location data. 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 - [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) Reps ask for retail shades, operations stocks tester SKUs, and the workflow holds the request until the recipient, item mapping and quantity are approved. - [Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv](https://www.stacksync.com/blog/personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv) Support, warehouse receipt, disposition and refund stay as separate states with separate owners, so a closed ticket never stands in for a completed return. [Explore all personal care integration and automation guides ↗](https://www.stacksync.com/industry/cpg/personal-care) ## Common evaluation questions ### Can unavailable testers be replaced with retail units automatically? Only an explicit approved policy could allow that substitution. The default process should ask the authorized owner and preserve what was approved. ### What happens when two reps submit the same tester request for one salon? The workflow checks the salon account's history before anything is allocated. A second request for the same location and shades is held and shown to the commercial owner alongside the first, rather than creating a second allocation. The owner decides whether the repeat is legitimate, for example a second display for a stylist who joined after the first shipment, and authorizes the quantity. Whatever ships, Extensiv returns the accepted reference and the actual assortment, and both reps see that single result in HubSpot instead of two competing wish lists. ### Do we need two-way sync before the tester workflow? Usually yes. Two-way sync between HubSpot companies and NetSuite customers and items gives the workflow a resolved salon account and approved tester items to work from. The workflow then carries each tester request through mapping, allocation approval, and the Extensiv fulfillment result. Genies come in when a repeated or unusual request needs account history and prior shipments gathered for the commercial owner to judge. EDI does not touch tester allocation; it matters only when retailers begin ordering the same products as partner documents.