How to Resolve Conflicting Electrical Ratings Across Supplier Datasheets

“Rated current” is one of the most overloaded phrases in electrical product data. Standards and manufacturers use several related quantities, and the same symbol appears with different meanings across product families. A catalog that stores one number in one field will eventually contradict a datasheet. This playbook gives a procedure for handling the contradiction without losing information.

Input and audience

• Input: two or more supplier documents (datasheets, catalog pages, or feed rows) that state different current values for what is supposedly one product.
• Audience: product-data and catalog managers who must publish one value, and the electrical specialist who signs off on contested ones.
• Output: a field-level provenance table, an explicit decision per field (canonical, conditional, or unresolved), and an escalation note where needed.

The conflict (illustrative / synthetic)

A contactor appears in two sources under the same type designation.

Illustrative / synthetic. The two sources are not necessarily in conflict. The 25 A value is tied to a motor utilization category and the 40 A value looks like a different category’s figure, but Source B does not say so. That is exactly the situation the steps below handle.

Step by step

1. 1
   Confirm both documents describe the same variant

   Compare the full type designation, coil voltage, number of poles, auxiliary contact configuration and revision of the product. A single suffix can change the electrical rating. If the variant is not confirmed, stop: you have two products, not a conflict. For variant versus duplicate handling see variant vs duplicate vs replacement.

2. 2
   Confirm both numbers measure the same property

   “Rated current” is a label, not a definition. Several related quantities exist, and a datasheet may use the same word for different ones. IEC 60947-1, the general rules for low-voltage switchgear, distinguishes, among others, the conventional free-air thermal current (Ith, the maximum test current used for temperature-rise tests of unenclosed equipment in free air) and the rated operational current (Ie, which is stated per utilization category and voltage). Circuit breakers for household installations under IEC 60898-1 use a rated current In with a reference ambient temperature. Match each number to the exact quantity named in its source, using the table below.

3. 3
   Compare the test and rating conditions

   Record, for each value: ambient temperature, utilization category (for contactors and similar equipment), voltage, frequency, conductor cross section or wire size for terminal and connection products, mounting or enclosure condition, and the governing standard (for example IEC versus UL). A number without conditions is a weaker observation than a number with them.

4. 4
   Check revision and context

   Compare document revision, date and market. A superseded datasheet, a regional catalog, or a catalog page that rounds or simplifies a datasheet value is a weaker source than the current manufacturer document. Note whether the number appears in a table, a headline spec block or a marketing summary.

5. 5
   Record every observation with provenance

   Create one row per source value in a provenance table (below). Do not merge rows. See data provenance and the extraction method in extract product specs from PDFs.

6. 6
   Decide by written rule, not by feel

   Apply a precedence rule agreed in advance, for example: current manufacturer document over distributor page; value with stated conditions over value without; value matching your schema’s property definition over a differently defined one. Output one of three states per field: canonical (rule picks one value for this property), conditional (both values are kept as separate properties or conditions), or unresolved (the evidence does not decide).

7. 7
   Escalate when the criteria are met

   Use the escalation criteria below. The escalation note should contain the provenance rows, the question for the specialist, and what is blocked until it is answered.

Which “rated current” is this?

The attribute library lists how these fields are structured for individual product categories: see circuit breakers and terminal blocks, which now cover rated current aliases, conditions and false friends. Symbols are not unique across product families, so any mapping from a symbol to a field must be conditional on the product category.

Raw to normalized to validated to reviewed

Illustrative / synthetic. Note that Source A also states a 40 A value for AC-1. It matches Source B’s number, which suggests but does not prove that Source B is quoting the AC-1 figure. Record that as a hypothesis, not as a fact.

Field-level provenance table

field,source,doc_date,page,extraction_method,claimed_value,conditions,confidence,review_state
rated_operational_current,SourceA datasheet rev C,2026-03-01,4,table_extraction,25 A,AC-3; 400 V,high,accepted
rated_operational_current,SourceA datasheet rev C,2026-03-01,4,table_extraction,40 A,AC-1; 400 V; 40 C,high,accepted
rated_current_unspecified,SourceB catalog page,2026-06-15,web,html_scrape,40 A,none stated,low,needs_review

Illustrative / synthetic. Keep these rows even after a decision. If a buyer later asks why the catalog says 25 A when the distributor page says 40 A, the table answers it in one lookup.

Preserve contradictions

• Never overwrite a stored value because a newer source disagrees. Add an observation.
• Keep the field-level decision (canonical / conditional / unresolved) separate from the observations that justify it.
• Where both values are true under different conditions, model the conditions as part of the data, for example one value per utilization category or per ambient temperature, rather than forcing one number into one field.
• Date every decision so it can be revisited when a new datasheet revision appears.

A second, simpler pattern: ambient temperature

Some conflicts come from reference temperature alone. Breaker datasheets commonly state a rated current at a reference ambient temperature and then give a derating table for other temperatures. As a published example, a Hager datasheet lists a 32 A breaker as carrying 32 A at 30 °C and less at higher ambient temperatures. A distributor that copies a derated figure from a table and a manufacturer that quotes the 30 °C figure will disagree without either being wrong. Capture the temperature as a condition and store the rated value and the derated values as separate rows.

Exceptions and escalation criteria

Escalate to an electrical specialist (and mark the field unresolved until answered) when any of these apply:

• The definition or test condition behind a value cannot be determined from the source.
• The two documents are different revisions and there is no changelog.
• The value drives a safety, certification or compliance claim (for example a marking, an approval or a regulatory data field).
• The conflict persists after variant, definition and conditions have all been confirmed identical.
• The only evidence for one side is a scraped or OCR value with low extraction confidence.
• A source quotes both IEC and UL figures and your schema has only one field.

Do not escalate when a conflict is fully explained by differing conditions that your schema can hold. Model it and move on.

Checklist and artifact

• Variant confirmed identical (full type designation, voltage, poles, revision)
• Each number mapped to a named quantity (Ie, Ith, In, nominal current, contact rating)
• Conditions captured: ambient temperature, utilization category, voltage, conductor size, standard
• Document revision, date and page recorded
• One provenance row per observation; none overwritten
• Decision state recorded: canonical, conditional or unresolved
• Escalation criteria checked; note written if triggered

The artifact is the provenance table plus a decision record for each contested field.

Related Claro workflow

Claro attaches a source reference and a confidence score to the values it produces, so a value can be traced back to the document it came from. You can run this playbook in a spreadsheet; the benefit of tooling is that every observation stays linked to its page and extraction method as the catalog grows.

Related

FAQ