--- title: "Outside-processing follow-up automation for metal…" description: "Coordinate late coating, plating, heat-treatment and other outsourced operations around the jobs they affect." canonical: https://www.stacksync.com/use-case/metal-fabrication-outside-processing-follow-up last_modified: 2026-09-21 --- Metal fabrication and machining # Outside-processing follow-up automation for metal fabricators > 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 ![Metal fabrication and machining systems connected through Stacksync two-way sync: Salesforce, Acumatica, NetSuite, PostgreSQL, Dynamics 365 F&O, SQL Server](https://www.stacksync.com/images/industry-heroes/icp-metal-fabrication-machining-800.webp) Coordinate late coating, plating, heat-treatment and other outsourced operations around the jobs they affect. Stacksync workflows can bring the relevant records into one handoff so purchasing and planning work from the same unresolved quantities. Start with evidence collection, owned follow-up and accepted recovery plans before extending transactional actions. Buyers and planners contact the same processor separately while the next shop operation waits for a return nobody has confirmed. [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 Operations leaders, production planners and IT teams at US metal fabricators and machine shops with 100–1,000 employees. ### Prioritize the real downstream impact Connect late quantities to the next operation and accepted customer commitment so the buyer knows why a batch matters. ### Coordinate one recovery conversation Retain supplier responses and assigned ownership, reducing duplicated status chasing across planners. ### Close against actual recovery Keep supplier dispatch, receipt and quality acceptance separate, with only the resolved quantity closed. The process, end to end ## Follow the work across systems an operations director manages several subcontract processors and needs one view of late batches, affected jobs and current promises. The evaluation should include a partial return and a missed revised date, showing who follows up and what remains unresolved. [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [PostgreSQL connector](https://www.stacksync.com/connectors/postgresql) Scope your implementation ## Bring these details to the demo - Current outside-processing dispatch and return records. - A named purchasing owner and planning escalation path. - Examples of partial returns, rejected work and supplier date changes. 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 - [Metal fabrication outside-processing delays: route late returns to the right job owner](https://www.stacksync.com/blog/metal-fabrication-outside-processing-late-return-workflow) 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. - [Machining drawing revisions: review a change against work already released](https://www.stacksync.com/blog/metal-machining-drawing-revision-released-job-workflow) A customer's revision D arriving mid-run should open a review of the pieces at each stage, not overwrite the revision C the shop and its processor are working to. [Explore all metal fabrication and machining integration and automation guides ↗](https://www.stacksync.com/industry/manufacturing/metal-fabrication-machining) ## Common evaluation questions ### Can this choose another processor? It can assemble approved alternatives and supporting information. Purchasing, engineering and quality retain the decision about the permitted process and supplier. ### What should the demonstration include? A late batch offered as a split return, competing downstream jobs and the resulting approved allocation. ### What is the economic measure? Use manual coordination time and delay-case aging, while keeping freight, rework and supplier performance outcomes separately attributed. ### Where does this follow-up workflow sit in the Stacksync product order? It comes second. Two-way sync between NetSuite and Postgres goes first, because a delay case needs the sent batch, required return date and affected job to resolve to the same records purchasing and planning already use. Then workflows carry the supplier’s recovery proposal, the allocation decision and escalation to named owners. Genies come later, if estimating wants RFQ emails and drawings turned into an evidence-based packet. EDI stays separate and last, covering customer PO lines and releases rather than anything a processor sends back.