--- title: "NetSuite Shopify Extensiv fulfillment workflow for CPG" description: "A workflow releases a Shopify order only after the NetSuite hold check, sends one Extensiv instruction, and tracks acceptance apart from shipment." canonical: https://www.stacksync.com/blog/cpg-fulfillment-workflows-with-netsuite-shopify-and-extensiv last_modified: 2026-09-21 --- # CPG Fulfillment Workflows With NetSuite, Shopify, and Extensiv > 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 Channel request, NetSuite release decision and approved pack conversion come together before an Extensiv instruction goes out, and a partial shipment leaves the rest open. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision A CPG fulfillment workflow should release only an eligible order, transmit the approved warehouse instruction, and reconcile the warehouse result to the originating channel and ERP lines. Keep synchronization, release approval, and physical shipment as distinct events. Extensiv is a workflow connector in this design; confirm the exact warehouse actions and available status fields before deployment. Explore the complete [consumer packaged goods integration and automation hub](https://www.stacksync.com/industry/cpg) for the systems and processes around this guide. ![Summary card: NetSuite Shopify Extensiv fulfillment workflow for CPG](https://www.stacksync.com/images/blog-highlights/icp-cpg-fulfillment-workflows-with-netsuite-shopify-and-extensiv.webp) ## What this looks like in consumer packaged goods A brand takes an online order for three multipacks while the warehouse picks individual units. The ERP shows a finance hold, but a support agent sees a paid Shopify order and asks the 3PL to ship. A reliable process combines the channel request, ERP release decision, and approved pack conversion before any warehouse instruction is issued. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Order eligibility | Order operations | Evaluate the current order revision, payment context, finance hold, and approved allocation policy. | | Warehouse instruction | Fulfillment manager | Store one approved request reference and the exact item, quantity, unit, and ship-to payload. | | Warehouse response | 3PL operations | Attach the accepted warehouse reference and distinguish receipt from actual shipment. | | Channel reconciliation | Customer operations | Report only confirmed outcomes that correspond to the original order lines. | ![Record ownership diagram: Order eligibility, Warehouse instruction, Warehouse response](https://www.stacksync.com/images/blog-diagrams/icp-cpg-fulfillment-workflows-with-netsuite-shopify-and-extensiv.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Build the release packet Gather the channel order, ERP transaction, ship-to, and product crosswalk. Validate the current revision so an old paid-order event cannot release an order that was later held or canceled. 2. 02 Check every physical quantity Translate multipacks using the approved conversion record. Retain both ordered and warehouse units so the 3PL response can be reconciled without guessing from a product description. 3. 03 Submit once and track acceptance Use a stable operation reference and inspect the destination response. A network timeout should trigger a lookup for the existing warehouse request before another submission is attempted. 4. 04 Reconcile partial outcomes Handle accepted, allocated, partially shipped, and canceled quantities separately. Do not convert a warehouse acknowledgment into a shipped status or close remaining lines merely because one package left. 5. 05 Hold one order in NetSuite mid-release and check Extensiv Run two paid Shopify orders through the release packet. Put the first on finance hold in NetSuite before release; the workflow must stop at eligibility with no request created in Extensiv. Release the second, then apply a NetSuite hold while the warehouse request is in flight. The workflow must halt every following action, record the race for the fulfillment manager, and show whether Extensiv accepted the request or can still cancel it. In Extensiv, confirm the accepted request and the later shipment appear as two distinct states. Stop the rollout if a held order produced a warehouse request, if the in-flight hold was ignored, or if acceptance displayed as shipped. ![5-step operating sequence: NetSuite Shopify Extensiv fulfillment workflow for CPG](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-cpg-fulfillment-workflows-with-netsuite-shopify-and-extensiv.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Hold applied during submission Stop subsequent actions and route the race to fulfillment; determine whether the warehouse can still stop the accepted request. ### 3PL response lacks a line reference Match using approved keys or escalate; do not distribute quantities across similar SKUs. ### Split shipment Keep each shipment reference while preserving the open remainder on the original order. ## What to verify before expanding - An ERP-held order cannot reach the approved warehouse submission step. - Warehouse acceptance and shipment are separate visible states. - After an ambiguous warehouse timeout, a repeated release resolves the existing request reference before another instruction is submitted. - A partial shipment leaves the remaining original order lines open and does not mark the whole order shipped. ## 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 order eligibility example and the exception your team handles most often, for example hold applied during submission. - [CPG Credit-Hold Release Workflows: Keep Finance Approval and Fulfillment in Step](https://www.stacksync.com/blog/cpg-credit-hold-release-workflows-keep-finance-approval-and-fulfillment-in-step) - [Wholesale CPG Account Onboarding: Coordinate Sales, Finance, and Operations](https://www.stacksync.com/blog/wholesale-cpg-account-onboarding-coordinate-sales-finance-and-operations) - [AI Agents for CPG Order-to-Cash: Investigate Order and Payment Exceptions](https://www.stacksync.com/blog/ai-agents-for-cpg-order-to-cash-investigate-order-and-payment-exceptions) - [Shopify–NetSuite Integration: Orders, Inventory, and Setup](https://www.stacksync.com/blog/two-way-sync-shopify-and-netsuite-comprehensive-real-time-integration-guide) - [Amazon Seller Central and NetSuite: Read-Only Sync and Reconciliation](https://www.stacksync.com/blog/two-way-sync-amazon-seller-central-netsuite) 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) - [Stacksync Shopify supported objects](https://docs.stacksync.com/two-way-sync/connectors/shopify) - [Shopify product variant model](https://shopify.dev/docs/api/admin-graphql/latest/objects/productvariant) FAQ ## Frequently asked questions Is Extensiv part of the two-way sync catalog? Treat Extensiv as a workflow connector in this design: the workflow calls a named warehouse action, such as creating an outbound order, and reads back the response and later status. It is not configured as a two-way sync pair with NetSuite or Shopify here, so no Extensiv field is kept in continuous agreement with the ERP. Scope each action, its credential and the customer account it targets during the pilot, and add nothing beyond that list. What stops a support agent from triggering a warehouse release from a paid Shopify order? A paid event in Shopify opens a review; it is an input to the eligibility packet, not a trigger for the warehouse step. The release action is reachable only from the workflow's eligible state, and only a fulfillment manager role can approve it, with the approver's identity stored on the instruction. Support sees the order's state and the reason it is waiting, and asks the fulfillment manager rather than the 3PL. Does the warehouse instruction carry units or multipacks? Both. The workflow looks up the approved pack record for each line, writes the warehouse unit quantity into the Extensiv instruction, and keeps the ordered multipack quantity on the same record so the 3PL response can be compared to either. A line whose variant has no approved pack record holds the order before submission; the workflow does not default the conversion to one unit and let the warehouse guess. 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 Shopify integrations](https://www.stacksync.com/connectors/shopify) - [connector Extensiv (3PL Central) integrations](https://www.stacksync.com/connectors/extensiv-3pl-central) - [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) [App tips Household Product Return Workflows: Route Damaged and Unsellable Goods for Review 5 min read read](https://www.stacksync.com/blog/household-product-return-workflows-route-damaged-and-unsellable-goods-for-review) [App tips Packaged Food Promotion Workflows: Coordinate Retail Commitments and Ecommerce Launches 5 min read read](https://www.stacksync.com/blog/packaged-food-promotion-workflows-coordinate-retail-commitments-and-ecommerce-launches) [App tips Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv 4 min read read](https://www.stacksync.com/blog/personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv) ## 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/)