News

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.

Create one controlled RFQ line for each application and require every supplier to return the proposed model, evidence status, supplied contents, unit and currency, quantity break, MOQ condition, packaging, readiness trigger and milestone, Incoterm and named place, payment assumptions, quote validity and exclusions. Convert units and currencies in separate buyer-calculated columns. Score unresolved technical fields before price and compare totals only among lines with equivalent scope.

Map supplier model, buyer SKU, PO, receipt, supplier lot or date code, package identifier, quantity, bin movements and outbound order lines in one auditable chain. When a field action or credible risk signal arrives, freeze the affected definition, block sale and transfer, count physical stock, identify shipped customers, preserve samples and issue a named disposition. Do not broaden or narrow the population from memory; use the notice, source evidence and controlled lot relationships.

Identify the affected supplier and buyer SKUs, current and proposed revisions, reason, first affected lot or date, application impact, dimensions and interfaces, materials or process evidence where relevant, ABS and connector details, BOM and hardware, labels, package and digital assets. Include validation evidence, sample need, remaining old stock, transition plan and requested approval date. The buyer should classify impact and reapprove only the affected records; silence or a repeat PO is not approval of an undisclosed change.

ACES communicates vehicle application and fitment relationships; PIES communicates product information such as descriptions, attributes, packages, prices, interchanges and digital assets. A wheel hub handoff should first control the supplier SKU, application evidence, axle and drive qualifiers, ABS configuration, product attributes, kit contents, package levels, images and revision dates. Schema validation checks structure, not truth, so distributors must also test completeness, conflicts, assets and source confidence before publication.

Capture the sold SKU and supplier model, OE and vehicle evidence, axle and side, order and lot identifiers, installation date and mileage if reliably available, symptom and diagnostic context, service procedure and application-specific torque source, related parts replaced, package and part photographs, scan results or codes as reported, and the returned unit’s custody and condition. Preserve facts separately from opinions, quarantine the part, and assign disposition only after the agreed warranty and technical review.

Record axle position, side and drive function independently. Front does not always mean driven, rear does not always mean non-driven, and a visible center opening does not by itself prove the power-transfer path. Confirm vehicle drive layout, the exact axle, spline or spindle interface, mounting geometry and ABS configuration from application-level evidence. Use physical features to classify a candidate family, then keep fitment unconfirmed until the OE or manufacturer catalog resolves the application boundary.

Record the complete part from controlled views, then measure only defined interfaces: center bore or spline, pilot, wheel and mounting flange patterns, offsets, flange diameters, stud or thread details, connector and lead routing, and supplied hardware. Identify the datum, tool, unit, sample and operator for every result. Use measurements to reject conflicts and narrow catalog candidates; do not convert a dimensional resemblance into vehicle fitment without an application-level source.

Check shipment identity, quantity, packaging condition, part and label traceability, visible corrosion or impact, flange and stud condition, bore or spline protection, seals and ABS lead or connector protection, agreed kit contents, and the drawing-defined characteristics selected for receiving inspection. Use an approved sample or controlled specification, calibrated measurement process and written sampling rule. Quarantine any conflict, preserve evidence by line and lot, and do not install a suspect unit to decide whether it fits.

Build a line-level demand and supply table. For each wheel hub assembly, record the evidence status, requested and forecast quantities, supplier-quoted MOQ, whether mixed references are allowed, sample and production stages, packaging condition, named Incoterm and place, readiness date, transit plan and review date. Keep supplier commitments separate from internal planning assumptions. Use scenario ranges, release points and exception triggers; do not advertise an MOQ or delivery time until the supplier confirms it for that exact quotation.

Confirm that the approved pack keeps metal and sensing interfaces clean and dry, prevents part-to-part contact and movement, protects studs, splines, seals, leads and connectors, identifies the exact item and lot, supports safe carton and pallet handling, and meets destination rules for any raw-wood packaging. Validate the pack for the planned distribution route and record its revision. Do not claim a material, corrosion duration, pallet treatment or transit performance unless the supplier has documented it for that pack.

Request legal and commercial identity, the exact product and application scope, source-controlled OE and fitment data, a drawing or specification for the proposed part, sample and revision controls, inspection methods and records, measurement traceability evidence, lot and label traceability, packaging specification, nonconformity and warranty-data workflow, and change-notification rules. Verify certificates with the issuer and confirm their entity, site, scope and validity. Score missing evidence as open; do not convert marketing claims into approval.

Separate the core assembly from loose items, assign each included component a part or controlled description, quantity, revision and evidence source, and compare the BOM with the quotation, sample, labels and final pack. Record absent items explicitly where the buyer might otherwise assume inclusion. Never infer universal contents from the word ‘kit,’ a representative photograph or another application. Installation hardware and torque requirements remain application-specific.

Assign the sample a stable ID, preserve its supplier model and RFQ line, verify the OE/application evidence, photograph every critical interface, compare drawing-defined characteristics with a controlled method, record ABS or encoder configuration and supplied hardware, review packaging, and resolve every deviation before release. Approve a named revision for a named customer scope—not a generic ‘looks good’ sample. Bulk supply must match the approved evidence, and any later change should trigger documented review.

Use twelve controlled checks: source OE number, vehicle and market, model-year or chassis boundary, axle, side, driven status, hub construction, flange and mounting pattern, bore or spline, studs and threads, ABS or encoder configuration, and kit contents. Record the source and status of every field. A candidate cross-reference is not confirmed fitment, a matching connector is not proof of signal compatibility, and a similar photograph is not interchange evidence. Final approval should link the exact quoted item to the evidence reviewed.

Use a wheel hub OE number as a traceable starting reference, then verify it against the vehicle and the physical hub configuration before ordering. Record the number exactly as shown on the OE catalog, label or sample, including prefixes, suffixes, spaces and hyphens. In separate fields, add the source, vehicle make and model, model year or chassis range, front or rear axle, left or right side, drive configuration, ABS encoder or sensor details, flange and bolt data, spline count, key dimensions and quantity. Keep OE numbers, aftermarket cross references and supplier model numbers in different columns so they are not mistaken for the same identifier type. If a number has been superseded or appears against several vehicle variants, mark the row for confirmation rather than assuming interchange. A supplier-ready RFQ is one application per row with evidence attached.