Pick ERP Roles Before Claude for Manufacturing Writes to NetSuite

Claude for Manufacturing is a plugin for existing Claude Team and Enterprise seats. It drafts quotes, nonconformance reports, 8D sections and the morning production report from your ERP, CAD and Microsoft 365 data, and a person approves each draft. Whether it can change your ERP depends on which ERP you run. On Infor M3, Anthropic's plugin only reads. On Oracle NetSuite, the plugin's own README lists the connector as "read and write." Infor ships its own plugin for changes, and only select customers can get it. So before anyone on the plant floor types "set us up," settle the ERP role Claude will sign in under.

Anthropic launched the plugin on November 12, 2026 with connectors for Autodesk Fusion, Infor, Microsoft 365 and Oracle NetSuite. It publishes no plugin price and names no customers. A technical webinar runs November 17 at 11:00 a.m. ET.

What Claude for Manufacturing Actually Does

The plugin is a bundle of 17 skills: 12 single tasks and 5 chains that hand work from one skill to the next, per the reference repository on GitHub. A skill, in Anthropic's sense, is a packaged set of instructions and reference files that Claude loads when a request matches it. Here they cover the daily paperwork of a discrete plant:

• quote-build prices a job from actual PO costs, labor and machine time, with setup amortized across quantity breaks.
• ncr-writeup drafts a nonconformance report, finds suspect parts and checks prior NCRs.
• root-cause-capa builds a timeline, computes control charts, ranks candidate causes and drafts 8D sections D1 to D5 and D7.
• breakdown-diagnosis ranks likely failure causes from sensor data, repair history and the manufacturer's fault trees.
• daily-production-report produces OEE, downtime, scrap in dollars and schedule exceptions.
• supplier-quote-request builds RFQ packages and compares bids, and the repository says it "never awards" a supplier.

The chains link these into longer runs: RFQ to quote, failed inspection to CAPA, and a supplier escape through root cause to an alternate source. Anthropic says onboarding starts when a user tells Claude "Set us up," after which it asks which systems the plant uses, tests the connectors and reports which skills cannot fully run yet (Anthropic).

Claude does not run machines. The solutions page says it does not operate equipment or run production control. Anthropic is working on equipment control separately as the Model Hardware Standard, a limited research preview, which we covered in the lab-instrument piece in August.

---

Which Systems Can Claude Change?

Claude can change records in NetSuite, and in Infor only through Infor's separate plugin. Everything else is read-only by default. The repository's ERP connector notes spell out the split:

System	Access in Anthropic's plugin	How it connects
Infor M3	Read only. No skill calls an M3 write transaction, "approved or not"	Custom connector using the MCP server address from your Infor administrator
Oracle NetSuite	Read and write; owners can require approval first	Connector enabled in Claude's settings; sign-in picks the account
Microsoft 365	Read-only by default	Connector in Claude's settings
Autodesk Fusion	Generates design variants; never touches the base model	Local MCP server inside the Fusion desktop app

The M3 exclusion is deliberate. Anthropic's notes say the M3 server exposes writes that can change customer orders, reschedule or delete work orders and change item prices, and that the skills call none of them. Ask Claude to "release MO 4001015937" and it drafts the change for a person to make in M3.

Anthropic's own pages don't agree on NetSuite. The solutions page says Claude does not "write to systems of record." The README says NetSuite is read and write. Both can be true if the plugin's skills only propose writes. Still, the connector underneath has the capability: Oracle's AI Connector Service FAQ says that with the MCP Standard Tools SuiteApp it can "create, read, update, and transform records" and execute record actions, limited to what the connecting role allows. What actually stops a write is the role you assign.

Oracle has made one call for you. The connector refuses Administrator roles and Oracle advises against any high-privilege role, so you need a custom role with the MCP Server Connection and OAuth 2.0 Access Tokens permissions, plus REST Web Services for the Standard Tools SuiteApp. Oracle says the service and the SuiteApp are free, although you still pay for the Claude subscription.

Anthropic's side adds an owner control on Team and Enterprise plans: owners can require approval before a connector changes anything, or block changes outright (Anthropic). Use both layers. The NetSuite role sets what Claude is able to do, and the Claude setting decides whether it asks first.

What Infor's Plugin Adds, and Who Can Get It

Infor's own plugin is the write path for Infor customers, and few of them can get it today. Infor's plugin and connector let approved users create purchase orders, reallocate stock to urgent orders, shift production lines after unplanned downtime and ship orders, with single sign-on and role entitlements taken from existing Infor permissions and each action recorded in Infor (Control Global). Initial availability is limited to select Infor Velocity Suite customers with the right Claude licensing and admin setup (Black Scarab).

Anthropic's launch post gives the example of a steel shipment that slips two weeks. The buyer sees the affected orders and stock at other sites, and after approval Claude releases a purchase order to another supplier and reschedules production. "Claude's access follows the buyer's Infor permissions," Anthropic writes (Anthropic).

The strongest objection comes from the planning side. Lisa Lang, a consultant who implements AI for custom manufacturers, argues that Infor's release says nothing about approving the operating rules that generate each recommendation, and that putting AI on top of requirements-planning logic "just accelerates the oscillations." She sells implementation services, so weigh it accordingly. The point holds anyway. A buyer who approves forty reasonable-looking PO changes a week can still amplify schedule nervousness if the reorder logic underneath is wrong. We made the same argument about reviewer fatigue in our guide to agent approval steps.

---

What It Costs and What Breaks

Anthropic publishes no separate price for the plugin, so budget for the seat plus usage. As of November 15, 2026, per Anthropic's pricing page, Team standard seats are $20 a month billed annually ($25 monthly) and premium seats are $100 ($125), for 2 to 150 seats. Enterprise is $20 per seat per month billed annually, with a 20-seat minimum and usage billed on top at API rates. On Enterprise, a scheduled morning report across several sites is metered usage. Set spend limits before you schedule it.

No customer results are published. The launch post names no customers or case studies. Control Global paraphrases a remark from Jessica Vincent of Oldcastle APG about asking questions where employees already work. Nothing in it says Oldcastle runs the plugin in production. The one statistic in the launch post is a 2025 Manufacturing Leadership Council survey finding that 79% of manufacturers enter data manually, which describes the problem and says nothing about results.

The README is candid about the gaps:

• Without connectors, 11 of the 12 single skills still run on scheduled CSV exports. Analysis from exports is only as current as the last export, a limit Black Scarab also flags.
• Design exploration needs a live Fusion connection. There is no fallback for SolidWorks, Creo, NX or Inventor.
• M3 provides no standard cost, quote history or routings, so quotes fall back to last purchase price and exports. M3 searches also cap silently at about 30 rows, and the skills are told to narrow and re-pull.
• A written spec with no drawing produces a budgetary estimate, not a firm quote.
• 8D sections D6 and D8 stay empty, because they require the corrective action to have taken effect.
• The morning report needs a scheduled trigger, since a plugin cannot start itself.

The GitHub repository also calls itself a reference implementation that is "not actively maintained," provided as is, at version 1.0.0. If you fork the skills to fit your plant, you own that fork.

Where to Pilot First

Start with skills that produce a document a person already reviews, and keep writes off until one of them has been checked against your records for a month. Quoting, NCR write-ups and the morning report all end in a human sign-off today, so a wrong draft costs an estimator's time and nothing reaches the ERP. Black Scarab suggests tracking quote accuracy and preparation time, and those are measurable within weeks.

Infor's agents on AWS were sold in May on 50% cost cuts, and Toyota North America moved agents into production fast because one platform security review covered many of them. The equivalent review for this plugin is your ERP role design, and it has to happen before the pilot.

This Week:

1. Ask your NetSuite administrator to create a dedicated non-admin role for Claude with the MCP Server Connection, OAuth 2.0 Access Tokens and REST Web Services permissions and view-only record access. Do not grant create or edit yet.
2. In Claude's owner settings, set the NetSuite connector to require approval before any change. Block changes entirely if you have not finished the role review.
3. Register for the November 17 webinar and bring two questions: when Anthropic will publish plugin pricing, and how the solutions page's "does not write to systems of record" squares with the README's read-and-write NetSuite connector.

This Month:

1. Run quote-build on ten jobs you have already quoted by hand and compare the totals line by line. Record where it fell back to last purchase price.
2. Run ncr-writeup and root-cause-capa on two closed nonconformances and have your quality lead grade the D1 to D5 drafts.
3. If you run Infor Velocity Suite, ask your Infor account team in writing whether you qualify for the Infor plugin, what it costs and which transactions it can execute.

Before Granting Any Write Access:

1. Map every NetSuite record type the Claude role could edit to a named approver. Confirm the approval lands in NetSuite's system notes, not only in the chat.
2. Have your planner review the reorder and scheduling rules that will drive Claude's suggestions, because per-change approval will not catch a bad rule.

The Bottom Line

Claude for Manufacturing is a document-drafting layer over the systems a plant already runs, priced into a seat you may already pay for. Infor M3 plants get a read-only assistant, and NetSuite plants get a connector that can write as far as the role allows. Infor's write plugin goes only to a short customer list. Industrial AI vendors were already competing over who owns plant data when we covered Schneider's Cognite deal in July. In this product, the ERP role your administrator creates decides what Claude may change, and Anthropic's plugin adds an approval prompt on top.

Create the read-only NetSuite role before anyone installs the plugin.

Continue Reading

• Human-in-the-Loop for AI Agents: Most Approval Gates Rubber-Stamp
• Toyota Ships an Agent in 4 Days. One Review Covers 50.
• Infor + AWS: 50% Cost Cuts With Manufacturing AI Agents
• 4 Instruments, 8 Hours. The Weeks Were Your Change Control.
• Your Claude Enterprise DLP Hooks May Let Unchecked Prompts Through
• Claude Data Turns On for Enterprise Plans November 19