How it works
Files in. Files out. Nothing in between touches your network.
Every enrichment vendor that needs API access into an ERP dies somewhere in procurement. We designed around that constraint from the start, which is why a Smooshe engagement clears security review as a data-handling question rather than an architecture review.
The constraint
Enterprise IT will not give you a key. Stop asking for one.
Mid-market industrial IT teams are small, overloaded, and correctly paranoid. A vendor requesting read access to the ERP is a six-month conversation with a coin-flip outcome. A vendor requesting a spreadsheet is a Tuesday.
What crosses the boundary
A file you exported, or the public pages you already publish. Nothing else. You choose what is in the export and you can redact anything before sending it.
What never happens
No VPN account. No service account. No API credential. No software installed on a machine you own. No process running inside your perimeter.
What comes back
A structured file in your platform’s import format, plus a review sheet. Your team imports it on your schedule, after your review, into your system.
The enrichment pipeline
Four agents, four jobs, one guardrail at the end
A single model asked to write a product description will happily invent a temperature rating that reads perfectly and is wrong. Splitting the work is what makes the output safe to publish.
- 01
Spec extractor
Pulls every attribute the source actually contains
Parses ERP columns, cut sheets, scraped tables and free-text descriptions into a normalised attribute set. Units are converted and reconciled; conflicting values between sources are flagged rather than silently resolved. Nothing downstream sees the raw source again.
- 02
Standards injector
Attaches the governing standards and category logic
Looks the extracted attributes up against the category knowledge graph — materials, compatibility envelopes, and the API, ASME, ANSI, NACE, ISO or NEMA standards that apply to that part class. Compliance is never inferred: a standard appears only when the source establishes it.
- 03
Description writer
Renders copy from confirmed data only
Writes for the persona the channel needs — a specifying engineer, a procurement buyer, an MRO tech. Because the writer only receives the confirmed attribute set, it structurally cannot invent a pressure rating. Every sentence traces back to a spec, a standard, or an application constraint.
- 04
Validation guard
Rejects fluff and unsupported claims
Hard block list on marketing adjectives with no measurable referent. Cross-checks every numeric claim against the extracted set. Anything a specifier needs that the source never provided is surfaced as an explicit gap for your SME instead of being smoothed over.
Your engineers stay in the loop, and their corrections stick. Every SME edit feeds a category feedback corpus that reshapes later batches. Batch ten is measurably better than batch one, and that accumulated judgement stays attached to your catalog rather than evaporating when a contractor rolls off.
Formats
We meet the stack you already run
Enrichment happens once against a normalised record. Output rendering is the cheap part, so the format your platform wants is not a negotiation.
Inbound
Outbound