Skip to content
IBC Recycle USA
Blog · October 15, 2022 · 7 min read

Updating Spec Language: From "Virgin Only" to "Functionally Equivalent"

A lot of corporate procurement language was written in the 1990s and silently bars reconditioned containers — often without any documented reason. Here is the language framework we have helped customers adopt to allow reused IBCs while keeping quality protections intact.

OperationsPost #8 of 34

Get a same-day reply.

Tell us what you need or what you have. We respond within one business day, every business day.

We reply by email — make sure it's correct.
US or Canada number — 10 digits.
US ZIP or Canadian postal code.
* Required · Replies within one business day

The problematic baseline

Common spec language: "All bulk product shall be shipped in new, unused intermediate bulk containers conforming to UN31HA1/Y." This bars reconditioned units entirely, regardless of their UN status or process documentation.

The recommended replacement

A functional-equivalence framework: "Bulk product shall be shipped in intermediate bulk containers conforming to UN31HA1/Y, either new or reconditioned per 49 CFR § 178.801 with documentation of: (a) prior-contents class and acceptability for current service, (b) wash and requalification cycle, and (c) current UN requalification date within compliance window."

What this preserves

Every legitimate quality concern the original spec was trying to protect: regulatory compliance, contamination risk control, container integrity. What it adds: roughly two-thirds cost savings and an order-of-magnitude carbon reduction.

How to navigate the change internally

Pilot with a single product line where the chemistry is well-understood and quality issues are unlikely. Document the program; report the cost and sustainability outcomes. Use that data to update the broader spec. Big-bang spec changes get pushback; pilot-with-data approaches almost always succeed.

Continue reading

← All 34 posts