Automotive and parts: fitment questions, part numbers and what an agent can match Free & Pro

'Does this fit my car?' is the parts question. There is no fitment database in the plugin; what there is (part numbers, fitment text, cross-sells) and how far it gets.

Updated October 13, 2026

Parts customers ask one question: does it fit. A personal agent asking your store on their behalf has only your words to go on. Agent Adapt gives it search by keyword and SKU, product descriptions, attributes and your cross-sells; it has no fitment database and no vehicle lookup. This page says how far that gets a parts store on WooCommerce, with facts from the plugin as it ships on 13 October 2026.

What customers will ask their assistant

  • "Brake pads for a 2018 Golf 1.6 TDI, front."
  • "The same oil filter as my last order."
  • "Is part number 06J115403Q in stock?"
  • "Can I return it if it’s the wrong one?"

Part numbers

The agent matches each search term against product titles and SKUs. Put the manufacturer part number in the SKU, and OEM and cross-reference numbers in the description text or an attribute, and the agent finds a part by any of them. "06J115403Q" in a SKU is an exact match; the same number in a PDF is invisible.

Fitment in words

Without a vehicle database, fitment is text. An attribute "Fits: VW Golf Mk7 2013–2020, 1.6 TDI, 2.0 TDI" is readable and comparable with what the customer told their assistant about their car. A fitment table in the description is read as text up to 5,000 characters. A fitment tool that queries a database from the product page is not part of the API; the agent can send the customer to the product page, whose URL it has, and say that fitment should be confirmed there. Be plain in descriptions about left and right, front and rear, and what is not included.

Vehicle-lookup plugins that filter the catalogue by registration or model are not part of the API either, and the agent searches the whole visible catalogue.

Reorders of consumables

Filters, fluids, wiper blades, bulbs: with the customer signed in and the agent approved, a past order’s items go back in the cart with one call, at today’s prices. SKUs are what make "the same filter as last time" exact.

Wrong-part returns

Your returns page is sent as plain text. Say the window, the condition (unfitted, in original packaging), whether electrical parts are returnable, and who pays return postage for a wrong-part return versus a wrong-supply return. With Pro, an agent can send a return request on a completed order within your return window; it adds a note and emails you and refunds nothing until you act.

Trade customers

A parts store with trade accounts should read B2B and wholesale: which account roles can be connected to an agent, and what happens to trade pricing.

What to set up

  1. Manufacturer part numbers in SKUs; OEM and cross-reference numbers in descriptions or attributes.
  2. Fitment in text: models, years, engines, positions.
  3. Cross-sells (the gasket that goes with the pump); the agent sees them.
  4. A returns page covering wrong parts and electrical items.
  5. Hidden visibility for anything you sell only to trade or on request.

Common questions

Can the agent look up a registration number?

No. There is no vehicle lookup in the agent API. The customer tells their assistant what car they have; the assistant compares that with your fitment text.

Will it get fitment wrong?

It can, if your text is ambiguous or the customer’s description is. Say in your returns page how wrong-part returns work, and consider a line in each description asking the customer to confirm fitment on the product page.

Does it see my fitment tool’s results?

No. Only the product’s text and attributes.

Can it order from my supplier when I am out of stock?

No. It works with your catalogue and stock. An out-of-stock part is reported as out of stock and not added.

Still stuck? Email [email protected].