It Started With a Routine Audit
Back in Q1 2024, I was doing what I do a few times a week—reviewing a batch of incoming industrial gas certificates. This particular shipment was for a hydrogen customer, mid-sized chemical plant. Nothing fancy. I was gonna check the spec sheet, sign off, move on.
But something caught my eye. The certificate said 99.9% purity. Which sounds fine, right? I mean, three nines is basically pure. I almost clicked approve. But I paused, because our contract for this customer specified 99.99%—four nines.
Honestly, I'm not sure why I noticed. The font was small, the cert looked legit. My best guess is that after reviewing a couple hundred of these, your brain starts flagging patterns. But I almost skipped it. Thought what's 0.09% between friends?
The Near Miss That Woke Me Up
Now, here's where it gets interesting. I called the supplier's quality rep, and they said: "Oh, the 99.9% is just a default on our template. The actual product meets 99.99%."
I wanted to believe them. I really did. But I've been around long enough to know that verbal promises and product specs are two different things. So I asked them to reissue the certificate with the correct value, and to send proof of the batch test results.
Three days later, they sent an updated cert—still showing 99.9%.
At that point, I had a decision. I could accept the "it's just a template issue" explanation, or I could hold the line. I knew I should reject the batch, but thought 'we've worked with them for years, what are the odds?' Well, the odds caught up with me when I remembered a story from a colleague: a similar purity discrepancy had ruined a catalyst bed in a specialty chemical plant. The repair cost? Over $22,000 and a three-week shutdown.
I rejected the batch.
What Happened Next
The vendor was not happy. They had to re-analyze the product, which meant pulling samples, running lab tests, and reissuing paperwork. It took them another week to confirm the product was actually 99.99%. It was. But the certificate still had the wrong number because of a template error.
We accepted the product, but I added a new requirement to every hydrogen contract since then: the certificate must include the specific batch test result, not just a template default.
The vendor implemented a new verification step on their end too. Now, before any cert leaves their facility, someone has to manually verify that the purity number matches the lab result. Sounds basic. But apparently it was a gap.
There's something satisfying about that—knowing that a simple check prevented a potential disaster. After the stress of that rejection, seeing the updated process in place—that's the payoff.
Here's What I Learned
This whole thing taught me a few things that apply way beyond just hydrogen purities:
- 5 minutes of verification beats 5 days of correction. My hesitation to check that cert saved at least a week of potential rework.
- "It's just paperwork" is a dangerous phrase. The spec sheet is the last line of defense before product reaches your line.
- Don't trust template defaults. Ever. If it looks off, it probably is.
Now, every time I review a gas certificate—whether it's for argon, nitrogen, or hydrogen—I check the purity against the contract spec. Not because I don't trust suppliers. But because I've learned that trust is great, but verification is cheaper.
So if you're sourcing industrial gases, especially hydrogen where contaminants can mess with catalysts or fuel cells—get the cert checked. Or better yet, add a line to your purchase order that says: "Certificate must include batch-specific test results, not template defaults."
Trust me on this one. I've rejected enough batches to know.
Continue The Conversation
If this topic connects to an active project or a planned technology transition, use the inquiry form below and our team will route the discussion to the right engineering contact.
Share the operating context behind your power requirement
Tell us about your site profile, control priorities, and energy transition targets so our team can respond with a more relevant configuration path.