The question arrives as a choice between two numbers, and the certificate that answers it usually lists both. IEC 62619 and IEC 63056 are not competing options for a home battery; they are two scope statements written for two different market framings, and the useful question is not which one a supplier holds, but what the certificate says it covers. A certificate names a level, a model range, a production site and a report revision. The designation alone names none of them.
The two designations side by side
A home battery sits in the second scope by application and in the first by cell technology, which is why suppliers hold both and why holding one is not automatically a defect. What matters is that the scope statement matches the product being shipped. If a certificate names one model and the shipment contains a variant with a different suffix, the document and the shipment are describing two Products , and no amount of designation reading closes that gap.
The wording that arrives, and how to challenge it
Common phrasing is usually accurate and always incomplete. The four lines below cover most of what reaches a purchase file.
Each of these is a starting point, not an answer. A safety certificate issued at cell level is evidence about cells. It does not establish that the pack built around those cells was evaluated, that its protection thresholds were reviewed, or that the model being ordered was part of the tested range.
The clause worth writing into the purchase file
The practical fix is a clause that forces the four alignment points into one sentence, so that the certificate can be checked against the shipment rather than admired.
The battery shall hold a safety certificate issued with electrical energy storage as the stated scope, naming the manufacturer, the production site, the exact model designation and the report revision. Where protection functions are covered by a separate report, that report shall be identified in the same submission. Any change to the cell model, the cell supplier, the control firmware release or the production site shall be notified in writing before shipment, together with an assessment of whether the certificate remains valid for the changed configuration.
Every sentence in that clause closes a specific risk. The scope statement closes the risk of a certificate that tests something other than what was ordered. The model designation closes the variant gap. The production site closes the second-line risk that appears when volume moves to another plant. The change notification closes the configuration risk, which is the one that arrives quietly, long after the certificate was filed.
What the alignment check looks like
Two questions decide most of these cases. Ask the supplier which report revision applies to the units being shipped, and ask what event triggers a retest or a new report, because a cell substitution and a firmware change are not equivalent events. Ask for the certificate and the declaration as documents, not as descriptions, and put the alignment requirement in writing before the order rather than after the first shipment.
Comparing two suppliers on certification requires the same four items on the same basis. A comparison that sets a system-level certificate against a cell-level report ranks nothing, and a cell-level report measured against a system-level requirement is the scope gap that costs the most time to close. A comparison that ignores the production site assumes a stability that the supply chain does not guarantee.
What cannot be changed later, and what travels with the goods
The certification configuration is fixed at approval. A different cell model, a different control firmware release or a different production site is a different configuration, and the evidence that applied to the first one does not transfer automatically. This is the point where a purchase decision becomes hard to reverse: the certificate was priced into the quotation, and a change after approval means new evidence, a new timeline and a new warranty conversation.
Three further gaps are outside the certificate entirely. Transport classification is a separate document, typically the UN 38.3 transport test documentation issued for the cell or battery design. Grid connection conditions are set by the local network rules rather than by a product standard. Installation requirements, including location and separation, belong to the market's own code. A product certificate is therefore necessary and never sufficient, which is the same position installers reach when an approval is refused after a compliant product was delivered.
What travels with the goods is the last part of the file. The handover pack for each shipment should carry the certificate, the declaration, the report revision and the change history in a form that can be retrieved by serial number months later, because an approval question or a warranty claim is answered from documents, not from memory. The certificate sets behind the packs Ruibit supplies are filed that way, by model and revision, so the scope statement can be checked against the configuration on the order.
Where the file stops and the market rules begin
Certification answers whether a product has been tested and to what scope. It does not answer whether a specific installation will be approved. The connection and installation rules differ by market, and the evidence they require is separate from the safety certificate: G98 and G99 in the United Kingdom, AS/NZS 5139 and the inverter approval route in Australia, VDE-AR-N 4105 in Germany, NRS 097 with municipal registration in South Africa, CEI 0-21 in Italy, and EN 50549 for European connection. Each of those decides something the product certificate does not.
Standards designations must be read against the edition in force for the destination market, and clause-level references are what a purchase file should quote rather than the designation on its own; they were current as of 2026-09. For the certification questions that sit alongside this one, see , the four-point , and what happens when the configuration moves, in . The collects the rest of this cluster.
FAQs
1. Does a home battery need IEC 62619 or IEC 63056?
Both can apply, because they are different scope statements rather than competing options. IEC 62619 covers industrial lithium cells and batteries; IEC 63056 states electrical energy storage as the scope. Ask which of the two the scope page names, at which level, for which model.
2. Is a cell-level certificate enough for a home energy storage system?
No. A cell-level document is evidence about cells. It does not establish that the pack built around them was evaluated, that its protection thresholds were reviewed, or that the ordered model was inside the tested range.
3. What must the certificate name for it to be usable?
Four items, aligned: the product scope, the exact model designation, the production site shipping the units, and the report revision in force. If any one of the four differs from the shipment, the document describes a different product.
4. We already have CE. Is that enough?
It answers a different question. CE is a marking route based on a declaration and a technical file. Ask which directives and which standards the declaration lists, and whether the stated scope covers the exact configuration being ordered.
5. What happens if the cell model or the firmware changes?
It becomes a different configuration, and the earlier evidence does not transfer automatically. The change should be notified in writing before shipment, with an assessment of whether the certificate still applies to what is being sent.
