DOT / SAE / CARB compliance per product, how do you surface it?

Compliance flags matter for two reasons: (1) legal liability if you sell a non-CARB part to a California customer, and (2) trade buyers filter by compliance certifications.

Implementation: compliance attributes per product:

• dot_compliant, required for safety-critical parts (brake hoses, lights, glass, tires).
• sae_certified, SAE J standards (J583 for headlamps, J637 for V-belts, etc.).
• carb_eo_number, California Air Resources Board Executive Order number for emissions parts (catalytic converters, ECU tunes, intake kits). Mandatory to sell into CA.
• epa_compliant, federal EPA emissions parts.
• nhtsa_recall_id, flagged if part is subject to active recall.

Front-end: filter compliance on layered nav, surface compliance badges on PDP, hard-block CA shipping addresses for non-CARB emissions parts at checkout with a clear error message. CARB enforcement is real, fines up to $37k per violation. If you sell ECU tunes, exhaust mods, or intake kits, this is non-negotiable.

Recall integration: nightly cron pulls NHTSA recall API by part number range, flags affected SKUs, optional auto-suspend listing or surface “Active recall” banner on PDP. Some states require notification to past purchasers, add a customer-segment query for buyers of recalled SKU and trigger an email notification campaign.