--- title: "Shopify–NetSuite Integration for Pet Food and Treat Brands" description: "Connect pet-product ecommerce orders to the exact recipe, bag size, and variety-pack definition in the ERP." canonical: https://www.stacksync.com/use-case/shopify-netsuite-integration-for-pet-food-and-treat-brands last_modified: 2026-09-21 --- Pet food and treats # Shopify–NetSuite Integration for Pet Food and Treat 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 ![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) Connect pet-product ecommerce orders to the exact recipe, bag size, and variety-pack definition in the ERP. This fits brands combining DTC and wholesale when teams need a reliable shared purchase trail for fulfillment and support. Keep product identity accurate without assuming it establishes the production lot shipped. Similar recipe names hide different bag sizes and mixed-pack contents across commerce and operational records. [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 exact product Connect stable Shopify variants to approved ERP recipe and package definitions. ### Retain useful trace context Keep historical pack and shipment references available for support while leaving lot attribution to verified operational evidence. ### Field ownership across Shopify and NetSuite Shopify products, variants, orders, and customers are the listed sync objects. Ecommerce owns the purchased variant; product operations owns the approved NetSuite item and package definition. Derived totals and final financial states stay with the application that calculates them. Inventory levels and fulfillment actions are separate decisions, so product sync alone never allocates stock or releases a shipment. The process, end to end ## Follow the work across systems A pet brand sells two bag sizes of one recipe and a trial pack containing several recipes. A demo should preserve all purchased variants and components, then show how support follows the actual shipment reference rather than guessing a lot from the catalog or order date. [Shopify connector](https://www.stacksync.com/connectors/shopify) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [Review the integration details ↗](https://www.stacksync.com/integrations/netsuite-and-shopify) Scope your implementation ## Bring these details to the demo - Orders with multiple bag sizes and a variety pack. - Approved recipe, package, and component mappings. - Field ownership for product and financial records. - Any required shipment-to-lot evidence and separate operational actions. 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 - [Shopify–NetSuite Sync for Pet Food Brands: Match Recipes, Bag Sizes, and Variety Packs](https://www.stacksync.com/blog/shopify-netsuite-sync-for-pet-food-brands-match-recipes-bag-sizes-and-variety-packs) One recipe in two bag sizes plus a trial pack should reach NetSuite as the same distinct products the customer chose in Shopify. - [Amazon–NetSuite Sync for Pet Brands: Reconcile Marketplace Returns and Original Orders](https://www.stacksync.com/blog/amazon-netsuite-sync-for-pet-brands-reconcile-marketplace-returns-and-original-orders) A refund for a variety pack sold weeks ago gets matched to its original Amazon order line and the pack contents on that date, not to today's catalog. - [HubSpot–NetSuite Sync for Pet Food Brands: Connect Independent Retailers and Reorder Status](https://www.stacksync.com/blog/hubspot-netsuite-sync-for-pet-food-brands-connect-independent-retailers-and-reorder-status) Reps see which store already has an accepted NetSuite order on the way, while the retailer's central payer and each location stay separate records in HubSpot. [Explore all pet food and treats integration and automation guides ↗](https://www.stacksync.com/industry/cpg/pet-food-treats) ## Common evaluation questions ### Does product synchronization prove the shipped lot? No. Product identity and lot attribution are different relationships. The latter needs reliable fulfillment or shipment evidence. ### What happens when a variety pack changes recipes after customers have bought it? The purchased definition stays with the order. Your product team versions the variety-pack composition with effective dates, and the Shopify order line keeps the components it was sold with. NetSuite carries the approved item relationship for the new assortment going forward. When support later reviews an older purchase, the synced record shows the original recipes and quantities, not the current catalog. The same rule applies when a bag size is renamed: retain the stable variant identity and check whether the physical package changed. ### Which Stacksync product should a pet food brand start with here? Start with two-way sync between Shopify variants, orders, and customers and the approved NetSuite items, so every purchase carries its exact recipe and bag size. Add workflows once you want a defined handoff, such as routing a wholesale exception before an order is released. Bring in Genies when support needs a sourced trace from a complaint back to the order and shipment. Add EDI when independent retailers send purchase orders as partner documents rather than through your storefront.