Skip to main content

Datasheet Library & BOM Import

Enter a part once. Every job after that is retrieval.

Count how many times your company has hunted down the datasheet for the same relay. The library ends that: one company-wide list of the parts you actually use, the right document attached to each, shared by every project.

The shared parts library: one entry per catalog number, documents and last-quoted price attached
A parts library of 32 parts listed by catalog number and manufacturer, such as an ABB ACH580 drive and an Allen-Bradley CompactLogix controller, with datasheet and manual checks and the last quoted price.

Documents live on parts, not projects

A datasheet attaches to the part and every project references it. Files are stored once by their content, so there is no datasheet_FINAL_v3(2) and no wondering which copy is current. A correction made on one job is inherited by the next.

BOM import that shows its work

  • Drop a CSV or XLSX on the register; import runs in the background while you keep working
  • The importer reads every sheet and column before deciding, and asks only when the file is genuinely ambiguous
  • Rows match the parts you already have, even when the spreadsheet spells the manufacturer differently
  • A review screen shows exactly what will change, and nothing imports until you say so

Datasheets found, not hunted

For a part with no datasheet, a document hunt searches the manufacturer's site and the web and shows each find with how it matches: a check when the file prints the catalog number, a circle for a family document. Nothing enters your library until you press Add, and a site that refuses downloads says so, so you can save the file yourself and upload it in seconds.

Attach a datasheet and the part fills in its ratings, such as supply voltage, SCCR, temperatures and listings, each linked to the page it came from. A value that needs a second look waits under Needs a look until you keep or clear it.

A library that stays clean

When two entries name the same part, merge them: datasheets, register items, and pricing history move to the one you keep. Delete parts in bulk, and anything still on a register, quote, or purchase order is skipped with the reason.

Findable when you need it

Search reads inside the library page by page, so a phrase you half remember from a 400-page datasheet opens the matched document at the matched page. The library is not a filing cabinet; it is the memory your packages compile from.

Questions integrators ask

RFI logDatasheet Library & BOM Import
RFI-01

What BOM formats can I import?

CSV and Excel workbooks. The importer reads every sheet, finds your header row, and understands columns such as Manufacture, Part # and PartNumber on its own. It asks only when the file is ambiguous, and nothing changes until you confirm the review screen.

RFI-02

What if the spreadsheet spells a manufacturer differently?

Each name is checked against your manufacturer profiles and the spellings they have learned. Confirm a new spelling once and it links on its own on every later import.

RFI-03

Can I re-import an updated BOM?

Yes. Sync adds what is new and updates what changed without deleting anything. Replace makes the location match the file exactly, and shows how many entries would go before it does.

RFI-04

Are parts shared across projects?

Yes. The library is company-wide, so a datasheet or price recorded on one job is already there on the next.