The application decides the product.
A seatbelt requirement is defined by where it is going, not by what it is called. Five application contexts, and what changes about the sourcing question in each.
Passenger Vehicles
In a passenger vehicle the seatbelt system is what keeps an occupant in their seat and in a controlled position. It is the most familiar restraint arrangement and the one buyers most often need to replace.
Each seating position in a car can carry a different arrangement. A front belt usually involves a retractor and an upper anchorage on the pillar; rear positions vary considerably between models, and the centre position frequently differs from the outer ones in the same row.
That variation is why we ask which position is involved before anything else. “A seatbelt for a hatchback” is not yet a sourceable requirement; “the rear left belt in this specific model and year” is close to one.
Most useful to send: make, model, model year, body type, the seating position, and photographs of the existing belt in place including the mounting points.
Commercial Vehicles
Vehicles in working use bring a different set of pressures. The component still has to be right, but availability and turnaround carry weight they do not carry for a private car.
Commercial vehicles typically accumulate hours faster, carry different occupants across a working week and operate in more demanding conditions. Restraint components in these vehicles see correspondingly more use, and replacement requirements arise more frequently as a matter of routine maintenance rather than exception.
Cab layouts also vary more than passenger car interiors. Seating arrangements differ between body types built on the same chassis, and a component that suits one configuration may not suit another that appears similar from outside.
Most useful to send: the vehicle and body type, the cab or seating configuration, the position involved, how quickly the vehicle needs to be back in service, and photographs of the existing arrangement.
Fleet Applications
When several vehicles are held to one standard, consistency becomes the requirement in its own right.
A fleet operator replacing a component across multiple units is not solving one sourcing problem repeatedly — they are trying to keep the fleet uniform. That changes what matters: the same component, supplied to the same description, available again when the next vehicle needs it.
It also changes the value of documentation. A fleet that has recorded what was fitted, when and to which vehicles can specify the next replacement in a sentence. One that has not is starting the identification from scratch every time.
Most useful to send: how many vehicles are involved, whether they are identical, whether this is a one-off or an ongoing requirement, and any internal standard the fleet works to.
Workshops and replacement requirements.
04 — Automotive Workshops
Trade05 — Replacement Requirements
DirectWhy accurate application data changes the answer
It narrows the search from a product family to a specific arrangement, which is the difference between a plausible option and a defensible one.
It surfaces the questions that would otherwise appear late — the counterpart component, the mounting arrangement, whether a retractor is involved.
It creates a record. The same application described accurately once can be sourced against again without repeating the identification work.
Tell us the application and we will work back to the component.
Vehicle, seating position, photographs. That is usually enough to begin.