FAQ - OEM Subscription

1. What is an OEM Subscription? 

An OEM Subscription allows Azuga to receive vehicle data directly from the vehicle manufacturer (OEM). This includes odometer, diagnostics, fuel information, and other telematics data without requiring a physical device. 

2. What do the “Subscribed,” “Pending,” and “OEM Candidate” statuses mean? 

• Subscribed – The vehicle is successfully connected and actively sharing OEM data. 
• Pending – The subscription request is initiated but awaiting confirmation from the OEM. 
• OEM Candidate – The vehicle is eligible for OEM data integration but not yet subscribed. 

3. What does “Candidate” mean? 

“Candidate” indicates a vehicle that currently uses an OBD device but is OEM-capable based on its VIN. This makes it easy to identify vehicles that could transition to OEM data connections. 

4. What new features are included in the OEM details drawer? 

The OEM details drawer displays: 

• Vehicle name, VIN, make, model, and group 
• Status indicators for Consent, Subscription, and Tracking 
• An Activity Timeline of recent events 
• Troubleshooting and Resolution Actions panels 
• A Resources panel with direct links to OEM-specific documentation.  

5. How does OEM compatibility checking work? 

• The system checks VINs to determine if they are OEM-compatible. 
• For vehicles already in Azuga, this check runs automatically. 
• For new VINs, you must still verify them manually via the Compatibility Checker. 
• Edge cases: brand-new or not-yet-manufactured models may temporarily show as “incompatible.” 

6. How are consent and subscription handled for OEM vehicles? 

• Some OEMs require two levels of consent: 
• Fleet-level consent (organization-wide) 
• Vehicle-level consent (specific VIN) 
• The Subscription object links the OEM vehicle to Azuga and tracks its activation status. 
• Once active, the subscription automatically associates the VIN with the vehicle record in Azuga. 

7. What does the “Offline” status indicate for OEM vehicles? 

Offline means Azuga has not received data from the OEM for a defined period. 

• Currently, this threshold is 3 days of inactivity. 
• OEM partners recommend extending it to 7–14 days, as OEMs report less frequently than OBDs. 
• This logic may evolve based on feedback from field teams and customer interactions. 

8. How can users identify whether a vehicle is connected via OEM or OBD? 

• On the Vehicle Admin Page, use the Data Source Filter to view vehicles by connection type. 
• Typing “OEM” in the search bar quickly isolates OEM-connected vehicles. 
• OEM serial numbers start with 999… — a simple way to distinguish them. 
• A future update will replace the generic vehicle icon with an OEM logo for quick identification. 

9. When can customers safely remove their OBD devices? 

Once the OEM subscription is active (status: Subscribed, and data visible on the map), customers can safely unplug their OBD devices. The system ensures OEM data is live before recommending removal.  

10. How long should a vehicle be offline before considering it a problem? 

While 3 days is the current threshold, OEMs suggest a longer window (up to 14 days).  Azuga is evaluating this logic based on real-world customer feedback to strike the right balance between timely alerts and avoiding false positives.