--- title: "Outside-processing delay workflow for NetSuite and Postgres" description: "Tie late heat-treatment batches to the jobs and NetSuite orders waiting on them, with one buyer owning supplier follow-up and planning approving recovery." canonical: https://www.stacksync.com/blog/metal-fabrication-outside-processing-late-return-workflow last_modified: 2026-09-18 --- # Metal fabrication outside-processing delays: route late returns to the right job owner > 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 When a processor returns heat-treated parts late or in a split shipment, one shared case shows the unresolved quantity, the affected next operation and who decides the allocation. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision An outside-processing delay workflow should identify which sent batches remain unresolved, which downstream jobs need them and who can approve a recovery plan. Compare the subcontractor’s latest confirmation with the internal requirement, then coordinate purchasing and planning follow-up. Keep expected return, carrier movement, physical receipt and inspection acceptance separate. The workflow is complete when the affected job has accepted material or an approved alternative, not when a reminder has been sent. Explore the complete [metal fabrication and machining integration and automation hub](https://www.stacksync.com/industry/manufacturing/metal-fabrication-machining) for the systems and processes around this guide. ![Summary card: Outside-processing delay workflow for NetSuite and Postgres](https://www.stacksync.com/images/blog-highlights/icp-metal-fabrication-outside-processing-late-return-workflow.webp) ## What this looks like in metal fabrication and machining A shop outsources heat treatment for three jobs. The processor confirms that one batch will return late but can split the shipment. A buyer currently forwards that email to several planners, each of whom may call the supplier independently. A shared delay case can collect the sent quantities, required return dates, existing responses and affected operations. Purchasing can request one coherent recovery plan, while planners decide whether a partial return changes their schedules and who should receive the limited available quantity. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Delay case | Subcontract purchasing | Tie the issue to a processor, operation and sent-batch identity with a named follow-up owner. | | Required return | Production planning | Preserve the date and quantity needed for the next operation rather than relying only on the customer ship date. | | Supplier recovery proposal | Purchasing | Record the offered split quantity, date and transport conditions as a proposal awaiting internal acceptance. | | Job allocation decision | Planning | Identify which job receives the recovered quantity and retain approval when priorities change. | ![Record ownership diagram: Delay case, Required return, Supplier recovery proposal](https://www.stacksync.com/images/blog-diagrams/icp-metal-fabrication-outside-processing-late-return-workflow.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Find the actionable outstanding quantity Calculate unresolved sent quantity from dispatches, receipts and agreed dispositions. Exclude batches already received but still awaiting inspection from the supplier-late queue; they need a quality or receiving follow-up instead. 2. 02 Assemble one supplier conversation Attach the latest confirmation and prior follow-ups to the case. Identify the buyer authorized to coordinate the supplier response. This avoids multiple planners requesting incompatible delivery promises against the same constrained batch. 3. 03 Evaluate the proposed recovery Show downstream operations, requested quantities and available alternatives to planning. If the processor offers a split return, ask which jobs it should cover. Capture any approved transport or process change before communicating an accepted plan. 4. 04 Follow the batch through acceptance Track the revised commitment, dispatch evidence, receipt and required inspection. Escalate when a promised milestone is missed. Close only the quantity actually resolved and keep the remainder open under the same traceable case. ![4-step operating sequence: Outside-processing delay workflow for NetSuite and Postgres](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-metal-fabrication-outside-processing-late-return-workflow.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The supplier says shipped but there is no receipt Keep the case in transit or awaiting receipt and retain the relevant evidence. Shipping confirmation does not make the parts available to the next operation. ### Two jobs compete for a partial return Route allocation to the planner who owns prioritization. Do not divide the batch automatically merely to clear both overdue flags. ### The returned work is rejected Create the appropriate quality disposition and reconnect the unresolved quantity to the delay case so purchasing does not assume recovery is complete. ## What to verify before expanding - Each late quantity has one current supplier-follow-up owner. - A partial recovery closes only the accepted quantity and leaves the balance visible. - Planners can see the next operation affected by the delay. - Supplier shipment confirmation cannot mark inspection-dependent work ready. ## 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 delay case example and the exception your team handles most often, for example the supplier says shipped but there is no receipt. - [Outside-processing follow-up automation for metal fabricators](https://www.stacksync.com/use-case/metal-fabrication-outside-processing-follow-up) - [Machining drawing revisions: review a change against work already released](https://www.stacksync.com/blog/metal-machining-drawing-revision-released-job-workflow) - [AI RFQ intake for metal fabricators: prepare a complete estimating packet](https://www.stacksync.com/blog/metal-fabrication-genie-rfq-drawing-intake) - [AI RFQ exceptions in metal fabrication: resolve material, revision and quantity ambiguity](https://www.stacksync.com/blog/metal-fabrication-genie-rfq-material-revision-exceptions) - [Acumatica API Integration: A Practical Guide](https://www.stacksync.com/blog/acumatica-api-integration-guide) - [Real-Time NetSuite to Database Sync: Implementation Guide and Best Practices](https://www.stacksync.com/blog/real-time-netsuite-database-sync-implementation-guide) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) FAQ ## Frequently asked questions Should every overdue batch generate another email? No. Use the current commitment and open conversation to decide when follow-up is due. Repeated reminders without new evidence can create noise while hiding the real unresolved decision. Can the workflow choose another subcontractor? It can assemble alternatives from approved information. Purchasing, engineering and quality must decide whether another processor is authorized for the affected operation. What should purchasing track about late outside-processing batches? Measure manual coordination touches, overdue confirmation age and the time from delay discovery to an accepted recovery plan. Compare similar outsourced operations rather than all supplier activity. 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 PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [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 Machine shops: connect NetSuite and Postgres outside-processing status 4 min read read](https://www.stacksync.com/blog/metal-machining-netsuite-postgres-outside-processing-status) [App tips Metal fabrication EDI orders: preserve drawing revision and release identity 4 min read read](https://www.stacksync.com/blog/metal-fabrication-edi-purchase-order-drawing-revision) [Data engineering Real-Time NetSuite to Database Sync: Implementation Guide and Best Practices 11 min read read](https://www.stacksync.com/blog/real-time-netsuite-database-sync-implementation-guide) ## 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/)