+86-18576679965
Product Updates

Smarter BOM Matching and Excel Upload at Restar

Smarter BOM Matching and Excel Upload at Restar

Introducing Smarter BOM Matching at Restar

Restar (瑞洋芯电) has enhanced its BOM ingestion pipeline so procurement teams can upload Excel or CSV bill-of-materials files and receive ranked match results against our franchise inventory and factory-backed channels for Texas Instruments, Analog Devices, Vishay, and partner lines listed on our manufacturers page.

The matcher is built for real-world BOM chaos: merged cells, duplicate MPNs with different QPA, legacy Linear Technology numbers sitting beside modern ADI prefixes, and customer descriptions like "U3 LDO 3V3" without a manufacturer. Instead of failing silently, the engine returns match confidence, suggested corrections, and deep links into categoryAll parametric search.

This article walks through column mapping, duplicate resolution, alternate ranking, and how to push a reviewed BOM directly into the RFQ workflow for consolidated pricing.

Supported File Formats and Column Mapping

Upload .xlsx, .xls, or .csv up to 10 MB per session. The first row should contain headers; the parser auto-detects common synonyms: "Part Number", "MPN", "Item", "Manufacturer Part", "Mfr", "Brand", "Qty", "Quantity", "Required", "Description", "Reference", "Designator".

Minimum viable BOM: MPN + quantity. Manufacturer name strongly improves match accuracy when MPN prefixes collide across vendors (e.g., generic "LM317" listings vs TI-branded devices). Optional columns—target_price, need_by_date, alternate_allowed—flow into RFQ without retyping.

For passive arrays such as the WSBR8536L0500JKA4 shunt resistor network family, include resistance value, tolerance, power rating, and TCR when your MPN is incomplete; the matcher uses parametric tables from Vishay and other franchise suppliers to propose exact catalog hits.

Match Confidence Levels Explained

Exact match: MPN and manufacturer align with a franchise SKU in Restar systems, including suffix rules (RoHS, G4, tape width).

Normalized match: Parser stripped packaging suffixes or fixed common typos (O vs 0, missing hyphens) and found a single candidate.

Multi-candidate: Several valid MPNs share the typed string; you must pick one before RFQ export.

Unresolved: No franchise hit; Restar may still broker through authorized distributor networks but flags the line for manual research rather than quoting grey-market sources.

Example Match Report

LineInput MPNResultConfidenceAction
12TPS62840DLCRTI buck regulatorExactAdd to RFQ
27LT3042ADI LDONormalizedConfirm suffix
4110K06033 Vishay candidatesMultiSelect RN73H

Duplicate Lines and Consolidation Rules

Duplicate MPNs on separate designators consolidate quantity unless you mark "do_not_merge" in a notes column—useful when the same part appears in electrically distinct depopulated variants.

Alternate groups: define "primary_mpn" and "alternate_mpn_list" columns or use Restar template tab "AltGroup". RFQ quotes primary first; alternates priced only when requested, saving quote churn on approved A/B lists.

Blanket vs line-specific quantities: if your ERP exports one row per board and you build 5,000 boards, either pre-multiply QPA or use the "board_qty" column so Restar computes extended demand correctly.

From Match Results to RFQ and Solutions

After review, click "Export to RFQ" to carry matched lines, quantities, and your notes into the quoting form. Unresolved lines remain attached as PDF appendix for sales engineering follow-up within one business day.

Cross-link application content: if a BOM block matches a reference design in our solutions hub, the UI surfaces related notes (e.g., PMIC sequencing, RF front-end bias networks) to validate that passive values were not copied from a different frequency plan.

Subscribe via news for matcher release notes—monthly updates add manufacturer-specific alias packs and improve recognition of automotive grade suffixes.

Best Practices for Excel BOM Hygiene

Freeze MPN column as text before CSV export to prevent scientific notation corruption on long numeric-looking TI orderable numbers.

Remove conditional formatting and macros; upload clean data sheets only.

Split mechanical BOMs from electrical BOMs when requesting component quotes to avoid false matches on screws and heatsinks.

Version your file name with date and ECN (e.g., BOM_PWR_RevC_20260711.xlsx) so Restar ties quotes to the correct revision.

Security and Data Handling

Uploaded BOMs transmit over TLS and reside on Restar quote servers with access restricted to assigned account teams. We do not resell BOM intelligence or share your design content with unrelated customers.

You may request deletion of quote artifacts after PO closure; retention defaults follow your master supply agreement if one exists.

Why BOM Matching Beats Manual Search

Manual line-by-line search on distributor sites consumes hours and still misses suffix rules. Restar matching encodes franchise SKU logic once, then scales across hundreds of lines.

Integrated RFQ means one email thread, one quote document, one shipment coordination point—critical when TI allocation letters arrive mid-build and you must pivot to ADI cross references quickly.

Start an upload today via RFQ, validate franchise coverage on manufacturers, and drill into parametrics on categoryAll.

Extended Guidance

Matcher performance improves when manufacturers release new alias packs; Restar imports these monthly without requiring customer software installs—re-upload stale BOMs quarterly to catch new mappings.

Enterprise customers may request SFTP drop zones for automated BOM diff between PLM releases; contact sales for integration scopes separate from standard Excel upload.

Optional script exports unmatched lines as JIRA CSV for engineering ticket tracking—reducing email ping-pong on typos.

Case study: a 640-line industrial control BOM uploaded with manufacturer column achieved 94% exact match on first pass; remaining lines were multi-candidate passives resolved in 15 minutes by selecting Vishay RN series consistently.

Passive manufacturer part numbers encode resistance only partially—always confirm power and TCR columns to avoid 0603 lines resolving to wrong wattage.

After RFQ export, maintain a read-only copy of the matched BOM in PLM as Restar_validated attachment for downstream CM access.

Unicode and special characters in descriptions can break CSV parsers—use UTF-8 with BOM when exporting from Excel on Windows procurement laptops.

Restar matcher logs revision IDs; include ECN in upload filename so support can trace which PLM release produced ambiguous passive lines.

Matcher performance improves when manufacturers release new alias packs; Restar imports these monthly without requiring customer software installs—re-upload stale BOMs quarterly to catch new mappings.

Enterprise customers may request SFTP drop zones for automated BOM diff between PLM releases; contact sales for integration scopes separate from standard Excel upload.

Optional script exports unmatched lines as JIRA CSV for engineering ticket tracking—reducing email ping-pong on typos.

Case study: a 640-line industrial control BOM uploaded with manufacturer column achieved 94% exact match on first pass; remaining lines were multi-candidate passives resolved in 15 minutes by selecting Vishay RN series consistently.

Passive manufacturer part numbers encode resistance only partially—always confirm power and TCR columns to avoid 0603 lines resolving to wrong wattage.

After RFQ export, maintain a read-only copy of the matched BOM in PLM as Restar_validated attachment for downstream CM access.

Unicode and special characters in descriptions can break CSV parsers—use UTF-8 with BOM when exporting from Excel on Windows procurement laptops.

Restar matcher logs revision IDs; include ECN in upload filename so support can trace which PLM release produced ambiguous passive lines.

Matcher performance improves when manufacturers release new alias packs; Restar imports these monthly without requiring customer software installs—re-upload stale BOMs quarterly to catch new mappings.

Enterprise customers may request SFTP drop zones for automated BOM diff between PLM releases; contact sales for integration scopes separate from standard Excel upload.

Optional script exports unmatched lines as JIRA CSV for engineering ticket tracking—reducing email ping-pong on typos.

Case study: a 640-line industrial control BOM uploaded with manufacturer column achieved 94% exact match on first pass; remaining lines were multi-candidate passives resolved in 15 minutes by selecting Vishay RN series consistently.

Passive manufacturer part numbers encode resistance only partially—always confirm power and TCR columns to avoid 0603 lines resolving to wrong wattage.

After RFQ export, maintain a read-only copy of the matched BOM in PLM as Restar_validated attachment for downstream CM access.

Unicode and special characters in descriptions can break CSV parsers—use UTF-8 with BOM when exporting from Excel on Windows procurement laptops.

Restar matcher logs revision IDs; include ECN in upload filename so support can trace which PLM release produced ambiguous passive lines.

Matcher performance improves when manufacturers release new alias packs; Restar imports these monthly without requiring customer software installs—re-upload stale BOMs quarterly to catch new mappings.

Enterprise customers may request SFTP drop zones for automated BOM diff between PLM releases; contact sales for integration scopes separate from standard Excel upload.

Optional script exports unmatched lines as JIRA CSV for engineering ticket tracking—reducing email ping-pong on typos.

Case study: a 640-line industrial control BOM uploaded with manufacturer column achieved 94% exact match on first pass; remaining lines were multi-candidate passives resolved in 15 minutes by selecting Vishay RN series consistently.

Passive manufacturer part numbers encode resistance only partially—always confirm power and TCR columns to avoid 0603 lines resolving to wrong wattage.

After RFQ export, maintain a read-only copy of the matched BOM in PLM as Restar_validated attachment for downstream CM access.

Unicode and special characters in descriptions can break CSV parsers—use UTF-8 with BOM when exporting from Excel on Windows procurement laptops.

Restar matcher logs revision IDs; include ECN in upload filename so support can trace which PLM release produced ambiguous passive lines.

Matcher performance improves when manufacturers release new alias packs; Restar imports these monthly without requiring customer software installs—re-upload stale BOMs quarterly to catch new mappings.

Enterprise customers may request SFTP drop zones for automated BOM diff between PLM releases; contact sales for integration scopes separate from standard Excel upload.

Optional script exports unmatched lines as JIRA CSV for engineering ticket tracking—reducing email ping-pong on typos.

Case study: a 640-line industrial control BOM uploaded with manufacturer column achieved 94% exact match on first pass; remaining lines were multi-candidate passives resolved in 15 minutes by selecting Vishay RN series consistently.

Passive manufacturer part numbers encode resistance only partially—always confirm power and TCR columns to avoid 0603 lines resolving to wrong wattage.

After RFQ export, maintain a read-only copy of the matched BOM in PLM as Restar_validated attachment for downstream CM access.

Unicode and special characters in descriptions can break CSV parsers—use UTF-8 with BOM when exporting from Excel on Windows procurement laptops.

Restar matcher logs revision IDs; include ECN in upload filename so support can trace which PLM release produced ambiguous passive lines.

Matcher performance improves when manufacturers release new alias packs; Restar imports these monthly without requiring customer software installs—re-upload stale BOMs quarterly to catch new mappings.

Enterprise customers may request SFTP drop zones for automated BOM diff between PLM releases; contact sales for integration scopes separate from standard Excel upload.

Optional script exports unmatched lines as JIRA CSV for engineering ticket tracking—reducing email ping-pong on typos.

Case study: a 640-line industrial control BOM uploaded with manufacturer column achieved 94% exact match on first pass; remaining lines were multi-candidate passives resolved in 15 minutes by selecting Vishay RN series consistently.

Passive manufacturer part numbers encode resistance only partially—always confirm power and TCR columns to avoid 0603 lines resolving to wrong wattage.

After RFQ export, maintain a read-only copy of the matched BOM in PLM as Restar_validated attachment for downstream CM access.

Need Components?

Get a quote within 24 hours

Request Quote
← Back to News

RFQ List

Submit RFQ