--- title: "HubSpot sample-to-order workflow for nutrition wholesale" description: "Route nutrition sample requests from HubSpot through approval, NetSuite fulfillment evidence and Slack prompts, so reps follow up on what shipped." canonical: https://www.stacksync.com/blog/wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite last_modified: 2026-09-21 --- # Wholesale Sample-to-Order Workflows for Nutrition Brands Using HubSpot and NetSuite > 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 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. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision A sample-to-order workflow should link the requested nutrition products, approved recipient, fulfillment evidence, and later wholesale opportunity. Use explicit sample authorization and keep the first paid order’s account approval separate. This gives sales an accurate follow-up trail without representing every sample shipment as a commercial sale. Explore the complete [nutrition and supplements integration and automation hub](https://www.stacksync.com/industry/cpg/nutrition-supplements) for the systems and processes around this guide. ![Summary card: HubSpot sample-to-order workflow for nutrition wholesale](https://www.stacksync.com/images/blog-highlights/icp-wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite.webp) ## What this looks like in nutrition and supplements A sales rep requests three flavors for a clinic evaluation. The request lacks the receiving contact and one flavor is unavailable. The workflow can obtain the missing address detail, route a proposed substitution for approval, and record what actually shipped before scheduling a useful follow-up. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Sample request | Sales | Specify account context, requested products, quantities, reason, and receiving contact. | | Sample approval | Commercial owner | Approve the allocation and any substitution within the agreed sample policy. | | Fulfillment result | Operations | Record actual shipped items and tracking evidence against the sample request. | | Wholesale conversion | Sales operations | Link the later opportunity or order without claiming that a sample itself established an approved payer. | ![Record ownership diagram: Sample request, Sample approval, Fulfillment result](https://www.stacksync.com/images/blog-diagrams/icp-wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Validate the request Resolve the clinic or retailer association and required ship-to details. Identify whether the recipient can receive the proposed items and whether the requested quantities fit the current sample policy. 2. 02 Approve exceptions Send unusual quantities, repeated requests, or substitutions to the named owner. Keep the approved item list separate from the rep’s original request so follow-up reflects what the recipient actually received. 3. 03 Track fulfillment evidence Submit only the verified action for the approved request. Store the destination reference and distinguish submitted, accepted, and shipped states before notifying sales. 4. 04 Connect the next commercial step Create a follow-up based on the shipment outcome and link any resulting opportunity. The first paid order still needs its own legal account, terms, and release checks. 5. 05 Send the same sample request twice and check what ships Have two reps submit the same clinic sample request a day apart. In HubSpot, the second request should attach to the first case with the account history visible, and only one approved allocation should reach fulfillment. After shipment, open the sample request in HubSpot and confirm the shipped item list matches what operations recorded in NetSuite, including any approved substitution, with tracking attached. Then check that the clinic still has no active NetSuite customer with terms. Stop the rollout if two shipments leave for the same request, if the rep sees the originally requested flavors instead of the shipped ones, or if the sample created an order-ready payer. ![5-step operating sequence: HubSpot sample-to-order workflow for nutrition wholesale](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Repeated request from another rep Compare the account and request history before approving another allocation. ### Requested flavor is unavailable Seek an approved substitute or revised request rather than choosing automatically. ### Recipient never confirms delivery Preserve shipment evidence and route the follow-up without asserting product receipt or use. ## What to verify before expanding - Sales sees the approved and actually shipped sample items. - A sample shipment does not bypass wholesale account approval. - Two reps forwarding the same sample request resolve to the reviewed allocation rather than creating separate sample shipments. - Shipment confirmation supports follow-up without being labeled recipient receipt, product use, or approval for the first paid order. ## Connect this process to the rest of your operation [Explore Stacksync workflows](https://www.stacksync.com/workflow-automation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real sample request example and the exception your team handles most often, for example repeated request from another rep. - [Wholesale Sample Automation for Nutrition Brands](https://www.stacksync.com/use-case/wholesale-sample-automation-for-nutrition-brands) - [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) - [AI Agents for Nutrition Brands: Assemble Product and Batch-Document Requests](https://www.stacksync.com/blog/ai-agents-for-nutrition-brands-assemble-product-and-batch-document-requests) - [Missing COAs and Batch Mismatches: Exception Handling for Nutrition Brand Agents](https://www.stacksync.com/blog/missing-coas-and-batch-mismatches-exception-handling-for-nutrition-brand-agents) - [Automating Quote-to-Cash Between HubSpot and NetSuite](https://www.stacksync.com/blog/automate-hubspot-netsuite-quote-to-cash) - [Syncing Custom Fields From a Legacy NetSuite to HubSpot](https://www.stacksync.com/blog/sync-netsuite-custom-fields-to-hubspot) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Workflows quick start](https://docs.stacksync.com/two-way-sync/workflows/workflows-quick-start) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Can sample follow-up create a paid ERP order? It can initiate an approved order process after account and commercial checks. Interest or a positive reply alone is not an accepted purchase order. What goes to Slack and what stays in HubSpot? Slack carries the decision prompts: the approver gets the request summary, the proposed substitution, and a link, and the decision is recorded on the sample approval. The record of what was requested, approved, and shipped lives in HubSpot and NetSuite, not in the channel thread, so a reviewer never has to reconstruct a decision from chat history. Slack messages are prompts and notices, not the system of record. Do we need a written sample policy before configuring the approvals? Yes, and it should state quantity caps per account and period, which substitutions the commercial owner may approve alone, and which need a second review. The workflow encodes those thresholds as routing rules; without them every request becomes a manual decision and the approver turns into the bottleneck the automation was meant to remove. Keep the policy version on each approval so a later audit knows which rule applied. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) 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 - [connector HubSpot integrations](https://www.stacksync.com/connectors/hubspot) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Slack integrations](https://www.stacksync.com/connectors/slack) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering HubSpot–NetSuite Sync for Nutrition Brands Selling to Practitioners and Retailers 5 min read read](https://www.stacksync.com/blog/hubspot-netsuite-sync-for-nutrition-brands-selling-to-practitioners-and-retailers) [Data engineering Syncing Custom Fields From a Legacy NetSuite to HubSpot 9 min read read](https://www.stacksync.com/blog/sync-netsuite-custom-fields-to-hubspot) [App tips EDI for Supplement Brands Entering Retail: Validate Item Numbers and Pack Configurations 4 min read read](https://www.stacksync.com/blog/edi-for-supplement-brands-entering-retail-validate-item-numbers-and-pack-configurations) ## 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/)