← Back to library

Join plant exports and ERP data, with mismatches explained

Anthropic's Claude for Manufacturing plugin, released November 12, 2026, includes a skill that builds one working dataset from a plant's scheduled file exports and its ERP and maintenance systems. It checks freshness first, explains every unmatched record with a suggested correction and outputs a spreadsheet plus a data quality report. We explain how to use it.

  • OutcomeUse the data-consolidate skill from Anthropic's Claude for Manufacturing plugin to identify each export file, check that every source covers the same dates before joining, pull matching ERP and maintenance records, normalize part and order numbers with a log of every rule applied, sort every record that fails to match into a named class with a proposed fix, and apply nothing without your yes.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditanthropics
View original
Works with
ClaudeClaude CoworkClaude Code

Published Nov 17, 2026Updated Nov 17, 2026AI dry run on sample input: passed Nov 17, 2026Source verified Nov 17, 2026

When should you use it?

  • Production, quality and maintenance numbers live in separate exports that never quite agree
  • Someone asks why totals from the shop floor and the ERP do not match
  • You want reports or quotes built from one checked dataset instead of raw files

Not for: Live sensor traces or high-frequency machine data; the skill does not carry them; Writing corrections back to the ERP automatically; it proposes fixes and waits for approval; Businesses with a single system of record, where there is nothing to join

What do you need, and what do you get?

You need

  • The folder where your MES, quality, maintenance and planning exports land
  • Optional ERP access (the skill's examples are NetSuite and Infor M3) and a maintenance system connector
  • A date window, or the latest export drop, and someone who can approve proposed fixes

You get

  • A spreadsheet dataset joined on part, work order, sales order, lot and asset, keeping original spellings
  • A data quality report with freshness per source, rows in versus rows joined and mismatches by class
  • A proposed correction for each mismatch class, with how many records it would fix
  • A reconciled figures block so every count in the report adds up

How does it work, step by step?

  1. Install the pluginAdd Claude for Manufacturing from the Claude plugin directory and complete its plant setup so it knows your export folder.
  2. Request the datasetName the period you need, such as the previous calendar month, or let it work from the latest export drop.
  3. Read the freshness bannerBefore any figures, check each source's date coverage. If windows only partly overlap, choose whether to narrow or wait for new exports.
  4. Review mismatch classesGo through each class, its example rows and the fix it proposes, and approve only the fixes you understand.
  5. Feed downstream workPoint your reports and quotes at the consolidated dataset rather than the raw files.

The prompt

Our adapted version, written to work in Claude, Claude Cowork and Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
Combine {export_folder} with ERP records for {date_window} into one dataset.
Before joining, tell me each source's last refresh and the dates it covers; if they do not line up, stop and give me the options.
Match on part, work order, sales order, lot and asset, keep the original spellings, and log every cleanup rule you apply.
Group every record that fails to match by cause, propose a fix with how many rows it would resolve, and change nothing until I approve each group.

The original skill is published by anthropics on GitHub (anthropics/claude-plugins-official). Open it there to install or import it; the prompt above is our own adaptation.

What can go wrong?

  • Joining stale exports. If one file is weeks old, the mismatches are manufactured; let the freshness check stop the run.
  • Giving a blanket yes. Approve each mismatch class after seeing its rule and examples, not all at once.
  • Leaving the plant scope unset. Without it, item counts can include parts from other sites or subsidiaries.
  • Anthropic labels the plugin a reference implementation it does not actively maintain, so have your operations or IT lead review the setup.

Our take

Plenty of AI reporting demos assume clean, connected data, but most small and mid-sized plants run on scheduled exports dropped into a shared folder. This skill starts from that reality and treats file-only as the normal case. Its most useful habit is checking freshness before joining anything: if two sources cover different weeks, it says so and offers two named choices instead of quietly producing a dataset full of false mismatches. We also like that it never stops at a count. Every unmatched record lands in a named class with a proposed correction and the number of rows that correction would fix, and nothing is applied without approval. Keeping the original spelling of every part number next to the normalized one is a small detail that will save floor staff real frustration. The trade-off is setup effort and a manufacturing-specific schema, so it fits plants and job shops far better than general businesses. In our dry run on fictional MES and ERP exports, it caught a two-week freshness gap, grouped revision-suffix and leading-zero mismatches with proposed fixes and waited for approval.

Where the time goes back: Reconciling exports from several plant systems by hand can take a planner or analyst hours every week, and the same key mismatches come back each time. A repeatable join with named mismatch classes and proposed fixes turns that into a short review.

FAQ

Do I need an ERP connector?
No. The skill is designed to run from files alone, connectors alone or both, and says which sources it read.
Will it change records in my systems?
No. It proposes corrections in its report and applies them to the working dataset only after an explicit yes; it does not write back to the ERP.
Who made it and what license does it use?
Anthropic published it in the anthropics/claude-plugins-official repository on GitHub under the Apache 2.0 license.

Source and credit

This playbook is based on work by anthropics. We summarize it and link to it and write our own adapted prompt.

Original
data-consolidate skill (anthropics/claude-plugins-official, Claude for Manufacturing)
Creator
anthropics
Published on
GitHub (anthropics/claude-plugins-official)
Original date
Nov 12, 2026
License
Apache-2.0
Originally for
Claude
AI dry run
Nov 17, 2026: passed. Dry-run tested by our AI test agent on sample input. Freshness before figures, every mismatch explained, approval per class; no live ERP connection or file output in the dry run.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 17, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

The original is licensed under Apache-2.0 by anthropics. Modified: our adapted prompt and summary are our own wording; the original skill {"was unchanged at the source when we snapshotted it (live source later removed)" if src_removed(s) else "is unchanged at the source link"}.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminRoutine✓ AI dry run

Get the plant report ready before the morning meeting

Schedule the morning-plant-pulse skill from Anthropic's Claude for Manufacturing plugin to combine the overnight exports from planning, production and maintenance, compute output against plan, OEE and its three parts, downtime ranked by minutes and by count and the cost of losses, then refresh one operations dashboard per site with 14- and 30-day trends, all without changing any business system.

Credit: anthropics

An afternoon+
Operations & AdminSkill✓ AI dry run

Have Claude fill PDF forms, even ones with no fields

Give Claude the pdf skill so that when you hand it a form and the answers, it first checks whether the file has real form fields, fills those by their IDs if it does, places text by measured coordinates on flat or scanned forms if it does not, validates every box before writing, and renders the filled pages as images so you can see where each answer landed before you sign or send it.

Credit: Anthropic

Minutes
Operations & AdminSkill✓ AI dry run

Price a custom manufacturing job with every cost traced

Use the quote-build skill from Anthropic's Claude for Manufacturing plugin to price a make-to-order job from the intake form, similar past jobs and cost history, citing the purchase order or work order behind each cost, spreading setup across every quantity break, keeping margin on a separate internal line and checking the promised date against shop load, with a person releasing the quote.

Credit: anthropics

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Turn a CSV export into a written report with charts

Upload an export and get back an HTML report that opens with the most useful finding, explains it with charts and ends with recommendations.

Credit: Anthropic

An afternoon+