FAQ

Do I need a separate fitment database? No. Axle reads fitment from the standard product feature “Fits vehicles” (one variant per vehicle). You edit it in the product page or the product import like any other feature. See Usage.

My vehicle names do not split into make and model. Name the variants Make · Model · Engine · Years (or with |). Make and model are required; variants that cannot be read are left out of the finder but still work as product features.

Is the shopper’s vehicle stored on my server? No. It is saved in the shopper’s browser (local storage) only, so pages stay cacheable and no personal data is stored.

My product photos have a white background. Do they work? Yes. Turn off Studio plinth behind product images in the Axle settings: photos are shown on a plain white card. Cut-out images (transparent background) look best with the plinth on.

The cards show no brand, position or fitment badge. They come from product features: Brand (AX_BRAND), Position (AX_POS), Fits vehicles (AX_FITS) or Universal fit (AX_UNIVERSAL), or your own features with those names.

Can shoppers search by OE number? Yes, when the number is in the product code, name or description (the core search). Axle also shows the OE numbers (AX_OE) as chips on the product page.

Does Axle work with the full page cache of CS-Cart 4.21? Yes. Theme output holds only catalogue data; the saved vehicle, the badges and the bundle totals are handled in the shopper’s browser, and cart and wish list counters come from the standard blocks.

What happens when the licence expires? The storefront shows the standard Responsive look; your store keeps selling. See Configuration.

Still stuck?

Work through the troubleshooting guide, then contact support with your CS-Cart version, edition, PHP version and the add-on version (1.0.0).