--- title: "Wholesale Sample Automation for Nutrition Brands | Stacksync" description: "Coordinate practitioner and retailer sample requests from approval through actual fulfillment and sales follow-up." canonical: https://www.stacksync.com/use-case/wholesale-sample-automation-for-nutrition-brands last_modified: 2026-09-21 --- Nutrition and supplements # Wholesale Sample Automation for Nutrition 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 ![Nutrition and supplements systems connected through Stacksync two-way sync: Shopify, NetSuite, Amazon Seller Central, HubSpot, Zendesk](https://www.stacksync.com/images/industry-heroes/icp-nutrition-supplements-800.webp) Coordinate practitioner and retailer sample requests from approval through actual fulfillment and sales follow-up. This fits nutrition brands whose reps, operations teams, and finance owners work from different versions of the sample request. Keep sample allocation distinct from the approval of a later paid wholesale account. Sales follows up on requested samples without knowing which flavors actually shipped or whether the recipient account is approved. [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 Nutrition and supplement brands combining manufacturing, DTC, marketplaces, practitioner sales, and retail distribution. ### Approve the intended allocation Resolve the recipient and requested products, then record the authorized sample items and quantities. ### Connect follow-up to evidence Report actual fulfillment and associate later opportunities without presenting the sample itself as a paid commercial order. ### Samples never create a NetSuite payer The workflow reads the HubSpot contact, company, and sample request, routes approval requests and shipment notices through Slack, and records the authorized allocation against the request. It does not create a NetSuite customer or set terms on its own; finance approves the legal payer before a paid order is released. The commercial owner approves substitutions, and operations owns the shipped items and tracking evidence. The process, end to end ## Follow the work across systems A rep asks for several flavors for a clinic. One is unavailable and the receiving details are incomplete. The workflow gathers the missing information, routes substitutions for approval, and gives sales the actual shipment result so the next conversation reflects what the clinic received. [HubSpot connector](https://www.stacksync.com/connectors/hubspot) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [Slack connector](https://www.stacksync.com/connectors/slack) Scope your implementation ## Bring these details to the demo - A typical clinic or retailer sample request. - Sample quantity and substitution policies. - Account and receiving-location ownership. - The verified fulfillment actions and desired follow-up outcome. 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 - [Wholesale Sample-to-Order Workflows for Nutrition Brands Using HubSpot and NetSuite](https://www.stacksync.com/blog/wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite) Three flavors requested, one unavailable and no ship-to contact: the workflow fills the gaps, routes the substitution, and records what shipped to the clinic before sales calls. - [Supplement Return Workflows: Connect Zendesk Requests to Warehouse and Finance Review](https://www.stacksync.com/blog/supplement-return-workflows-connect-zendesk-requests-to-warehouse-and-finance-review) Wrong tub size reported, nothing back at the warehouse yet: the workflow keeps the ticket, the authorization, the receipt, and the credit as four separate facts. [Explore all nutrition and supplements integration and automation guides ↗](https://www.stacksync.com/industry/cpg/nutrition-supplements) ## Common evaluation questions ### Will a sample recipient automatically become an ERP customer? No. Samples can establish sales activity while legal account, terms, and ordering approval remain separate business decisions. ### What happens when a requested flavor is out of stock or two reps ask for the same clinic? An unavailable flavor is not swapped by the workflow. It flags the gap to the commercial owner, who approves a substitute or a revised request, and the approved item list is stored apart from the rep's original ask so follow-up reflects what shipped. When a second rep forwards the same clinic request, the workflow compares the HubSpot account and request history and resolves both to the reviewed allocation instead of shipping twice. Sales sees the actual shipment result, not an assumed delivery. ### Should we start with workflows or with two-way sync for sample requests? Start with two-way sync so HubSpot contacts and companies resolve to the correct NetSuite payer before any sample moves. Workflows are the product for this page: they carry the sample request through validation, approval, fulfillment evidence, and Slack notification with named owners at each state. Genies fit later, when a wholesale buyer asks for batch documents that need assembling from several sources. EDI becomes relevant once a retailer wants pack configurations and item numbers exchanged as partner documents.