# Integration considerations

## Device linking recommendations

Encourage all users to link a [compatible charger](https://developers.enode.com/brands?asset-type=charger). Pairing improves command reliability and enables features that depend on consistent control.

Frame the request based on the vehicle's standalone capabilities. Check the [brands overview](https://developers.enode.com/brands) to determine which approach applies.

### Scenario A: Incapable or unreliable vehicles

Frame linking as mandatory. The user can't activate smart charging without linking their charger.

### Scenario B: Capable vehicles

Frame linking as recommended. The user can proceed with the vehicle alone, but linking their charger provides:

- Faster plug-in detection
- A control fallback if the vehicle goes offline
- `chargeRate` from the charger when the vehicle doesn't report it

## UX recommendations

### Use contextual onboarding

Don't ask users to link both their vehicle and charger in a single flow. Instead, introduce the charger as an optional enhancement (or mandatory step) after the vehicle is successfully linked.

### Communicate the benefit

Be clear about why you're asking for charger access.

#### Example A: Mandatory charger linking

Prompt the user to link their charger after they link their vehicle. Keep the prompt visible until they complete the step, and disable charging until they do.

![Screenshot showing state when charger pairing is required](https://developers.enode.com/images/evc-pairing/EVC-considerations-mandatory.png)

When charger linking is mandatory, tell users upfront—before they start the vehicle linking flow.

![Screenshot showing charger pairing being required early in the linking flow](https://developers.enode.com/images/evc-pairing/EVC-considerations-linking.png)

#### Example B: Optional charger linking

Prompt the user to link their charger after they link their vehicle. Let them dismiss the prompt, and keep charging enabled even without a linked charger.

![Screenshot showing state when charger pairing is optional](https://developers.enode.com/images/evc-pairing/EVC-considerations-optional.png)

### Unlinking chargers

Let users unlink their chargers, but make the implications clear:

- **Mandatory charger:** Unlinking disables smart charging. If they confirm, show the Example A prompt again.
- **Optional charger:** Unlinking reduces reliability but doesn't disable smart charging. If they confirm, stop prompting them to link a charger, but let them re-link through settings.

![Screenshot showing state after unlinking a charger](https://developers.enode.com/images/evc-pairing/EVC-considerations-unlinking.png)

### Capability persistence

Capabilities unlocked by the charger persist as long as both devices remain linked:

- Show users they're still enrolled in smart charging even when the vehicle is unplugged or away from home
- Interventions for charger-provided capabilities stay suppressed
- If we detect the pairing is no longer valid (for example, repeated failed commands while unplugged), capabilities return to `false` and we show any unresolved interventions again

## Rollout considerations

**For new product launches**

Design your linking flow to support both vehicles and chargers from the start.

**For expanding existing use cases**

If you're already live with vehicle-only managed charging, consider a phased rollout. Each phase builds on the previous one.

**Phase 1: Optional charger linking for better reliability**

- **Goal:** Improve charging reliability with minimal changes to your UX.
- **Target:** Existing users who have already linked a vehicle.
- **Approach:** Add charger linking as an optional step. See [Example B: Optional charger linking](https://developers.enode.com/#example-b-optional-charger-linking).

**Phase 2: Mandatory charger linking for unreliable vehicles**

- **Goal:** Fix known reliability issues and reduce support load.
- **Target:** Users with high error rates, frequent support tickets, or vehicles with [Limited reliability](https://developers.enode.com/brands).
- **Approach:** Make charger linking mandatory for these users. See [Example A: Mandatory charger linking](https://developers.enode.com/#example-a-mandatory-charger-linking). Roll out incrementally per brand and monitor performance.

**Phase 3: Mandatory charger linking for incapable vehicles**

- **Goal:** Expand to users with incapable vehicles who were previously ineligible.
- **Target:** Users whose vehicles can't start/stop charging or report location (see [brands](https://developers.enode.com/brands)), but who own a compatible charger.
- **Approach:**
  - Update eligibility rules to allow incapable vehicles when paired with a compatible charger
  - Enable the relevant brands in your app and the Enode Dashboard
  - Make charger linking mandatory. See [Example A](https://developers.enode.com/#example-a-mandatory-charger-linking).

## Supported features

**Better vehicle data**

- `pluggedInChargerId` on the vehicle identifies which charger is connected
- `chargeRate` falls back to the charger's value when the vehicle doesn't report it
- Faster plug-in detection using data from both devices

**Unlocked capabilities**

Linking a charger unlocks capabilities on the vehicle:

- **Charging control:** `startCharging` and `stopCharging` become capable when a charger is linked
- **Location:** `location` becomes capable when it can be inferred from the charger's location
- **Smart Charging:** Vehicles that previously couldn't be controlled become eligible

**Unified control**

Send charging commands to the [Vehicle API](https://developers.enode.com/api/reference#vehicles). When the vehicle is plugged into its paired charger:

- We route commands to the right device automatically
- If unplugged or connected to a different charger, commands go to the vehicle only
- [Smart Charging](https://developers.enode.com/docs/smart-charging/introduction) and [Schedules](https://developers.enode.com/docs/scheduling) use charger controls automatically when executing

[Read next: Integration steps](https://developers.enode.com/docs/ev-charger-pairing/integration-steps)