The question sounds simple, but it steals time

“Which part do I need?”

If you sell spare parts, you know that question well.

It might come through email, phone, chat, or a photo sent from a workshop bench. The customer has a product in front of them. Something is broken. They can see the part, but they cannot identify it from your store.

So they ask you.

That is normal for complex products. But when the same question comes up every day, the problem is not just customer support. The problem is that the store is not carrying enough of the explanation.

Why customers ask in the first place

Customers ask because they are not confident.

They may be looking at a collection of similar parts. They may have a PDF open in one tab and your store in another. They may be trying to match a worn part in their hand to a product image online.

If the product titles are technical, they hesitate. If two parts look alike, they hesitate. If they cannot tell where the part sits on their model, they stop.

That hesitation turns into a support enquiry.

The customer is not always asking you to diagnose the problem. Often, they are asking you to identify the thing they are already looking at.

The old support flow

The old flow usually looks like this:

  • The customer calls or emails.
  • You ask for the model number.
  • They send a photo.
  • You check the diagram or manual.
  • You identify the part.
  • You send them a product link.
  • They ask whether it is in stock.
  • You answer again.

That process works, but it does not scale well. It also puts you in the middle of every basic parts order.

If the question is unusual, that is fine. If it is the same identification question repeated across common models, the store should be able to answer it.

The better flow

A better flow starts on the product page.

The customer finds the model they own. They open the page. They see the diagram. They click the part. The matching item is shown in the parts list with its product image, price, SKU, stock status, and add-to-cart button.

That does not remove every support question. It removes the unnecessary middle step where you have to point at the diagram for them.

With Konfigr, that is the job of the Konfig. You create a page for the parent product, upload the diagram, place hotspots, and link each part to your existing Shopify products.

The customer can self-identify the part before they contact you.

What a diagram can answer

A good parts diagram can answer the repetitive questions:

  • Where is this part on the product?
  • Which product in the list matches this number?
  • What is the part called?
  • What is the SKU?
  • Is it currently available?
  • Can I add it to cart now?

Those are page-level questions. The customer should not need to call you for every one of them.

Konfigr’s diagram and parts list are connected. Clicking a hotspot points the customer to the part in the list. The parts list gives them the product information they need to decide.

What still needs a human answer

Some questions should still come to you.

If the customer is not sure which model they own, you may need to help. If there were production changes across years, you may need to confirm details. If a technician needs repair advice, that is outside the diagram. If the customer wants a custom quote or special pricing, that is not what Konfigr handles.

Konfigr is not a compatibility checker. It does not diagnose faults, quote jobs, or modify checkout. It gives you a clear way to present the parts for a product so customers can identify and order them with less back-and-forth.

That honesty matters. The aim is not zero support. The aim is fewer repetitive identification questions.

Stock and SKU visibility matter for support

Many support questions are not only about identification.

Trade buyers often ask by SKU. Retail customers ask whether the part is available. Technicians want to know whether they can get the part before they commit to a job.

When you show SKU and stock status in the parts list, the page answers more of those questions upfront.

Konfigr reads product data directly from Shopify. If the stock status or price changes in Shopify, the diagram page uses the current product data. You are not updating a separate parts list manually.

Let customers stay on the page

Support volume increases when customers have to jump between resources.

A PDF diagram is useful, but it is not shoppable. A product collection is shoppable, but it does not show the part in context. A product page shows detail, but it may not show the full assembly.

A Konfig brings those pieces together.

The customer can see the parent product, the diagram, the parts list, and the add-to-cart buttons in one place. If you allow product links, they can still open the full product page for more detail. If the part is simple enough, they can add it from the list.

That keeps the buying path clean.

The real win is confidence

People ask “which part do I need?” because they do not want to order the wrong thing.

If your page gives them enough context, many customers will answer the question themselves. They will not need to wait for a reply. You will not need to identify the same seal, bracket, bearing, or switch ten times a week.

That is what a good parts page should do.

It should not just display products. It should carry the knowledge that normally lives in your head, your parts manual, or your support inbox.

Show the model. Show the diagram. Show the part. Show the stock. Then let the customer order.

Related Articles

Continue your learning with these related resources: