What Should You Verify Before Procuring the 2026 CATL TENER Sodium Energy Storage System?

A supplier's product announcement looks convincing, but the project-specific delivery scope and acceptance criteria are still unclear.

Fastest fix: treat CATL TENER Sodium procurement as a document-and-test process; do not approve purchase until configuration, guarantees, interfaces, site tests, and remedies are enforceable in the contract.

Who should read this: Project owners translating technical claims into purchase and acceptance conditions.
EPC teams and integrators checking interfaces, configuration, and test responsibilities before design freeze.
Procurement and legal staff assessing delivery schedules, guarantees, and remedies they can enforce.

Last updated October 1, 2026. Delivery status and product statements were checked against CATL’s official announcements; procurement and acceptance guidance was cross-checked against the cited U.S. Department of Energy, NREL, and IEEE materials.

What should CATL TENER Sodium system procurement verify first?

Begin with the evidence that will decide whether the project can be delivered and accepted—not with a headline performance figure. CATL says that the first deliveries of TENER Sodium in China were planned to begin in September 2026. That is a published plan, not evidence that a particular project has shipped, passed inspection, or met a guarantee. Confirm the status of your order directly with the supplier and record the evidence in the contract file. CATL’s announcement describes the planned delivery timing.

A separate CATL announcement may help you understand a public cooperation arrangement, but a partnership announcement does not establish that a specific supplier is authorized to deliver your contracted configuration or assume your project obligations. Ask the bidder to identify the contracting entity, manufacturing and delivery responsibilities, and any subcontractors. Then verify that the named parties accept the responsibilities assigned to them in your contract. CATL’s announcement of a cooperation arrangement is context, not a substitute for project-specific commitments.

Your first gate should be a complete, consistent evidence set:

A project-specific scope of supply and configuration.
A delivery schedule tied to named locations and responsibilities.
Guarantees with test conditions and measurement boundaries.
Interface files that match the project design.
An acceptance protocol with pass criteria and remedies.

The U.S. Department of Energy’s battery energy storage procurement checklist can help structure the request for information and procurement review. Use it as a prompt, not as a replacement for your jurisdiction’s rules, project specifications, or negotiated contract.

During inquiry and tender, pin down what the price includes

A quotation can be difficult to compare when different bidders price different boundaries. Require each supplier to state the battery chemistry and proposed system configuration, included equipment and services, delivery location, exclusions, and who owns each interface. Ask for the documents behind those statements, not just a summary slide.

Keep these items distinct in the tender review:

Equipment scope: Identify the included system components, quantities, revisions, and any options. Ask bidders to distinguish base scope from items supplied by others.
Services: Separate design support, installation supervision, commissioning, training, and ongoing support. A service mentioned in a presentation is not automatically included in the purchase.
Delivery and risk: Define the delivery point, shipping and handling responsibilities, required documentation, and the event that counts as delivery. The project schedule should name dependencies and the party responsible for each.
Evidence status: Label materials as approved project documents, manufacturer publications, preliminary proposals, or third-party evidence. Do not treat them as equivalent.

CATL’s public delivery plan gives you a useful question to put to the bidder: what evidence supports the delivery date for this project, at this location, under this contract? Ask for a dated schedule, confirmation of the ordered configuration, and the conditions that could change the date. If the supplier cannot support the proposed timing with project-specific evidence, retain a contractual remedy rather than relying on a public forecast.

A common tender risk is comparing one complete offer with another that leaves controls, commissioning, or testing to the owner or EPC. The lower price may carry additional cost, schedule exposure, and coordination work. Make the exclusions visible before bid evaluation, then ask each bidder to price or explicitly assign responsibility for the same scope.

Before signing, turn performance language into testable guarantees

Words such as capacity, efficiency, availability, response, and degradation are not self-executing guarantees. For every value that affects project economics or acceptance, write down what is measured, where it is measured, under which conditions, by whom, and what happens if the result misses the agreed threshold.

A contract schedule should address:

Capacity: Define the measurement point, operating state, permitted auxiliaries, environmental conditions, and test procedure. State whether the figure applies at the battery, system, or grid connection boundary.
Efficiency: Specify the charge and discharge method, energy accounting, auxiliary loads, operating range, and test duration. Do not compare values that use different boundaries.
Availability: Define eligible operating hours, planned maintenance treatment, exclusions, data source, and calculation method. Clarify whether availability applies to equipment, the complete system, or a defined service.
Response capability: Set the command, measurement point, operating conditions, tolerance, and test method. Identify which controller or external system issues the command.
Degradation: State how it is measured over time, how operating history is considered, and what action follows a deviation. A year-by-year warranty statement needs a method for verifying the result.

The DOE’s battery energy storage performance evaluation method is useful when defining measurement and evaluation boundaries. NREL’s energy storage technical due diligence report provides another reference for organizing technical review. Neither resource makes a supplier’s marketing figure a project guarantee; the signed documents must still set the applicable conditions and remedies.

Do not accept “performance subject to final testing” as a complete term. Define the test, the witness rights, the record of results, the retest process, and the consequence of a confirmed shortfall.

For each guarantee, negotiate a remedy that fits the project: correction, repeat testing, replacement, agreed compensation, or another expressly defined outcome. Specify who pays for the retest, what happens if the parties disagree about results, and how a dispute affects delivery acceptance or payment. A general promise to “work together” does not tell your team what to do when a test fails.

At design freeze, close the interface gaps

A system can have technically sound components and still create project problems when the interfaces do not match. Before design freeze, review the electrical, thermal management, fire protection, communications, battery management system (BMS), and energy management system (EMS) documents against the project design. For each interface, identify the document revision, approving party, and outstanding decision.

Ask the supplier and integrator to confirm:

Electrical connection points, protection responsibilities, and required project inputs.
Thermal and fire-system interfaces, alarms, and response responsibilities.
Communication protocols, signals, data ownership, and failure behavior.
BMS and EMS command authority, operating modes, and alarm handling.
Applicable grid studies, test requirements, and the party responsible for evidence.

If a proposal says the system is compatible with a platform or can reduce repeat certification work, request formal, project-specific evidence. That evidence should identify the relevant equipment, versions, scope, and limitations. A general compatibility statement cannot establish that your site, local approval route, or final configuration is covered.

Grid-related verification also depends on the applicable rules and project design. The IEEE 1547.1-2020 standard page identifies a standard for testing conformance of distributed energy resources to interconnection requirements. Confirm with the responsible engineer and authority which standards and tests apply to your project; a reference to a standard alone does not prove that the installed system has passed the required tests.

At delivery, compare the shipment with the approved configuration

Treat receiving inspection as a formal project hold point, not a quick visual check. Before equipment is installed, compare the physical delivery and its records with the purchase order, approved drawings, and contracted configuration. Capture discrepancies while the evidence is accessible and before they become difficult to distinguish from installation changes.

Check and record:

Equipment names, model or configuration identifiers, and nameplates.
Serial numbers and their match to the packing and quality records.
Packing list, quantities, accessories, and any separately shipped items.
Hardware, software, and firmware versions where they are contractually controlled.
Visible transport damage, packaging condition, and required shipping records.
Certificates, inspection records, manuals, and approved drawing revisions.

For every mismatch, record what was expected, what arrived, the evidence, who owns the resolution, and whether installation must pause. Keep an issue log with a responsible party and closure evidence. A supplier email saying that a replacement part is on the way may be useful, but it does not close the discrepancy until the project team confirms resolution and updates the controlled records.

At site acceptance, test the installed system under project conditions

Factory tests, demonstrations, site acceptance tests, and operating data answer different questions. A factory test can establish that a defined unit passed a defined procedure before shipment. A demonstration can show a selected function. Site testing checks the installed system, its interfaces, and project-specific operating behavior. Long-term operating data can show trends that a short commissioning test cannot.

Before the test window, approve a method statement that identifies test sequence, prerequisites, instruments, measurement points, data retention, witnesses, and pass/fail criteria. Include project-specific checks for:

Start-up and shutdown under the agreed procedure.
Charge and discharge commands across the operating modes needed by the project.
Protection functions, alarms, trips, and recovery behavior.
Communications between system controls and project monitoring or dispatch systems.
Grid-facing functions and operating limits specified for the site.
Recording, review, and sign-off of raw data and test exceptions.

Do not let a single successful demonstration stand in for system acceptance. If one function passes but a required communication path, protection action, or operating mode does not, record the result against the relevant acceptance criterion. Specify whether the system can be conditionally accepted, what must be corrected first, and whether payment or warranty milestones depend on closure.

A common acceptance scenario

Suppose a delivered unit starts and charges during a demonstration, but the project’s EMS cannot issue one required operating command. The demonstration proves that some local functions work; it does not establish that the project interface is complete. Keep the test open, preserve the logs, assign the interface fix, and repeat the affected test after correction. The contract should say whether the retest is witnessed and who pays for it.

After grid handover, keep performance verifiable

Acceptance is not the end of evidence collection. At handover, assemble the operating and maintenance manuals, final configuration and version records, approved drawings, warranty contacts, spare-parts arrangements, monitoring access, and incident response process. Confirm that the owner’s team can access the data required to check the guarantees after commissioning.

Define how a later performance deviation will be handled:

Which operating data and event records must be retained.
Who can access the monitoring system and export the relevant records.
How the parties determine whether project conditions met the guarantee assumptions.
Who can request a repeat test and who pays for it.
What notice, corrective action, and response deadlines apply.
How a confirmed deviation triggers warranty review or another remedy.

The DOE guidance on post-acceptance performance assurance is a reference for maintaining performance oversight after acceptance. Use it to prompt your handover planning, then put the project’s actual data access, review, and remedy process into the contract and operating documents.

Procurement release checklist

Do not release the purchase order or sign off the acceptance milestone until the relevant items below are checked and supported by controlled project records.

[ ] The supplier has identified the contracting entity, supply scope, configuration, delivery location, and responsibility boundaries.
[ ] The delivery schedule is project-specific, supported by evidence, and linked to a remedy for supplier-caused delay.
[ ] Each performance guarantee states test conditions, measurement boundary, test owner, pass criteria, and remedy.
[ ] Electrical, thermal, fire, BMS, EMS, and communications interfaces have current documents and named approvers.
[ ] Compatibility or certification claims are supported by evidence that applies to the project configuration.
[ ] The receiving team has a plan to verify names, serial numbers, quantities, versions, transport condition, and quality records.
[ ] The site acceptance procedure covers project operating modes, protection, communications, and applicable grid tests.
[ ] Factory results, site results, and operational performance records are kept distinct.
[ ] Open deviations have owners, closure evidence, and defined consequences for acceptance or payment.
[ ] Handover includes monitoring access, maintenance documents, warranty contacts, spares, and a post-acceptance performance process.

Frequently asked questions

What documents should I request from a CATL TENER Sodium supplier?

Request a project-specific scope of supply, bill of materials, delivery schedule, configuration and version records, interface documents, test procedures, quality records, warranty terms, and the proposed acceptance protocol. Ask the supplier to identify which documents are approved for your project and which are preliminary. Tie each performance claim to a test method, measurement boundary, responsible party, and remedy if the result falls short.

How can I check delivered battery equipment against the contract?

Compare the approved configuration and bill of materials with purchase-order documents, nameplates, serial numbers, packing lists, software or firmware versions, and quality records. Record any mismatch before installation, assign an owner and due date, and keep evidence of closure. Do not treat a matching container label or packing list as proof that the installed system has the contracted capacity or operating capability.

Which site tests belong in sodium-ion storage acceptance?

Use the signed acceptance protocol to test start-up, charge and discharge control, protection trips, communications, operating modes, and grid-related functions that apply to the project. State the site conditions, instruments, measurement points, test duration, witnesses, and pass criteria in advance. Factory demonstrations can support verification, but they do not replace tests of the installed system under the project's agreed operating conditions.

What should I do if storage performance misses a contract guarantee?

Follow the contract's measurement and notice procedure first. Preserve raw test data, confirm that the agreed conditions and measurement boundary were met, and request a witnessed retest if the method permits one. The contract should then define correction, retesting, replacement or other remedies, cost allocation, deadlines, and any warranty consequences. Avoid relying on a general promise to investigate without a defined resolution path.

A disciplined storage system procurement process can still leave your team with a separate operational burden: comparing tender files, tracking revisions, and reviewing test records across different project environments. Shared workstations can create access and version-control complications; a cloud desktop may add network dependence; buying dedicated hardware can be excessive for a temporary review or integration task. A rented Mac is not a substitute for site engineering tools, local compliance expertise, or a system acceptance test, and it may not suit workloads that require specific Windows-only software or physical interfaces. But if your team needs a temporary, dedicated Mac environment for document review or compatible development work, Kvmzen’s Mac rental use cases can help you assess whether rental fits. Use Kvmzen’s contact page to discuss a temporary setup; keep the procurement decision itself anchored to project documents, supplier commitments, and witnessed acceptance evidence.