The model comes before the part
If you sell parts for several machine models, the store structure matters.
A customer with Model A should not have to filter through parts for Models B, C, D, and E. They need to find their machine first, then choose from the parts that belong to it.
This is the central structure for multi-model parts stores.
Machine first. Diagram second. Part third.
Use one Konfig per model
The cleanest starting point is one Konfig per machine model.
Each model gets its own parent product page, diagram, and parts list. The customer lands on the machine they recognise and sees the parts for that machine only.
This keeps model differences clear.
If two machines use different diagrams or part sets, they should not be forced into one generic page.
Use collections to group the machines
Shopify collections are still useful.
Use them to group the parent machine pages, not just the individual parts.
For example, a pool equipment store might have a “Pool Pump Parts” collection containing model-specific Konfig products. An agricultural dealer might group tractor models, harvester systems, or implement ranges.
The collection gets the customer to the right model. The Konfig handles the parts.
Name model pages consistently
Naming matters more as the catalogue grows.
Use a consistent pattern such as:
- Brand Model Spare Parts
- Brand Model Pump Parts
- Brand Model Hydraulic Parts
- Brand Model Service Parts
Consistency helps customers, staff, and search engines understand the structure.
Avoid internal shorthand that only your team understands.
Separate systems when one model is too large
Some machines are too complex for one Konfig.
A tractor, harvester, industrial machine, or large appliance may have several major assemblies. One page containing every part may become difficult to use.
In that case, create Konfigs by system within the model.
For example: Model X hydraulics, Model X engine, Model X electrical, Model X transmission.
Do not combine models just because they look similar
Similar models can be dangerous.
Two machines may share a housing shape but use different internal parts. A later revision may use a different seal, cable, bearing, or bracket. A model sold in one region may have a different assembly.
If the parts differ, separate the Konfigs.
A cleaner structure is worth more than a shorter list of pages.
Use shared parts where the item is truly the same
Some parts will appear across many models.
A seal, filter, bearing, fastener, belt, O-ring, sensor, or bracket may be used in several machines.
When the physical product is identical, keep it as one Shopify product and link it to each relevant Konfig.
Each model page can show the part in its own position while the product record stays centralised.
Scaling from five models to fifty
The same principles apply as the store grows.
With five models, you might manage everything manually. With fifty, consistency becomes critical. Page naming, collections, product titles, shared parts, and diagram structure all need to follow a pattern.
Do not wait until the catalogue is messy before creating rules.
Decide early how models, systems, and shared products will be named and organised.
Keep internal and customer naming aligned
Your team may use internal model names, supplier codes, or shorthand.
Customers may use the name printed on the machine, the retail model, or a common nickname.
Where possible, use customer-facing names in page titles and product names, while keeping internal references in SKUs or product data.
The page should match how buyers search and recognise their machine.
The architecture should be boring
A good multi-model structure is not clever.
It is predictable.
The customer chooses the product category. Then the model. Then the system if needed. Then the part.
Konfigr fits into that structure by giving each model or system its own visual parts page.
That is how a multi-model Shopify parts store stays understandable as it grows.
