Why matching commercial vehicle OEM part numbers in SQL is messy (and how we open-sourced our parser)

说明与用途

在汽车行业，同一 OEM 零件编号以多种格式出现，导致 SQL 匹配不可靠。开源 TypeScript 库 @crazypartsnatcher/oem-normalizer 通过规范化编号、生成搜索变体并检测制造商格式，提升匹配准确性。

问题

Inconsistent OEM and OES part numbers across supplier feeds make SQL matching unreliable, causing missed offers in a commercial vehicle price comparison engine.

结果

The open‑source normalizer library resolved the part number mismatch issue, enabling accurate matching across supplier feeds and improving the reliability of the price comparison engine.

工作流

• 1. Install the package via npm: npm install @crazypartsnatcher/oem-normalizer
• 2. Import functions in Node.js/TypeScript: import { normalizeOem, generateSearchVariants, detectManufacturerFormat, buildPartSearchUrl } from '@crazypartsnatcher/oem-normalizer';
• 3. Normalize raw input: const cleanKey = normalizeOem(rawInput);
• 4. Generate search variants: const variants = generateSearchVariants(rawInput);
• 5. Detect manufacturer format: const formats = detectManufacturerFormat(rawInput);
• 6. Build comparison URL: const comparisonUrl = buildPartSearchUrl(cleanKey);
• 7. Use normalized key for SQL/MariaDB lookups and variants for fuzzy search queries.

证据

When building an automotive or commercial vehicle price comparison engine, the biggest data bottleneck isn't scraping or API rate limits—it's inconsistent OEM and OES part numbers across different supplier feeds.

来源

We extracted it into a lightweight, zero-dependency TypeScript/JavaScript package and published it on npm and GitHub.

来源

It handles four core tasks out of the box: normalizeOem, generateSearchVariants, detectManufacturerFormat, buildPartSearchUrl.

来源

Install via npm: npm install @crazypartsnatcher/oem-normalizer

来源