--- title: "Freight threshold workflow for beverage distributor orders" description: "A NetSuite and Salesforce workflow that holds a beverage distributor order until the freight threshold and the depot's receiving window are confirmed." canonical: https://www.stacksync.com/blog/beverage-distributor-order-workflows-check-freight-thresholds-and-delivery-windows last_modified: 2026-09-21 --- # Beverage Distributor Order Workflows: Check Freight Thresholds and Delivery Windows > 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 Under-threshold freight and unconfirmed depot windows go to a named approver in Slack, and the order leaves NetSuite for the warehouse only with both decisions attached. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision A distributor-order workflow should validate the accepted commercial terms and receiving window before releasing beverage freight. Keep minimum quantities, freight thresholds, requested dates, and approved exceptions as explicit fields. A salesperson’s requested date should not become a confirmed logistics commitment without the required review. Explore the complete [beverages integration and automation hub](https://www.stacksync.com/industry/cpg/beverages) for the systems and processes around this guide. ![Summary card: Freight threshold workflow for beverage distributor orders](https://www.stacksync.com/images/blog-highlights/icp-beverage-distributor-order-workflows-check-freight-thresholds-and-delivery-windows.webp) ## What this looks like in beverages A distributor orders just below the agreed freight threshold and requests a narrow delivery window at a depot with limited receiving hours. Sales wants to ship immediately. The workflow should route the freight exception and verify the receiving commitment before an order reaches the warehouse or carrier. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Distributor order | Sales operations | Preserve requested quantities, destination, date, and commercial reference. | | Freight policy | Commercial owner | Own the applicable threshold, unit, terms, and approved exceptions. | | Receiving window | Logistics | Confirm destination-specific time and date requirements with current evidence. | | Release decision | Order operations | Require the approved commercial and logistics conditions before execution. | ![Record ownership diagram: Distributor order, Freight policy, Receiving window](https://www.stacksync.com/images/blog-diagrams/icp-beverage-distributor-order-workflows-check-freight-thresholds-and-delivery-windows.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Evaluate the correct threshold Apply the agreement for this distributor and destination, using its stated unit and value basis. A case threshold and an order-value threshold are different rules and need different evidence. 2. 02 Confirm the delivery context Check the receiving location, requested date, and any appointment requirement. Store the time zone and source of the approved window so a date-only field cannot hide a timing conflict. 3. 03 Route exceptions explicitly Send under-threshold freight or an unconfirmed window to the authorized owner. Record whether the decision changes the charge, quantity, date, or release condition instead of using a vague approved flag. 4. 04 Recheck before release Compare the final order and destination against the approval. A reduced quantity or changed depot can invalidate the earlier decision and should return to review. 5. 05 Reduce a NetSuite test order below the threshold before go-live Approve a test distributor order in the workflow, then open the approval record and confirm it names the case quantity or order value it covers, not a bare approved flag. In NetSuite, the released sales order must show the confirmed depot, delivery date, time zone, and the window logistics accepted. Next, reduce the quantity below the freight threshold after approval. The workflow should pull the order back into review and post the new exception to the approver. Stop the rollout if the reduced order releases on the old approval, if the destination or window is blank on the released order, or if the approval cannot say what it covered. ![5-step operating sequence: Freight threshold workflow for beverage distributor orders](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-beverage-distributor-order-workflows-check-freight-thresholds-and-delivery-windows.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Order quantity drops below threshold Reassess freight terms before release instead of inheriting the earlier approval. ### Depot changes the window Route the new requirement to logistics and preserve the previous commitment. ### Sales offers free freight Require the commercial authorization associated with that exception. ## What to verify before expanding - Freight approval identifies the order amount or quantity it covers. - The released order carries the confirmed destination and delivery window. - Reducing quantities below the agreed freight threshold reopens the commercial decision before order release. - A depot window change preserves the earlier commitment and requires logistics acceptance of the revised time zone and window. ## 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 distributor order example and the exception your team handles most often, for example order quantity drops below threshold. - [Distributor Delivery-Window Automation for Beverage Brands](https://www.stacksync.com/use-case/distributor-delivery-window-automation-for-beverage-brands) - [Beverage Returns Workflows: Route Breakage Claims From Support to Finance](https://www.stacksync.com/blog/beverage-returns-workflows-route-breakage-claims-from-support-to-finance) - [AI Agents for Beverage Brands: Investigate Distributor Delivery Claims](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) - [Broken Cases and Disputed Delivery Windows: Exception Handling for Beverage Claim Agents](https://www.stacksync.com/blog/broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents) - [Reconcile Freight Rates and Dwell Times Before Issuing Credits](https://www.stacksync.com/blog/reconcile-freight-rates-and-dwell-times-before-issuing-credits) - [Investigate Freight Invoice Disputes Across NetSuite and Postgres](https://www.stacksync.com/blog/investigate-freight-invoice-disputes-across-netsuite-and-postgres) 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 a calendar date alone establish delivery readiness? No. The receiving location, its time zone, any appointment requirement, and the accepted window all bear on whether a truck can unload. A date-only field lets an order pass the check while the depot is closed that afternoon. Confirm which of these fields the distributor agreement makes mandatory and require each one before the release step treats the delivery context as complete. Does the workflow release the order to the warehouse on its own? It submits the release only after the commercial and logistics decisions are recorded and the order still matches what they covered. The release itself is a scoped NetSuite write; order operations owns the final go, and the workflow reads the order status back before telling sales in Slack. A Slack message is a notification rather than the release event, so nobody treats a thread reply as a shipping instruction. Where should the freight rules live so the workflow can read them? As structured fields on the distributor's record, with the unit (cases or order value), the amount, the destinations it applies to, and effective dates, rather than as notes on the account or in a rep's email. Load and review those rules with the commercial owner first, and keep them in one place, whether NetSuite or Salesforce, so the workflow and the approver read the same rule. Any order without a matching rule goes to review by default. 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 NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [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 Salesforce–NetSuite Sync for Beverage Brands: Connect Distributor Accounts and Delivery Locations 5 min read read](https://www.stacksync.com/blog/salesforce-netsuite-sync-for-beverage-brands-connect-distributor-accounts-and-delivery-locations) [App tips Beverage EDI: Reconcile Pallet Shipments, Advance Ship Notices, and Distributor Receipts 5 min read read](https://www.stacksync.com/blog/beverage-edi-reconcile-pallet-shipments-advance-ship-notices-and-distributor-receipts) [App tips Beverage Returns Workflows: Route Breakage Claims From Support to Finance 5 min read read](https://www.stacksync.com/blog/beverage-returns-workflows-route-breakage-claims-from-support-to-finance) ## 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/)