Try the demo — no signup
Menu
Products
BOM Health CheckCheck a single export for data quality issuesBOM CompareCompare revised BOMs and material exportsMaterial DeltaEstimate the cost impact of revision changesPrice DeltaTrack price movement, quote exposure, and approved alternate pricingQuote CompareValidate supplier quotes against your BOM
Solutions
PrefabricationVDC / BIMProcurementMechanical & FPDistributionNew
Pricing
Resources
Sample reportsBuyer packetSecuritySupport
Log inTry the demo — no signup
Support home

Files and columns

Column mapping explained

Understand how Partrek detects part number, quantity, unit, price, supplier, and category columns.

Anyone reviewing detected columnsUpdated May 10, 2026

Common questions this answers

  • What if the detected column is wrong?
  • What columns are required?
  • Can I save mappings for later?

Required columns depend on the workflow

  • BOM Health Check usually needs part number and quantity to produce useful diagnostics.
  • BOM Compare needs quantity on both original and revised files, plus either part-number identity or description identity.
  • Quote Compare needs a BOM/buyout part number and a quote part number, plus quantity when you want quantity mismatch checks.
  • Price Delta needs an identifier column and price column on the compared price sources.

Description-only comparison

If a BOM has no part codes, Partrek can compare by exact normalized descriptions. This is useful for messy exports, but it is review-first: generic descriptions, unit changes, and duplicate descriptions with different source part numbers are flagged before the report is trusted.

If detection is wrong

Open the mapping controls and select the correct column manually. Partrek shows low-confidence and ambiguous matches so a human can confirm before the report is trusted.

Saved profiles

Signed-in workspaces can save repeat import profiles when the plan allows it. Profiles store mappings and settings, not raw source rows or uploaded files by default.