What Intake does with a bill of materials, what it refuses to do, and where the line between the two falls.
Intake is Adesio’s front door, for electronics manufacturing services (EMS) companies and their engineering and purchasing teams. You drop a bill of materials — Cadence .ebom, CSV, Excel, PDF with a text layer — and Intake recognises its format, reads it line by line, and reports what the file states: what can go to matching as it stands, and what still needs a decision.
Four doors, one product: the app, the command line, the HTTP API and the Claude connector read the same file the same way and produce the same canonical document.
No, and that is a choice. During an analysis no line is sent to an aggregator or a distributor. A part number reported as found means the file states it unambiguously, or that an operator confirmed it; a single uncertain candidate stays ambiguous.
Matching, quotation and procurement happen downstream, inside Adesio, on the part number Intake has made clean. Intake also counts what that step will cost: the DISTINCT parts to be looked up, never the number of lines.
Intake does not give you an opinion, it makes your file readable. Every status, category, value and package carries the basis it was established on: a column, a documented position in the description, or a person. That is what lets you contest a conclusion rather than believe it.
Anything that does not come from the file is badged as inferred. Before any decision, check critical information against the manufacturer’s datasheet.
Cadence .ebom exports, CSV files and Excel workbooks, including those whose header does not start on the first row, and files exported from an ERP. A PDF is accepted if it carries a text layer: Intake recovers the table geometry from it.
A scan with no text layer is refused, with the reason. Intake will never run optical character recognition: a character invented inside a part number is the worst error this pipeline can make.
Three outcomes. The line states one unambiguous manufacturer part number: it is resolved, and the report says on what basis. It describes a component by its characteristics — a value and a package — and becomes a matchable generic, ready for a search. Or the file does not say enough, and it goes to the review queue.
You can correct the reading — encoding, sheet, header row, a column’s role — and have the same bytes read again. What an operator settles can be saved as a reusable format, so the next file from the same exporter is read correctly from the start.
You can drop it, but it will not be reported as resolved. Every manufacturer has its own numbering logic, and a partial reference produces uncertain matches, or wrong ones.
Give the most complete reference you can. Failing that, the description is often enough: value and package make a parametric search, and Intake exports the list of searches to run, deduplicated.
No. It is work remaining, not a failure: Adesio resolves downstream what Intake could not settle. The review queue groups lines by PART rather than by line, and one confirmation answers the same part in the next bill of materials.
The detail is on the Security page: what stays private, what is pooled across clients, and why. In short, your files, your reports and your links stay yours; only universal facts — a part number, a manufacturer, the structure of a format — are pooled.
This instance is a demonstration: do not drop a confidential bill of materials on it.
A recent version of one of the following browsers:
An old or unsupported browser may behave unpredictably and keep you from reaching some features. The pages render without JavaScript; dropping a file and the decision buttons need it.
Not finding your answer? Write to contact@adesio.io. What becomes of your file is set out on the Security page; the terms of use are on the Legal notice page.