Catalog questions
Use this path when the request involves naming, category placement, cross-reference review, or online catalog preparation for Driveline & Clutch Parts.
[email protected]Contact ZF
Route your Driveline & Clutch Parts request with useful application detail.
The sourcing desk can respond more clearly when the first message includes the vehicle application, part family, business channel, and documentation requirement.
Distributor sourcing
Use this path when procurement needs target volumes, replenishment planning, packaging questions, or part-family availability for wholesale programs.
[email protected]Service workflow
Use this path when repair networks, warranty teams, or performance garages need installation context and application support before a quote moves forward.
[email protected]Quote form
What to include in the first message
ZF requests work best when the buyer includes specific information rather than a broad part family. Mention the platform or vehicle group, the part family, the intended channel, target quantity, and whether the request is for current replenishment, a new catalog range, or service support. If there are return issues, warranty observations, or image and attribute requirements, include those notes as well.
The form is intentionally simple so procurement, catalog data, quality, and service operations can use the same entry point. A distributor may start with annual volume and stocking priority. A performance garage may start with installation scenario. An OEM or OES team may start with validation language and compliance references. Each path helps the desk understand the decision behind the request.
If the request is urgent, describe the business reason as clearly as the part family. A warranty recovery program, a new online catalog launch, and a fleet maintenance stocking plan each require a different response rhythm. Mention whether the priority is lead-time visibility, technical documentation, replacement hierarchy, or confirmation that related wear items should be quoted together.
- Vehicle application or platform
- Product family and related wear items
- Target region and business channel
- Documentation or cross-reference needs