Wheel Hub Landed-Cost RFQ Worksheet for Import Distributors
Landed cost is a buyer-specific calculation, not a supplier slogan or a universal percentage. A useful wheel hub worksheet connects the exact quoted item and pack to the Incoterm, named place, transport plan, import treatment and internal costs while keeping estimates separate from invoices.
What belongs in a wheel hub landed-cost worksheet?
Start with the technically approved SKU, sale-unit scope, quantity and actual package hierarchy. Record supplier price, currency and validity; the Incoterm rule and precise named place; origin charges, main carriage, insurance, destination handling, customs value method, tariff classification under buyer review, duty and tax treatment, broker and bank fees, inland delivery, inspection, repacking, damage allowance and internal handling. Cite the source and date for each value, preserve estimates separately, and recalculate when quantity, pack, route or terms change.
Lock the product and package scope before costing
Ensure the worksheet represents the same technical item and shipped pack as the quotation. This is the controlling question for wheel hub landed-cost planning, since a lower part price can require a different carton count, hardware purchase or damage-control method. Procurement, catalog and quality teams should use the same definition so that a technical note cannot be converted into a stronger public or contractual claim downstream.
Collect approved RFQ line, BOM, each/case/pallet quantities, dimensions, weights and packaging revision. After intake, reconcile supplier declarations with the sample or approved pack and mark provisional data. Do the comparison line by line rather than by overall resemblance, total price or a supplier’s confidence. Evidence can eliminate a candidate without proving the remaining candidate, and the workflow should preserve that distinction.
Decision rule and evidence owner
The evidence packet must link every physical and commercial input to the exact quote and pack revision. Give files stable names, retain the unedited originals and connect every conclusion to its source. A screenshot without the URL and access date, or a photograph without the SKU and sample ID, is difficult to reuse and should not carry an approval by itself.
Worked situation: a supplier changes case quantity after the freight estimate but the worksheet keeps the old cube. Hold the decision if the shipped hierarchy cannot be identified. Explain the hold with the disputed field and required evidence rather than speculation. That approach gives suppliers and customers a solvable question while protecting the distributor from an accidental interchange, capability or delivery promise.
Record the Incoterm rule and named place together
Define where cost and risk responsibilities transfer for the quoted movement. This is the controlling question for wheel hub landed-cost planning, since FOB, CIF, DAP or another shorthand without a place and version is incomplete. Procurement, catalog and quality teams should use the same definition so that a technical note cannot be converted into a stronger public or contractual claim downstream.
Collect quoted rule, Incoterms version, named port or place, carrier plan and contract wording. After intake, map seller and buyer tasks to the actual route and confirm exceptions in writing. Do the comparison line by line rather than by overall resemblance, total price or a supplier’s confidence. Evidence can eliminate a candidate without proving the remaining candidate, and the workflow should preserve that distinction.
A workable release condition
The evidence packet must retain who pays, who contracts and where risk transfers for each leg. Give files stable names, retain the unedited originals and connect every conclusion to its source. A screenshot without the URL and access date, or a photograph without the SKU and sample ID, is difficult to reuse and should not carry an approval by itself.
Worked situation: CIF is quoted without naming the destination port or identifying post-arrival charges. Hold the decision if the parties interpret the delivery point differently. Explain the hold with the disputed field and required evidence rather than speculation. That approach gives suppliers and customers a solvable question while protecting the distributor from an accidental interchange, capability or delivery promise.
Build costs by transport event
Separate origin, main carriage, destination and final-delivery components. This is the controlling question for wheel hub landed-cost planning, since one bundled freight number can hide excluded terminal, documentation or on-carriage charges. Procurement, catalog and quality teams should use the same definition so that a technical note cannot be converted into a stronger public or contractual claim downstream.
Collect forwarder quote, route, equipment, chargeable measure, validity, free-time assumptions and delivery location. After intake, place every charge on an event timeline and avoid counting an included cost twice. Do the comparison line by line rather than by overall resemblance, total price or a supplier’s confidence. Evidence can eliminate a candidate without proving the remaining candidate, and the workflow should preserve that distinction.
How to document the exception
The evidence packet must store original quote currency, units, conditions and expiry. Give files stable names, retain the unedited originals and connect every conclusion to its source. A screenshot without the URL and access date, or a photograph without the SKU and sample ID, is difficult to reuse and should not carry an approval by itself.
Worked situation: a forwarder includes ocean freight but excludes destination handling and chassis fees. Hold the decision if the scope of a logistics amount is not stated. Explain the hold with the disputed field and required evidence rather than speculation. That approach gives suppliers and customers a solvable question while protecting the distributor from an accidental interchange, capability or delivery promise.
Use reviewed customs and tax inputs
Treat classification, valuation, origin and tax as jurisdiction-specific decisions. This is the controlling question for wheel hub landed-cost planning, since an online duty percentage or supplier HS suggestion may not control the import entry. Procurement, catalog and quality teams should use the same definition so that a technical note cannot be converted into a stronger public or contractual claim downstream.
Collect buyer or broker classification review, origin evidence, customs value basis, duty, tax and trade-measure status. After intake, obtain qualified destination-market advice and record the source and effective date. Do the comparison line by line rather than by overall resemblance, total price or a supplier’s confidence. Evidence can eliminate a candidate without proving the remaining candidate, and the workflow should preserve that distinction.
A case that exposes the hidden risk
The evidence packet must keep disputed and confirmed inputs separate and document refunds or deferrals. Give files stable names, retain the unedited originals and connect every conclusion to its source. A screenshot without the URL and access date, or a photograph without the SKU and sample ID, is difficult to reuse and should not carry an approval by itself.
Worked situation: two similar hubs fall under the same supplier description but the broker requests additional construction evidence. Hold the decision if the worksheet relies on an unverified tariff code or legal conclusion. Explain the hold with the disputed field and required evidence rather than speculation. That approach gives suppliers and customers a solvable question while protecting the distributor from an accidental interchange, capability or delivery promise.
Show estimates, actuals and risk allowances separately
Let decision makers see which total components can still move. This is the controlling question for wheel hub landed-cost planning, since a single landed-cost number creates false precision and obscures route, damage or currency exposure. Procurement, catalog and quality teams should use the same definition so that a technical note cannot be converted into a stronger public or contractual claim downstream.
Collect estimate/actual status, confidence, source date, currency basis, scenario and owner. After intake, calculate base, conservative and exception scenarios only from explicit assumptions. Do the comparison line by line rather than by overall resemblance, total price or a supplier’s confidence. Evidence can eliminate a candidate without proving the remaining candidate, and the workflow should preserve that distinction.
What a second reviewer should see
The evidence packet must retain formulas, exchange-rate source and variance after receipt. Give files stable names, retain the unedited originals and connect every conclusion to its source. A screenshot without the URL and access date, or a photograph without the SKU and sample ID, is difficult to reuse and should not carry an approval by itself.
Worked situation: freight is firm but destination inspection and storage exposure remain conditional. Hold the decision if an allowance is embedded in another cell or presented as a known invoice. Explain the hold with the disputed field and required evidence rather than speculation. That approach gives suppliers and customers a solvable question while protecting the distributor from an accidental interchange, capability or delivery promise.
Landed-cost worksheet field map
The worksheet should reveal the source and status of every cost rather than promise a universal landed price.
| Layer | Example inputs | Source/status |
|---|---|---|
| Product | Price, unit, currency, quantity, scope | Supplier quote revision |
| Pack | Each/case/pallet quantity, dimensions, weight | Approved pack or provisional |
| Trade term | Rule, version, named place | Contract/quote review |
| Transport | Origin, carriage, destination, on-carriage | Forwarder quote and validity |
| Border | Classification, value, origin, duty/tax | Buyer/broker review |
| Internal | Inspection, finance, storage, repack, damage | Buyer estimate then actual |
Reconcile the estimate after the shipment closes
Freeze a pre-order snapshot with the selected technical line, quote, pack and route. Recalculate before release if quantity, carton, named place or milestone changes. This prevents a late commercial change from passing through a stale landed-cost decision.
After receipt, replace estimate cells with actual invoice or entry data without deleting the estimate. Explain material variance by event: product, origin, carriage, border, storage, damage or internal handling. Use the result to improve the next scenario, not to publish a universal cost claim.
Keep customs, tax and Incoterms interpretation with the buyer's qualified advisers and contract owners. The supplier can provide origin, product and package evidence, but it should not be asked to make an unsupported destination-market legal determination. This division of responsibility produces a more reliable RFQ.
Claim boundary: This is an operational worksheet, not customs, tax, legal or financial advice, and it contains no live freight, duty or supplier pricing.
Additional review scenarios for wheel hub landed-cost planning
Review scenario 1 for wheel hub landed-cost planning: Start from approved RFQ line, BOM, each/case/pallet quantities, dimensions, weights and packaging revision. The reviewer should reconcile supplier declarations with the sample or approved pack and mark provisional data. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will link every physical and commercial input to the exact quote and pack revision. If the shipped hierarchy cannot be identified, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 2 for wheel hub landed-cost planning: Start from quoted rule, Incoterms version, named port or place, carrier plan and contract wording. The reviewer should map seller and buyer tasks to the actual route and confirm exceptions in writing. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain who pays, who contracts and where risk transfers for each leg. If the parties interpret the delivery point differently, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 3 for wheel hub landed-cost planning: Start from forwarder quote, route, equipment, chargeable measure, validity, free-time assumptions and delivery location. The reviewer should place every charge on an event timeline and avoid counting an included cost twice. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will store original quote currency, units, conditions and expiry. If the scope of a logistics amount is not stated, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 4 for wheel hub landed-cost planning: Start from buyer or broker classification review, origin evidence, customs value basis, duty, tax and trade-measure status. The reviewer should obtain qualified destination-market advice and record the source and effective date. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will keep disputed and confirmed inputs separate and document refunds or deferrals. If the worksheet relies on an unverified tariff code or legal conclusion, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 5 for wheel hub landed-cost planning: Start from estimate/actual status, confidence, source date, currency basis, scenario and owner. The reviewer should calculate base, conservative and exception scenarios only from explicit assumptions. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain formulas, exchange-rate source and variance after receipt. If an allowance is embedded in another cell or presented as a known invoice, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Related wheel hub buyer resources
- Wheel Hub Assembly catalog
- Wheel Hub Bearing catalog
- wheel bearing versus wheel hub assembly guide
- ABS encoder identification guide
- wheel hub OE number and RFQ guide
- fitment verification workflow
- sample approval workflow
- kit contents and BOM verification
- supplier evaluation evidence guide
- export packaging checklist
- MOQ and lead-time planning guide
- incoming inspection checklist
- About Jinan Huayuan Auto Bearing
Sources, dates and claim boundaries
- ICC Incoterms 2020 guidance — delivery point, carriage, cost and risk responsibility boundaries
- Auto Care Association: ACES 5.0 and PIES 8.0 — current fitment/product-data exchange roles, digital assets, package configurations and file hashing
- TecAlliance catalog and data-package overview — standardized article, reference, package, image and vehicle-linkage data for distributors
- SKF wheel hub bearings and kits — hub generations, included kit items and application-specific installation resources
Technical review: Jinan Huayuan Auto Bearing editorial review for source fidelity, procurement-data consistency and unsupported-claim removal. This review does not replace an OE catalog, vehicle service procedure, legal or customs advice, a customer-approved drawing, or mutually agreed commercial and inspection terms.
Corrections: Send the page URL and supporting evidence through the contact page. Material corrections are reviewed, linked records are rechecked and the updated date is changed when warranted.
