Shopify OBD-II Diagnostic Scan Tool Schema — Protocol Support, Scan Modes, Bidirectional Control Structured Data

Why OBD-II Scan Tools Are Structurally Invisible to AI Shopping Agents

OBD-II (On-Board Diagnostics II) has been federally mandated on all passenger cars and light trucks sold in the United States since 1996. But "OBD-II compatible" is not a homogeneous specification — it describes five different physical layer protocols, each used by different manufacturers during different periods. A scan tool claiming "1996+ OBD-II compatibility" that supports only ISO 15765-4 CAN (the modern protocol, mandatory from 2008) will fail to communicate with an enormous segment of vehicles from the 1996–2007 period: all GM trucks from 1996–2008 use SAE J1850 VPW, all Ford vehicles from 1996–2007 use SAE J1850 PWM, and many Chrysler, European, and Asian vehicles from 1996–2004 use ISO 9141-2 or ISO 14230-4 KWP2000. A buyer with a 2005 Silverado who purchases a CAN-only scanner bought a non-functioning tool. "OBD-II compatible" in product text conveys nothing about which of the five protocols are supported.

Bidirectional capability is the most significant functional distinction in the scan tool market — and the most obscured by vague marketing language. All four tiers of scan tools "read OBD-II codes." The question is what they can do beyond reading codes. Tier 1 (basic code readers, typically $20–$60) reads and clears diagnostic trouble codes and little else. Tier 2 (full OBD-II scanners, $60–$150) supports all 10 SAE J1979 service modes including live data streams, freeze frame, O2 sensor tests, and I/M readiness monitors. Tier 3 (enhanced scanners, $150–$400) adds OEM-specific codes for ABS, SRS airbag, automatic transmission, and body control — codes that are outside the SAE J1979 standard and require manufacturer-specific data libraries. Tier 4 (bidirectional/full-system, $400–$2000+) adds actuator tests: commanding the ABS pump to activate for brake bleeding, firing individual fuel injectors for balance testing, performing idle relearn procedures, and in some cases ECU programming. A buyer searching for "scanner to bleed ABS brakes" needs Tier 4 — a Tier 3 scanner cannot send commands to the ABS module even if it can read ABS codes. Without capability tier in schema, all scan tools look equivalent to an AI agent.

Wireless connectivity protocol determines iOS compatibility in a way that is frequently misrepresented. Bluetooth Classic (BR/EDR, the traditional Bluetooth used in audio and most ELM327 adapters) is not compatible with iOS as an OBD-II communication interface — Apple requires MFi (Made for iPhone) certification for Bluetooth Classic accessories, and generic ELM327 adapters do not carry this certification. ELM327-based adapters with Bluetooth Classic work on Android and Windows but will not connect to OBD apps on iPhone. Bluetooth 4.0 LE (BLE) does not require MFi certification and works with iOS 14+ for OBD-II applications. WiFi 2.4GHz adapters work on both iOS and Android. A buyer searching "OBD-II scanner for iPhone" who purchases a Bluetooth Classic adapter has a non-functional product. Encoding "Bluetooth" without specifying BLE vs Classic is an ambiguous compatibility declaration that AI agents cannot resolve correctly.

OEM-enhanced diagnostic codes cover the systems that most commonly produce warning lights that are not powertrain-related. An illuminated ABS warning light, SRS airbag light, TPMS light, or transmission temperature light produces codes that are outside the SAE J1979 OBD-II standard. These codes require OEM-specific data libraries that are licensed from manufacturers. A Tier 2 full OBD-II scanner will not read an ABS code — not because the scanner is defective, but because ABS codes are outside its protocol scope. Buyers searching for "scanner that reads ABS codes on 2015 Toyota Camry" need a product with Toyota ABS coverage in its OEM-enhanced brand list. This brand-by-system coverage must be encoded as a structured list in the product schema — "enhanced OEM coverage" without brand names is an unverifiable claim.

OBD-II Protocol by Vehicle Make and Model Year

SAE J1979 OBD-II Service Mode Reference

Complete OBD-II Scan Tool Schema — Tier 3 Enhanced Professional Scanner Example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "DiagPro T3 Enhanced OBD-II Scanner — ABS/SRS/Transmission + BLE Wireless",
  "description": "Professional Tier 3 enhanced OBD-II scanner. Supports all 5 OBD-II protocols (CAN, J1850 VPW, J1850 PWM, ISO 9141-2, KWP2000). All 10 SAE J1979 service modes. OEM-enhanced ABS/SRS/Transmission codes for GM, Ford, Chrysler, Toyota, Honda, Nissan, Hyundai, Kia. Wireless: Bluetooth 4.0 LE (BLE) — iOS and Android compatible. Standalone display: 2.8-inch TFT color touchscreen. Does NOT perform bidirectional actuator tests (Tier 4 required).",
  "sku": "DP-T3-BLE",
  "brand": { "@type": "Brand", "name": "DiagPro" },
  "additionalProperty": [
    {
      "@type": "PropertyValue",
      "name": "Supported OBD-II Protocols",
      "value": "ISO 15765-4 CAN (11-bit and 29-bit); SAE J1850 VPW; SAE J1850 PWM; ISO 14230-4 KWP2000; ISO 9141-2",
      "description": "All 5 OBD-II physical layer protocols supported: (1) ISO 15765-4 CAN — all 2008+ US vehicles, all EU 2008+, and early-adopter models from 2003–2007 including most European brands and many Japanese makes. Both 11-bit (standard) and 29-bit (extended) CAN addressing supported. (2) SAE J1850 VPW — GM vehicles 1996–2008 including Chevrolet, GMC, Buick, Cadillac, Pontiac, Oldsmobile, and Saturn. (3) SAE J1850 PWM — Ford vehicles 1996–2007 including Ford, Lincoln, and Mercury. Note: 2008+ Ford switched to CAN. (4) ISO 14230-4 KWP2000 — Asian and European OBD-II compliant vehicles 2000–2008. (5) ISO 9141-2 — Chrysler (1996–2004), European (BMW, Mercedes, VW, Volvo, Fiat 1996–2004), and Asian (Honda, Toyota, Hyundai, Kia 1996–2003) vehicles. Auto-detect: scanner automatically identifies the vehicle's active protocol on connection."
    },
    {
      "@type": "PropertyValue",
      "name": "Supported Scan Modes",
      "value": "All 10 OBD-II service modes — Mode 01 through Mode 0A",
      "description": "Full SAE J1979 mode support: Mode 01 (live data — 200+ standard PIDs including engine RPM, vehicle speed, coolant temperature, intake air temp, MAF sensor, throttle position, O2 sensor voltage × 4–8 sensors, short-term/long-term fuel trim × 2 banks, absolute barometric pressure, catalyst temperature); Mode 02 (freeze frame data at DTC set point); Mode 03 (stored confirmed DTCs); Mode 04 (clear DTCs and reset I/M readiness — resets all 8 readiness monitors); Mode 05 (O2 sensor tests — for non-CAN vehicles only; CAN vehicles use Mode 06); Mode 06 (on-board monitor results — catalyst efficiency, EVAP system, O2 sensor response, EGR system, secondary air, fuel system); Mode 07 (pending DTCs — codes set but awaiting second drive cycle confirmation); Mode 08 (bidirectional control — NOT SUPPORTED on this unit; Tier 4 required); Mode 09 (VIN retrieval, calibration ID, CVN verification); Mode 0A (permanent DTCs — cannot be cleared with Mode 04; require completing readiness drive cycle)."
    },
    {
      "@type": "PropertyValue",
      "name": "Capability Tier",
      "value": "Tier 3 — Enhanced OBD-II + ABS/SRS/Transmission (not bidirectional)",
      "description": "Tier 3 capability: reads and clears all OBD-II standard codes (powertrain P-codes) plus OEM manufacturer-specific codes for ABS (anti-lock braking system), SRS airbag, automatic transmission, and TPMS (tire pressure monitoring system) on supported makes. Tier 3 does NOT perform bidirectional actuator tests — this scanner can read an ABS fault code, it cannot command the ABS pump motor to activate for manual brake bleeding (Tier 4 required). Also does NOT perform ECU coding, key programming, injector balance testing, or idle relearn on makes requiring bidirectional commands. If you need to bleed ABS brakes with a scan tool or perform active tests: Tier 4 bidirectional scanner required."
    },
    {
      "@type": "PropertyValue",
      "name": "OEM Enhanced Coverage",
      "value": "GM, Ford, Chrysler, Toyota, Honda, Nissan, Hyundai, Kia — ABS, SRS, Transmission",
      "description": "OEM-enhanced manufacturer-specific diagnostic coverage (ABS, SRS airbag, automatic transmission codes beyond SAE J1979 standard): General Motors (Chevrolet, GMC, Buick, Cadillac, Pontiac); Ford (Ford, Lincoln, Mercury); Chrysler (Chrysler, Dodge, Jeep, Ram); Toyota (Toyota, Lexus, Scion); Honda (Honda, Acura); Nissan (Nissan, Infiniti); Hyundai (Hyundai, Genesis); Kia. Coverage depth: ABS fault codes (C-codes) and live ABS sensor data; SRS airbag fault codes and deployment history; transmission fault codes, gear selector position, and live ATF temperature. Manufacturers NOT in OEM enhanced list (OBD-II standard powertrain only): BMW, Mercedes-Benz, Volkswagen, Audi, Volvo, Subaru, Mazda, Mitsubishi. For full OEM enhanced coverage of European brands: requires a make-specific professional tool (VCDS for VAG, Carly for BMW, iCarsoft for multi-brand European)."
    },
    {
      "@type": "PropertyValue",
      "name": "Vehicle Year Coverage — US OBD-II",
      "value": "1996–present (US OBD-II; all 5 protocols)",
      "description": "US OBD-II coverage: 1996+ all passenger cars and light trucks (under 8,500 lb GVWR) sold in the United States, as mandated by EPA OBD-II regulations under 40 CFR Part 86. Protocol coverage by era: 1996–2007 full coverage (all 5 protocols: CAN for early adopters, J1850 VPW for GM, J1850 PWM for Ford, ISO 9141-2/KWP2000 for Chrysler and imports); 2008+ full coverage (CAN protocol for all new models; legacy J1850 and 9141 for carry-over models). Exceptions (no OBD-II port): motorcycles, heavy trucks over 8,500 lb GVWR (use OBD-HD/J1939 instead), pre-1996 vehicles, some non-US-market imports (require EOBD protocol, see below)."
    },
    {
      "@type": "PropertyValue",
      "name": "Vehicle Year Coverage — EOBD (European)",
      "value": "EU petrol 2001+; EU diesel 2004+ (EOBD)",
      "description": "EOBD (European OBD) coverage under EU Directive 98/69/EC: all petrol-engined passenger cars and light commercial vehicles registered in the EU from 2001 model year; all diesel-engined vehicles from 2004 model year. EOBD uses the same OBD-II connector (SAE J1962) and overlapping protocols (ISO 15765-4 CAN for modern vehicles; ISO 14230-4 KWP2000 and ISO 9141-2 for 2001–2008 European petrol). This scanner supports EOBD protocols. Note: EOBD standard codes are a subset of US OBD-II codes; OEM-enhanced European coverage (BMW, Mercedes, VAG group) not included in this unit."
    },
    {
      "@type": "PropertyValue",
      "name": "Wireless Protocol",
      "value": "Bluetooth 4.0 LE (BLE)",
      "description": "Bluetooth 4.0 Low Energy (BLE) wireless interface. iOS compatibility: YES — BLE does not require Apple MFi certification; works with iOS 14+ (iPhone 6s released 2015 and later). Android compatibility: YES — Android 8+ (API level 26+). Unlike Bluetooth Classic (BR/EDR) — used by most generic ELM327 adapters — BLE is compatible with iPhone OBD apps. Compatible apps confirmed: OBD Fusion (iOS/Android), Car Scanner ELM OBD2 (iOS/Android), DashCommand (iOS/Android), Torque Pro (Android only). BLE connection range: up to 10m line-of-sight. Simultaneously usable as standalone handheld scanner (built-in display) OR wirelessly connected to smartphone app."
    },
    {
      "@type": "PropertyValue",
      "name": "App Platform Compatibility",
      "value": "iOS 14+ / Android 8+ — companion app + third-party BLE OBD apps",
      "description": "Companion app: DiagPro Connect (iOS 14+ / Android 8+) — free download; provides OEM-enhanced ABS/SRS/Transmission access that third-party apps do not support (OEM enhanced requires DiagPro's proprietary data libraries). Third-party app compatibility: OBD Fusion, Car Scanner ELM OBD2, and similar BLE OBD apps support Mode 01–06 live data and Mode 03/04 DTC read/clear using standard OBD-II PIDs only — OEM enhanced codes require DiagPro Connect app. Standalone use: all functions available on 2.8-inch TFT color touchscreen without any app or phone connection."
    },
    {
      "@type": "PropertyValue",
      "name": "Display",
      "value": "2.8-inch TFT color touchscreen",
      "description": "Built-in display: 2.8-inch (71mm diagonal) TFT color capacitive touchscreen. Resolution: 320 × 240 pixels. Viewable in direct sunlight (outdoor use tested). Interface language: English (additional languages via firmware update). Standalone operation: full access to all scan functions without a smartphone or PC. Battery: rechargeable Li-ion 2000mAh internal battery; 8 hours continuous operation; charges via USB-C (cable included). Can also operate on OBD-II port power (5V from vehicle)."
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "FCC ID",
      "certificationIdentification": "FCC ID: 2ABCD-T3BLE",
      "issuedBy": {
        "@type": "Organization",
        "name": "Federal Communications Commission",
        "url": "https://www.fcc.gov"
      },
      "description": "FCC Part 15 Class B authorization for Bluetooth 4.0 LE radio. Authorization number visible on device label."
    },
    {
      "@type": "Certification",
      "name": "CE Mark",
      "issuedBy": {
        "@type": "Organization",
        "name": "European Commission"
      },
      "description": "CE marking per Radio Equipment Directive (RED) 2014/53/EU and RoHS Directive 2011/65/EU. Complies with EN 300 328 (BLE radio), EN 62368-1 (electrical safety), and EN 55032 (EMC emissions)."
    }
  ],
  "offers": {
    "@type": "Offer",
    "price": "189.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
</script>

Scan Tool Capability Tier Comparison

Wireless Protocol iOS/Android Compatibility Matrix

OBD-II Scan Tool Metafield Namespace Reference

5 Critical OBD-II Scan Tool Schema Mistakes

1. Encoding "supports OBD-II" without specifying which protocols. There are five distinct OBD-II physical layer protocols, and a scanner that supports only CAN (ISO 15765-4) will not communicate with pre-2008 GM vehicles (J1850 VPW), pre-2008 Ford vehicles (J1850 PWM), or pre-2005 Chrysler, European, and Asian vehicles (ISO 9141-2 / KWP2000). "OBD-II compatible — 1996+" implies full compatibility across all vehicles from 1996 onward when it may only function on 2008+ CAN vehicles. Every supported protocol must be listed as a distinct additionalProperty entry. AI agents matching "OBD-II scanner for 2003 Ford F-150" cannot evaluate protocol compatibility from "OBD-II compatible" alone.
2. Calling all scan tools "professional" without encoding capability tier. A $25 code reader and a $1,500 bidirectional professional scanner are both "OBD-II scan tools" that "read fault codes." The capability tier — the difference between a Tier 1 basic code reader, Tier 2 full OBD-II scanner, Tier 3 enhanced with ABS/SRS, and Tier 4 bidirectional — is the primary purchase decision criterion for a buyer who knows what they need. Encoding a Tier 1 product as "professional-grade OBD-II scanner" without a capability tier descriptor guarantees that buyers who need ABS code reading (Tier 3) or ABS brake bleeding (Tier 4) will purchase an inadequate tool. Encode capability tier explicitly with what the tool can and cannot do.
3. Not encoding wireless protocol iOS compatibility — Bluetooth Classic doesn't work with iOS. "Wireless OBD-II adapter with Bluetooth" describes two completely different products: a Bluetooth Classic adapter that works on Android but not iPhone, and a BLE adapter that works on both. Buyers purchasing for iPhone who receive a Bluetooth Classic adapter have a non-functional product — generic Bluetooth Classic OBD adapters do not carry Apple MFi certification and cannot pair with iPhone OBD apps. Always encode the specific Bluetooth version: "Bluetooth 4.0 LE (BLE) — iOS compatible" vs "Bluetooth Classic BR/EDR — Android only." This is one of the highest-return corrections an automotive electronics retailer can make to reduce returns.
4. Missing vehicle year coverage context — "1996+" is technically correct but doesn't help a buyer with a 2006 Toyota. "OBD-II coverage from 1996" without protocol context creates a false expectation. A 2006 Toyota Camry uses ISO 9141-2 or ISO 14230-4 KWP2000 — if the scanner supports CAN only, it will not communicate with this specific vehicle despite the "1996+ coverage" claim. The vehicle year coverage must be paired with protocol information: "1996–2007 vehicles: supports J1850 VPW (GM), J1850 PWM (Ford), ISO 9141-2 and KWP2000 (Chrysler, European, Asian); 2008+ vehicles: ISO 15765-4 CAN." A year range without protocol breakdown misleads buyers into purchasing incompatible tools for pre-CAN vehicles.
5. Not distinguishing OBD-II standard J1979 PIDs from OEM-enhanced codes — many buyers need ABS/SRS codes which are manufacturer-specific. The most common scan tool return situation: buyer purchases a "full OBD-II scanner" to diagnose an ABS warning light, then discovers the scanner reads only powertrain P-codes and cannot access the ABS module. ABS, SRS airbag, automatic transmission, and TPMS codes are outside the SAE J1979 OBD-II standard. They are manufacturer-specific codes that require OEM data library licensing. A full Tier 2 OBD-II scanner is genuinely incapable of reading ABS fault codes regardless of vehicle make or year — it is not a limitation of the scanner's quality, it is a protocol boundary. Encode OEM-enhanced coverage with specific make names and the systems covered (ABS/SRS/Transmission) so AI agents can correctly route buyers with non-powertrain warning lights to Tier 3 products.

Related Guides

• Shopify Vehicle Parts Fitment Schema — Year/Make/Model Compatibility Structured Data
• Shopify Automotive Accessories Schema — Structured Data for Car Parts
• Shopify Electronics & Hardware Schema — Connectivity, Protocol, Specification Structured Data
• Ecommerce Product Specifications Schema — Technical Spec Structured Data
• CatalogScan Blog — AI Shopping Agent Optimization