SSH EnergyStorage Sourcing
BUYER GUIDES / TENDER

BESS Tender: Which Documents to Request and Why

· SH Energy editorial

A tender file is not a folder of certificates. It is a set of answers.

Every document you require should map to a question someone will ask later — at evaluation, at customs, at commissioning, or at the first failure. If a document answers no question, it adds pages and no protection. Here is the mapping, and the wording that makes bids comparable.

1. Start from the questions, not the documents

Tenders often inherit a document list from a previous project. The list grows, nobody removes anything, and bidders respond with whatever they have most of. A cleaner approach is to write down the five questions first:

Each answer needs a specific document. Anything outside that set is optional.

2. Product safety evidence: name the model and the standard

The requirement that produces comparable answers is not "certificates required". It is:

Evidence of assessment against the named standard, for the exact model and configuration offered, naming the issuing laboratory and the holder.

Two things make this work. First, the model — a family brochure cannot tell you which tier is covered. Second, the document type. A verification of compliance issued by a testing laboratory is not an accreditation certificate from a certification body, and the two should not be used interchangeably. A tender that asks for "certified" and accepts either gets neither reliably.

Where a model holds no such evidence, the response should say Not held. That is a usable answer: you can weigh it, price the risk, or require an alternative model. A vague "available on request" is not.

3. Transport documents: per shipment, not per project

Carriage documents are checked against a shipment, not against a tender. Ask for:

Two practical notes. The carrier has the final say on what it accepts, so a document that worked last year is not a guarantee for this booking. And the summary must match the type being shipped — a similar model in the same family is not a substitute.

4. Datasheet: the only place capacity belongs

Capacity, power and operating limits come from the datasheet, and the datasheet should be required for the exact model. Certificates typically identify the model, not the energy in kWh — so a tender that expects capacity on a certificate is asking for something that generally does not exist, and will receive a typed-in number instead of evidence.

Ask explicitly: state the nameplate and usable capacity, the definition of usable capacity used, and the datasheet revision.

5. The pairing statement

Battery and inverter compatibility is the most under-documented part of most tender files. The useful requirement is a written statement covering:

"The port exists on both units" is not evidence. Neither is a marketing compatibility list without model numbers. For the detail behind this, see four compatibility checks.

6. The after-sales path

This section is usually one line in a tender and three weeks of argument in practice. Ask for:

The RMA evidence checklist covers what a claim actually needs; a tender that requires it in advance avoids the argument later.

7. Copy-ready tender requirement set

1. Model and configuration offered, stated exactly 2. Product safety evidence for that model: standard with year, issuing laboratory, holder, or "Not held" 3. Datasheet for that model: nameplate and usable capacity, usable capacity definition, revision 4. Transport pack for the shipment: UN 38.3 summary, MSDS, sea-transport appraisal where required 5. Written pairing statement: battery and inverter model, firmware, interface, protocol, confirming party 6. After-sales path: RMA destination, evidence list, spare parts recommendation, named contact 7. Declaration of what is not held, for each of the above

The last line is the one that changes behaviour. A supplier who declares what it does not hold is telling you its file is audited. A supplier that answers everything affirmatively, on a model that plainly has gaps, has told you something else.

8. How to score the answers

Three grades are enough for most evaluations:

That last habit matters. A tender process that punishes honesty produces bids that shade the truth, and the shading surfaces at commissioning — the most expensive moment to find it.

Where this fits

Our own model-by-model position, including where we hold nothing, is on the documents centre. If you are preparing a tender and want the pack for a named model, start at the partner desk.

FAQ

What documents should a BESS tender ask for?

Ask for the ones that answer a specific question: product safety evidence for the exact model, transport documents for the shipment, the datasheet for capacity and power, a written compatibility statement for the pairing, and a defined RMA path. A file of unrelated certificates answers none of them.

Should a tender require a certification-body certificate?

Only if the standard and the document type are both named. Many suppliers hold a verification of compliance issued by a testing laboratory, which is a different document from an accredited certificate. Requiring one while accepting the other makes the evaluation meaningless in both directions.

Why ask for documents per model rather than per family?

Because evidence attaches to a model and configuration. A family brochure cannot tell you which tier is covered, and it cannot be audited. Naming the model in the requirement is what makes the answers comparable between bidders.

What belongs in the transport pack?

A UN 38.3 test summary and an MSDS matching the cells or batteries being shipped, plus a sea-transport appraisal where the mode requires it. The carrier decides what it accepts, so the pack is confirmed per shipment rather than assumed from a previous one.

Send the requirement set to a supplier

If you want it answered for a named model, send the list to jimmy@sunhongenergy.com, or message the desk on WhatsApp.

Scope

This guide describes how to specify and evaluate tender documents. It states no prices, lead times or warranty terms. Document status is per model and is confirmed in writing; where a model holds no evidence, the answer is Not held rather than an implied family-wide cover.