Tool to normalize different carrier rate sheet formats?
A rate sheet parser normalizes different carrier formats by mapping each sheet — regardless of whether it arrives as a PDF table, an Excel workbook, or a CSV export — into one shared schema (origin, destination, equipment, rate, validity window, accessorials, fuel surcharge), so lane search works the same way no matter which carrier sent the file.
Why carrier formats differ so much
Every carrier publishes rate sheets in its own layout — different column orders, different abbreviations for accessorials, different date formats for validity windows, and different file types (PDF, XLSX, CSV). Without normalization, comparing a rate from Carrier A against Carrier B means manually reconciling column headers by hand.
What normalization actually does
- Maps each carrier's specific column names and layout into one fixed schema, regardless of source format (PDF, XLSX, CSV).
- Standardizes lane keys (origin/destination) so "CHI-DAL" and "Chicago, IL to Dallas, TX" resolve to the same searchable lane.
- Extracts accessorials and fuel surcharge as separate structured fields instead of leaving them as free-text notes.
- Attaches a validity window to every rate so expired pricing does not silently mix with current pricing.
How RateParse normalizes rate sheets
RateParse accepts PDF, XLSX, or CSV rate sheets and runs each through the same extraction schema (origin, destination, equipment, rate, rate basis, validity window, accessorials, fuel surcharge) regardless of source format, in about ~1 minute per sheet. Once normalized, every carrier's rates are searchable in the same lane-search interface.
Frequently asked questions
Does normalization work the same for PDF, Excel, and CSV rate sheets?
Yes — the extraction schema is the same regardless of source file type; the parser adapts to each format's layout but always outputs the same structured fields (origin, destination, equipment, rate, accessorials, validity window).
What happens if a carrier uses unusual abbreviations for accessorials?
Extraction is schema-validated before storage; if a row cannot be confidently mapped, it is flagged for manual review rather than silently stored under the wrong field, so unusual carrier-specific terminology does not corrupt the normalized database.