EV charging station translation, charger display terminology and kWh pricing: a correct translation must let a driver identify the connector, know whether charging has started, understand the complete tariff and stop the session safely. It must not turn a maximum charging power into a promise or turn a time-based occupancy fee into an energy fee. This guide shows how to translate charging instructions accurately across languages without making the technology or payment terms say something different.
People searching for EV charging translation, CCS2 versus Type 2, charger screen localisation, kilowatt versus kilowatt-hour, EV charging cost per kWh, idle fee meaning, payment authorisation, charging session receipt and public-charger error messages need more than vocabulary. They need a tested relationship among words, hardware, price units and user actions. An error in any one part can change which connector they select, when they return to move the car or what they believe they owe.
Did you know that a charger labelled ‘150 kW’ may deliver far less power to a particular vehicle during part of a session? The United States Department of Energy’s Alternative Fuels Data Center describes charging equipment and connector differences; the European Union’s Alternative Fuels Infrastructure Regulation sets public charging price-disclosure rules for relevant EU stations. Neither source makes a single worldwide tariff. The lesson is to translate the specific product or jurisdiction on the screen, rather than a convenient generalisation.
The visible problem: a correct-looking translation can mislead a driver
Imagine arriving late at a public charger with limited battery charge. The translated display says ‘fast charging guaranteed’, ‘price 0.39 per minute’ and ‘payment complete’. The underlying source actually said ‘up to 150 kW’, ‘€0.39 per kWh’ and ‘authorisation accepted’. All three phrases are fluent; all three are wrong. Together, they change the estimated journey time, bill and sense of whether the equipment is working. That is the practical cost of translating labels without the system they describe.
Unlike a travel brochure, a charger interface is an operational sequence. A user first checks a connector, then the terms, then a payment method, then the charging state, then the bill. Accurate translation therefore includes physical units, software status, customer action and financial conditions. A technically impressive translation fails if the driver cannot use it correctly or if support staff cannot reconcile the resulting receipt.
The canonical job of this article is narrow: public electric-vehicle charging displays, connector labels, energy and time-based prices, session states, payment authorisation and receipts. It is not a general article about electrical engineering, battery chemistry or global transport regulation. That distinction helps readers choose the right guide and keeps the translation rules tied to something observable.
First principles: what cannot change when charging information changes language
1. Power versus energy
A charging station rated at 150 kW advertises potential instantaneous power, not a promise that every vehicle will receive 150 kW. A receipt showing 24.6 kWh records energy delivered over time, not the charger’s peak rating. Treat kW and kWh as separate facts and check every occurrence of the unit.
The practical boundary is this: An unchanged number next to the wrong unit can produce an apparently plausible but technically false translation. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
2. Connector versus charging protocol
Type 2, CCS Combo 2, SAE J1772, CHAdeMO and J3400 refer to interfaces or connector families in different markets. A connector label is not a word that should be creatively translated. Keep the designation, explain only when the context demands it and do not assume that an adapter makes every vehicle compatible.
The practical boundary is this: Regional connector availability and the vehicle’s own port determine practical compatibility, not the translator’s preference. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
3. Available power versus delivered power
A posted maximum is equipment capability; a vehicle may draw less because of its battery state, battery temperature, onboard limits or power sharing. Translate ‘up to’ faithfully, keep estimated charging times conditional, and never replace a maximum with a guaranteed speed.
The practical boundary is this: The difference is crucial when a driver plans a stop on a long trip. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
4. Price components
A station may price by energy, time, session, occupancy or a combination. Read the tariff as a schedule rather than a single headline price. Preserve the currency, unit, tax statement, start time and conditions of every fee.
The practical boundary is this: A cheap energy rate can still produce an expensive session if an undisclosed time or occupancy fee is silently dropped. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
5. Charging state versus parking state
Available, preparing, charging, finishing, suspended and faulted are not synonyms. Some displays distinguish a plugged-in cable, an authorised session, actual energy transfer and the release of the connector. A translation must identify the stage the user has reached.
The practical boundary is this: Telling a driver that charging has started when the session is only authorised can create a serious planning error. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
6. Ad hoc payment versus account roaming
Ad hoc charging generally concerns paying without a long-term contract with that operator. Roaming, automatic authentication, membership prices and app-based payments may involve different billing organisations. Translate who charges the customer and which tariff applies, not merely how the screen looks.
The practical boundary is this: The user needs to know whether the displayed amount is the operator rate or the final service-provider rate. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
7. Time boundaries
A per-minute idle fee may start when the car stops drawing energy, when the session ends, after a grace period or by another rule stated by the operator. Preserve the actual trigger. Clock time, elapsed duration and local time zone should not be exchanged.
The practical boundary is this: Changing ‘after charging completes’ to ‘after unplugging’ reverses what the fee is meant to discourage. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
8. Session and receipt identity
Transaction ID, station ID, connector ID, authorisation reference and receipt number may look linguistic but often serve as audit keys. Preserve character order, leading zeroes, punctuation and relevant identifiers. Translate the label around the identifier, not the identifier itself.
The practical boundary is this: Without a stable reference, a customer cannot challenge a charge or report a faulty dispenser accurately. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
9. Fault and safety instructions
A charger warning about a damaged cable, connector overheating, emergency stop or a locked plug is an instruction with consequences. Preserve any prohibition, waiting requirement and authority to contact. Do not turn ‘do not disconnect’ into a friendly suggestion.
The practical boundary is this: Safety copy has a different review priority from promotional descriptions. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
10. Jurisdiction and tariff scope
There is no single worldwide tariff or connector standard. The EU Alternative Fuels Infrastructure Regulation contains specific public-charging transparency duties, while other jurisdictions have different rules and commercial practice. Identify the market and date before presenting any rule as universal.
The practical boundary is this: An accurate translation separates what a display says from what a particular law requires. To verify the target, compare the original label and its actual effect on the customer. A translation review should ask what a driver would do, what quantity would be counted and which operator record could prove the displayed claim. If those answers differ between languages, the sentence still needs work.
A repeatable ten-stage translation method
Use these stages in order, but do not force every project into the same tool. A photographed charger screen, a mobile app resource file and a network provider’s billing export have different evidence available. In all three cases, build a traceable route from source string to operational effect.
Step 1: Capture the entire screen sequence
Photograph or export the start screen, tariff screen, authorisation prompt, live session, stop screen and final receipt. Note which text appears before or after payment and whether it changes as the session progresses.
A one-line string list cannot show a translator whether ‘Stop’ cancels payment or ends energy transfer. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 2: Build a field ledger
Record the exact label, number, unit, currency, status, connector designation, button behaviour and source screenshot location. Add a column for items that must remain unchanged.
A useful ledger separates translatable user language from protected operational data. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 3: Map the payment calculation
Break the total into energy price, time charge, session charge, occupancy fee, tax and possible service-provider additions. Where rules are incomplete, mark them as unresolved rather than guessing.
Readers should be able to reconstruct a hypothetical invoice from the target text without discovering an extra fee. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 4: Confirm who is speaking
Identify the station operator, the mobility-service provider, a payment processor and the vehicle manufacturer where applicable. Keep notices attributed to the right actor.
‘We will refund’ must not be translated as a promise from an operator who only refers the driver to another company. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 5: Confirm connection compatibility
Inspect the interface label separately from the charge standard and the charging mode. Preserve AC versus DC, socket versus tethered cable, and whether an adapter is supported.
A charger advertising CCS cannot be presented as a Type 2 AC session just because the shapes are related. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 6: Preserve conditional words
Protect ‘may’, ‘up to’, ‘estimated’, ‘when available’, ‘after’, ‘unless’ and ‘excluding’. Translate them as operational conditions rather than as polite decoration.
A short qualifier can be more important to correct use than a full sentence of marketing copy. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 7: Test status transitions
Simulate the user progressing from plug-in through authorisation, charging, stopping and releasing the connector. Check every translated command against the actual next state.
The best proof of a button label is that the user can predict its result. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 8: Run numerical consistency checks
Check that displayed rate times the billing basis could give the stated illustration; preserve decimal separators under the target locale without changing numeric value. Verify rounding separately.
20.0 kWh at €0.40 per kWh is €8.00 before any extra fee; a translated receipt suggesting €0.80 has failed. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 9: Review safety strings independently
Get a second check of emergency instructions, electrical hazards, cable-release warnings and blocked-bay instructions. Compare original and target action verbs side by side.
Do not allow an attractive translation to neutralise a stop instruction. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Step 10: Perform device and accessibility review
Check line wrapping on small screens, reading order, screen-reader labels and spoken currency or units. Test on a simulated poor network connection and with a long locale string.
A translation that is correct in a spreadsheet but truncated on the charger is not operationally complete. Write a source-side observation, then make the smallest translation that preserves it. A second reader should be able to audit the step without assuming that the person who translated the words also designed the billing system. Record unresolved questions and obtain the responsible operator’s answer before release.
Fourteen worked translation cases: source, tempting error and safer result
The examples below are fictional training records. Prices, equipment, station IDs and session figures illustrate translation logic; they are not live tariffs or promises for a real charger. Quoted ‘source’ text is English for transparent comparison. The same audit works when the original is another language.
Worked case 1: A maximum-power promise
Source: ‘DC fast charger — up to 150 kW.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘This charger delivers 150 kW throughout the session.’ Faithful explanatory English: Safe: ‘DC fast charger — maximum rated power up to 150 kW.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
The displayed specification caps the equipment rating; it does not describe the vehicle’s complete charging curve. A battery can taper its draw, particularly toward a higher state of charge. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Check that the translated screen keeps both the maximum and the conditional wording; compare it with the technical label on the hardware. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 2: The energy receipt
Source: ‘Energy delivered 24.6 kWh; €0.42/kWh.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Charging speed 24.6 kW; €0.42 per minute.’ Faithful explanatory English: Safe: ‘Energy delivered: 24.6 kWh. Energy price: €0.42 per kWh.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
The source records a quantity and its energy-based unit price. The illustration yields €10.332 before rounding and additional charges; the final billed value depends on published calculation and tax rules. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Check original unit placement, currency, decimals and whether the receipt presents a final total or a subtotal. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 3: Two fee types
Source: ‘€0.39/kWh + €0.05/min occupancy fee after charging ends.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘€0.39 per charging minute including parking.’ Faithful explanatory English: Safe: ‘€0.39 per kWh, plus an occupancy fee of €0.05 per minute after charging ends.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
Combining an energy rate with a later time-based occupancy charge destroys the billing logic. The driver needs to know exactly when the second rate begins. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Verify whether the operator defines the trigger as charging completed, session ended or a grace period. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 4: The connector family
Source: ‘CCS Combo 2 / DC / cable attached.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Type 2 slow AC socket; bring your cable.’ Faithful explanatory English: Safe: ‘CCS Combo 2 connector; DC charging; charging cable attached.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
The source makes a practical compatibility claim. CCS Combo 2 must not be replaced with the similarly named Type 2 AC socket, and the tethered cable cannot vanish. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Compare the displayed interface with the station photograph and manufacturer documentation for that market. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 5: A short authorisation
Source: ‘Authorisation successful. Connect vehicle to start.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Charging completed successfully.’ Faithful explanatory English: Safe: ‘Payment authorisation succeeded. Connect your vehicle to begin charging.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
Authorisation is a permission step, not proof that energy has flowed. A driver who sees the bad version may assume a full battery and leave. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Walk through the user journey and confirm that the energy meter remains at zero before connection. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 6: A paused delivery
Source: ‘Charging suspended by vehicle.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Charger permanently out of service.’ Faithful explanatory English: Safe: ‘Charging is paused by the vehicle.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
The cause of a pause matters. A vehicle-controlled interruption may resume; a device fault may require assistance. Do not invent a lasting breakdown. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Cross-reference state messages with the session log and the interface’s recovery instructions. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 7: A pricing preview
Source: ‘Estimated session cost; final charge shown on receipt.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Total amount charged, guaranteed.’ Faithful explanatory English: Safe: ‘Estimated session cost. The final amount will appear on the receipt.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
The estimate is not a completed financial transaction. A target-language interface can be concise without erasing provisional status. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Compare pre-session estimate with post-session receipt; ensure the screen distinguishes both. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 8: A connector release
Source: ‘Stop session before disconnecting connector.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Pull the connector to stop charging.’ Faithful explanatory English: Safe: ‘End the charging session before disconnecting the connector.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
Imperatives preserve order of operations. Reversing the steps could leave a cable locked or cause unsafe use, depending on the equipment. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Test which UI action releases the connector and preserve the manufacturer’s stated procedure. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 9: A roaming condition
Source: ‘Operator price shown. Your service provider may apply additional fees.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘The price displayed is always the total you pay.’ Faithful explanatory English: Safe: ‘Operator price shown. Your service provider may add charges.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
In a roaming arrangement, the customer’s bill can differ from the operator’s ad hoc price. The translation must preserve whose price is visible. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Check the user-facing contract or payment provider statement before any reassurance about the final bill. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 10: Tax disclosure
Source: ‘Rate excludes applicable taxes.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘All taxes included.’ Faithful explanatory English: Safe: ‘The displayed rate does not include applicable taxes.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
A negation can reverse the customer’s price expectation. Currency does not tell readers whether a figure includes tax. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Compare tax language on tariff boards, checkout screen and receipt, and preserve the exact scope. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 11: Unknown station identifier
Source: ‘Station EV-0073; connector 02; session 000984.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Station EV-73; connector 2; session 984.’ Faithful explanatory English: Safe: ‘Station EV-0073; connector 02; session 000984.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
Leading zeroes may be necessary for support and billing reconciliation. These are identifiers, not quantities to be simplified in prose. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Check each identifier character against the backend support interface rather than relying on visual similarity. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 12: A failed payment
Source: ‘Card pre-authorisation declined; no session started.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Your card has been charged and charging is running.’ Faithful explanatory English: Safe: ‘Card pre-authorisation was declined. No charging session has started.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
A failed authorisation must not be recast as a completed debit. Distinguish authorisation, capture, refund and release of a hold in any support message. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Review transaction records, not just the visible charging screen, when diagnosing a user complaint. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 13: An estimated completion time
Source: ‘Estimated time remaining 28 minutes; may vary.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘Charging will finish in exactly 28 minutes.’ Faithful explanatory English: Safe: ‘About 28 minutes remaining; the estimate may change.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
The charging rate can vary with the battery and infrastructure. Treating an estimate as a deadline gives misleading travel advice. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Confirm that the interface recalculates the estimate and that the translation does not promise exact timing. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Worked case 14: The idle-fee exemption
Source: ‘No idle fee during the first 10 minutes after charging completes.’ The source should first be read as a statement about a real charging step or bill, not a bag of words. Inspect the surrounding screen and ask who is expected to act next.
Dangerous rewrite: Bad: ‘An idle fee starts as soon as charging completes.’ Faithful explanatory English: Safe: ‘There is no idle fee for the first 10 minutes after charging finishes.’ These are deliberately contrasted versions to show how a tiny change in a unit, qualifier or state can overturn the meaning even when the language sounds natural.
A grace period is financially meaningful, and the number belongs to a time interval, not the energy price. The key task is not to preserve the exact original sentence order at all costs; it is to preserve every decision-relevant fact. Keep stable designations and numbers, choose clear target-language syntax and make the instruction readable at the point of use.
Verification: Test the fee start time with a simulated session or the authoritative operator tariff. Then challenge the result with a scenario: a driver chooses a connector, authorises payment, observes energy transfer and receives a receipt. Would the target text predict the same outcome? If not, revise and retest before publication.
Common failure modes and the repairs that actually work
Failure 1: kW becomes kWh
A power rating is reported as an energy quantity, so users infer an impossible billing unit. Return to the hardware label, name the physical quantity and check the calculation. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 2: The word ‘up to’ disappears
A technical maximum becomes a guaranteed result. Restore the conditional phrase and add context only if the source permits it. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 3: A connector name is localised creatively
A driver may choose an incompatible socket or cable. Keep the technical designation and verify the region-specific interface. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 4: Per-minute charges are hidden
The user sees only an energy tariff and cannot anticipate occupancy cost. Separate each unit rate and reproduce its trigger. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 5: A price estimate becomes a final receipt
The translation gives a false impression that billing is complete. Label estimates and final charges distinctly. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 6: A pause becomes a failure
Users misunderstand whether energy transfer might resume. Check the charging state and display cause without speculation. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 7: A session stop becomes an emergency stop
The button may have different consequences than the driver expects. Use the precise operational action and test the UI. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 8: Currency formatting changes value
A decimal or thousands separator is misread as a different amount. Apply locale formatting with numeric comparisons. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 9: Receipt identifiers lose zeroes
Support agents cannot locate the reported transaction. Protect identifiers as strings and verify byte-for-byte. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 10: Payment actors are conflated
A promise made by one service appears to come from another. Attribute every tariff, refund and dispute action to its source. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 11: Tax status is reversed
A rate that excludes tax appears all-inclusive. Check every negation and condition in final pricing. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Failure 12: Screen text is truncated
The warning or fee trigger is cut off on a small device. Validate the actual hardware display with long-language examples. The reviewer should point to the specific source field rather than merely saying that the target phrase ‘sounds better’. When financial or physical consequences are involved, the correct repair is demonstrated by a matched calculation, a compatible connector, a verified state transition or the manufacturer’s actual instruction.
Guided practice: apply the method without guessing
Work each miniature case twice. First underline the protected token or condition. Then draft one plain-language target that keeps it visible. Compare your answer with the diagnostic guidance, not just with a model sentence. Translation skill grows when a reader can explain why one alteration changes the transaction.
Practice 1: ‘150 kW charger; vehicle may draw less’
Keep the 150 kW as an equipment maximum and the vehicle limitation as a separate clause. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
Practice 2: ‘Session energy 12.8 kWh’
Name energy delivered, not power or battery capacity, and preserve 12.8 and kWh. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
Practice 3: ‘€0.10/min after 5-min grace period’
Identify the time-based component and state that it begins after five free minutes. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
Practice 4: ‘CCS Combo 2 cable attached’
Retain the connector designation and the tethered-cable fact. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
Practice 5: ‘Payment held pending settlement’
Distinguish a temporary authorisation hold from a final debit. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
Practice 6: ‘Stop charging, then release cable’
Maintain action order and avoid a direct instruction to pull a locked connector. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
Practice 7: ‘Charging paused: vehicle temperature’
Keep the vehicle-side cause and a temporary state; do not invent hardware failure. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
Practice 8: ‘Pricing includes energy and a parking fee’
Separate the fee bases and look for missing units before translating. Next, test a deliberately bad variant: remove a qualifier, replace one unit or change the order of events. Explain precisely which customer action or bill would change. A learner who can detect that failure has acquired a transferable checking skill instead of memorising one phrase.
A quality-control checklist for editors and students
Read the translated start screen with no access to the original. Can you identify the correct cable and connector, the charging speed claim, the unit of payment, taxes or extra fees, and the start condition? Return to the source. The same answers must be recoverable from both versions. Then test a failed authorisation, a suspended session and a stop sequence; error messages matter as much as the happy path.
For calculation checks, retain a small ledger: display price, price basis, energy or time measured, extra fee conditions, net amount, taxes when specified and final amount. Check numeric equivalence before applying locale punctuation. Confirm that device IDs and session IDs remain identical. If the target explanation includes extra background for new drivers, mark it as explanation rather than part of the operator’s original claim.
For human factors, test the display in actual or simulated screen dimensions, with screen-reader software where supported and with a slow connection. An instruction may be truncated after the word ‘not’, which can be worse than a grammar mistake. Someone who has not seen the source should attempt the whole charging journey. Their hesitation is evidence about clarity, not evidence that the reader is unintelligent.
Frequently asked questions
Is kW the same as kWh?
No. kW measures power at a moment; kWh measures an amount of energy. The translator must preserve both the physical quantity and the unit. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
Does a 150 kW station always deliver 150 kW?
No. The actual rate depends on vehicle capability, battery state, thermal conditions and station conditions. Translate maximum as maximum. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
Can I translate CCS2 into Type 2?
Do not replace the name blindly. CCS Combo 2 DC and Type 2 AC are related in some markets but not interchangeable service claims. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
Is a per-minute fee always an idle fee?
No. A station can charge per minute for charging time or for occupancy under specific conditions. Preserve the fee definition. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
Should I convert prices into my reader’s currency?
Only with an explicitly agreed conversion policy, date and rate. Otherwise preserve the source currency and amount as a factual tariff. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
What if the charger screen shows a price without taxes?
Preserve whether tax is included, excluded or not stated. Do not invent a tax outcome. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
What if the operator uses a mobile app?
Identify which information belongs to the station and which belongs to the app or roaming provider; final customer charges may differ. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
How should technical IDs appear?
Treat them as protected strings, including any leading zeroes, hyphens, spaces and case-sensitive codes. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
Can AI translate a charger interface?
It can produce a draft but should not verify technical units, payment rules or device behaviour without authoritative records and testing. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
What is the fastest quality check?
Reconstruct one session from tariff preview to receipt, including an error state. If the translated interface predicts the same actions and costs, it is closer to reliable. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
Do EU public-charging rules apply worldwide?
No. European Union requirements are jurisdiction-specific. Other markets may have their own laws and pricing practice. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
When should a translator escalate?
When source rates, fee triggers, compatibility statements, payment roles or safety procedures are ambiguous. Clarification is better than a confident invention. In practice, preserve the source evidence, identify whether a claim is an amount, status, condition or instruction, and test the translated wording at the exact stage where a driver sees it.
What to read next
For a parallel high-stakes example, see translating NAVTEX navigation warnings, where cancellation and timing rules also matter. The guide to food allergen labels explores another field in which warning language must not be softened. If your problem is general word choice, return to the Vocabulary Learning Hub and How English Works for background on precise meaning and readable explanations.
Sources and scope
Technical descriptions and regional pricing requirements were checked against the U.S. Alternative Fuels Data Center and the EU Alternative Fuels Infrastructure Regulation. Regulations and tariffs change, and a local operator’s current display and terms govern the individual session. This is educational translation guidance, not an equipment compatibility certification or a binding quote.