Skip to content

Claude for Manufacturing and NetSuite: What It Reads and What It Can Write ​

Anthropic released Claude for Manufacturing in the week of November 12, 2026, and Oracle NetSuite is one of the four systems it connects to. The plugin reads from an ERP and drafts the documents a plant already produces: quotes, nonconformance reports, 8Ds, production reports.

I installed it and read every skill it ships with, alongside the published documentation on both sides. One detail in there matters more than the feature list, so it goes first.

This article is the documented version: what the plugin is built to do, and what the published material on both sides actually says. A second article follows it with the results of running the thing against a NetSuite manufacturing account.

I have no affiliation with Anthropic, and nobody paid for this article.

What is Claude for Manufacturing? Claude for Manufacturing is a plugin for Claude rather than a separate product. It adds seventeen skills covering quoting, quality, maintenance, production reporting, sourcing and design, plus connectors for Microsoft 365, Oracle NetSuite, Infor M3 and Autodesk Fusion. It reads your data and drafts documents for a person to review. Anthropic states that it does not run production control, operate equipment, or write to your systems of record.

NetSuite Is the One Connector Documented as Writable ​

The Claude for Manufacturing product page is unambiguous. It says Claude drafts documents for your team to review, and that it does not run production control, operate equipment, or write to your systems of record.

The plugin documentation describes the four connectors one at a time, and it does not say the same thing.

ConnectorWhat the plugin documentation says
Microsoft 365"read-only by default"
Infor M3"The plugin only reads from it"
Autodesk Fusionthe only connector the plugin declares itself, at a local address
Oracle NetSuite"Read and write; the sign-in picks your account, so there is no account ID to enter here"

Two ERP options, and a plant connects one. Pick Infor M3 and the plugin reads. Pick NetSuite and the same documentation grants it read and write.

This is not a case of one vendor contradicting another. Both statements are Anthropic's, published the same week, about the same plugin.

The plugin side does not leave the write path unguarded. Its documentation states that every skill which would change something pauses first, and that nothing is applied, sent or written to your systems without your say-so. One chain is called out as the exception, and the reason given is that it writes to no system of record at all. So the design is a gated write rather than an open one, and the gate is described consistently.

What the product page does is omit the capability. A manufacturer who reads the marketing copy, concludes that nothing can reach the ERP, and skips the role conversation has been told something that the plugin documentation does not support.

The Role Decides What a Write Could Reach ​

The plugin has no NetSuite integration of its own. It uses the Oracle NetSuite connector you enable in Claude, which runs on Oracle's NetSuite AI Connector Service, the same MCP connection any Claude user can set up today.

That matters because the standard tools on that connection include record create, update and transform, plus record actions. The approval gate in the plugin is a property of the skills. The permissions on the connection are a property of your NetSuite role. If the role a user signs in with can create item receipts, edit work orders or post adjustments, that is the real boundary, and it holds whether or not a skill chose to pause.

Two controls sit above it. On Team and Enterprise plans, Anthropic states that owners can require approval before a connector changes anything, or block changes entirely. That is a setting somebody has to turn on. And Oracle states that the AI Connector does not support Administrator roles, so there is a floor under how much any connection can reach, though a floor is not the same as a design.

So a manufacturer turning this on has three decisions, and none of them is technical:

  • Which role each Claude user connects with, and whether that role can create or edit transactions at all.
  • Whether the Claude workspace requires approval for connector changes.
  • Who reviews a drafted quote, NCR or production report before it leaves the building.

This is the principle NetSuite has always run on. The role is the control. AI does not change that, and it does make it easier to forget.

What Is in the Plugin ​

Seventeen skills. Twelve do a single job, and five are chains that run several of those jobs in order with approval points between them.

AreaSkillsWhat they produce
Setup and dataOnboarding, Data Consolidate, Custom ConnectorA plant profile, a joined dataset from your ERP and export files, and a path for systems with no connector
Sales and quotingCustomer Inquiry Intake, Quote Build, RFQ to Quote (chain)An intake from a customer RFQ, a bid or no-bid call, and a quote with every number traced to its source
QualityNCR Writeup, Root Cause and CAPA, Inspection to CAPA (chain)Nonconformance reports, ranked candidate causes with the evidence for and against each, and 8D drafts
OperationsDaily Production Report, Breakdown Diagnosis, Morning Plant Pulse (chain), Breakdown to Next Report (chain)Output against plan, OEE, ranked downtime, priced scrap, and ranked likely causes for a machine failure
Supply chainSupplier Quote Request, Supplier Escape to Alternate Source (chain)RFQ packages for suppliers, bid comparisons, and a sourcing action when a supplier causes a defect
DesignDesign Space Explore, Trade Study ReportCAD variants in Autodesk Fusion and a scored comparison with a sensitivity check

A few choices in the build are worth noticing. The quality skills label an unconfirmed root cause as not validated and propose the cheapest test that would separate the candidates. The quoting skills trace material cost to a named purchase order and machine hours to a stated basis, such as the current routing or actual hours on closed jobs. The design skills save a variant as a new document rather than touching the original.

One caveat belongs with all of this. The published implementation carries a maintenance status of "Reference implementation. Not actively maintained or monitored, and not accepting contributions," provided as is and without warranty. Version 1.0.0. That is a reasonable way to ship a first release, and it is also a specific thing to know before a plant builds a quoting process on top of it.

What NetSuite Data the Plugin Uses ​

The Data Consolidate skill is where NetSuite comes in. It joins ERP records with files from your other systems and keys everything on identifiers a plant already has: part number, production work order, sales order, lot, asset, supplier. From NetSuite it reads items, sales orders, production work orders, purchase orders, inventory, routings, and actual operation times from closed jobs.

When a key fails to match across systems, the skill classifies the mismatch and proposes a correction. Nothing is applied without a yes.

The quoting skills lean on the same data. Material is priced at what you actually paid on a named purchase order. Machine hours come from the current routing or from actual hours on closed jobs, with setup and run time kept separate. The promised date is checked against real shop load. For a manufacturer with clean routings and completed work orders, that is a quote built from your own history rather than from an estimator's memory of the last one.

Which is also where the ERP choice stops being neutral. The plugin documentation states that Infor M3 gives it no standard cost, no quote history and no routings. Those are the three inputs the quoting skills are built on. A plant running M3 gets the quality and maintenance skills with most of the quoting basis missing. A plant running NetSuite is the case the quoting skills were designed for.

Two limits come from NetSuite rather than from Claude:

  • Your enabled features decide what it can see. Bill of materials revisions, manufacturing routings and work in process transactions are only present when those features are on. Without them the plugin falls back to what it can reach.
  • Some planning records are not exposed. Item demand plans are not available through REST web services, and planned orders exist only as lines on the item supply plan. Anything built around demand planning needs a saved search export or custom work.

Where Oracle's Built-In AI Fits Better ​

Oracle ships its own AI inside NetSuite, and some of it overlaps. Ask Oracle, SuiteSkills and the industry SuiteAgents announced at SuiteWorld in October 2026, including the Product SuiteAgent, cover questions that live entirely inside NetSuite: inventory balances, the inventory effect of a transaction, fulfillment analysis, inventory exposure. They run inside the product and are included with the licence.

A workable division:

  • If the answer lives entirely in NetSuite and Oracle ships a skill or agent for it, start with Oracle's. It is already paid for, and it runs under the role model you already maintain.
  • If the answer needs documents or systems outside NetSuite, such as a customer drawing package, supplier email threads, inspection files, sensor exports or a CAD model, that is the gap this plugin was built for.

Most manufacturers will end up running both, which raises the question of who decides which tool handles which job. One thing to carry across from the NetSuite side: requests through the AI Connector do not consume NetSuite AI Units, so this route does not draw down the pool. How that pool works, and who should own it, is a separate problem with its own owner.

A Setup Checklist for NetSuite Manufacturers ​

None of this needs a project. It needs a handful of decisions made before the first person connects.

Coming Next: Running It Against a Real Account ​

Everything above is what the plugin is documented to do. The next article runs it against a NetSuite manufacturing account to find out what it actually does: which records it reaches with a given role, whether the NetSuite connector behaves as read and write in practice, how a generated quote compares against the NetSuite data it cites, and where it gets things wrong. That one will carry the numbers.

Who Should Own This ​

The plugin is a careful piece of work in a narrow lane. It reads, joins and drafts around production work, it shows its evidence, and it stops before it commits anything. The NetSuite side of it is only ever as good as the data and the role you hand it.

Which is the part your implementation partner did not set up, because none of this existed when you went live. Role design that was reasonable for a person running searches is a different question once the same credentials sit behind a connector that is documented as writable. If you are weighing this up and want an independent read of the role design, the data and the approval settings before the first person signs in, a NetSuite Health Check is where that work starts.

Frequently Asked Questions ​

Does Claude for Manufacturing work with NetSuite? ​

Yes. Oracle NetSuite is one of four connectors and one of the two ERP options, and a plant connects one ERP. The plugin ships no NetSuite integration of its own. It uses the Oracle NetSuite connector enabled in Claude, which runs on the NetSuite AI Connector Service.

Can Claude for Manufacturing change records in NetSuite? ​

The Claude for Manufacturing product page states that the plugin does not write to systems of record. The plugin documentation describes the Oracle NetSuite connector as read and write, and describes Infor M3 as reading only. Both statements come from Anthropic. The practical limit is the NetSuite role a user signs in with, because that role decides what any write could reach.

What does Claude for Manufacturing cost for NetSuite customers? ​

There is no separate price for the plugin. Anthropic lists it as available on paid plans, including Enterprise purchased through AWS Marketplace. On the NetSuite side, Oracle states that the AI Connector Service is not a paid feature and that the MCP Standard Tools SuiteApp is free.

Does Claude use NetSuite AI Units? ​

No. Oracle puts external AI clients reaching the account through the AI Connector Service outside the AI Unit meter, because the model itself runs outside NetSuite. Your Claude plan carries that cost in its place.

Can I connect Claude to NetSuite with the Administrator role? ​

No. Oracle states that the NetSuite AI Connector Service does not support Administrator roles. Every request runs with the permissions of the role the user connected with, which is why role design is the control that matters here.

Do I need Advanced Bill of Materials or WIP for the plugin to work? ​

No, but the features enabled in your account decide what it can see. Bill of materials revisions, manufacturing routings and work in process transactions are only present when those features are on. Without them the plugin works from the records it can reach, such as items, work orders, purchase orders and inventory.

Need help with NetSuite?

A connector documented as writable, pointed at the system your plant runs on, is a role design question before it is an AI question. Reviewing which role your people would connect with, and what it can reach today, is worth doing before the first person signs in rather than after.

Patrick Olson - LinkedIn ProfileBy: Patrick Olson 11/16/2026

Read Next - NetSuite AI Unit Monitoring: The Tools and the Gaps

Last updated:

NetSuite Implementation Advisory & Administration