Make compatibility part of your catalog workflow.

Use a shared fitment engine to enrich wheel listings and support vehicle-based filters across supplier catalogs and business customer portals.

Normalize your supplier data first

Map supplier fields to PCD, diameter, width, ET and DIA before calling the API. FitmentCore works with wheel specifications; it does not import supplier feeds or synchronize warehouse stock by itself.

• Identify your wheel dimensions and measurement units.
• Use the reverse lookup to obtain matching vehicles.
• Store compatibility alongside the product record in your own catalog.

Support complete wheel sets

Front and rear parameters can be supplied separately for staggered setups, including distinct diameters and center bores. Match a complete pair instead of combining unrelated axle results.

• Use mode=stag for front/rear filters.
• Supply diameter_rear and cb_rear where the axles differ.
• Use returned catalog names and slugs consistently across your products.

Agree volume and access before connecting

Request quotas are shared across your company’s keys, while IP allowances are configured per key. Describe expected query volumes and server locations so we can agree the access configuration.

• Confirm the vehicle coverage needed by your business.
• Plan backend caching and retry behavior for quota responses.
• Keep compatibility results separate from your availability and pricing rules.