FOR PARTS STORES · CMS · ERP

Check orders by VIN — OEM and aftermarket parts

Reduce repetitive checks for your managers. Your CMS/ERP supplies the order VIN and OEM numbers, including cross-references for aftermarket parts; the Vinalfa API helps check them against vehicle catalog data.

Less routine work, more attention to customers

Reduce managers’ workload

The integration handles repeatable checks. Managers review items without confirmation and ambiguous results.

One workflow for different parts

An order can contain OEM and aftermarket parts. For aftermarket items, use OEM numbers from your CMS/ERP cross-references.

Offer related parts

Diagrams reveal nearby components and help propose a complete repair set. This creates opportunities for additional items and a higher basket value.

How an order check works

One order VIN, every supplied OEM candidate, and a clear result for each line.

  1. Read the order

    The CMS/ERP provides the VIN and each line’s part number and brand.

  2. Resolve OEM and aftermarket items

    For aftermarket parts, the CMS/ERP supplies OEM cross-references. The integration processes every available OEM candidate from those references, not just the first number.

  3. Check OEM numbers against the VIN

    The integration calls Vinalfa with the OEM part number, OEM brand and VIN to retrieve available catalog results and diagrams.

  4. Return results to the manager

    Group responses by order line. Separate catalog-confirmed results from items with insufficient data or those requiring manual review.

Aftermarket → OEM cross-references come from the client’s CMS/ERP. Vinalfa checks the supplied OEM numbers against catalog data; a cross-reference database is not automatically included in this integration.

A button, an event or cron

“Check order” button

The manager starts a check from the order screen and receives results for its lines.

A CMS/ERP event

Start a background job when an order is created, a VIN is added or its items change.

Scheduled cron

Check an order queue automatically on a schedule. Account for API limits, retries and changed items.

An integrator configures the button, event handlers, queue and cron in the client’s CMS/ERP. This is a server-side integration workflow, not a ready-made order-check button in the published widget modules.

70–80%

of popular vehicles in the global market — Vinalfa coverage estimate

1.5 billion+

VINs in the Vinalfa information system

According to Vinalfa as of 24 October 2026. Estimated coverage is 70–80% and varies by make, model, year, specification and region. The system keeps evolving; validate your own vehicle sample before integration.

Open diagrams with a link

With the order VIN

https://vinalfa.com/original-catalogs/?vin={vin}&article={article}&brand={brand}

Without a VIN — by part number and brand

https://vinalfa.com/original-catalogs/?article={article}&brand={brand}

Replace placeholders and URL-encode their values. For an aftermarket part, use the corresponding OEM number and OEM brand from CMS/ERP cross-references. A link opens the catalog; it does not replace a server-side check of the entire order.

Find diagrams and build a complete order

An OEM number or the OEM cross-reference of an aftermarket part can locate available diagrams even without a VIN and reveal related items. This helps offer fasteners, seals and nearby parts for the repair. Without a VIN, a diagram alone does not confirm fitment to the customer’s vehicle; some catalogs require a VIN.

Results that support a decision

Found for the VIN

A catalog result exists for the supplied OEM number and vehicle; open the part details and diagram.

Not confirmed

No result or insufficient data. This does not automatically mean the part does not fit.

Manager review required

Ambiguous references, multiple variants, catalog restrictions or access errors need review.

Connect through the server API

Your CMS/ERP iterates OEM candidates, calls documented API methods and combines responses into order results. Keep the server Bearer token on the backend. Method access and results depend on the subscription and catalog.

Example request for one OEM candidate supplied by the CMS/ERP
POST https://api.vinalfa.com/oem/v2/article-schemes/search
Content-Type: application/json
Authorization: Bearer YOUR_SERVER_API_TOKEN

{
  "article": "OEM_NUMBER_FROM_CMS",
  "brand": "OEM_BRAND",
  "vin": "VIN_FROM_ORDER"
}

Start with a known order

Use a familiar VIN and several OEM and aftermarket items with cross-references from your system. Validate the results with a manager, then configure automated runs. Trial: 5 days and 10 VINs.

Start Trial