Frequently Asked Questions

Open any product in the FitmentPro app, use the 6-stage vehicle selector to choose compatible vehicles, and save. The compatibility data is automatically stored in product metafields and displayed on your storefront.

Our database includes over 900,000 vehicles across dedicated EU (TecDoc K-Type), US, UK and Australian catalogs — cars, motorcycles, and commercial vehicles from 1990 to present. The European catalog is TecDoc-compatible with K-Type numbers.

HSN (Herstellerschlüsselnummer) and TSN (Typschlüsselnummer) are German vehicle registration codes. Customers can enter these codes from their registration documents to instantly identify their exact vehicle model.

No. All storefront filtering uses native Shopify Liquid and product metafields. There are no external API calls for vehicle matching, ensuring fast page loads and reliable performance.

Yes. FitmentPro supports Excel and CSV import. You can bulk import vehicle-to-product mappings or use our template system to quickly apply common fitment patterns.

Your compatibility data remains stored in product metafields. Theme blocks will continue to display the data. You can re-subscribe anytime to resume editing.

Yes. All paid plans include a 14-day free trial. No credit card required to start. You can test all features before committing.

FitmentPro works with all Online Store 2.0 themes (Dawn, Craft, Sense, and custom themes). Theme blocks are added through the theme customizer without code changes.

Yes, each Shopify store requires its own FitmentPro installation and subscription. Your templates and vehicle database are available across all installations linked to your account.

Contact our support team with the vehicle details (Year, Make, Model, Engine). We regularly update our database based on merchant requests. Enterprise customers receive priority additions.

Yes. The versioned public REST API is available from the Pro plan upward. Create an API key under Settings → API Access, then query the vehicle cascade (brands, models, platforms, variants, years) and product fitment, or sync with external systems. A full OpenAPI specification documents every endpoint.

On the TecDoc plan, FitmentPro connects to the TecDoc catalog for professional parts data: OE/part-number and EAN lookup, article search and linking, and catalog-wide bulk sync. Customers can also search by part number via the OE Number Lookup storefront block. The TecDoc AI plan adds automatic AI product categorization with no API key required.

Two ways. Branded parts with a TecDoc or OE number are linked to compatible vehicles automatically by the TecDoc integration — like any other part. For your own-brand consumables that only have a spec in the title, the Consumable Finders (Enterprise Plus and above) map each vehicle to the spec it needs — battery size/Ah/cold-cranking amps plus start-stop AGM/EFB, wiper blade lengths, bulb type, oil viscosity & OE approvals — and match your products from their title, written as standard fitment. Shoppers then use your normal vehicle filter or My Garage; nothing extra is added to your theme.

Yes. The Enterprise Plus plan adds vehicle-aware merchandising: cross-sell and upsell recommendations, a Bundle Builder for vehicle-specific bundles, and a Garage Smart Feed that highlights products fitting the customer's saved vehicle. These appear on the storefront through the Sales Boost, Bundle Builder, and Garage Smart Feed theme blocks.

Customers can save their vehicles to a personal garage stored in their browser. When they return to your store, their saved vehicles are instantly available for filtering. No account required.

Yes, the theme blocks use CSS custom properties and standard Shopify theme settings. You can adjust colors, fonts, and layout through the theme customizer or with custom CSS.

VIN (Vehicle Identification Number) is a unique 17-character code assigned to every vehicle. Customers enter their VIN and FitmentPro decodes it using the NHTSA database to automatically identify make, model, year, and engine. This provides the most accurate vehicle identification possible.

The Brand Whitelist lets you control which vehicle brands appear in your store's vehicle selector. Instead of showing hundreds of brands, you can enable only the brands relevant to your product catalog, giving customers a cleaner browsing experience.

Yes, fitment data is stored in standard product metafields accessible via the Storefront API. You can query this data in any headless implementation using GraphQL.

Automations (Pro plan and above) let you automatically apply fitment rules when products are created or updated. For example, add all BMW 3-series vehicles to any product with 'BMW E90' in the title.

Free plan: Community forum and documentation. Growth plan: Email support (48h response). Pro plan: Priority email support (24h response). Enterprise plan: Dedicated support contact.

FitmentPro supports four vehicle markets: Europe (TecDoc / K-Type), the United States (ACES / ePID), the United Kingdom, and Australia. Choose your market under Settings → Smart Dropdowns → Vehicle data region. The entire vehicle cascade, storefront filter, and fitment rules are scoped to that region — EU and US data never mix, so customers only see vehicles relevant to your market.

Yes. Connect your eBay seller account in Settings → eBay, then run an import from the Bulk page. FitmentPro pulls vehicle compatibilities from your eBay listings and matches them to Shopify products by SKU — using K-Type for eBay.de and ePID for eBay.com. You choose whether to add to existing fitment or overwrite it.

Yes — eBay Auto-Sync keeps Shopify and eBay aligned without manual work. Once connected, it periodically re-pulls your eBay compatibilities so new listings and updated fitment flow into your storefront on their own. You can still trigger a manual sync from the Bulk page whenever you want.

Yes. On US shops, FitmentPro accepts myFitment.com CSV exports directly. Upload the file on the Bulk → Import page; the format is auto-detected and each Year/Make/Model/Engine row is matched to US vehicles automatically. Any rows that can't be matched are reported as errors rather than dropped silently.

Yes, on US shops with the Enterprise Plus plan. FitmentPro imports and exports fitment in the Auto Care ACES standard and exports your catalog as PIES product data — the gateway to large US distributors and marketplace fitment. Because real ACES references vehicles by VCdb BaseVehicleID (licensed data we can't ship), you upload your own VCdb extract under Settings → US ACES / VCdb for fully standard-compliant output; without it, ACES files still match by Year/Make/Model. ACES import is auto-detected when you drop an .xml file on the Bulk → Import page.