Engineering Notes

What I Check Before Approving Any Solar or Battery Purchase

Renewable energy engineering workspace

The cheapest quote is rarely the cheapest decision

If you're sourcing solar inverters or lithium batteries for a company, don't pick the lowest quote on the sheet. Check two things first: the quality of their technical documentation and whether they can produce a clean invoice. I've seen both fail, and both cost us more than a few hundred dollars in savings were worth.

Here's the short version: a vendor who can't produce a real spec sheet or a compliant receipt will cost you more in time, rework, and finance headaches than any discount they offer.

I manage procurement for a 400-person company across three locations. That means roughly $400k in annual spend across eight vendors—everything from janitorial supplies to the backup power systems we installed at two facilities last year. I report to both operations and finance, so when something goes sideways, I'm the one explaining it.

Why I now read the manual before I read the price

When I took over purchasing in 2020, I had a simple approach: get three quotes, pick the middle one, confirm delivery. That approach lasted about eighteen months.

What broke it was a solar backup project. We were adding battery backup to two offices—mostly to keep servers and security systems running through outages. Not a massive system, but enough that the inverter choice mattered. My first instinct was to treat inverters like any other equipment purchase. Power rating, efficiency, warranty. Compare and buy.

That works until you realize "5kW hybrid inverter" means different things to different vendors. One supplier quoted us a unit where half the settings were locked behind a proprietary app, and the manual was machine-translated. Our installer asked three wiring questions in the first week. Each answer took two days to come back. I wasn't the one installing it, but I was absolutely the one getting emails from our facilities manager asking why the timeline had slipped by a week.

We switched to srne inverters on the recommendation of our installer. The srne 5kW hybrid inverter came with a full manual—wiring diagrams, parameter tables, fault codes, firmware version notes. Not glamorous. But our installer had two questions total that whole installation, because everything was already documented. Those two questions were about site specifics, not basic operation.

I'm not saying srne is the only brand that does this. I'm saying that's the bar I now hold vendors to, and it's why I stopped treating documentation as a nice-to-have.

The marine charger lesson I should have learned the first time

Same procurement cycle, we needed lithium batteries. One of our sites has a workboat that the operations team uses for site surveys along the river. That meant a LiFePO4 marine battery charger, which I initially filed in my head as "just another accessory." I'd used plenty of chargers for office equipment. How different could it be?

Considerably, as it turns out. Marine chargers deal with salt air, vibration, and voltage sags that don't exist in an office closet. The first unit we tried had a datasheet that was one paragraph long. No temperature range listed. I asked the supplier about cold-weather operation and got "should be fine for standard use." I approved it, because we were on a deadline.

Three months later, the charger started thermal-throttling in low temperatures—right during spring runoff, when the boat needed to be ready at a moment's notice. It wasn't a defective product. It was a product whose limits weren't documented, and I hadn't asked the right questions because the documentation didn't prompt me to.

The replacement came from a vendor whose datasheet listed operating temperatures, charge profiles for LiFePO4 chemistry, and a compatibility note with the battery management system we were using. That's what I mean by documentation quality. It's not about marketing polish. It's about whether the vendor has actually characterized their product at the edges, where your problems live.

What "battery storage for renewables" actually requires from a buyer

The battery storage piece of that project taught me a different lesson: you're not just buying cells. You're buying an integration story.

I don't need to understand battery chemistry. I need to understand three things:

  • How the battery communicates with the inverter (protocol, cable, configuration)
  • Whether the vendor's compatibility claims are tested or just asserted
  • What happens when a cell fails—can it be replaced in the field, or does the whole pack become a paperweight?

We ended up with srne's LiFePO4 battery storage for renewables—partly because the integration documentation was explicit about how their batteries communicate with their inverters. That meant I didn't have to call anyone to verify compatibility. The doc answered it.

Not every vendor does this. Some will tell you their battery "works with any major inverter." Push on that. Ask for the test report. Ask which firmware versions. If the answer involves the word "should," keep looking.

The part where I admit I'm out of my depth

Our facilities team recently started planning EV charging for the fleet lot. That's a different beast entirely, and I want to be clear: how to develop an EV charging station app is not in my wheelhouse. I'm a procurement person, not an engineer or a product manager. If you're evaluating a build-vs-buy decision on the software side, get someone technical involved before you sign anything.

What I can tell you from the buying side is this:

  1. Make the vendor demo the app live. Not a recorded walkthrough, not a slide deck. Live. Click through the billing flow yourself.
  2. Have your IT and security people review the data flow before contract signature. Charging apps handle payment data and user access. That's not a "we'll figure it out later" category.
  3. Ask whether you're buying the source code or a license. Those are very different long-term propositions. If you want control over the software, the answer changes the whole deal structure.

I've watched two companies get burned on this because they let hardware-focused procurement logic drive a software decision. The hardware is easy. The app is where the surprises live.

When this approach doesn't apply

If you're putting in a single small solar setup—one inverter, a couple of batteries—going through a local installer who bundles the equipment may be cheaper and lower-risk than sourcing directly from a brand. The installer absorbs the specification risk. That's worth something, and I don't recommend trying to replicate it unless your project is large enough to justify the internal effort.

Also: if your site has critical loads or regulatory requirements, don't let a procurement person like me do your system design. Hire an electrical engineer to write the spec. I can vet a vendor against a spec. I can't write the spec safely.

And one more honest caveat—the documentation standard I'm describing will disqualify some smaller vendors who make decent products but can't write a proper manual. If you have in-house technical staff who can fill those gaps, that's a legitimate tradeoff. If you don't—if you're relying on the vendor's documentation to guide your installer—then don't buy the cheaper option. Buy the one that tells you what you need to know before you need it.

That's not glamorous advice. But it's the difference between a procurement that ends at the purchase order and one that ends with a working system and a clean expense report.

Discuss this topic with Siemens
Adewale Okoye

Adewale Okoye

Adewale Okoye is a battery energy storage systems analyst specializing in containerized BESS, power conversion systems, energy management systems, HVAC, fire detection, auxiliaries, and grid services. He uses IEC 62933-5-2:2025 system-safety requirements and UL 9540A thermal-runaway propagation evidence while measuring usable energy, rated power, dispatch duration, auxiliary demand, round-trip efficiency, response time, state-of-charge limits, and separation assumptions. His engineering guides help developers, utilities, and integrators define system boundaries, safety documentation, control interfaces, performance guarantees, and commissioning criteria.