--- title: "Approved Lot-Hold Automation for Pet Food Operations" description: "Carry a quality owner’s approved lot-hold decision into verified order and warehouse operations." canonical: https://www.stacksync.com/use-case/approved-lot-hold-automation-for-pet-food-operations last_modified: 2026-09-21 --- Pet food and treats # Approved Lot-Hold Automation for Pet Food 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 ![Pet food and treats systems connected through Stacksync two-way sync: Shopify, NetSuite, Amazon Seller Central, HubSpot, Zendesk, PostgreSQL](https://www.stacksync.com/images/industry-heroes/icp-pet-food-treats-800.webp) Carry a quality owner’s approved lot-hold decision into verified order and warehouse operations. This fits pet-food teams that need a clear record of which actions succeeded, which records are ambiguous, and which cases require manual review. The workflow coordinates an authorized decision and does not determine product safety. A hold decision reaches multiple teams, but no shared record confirms the actual operational state for every affected location. [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 Pet food and treat brands combining production, DTC, marketplaces, independent retail, and wholesale distribution. ### Preserve the approved scope Keep product, lot, location, approver, action, and effective time attached to every operational handoff. ### Verify actual execution Read back the intended state and leave unsupported, failed, or ambiguous actions visibly incomplete for the named owner. ### Quality owns the decision, not the workflow The approved hold, with its product, lot, locations, approver, and effective time, is entered once by the quality owner and is not edited by the workflow. The workflow reads lot-to-order evidence from NetSuite and Postgres, applies only the ERP or warehouse actions you have confirmed and permissioned, and posts each result to Slack. Releasing the hold takes a new approved decision. The process, end to end ## Follow the work across systems A quality manager approves a hold for a specific product and lot at two warehouses. A demo should show the authorized scope, reliable affected-record links, verified actions, and an already-shipped exception that remains assigned to quality and logistics rather than being falsely marked stopped. [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [PostgreSQL connector](https://www.stacksync.com/connectors/postgresql) [Slack connector](https://www.stacksync.com/connectors/slack) Scope your implementation ## Bring these details to the demo - An approved lot-hold decision and its exact scope. - Reliable lot-to-location and lot-to-order evidence. - Verified ERP or warehouse control actions. - Quality approval, exception, and release policies. 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 - [Pet Food Wholesale Workflows: Route Minimum-Order and Freight Exceptions](https://www.stacksync.com/blog/pet-food-wholesale-workflows-route-minimum-order-and-freight-exceptions) Under-minimum and free-freight requests from independent stores go to the person with authority, and the approved terms stay attached to the NetSuite order. - [Pet Food Lot-Hold Workflows: Carry Approved Quality Decisions Into Order Operations](https://www.stacksync.com/blog/pet-food-lot-hold-workflows-carry-approved-quality-decisions-into-order-operations) A quality manager's hold on one lot at two warehouses becomes a checklist of confirmed NetSuite actions, open manual tasks, and escalations for goods already gone. [Explore all pet food and treats integration and automation guides ↗](https://www.stacksync.com/industry/cpg/pet-food-treats) ## Common evaluation questions ### Does this decide whether a product is safe? No. The quality team owns that decision. The workflow carries the accepted instructions and verifies the operational result. ### What happens to a shipment that already left before the hold was approved? It goes to the exception case, owned by quality and logistics, with the original decision attached. The workflow does not report it as stopped, because an internal hold does not recall goods already in transit. Lot-to-order evidence in NetSuite and Postgres tells you which released orders carried the affected lot; where an order has no reliable lot association, the case is escalated under the quality owner's policy rather than guessed. The Slack notice to the owners names the shipment, the lot, and the decision it needs. ### Do we need two-way sync before a lot-hold workflow, and what comes after it? Two-way sync keeps lot, order, and location records consistent between NetSuite and Postgres, and that shared copy is what the hold workflow reads. The workflow is where you start here: it carries the quality owner's approved hold into confirmed ERP actions, reads back each state, and posts exceptions to Slack. Genies follow when a complaint must be traced to an order and lot before quality decides on a hold. EDI matters once retailer purchase orders and shipment notices enter the same operation.