Mattress Change-Control Procedure for OEM/ODM Projects: How to Approve Material Substitutions

By Nancy Yu, BONJOUR LUXE (佰仕禄) · Published 2026-09-12 · Last updated 2026-09-12

Direct Answer: Change control for an OEM/ODM mattress program is the written process that decides whether a proposed change — a different wool lot, a substituted fabric, a tweaked layer thickness, a new tufting pattern — is allowed into production, and what has to happen before it is. The core rule: every change is declared in writing, classified by risk, re-tested where the class requires it, approved by a named person on the buyer's side, and reflected in an updated golden sample and BOM before any unit ships. If it isn't on the approved paperwork, it isn't the product — even if the supplier says it "looks the same."

I've seen a program lose a five-year listing because a supplier swapped a horse-hair supplier mid-run and mentioned it "after the fact" in passing. Nobody lied. Nobody thought it mattered. It mattered. That's why change control exists: good people under delivery pressure make small, reasonable-looking decisions that quietly break an approved spec.

Why "Verbal Confirmation" Is Never Enough

Start here, because everything else follows from it. A verbal "we'll use the same fill, don't worry" is not a control. It cannot be audited, traced, disputed, or defended in front of a hotel owner who has 400 rooms full of a product that no longer matches the spec.

Three failures verbal confirmation guarantees:

1. No traceability. When a complaint arrives 18 months later, there's no record of what changed or when.
2. No accountability. Nobody signed anything, so nobody owned the decision.
3. No re-test. If it wasn't formalised, it probably wasn't tested — and untested changes are exactly how firmness, height or hand-feel drift enters a program.

If a supplier resists putting changes in writing, that's information about the supplier. Treat it as such.

What Must Be Declared

A useful change-control system starts with a short, unambiguous list of what counts as a change. Anything on this list triggers the process. Anything not on this list doesn't.

Declare it if it touches:

• Fill materials — any of the natural fills (horse hair, wool, cotton, camel hair, alpaca hair, silk): supplier, lot, grade, blend ratio, or conditioning.
• Fabrics — the main materials (cotton, wool, silk): supplier, weave, weight, finish.
• Construction — layer count, layer order, layer thickness, tufting pattern or density, seam/finishing method.
• Components — any ticking, handles, vents, tapes or labels that form part of the product.
• Process — a change of crew, line, or a material conditioning step that affects the finished unit.
• Spec-adjacent items — size, firmness grade, or packaging where the buyer's spec locks them.

Do not require a formal change for things that genuinely can't affect the product — an admin contact, a logistics provider, an invoice format. Keep the list tight; a process that flags everything gets ignored.

Change Classes: Not Every Change Deserves the Same Treatment

Classify by risk and by whether the buyer's spec or legal claims are affected. Here's the classification I'd default to, and you should tune it to your own risk posture.

The line between Class 2 and Class 3 is where most programs fail. Moving to a new supplier of the same nominal material is almost always Class 3, not Class 2 — because a different supplier means a different lot behaviour, different loft, different retention. "Same material, different source" is not the same product.

Note the obvious: the change-class table above is a decision structure, not a legal standard. Map the classes and their required tests to your own spec sheet, contract and any certification obligations. And any illustrative re-test intervals or sample counts mentioned below are examples, not published standards.

The Change Request Form: One Page, No Ambiguity

A change request should fit on one page and force the supplier to answer every question you'd otherwise have to chase.

Change Request — minimum fields:

1. CR number and date (sequential, unique).
2. Product / SKU and affected batches.
3. Description of the change — from (current) → to (proposed), precisely.
4. Reason — why is this needed? (availability, cost, performance, customer request).
5. Change class (see table).
6. Materials affected and whether they touch any certification (OEKO-TEX, GOTS).
7. Risk assessment — what could this affect? (firmness, height, weight, feel, durability, claims).
8. Proposed re-test plan — what will be tested, on how many units, by whom.
9. Effective date requested, and whether the supplier is already holding affected stock.
10. Supplier sign-off — name, role, date.
11. Buyer decision block — Approved / Approved with conditions / Rejected, name, role, date.
12. Golden sample update required? Yes/No, and new sample ID.

Field 9 is the sneakily important one. "Are you already holding affected stock?" catches the change that's already happened and needs to be legitimised — or reversed.

The Decision Tree: Where a Change Actually Goes

Follow the path; don't shortcut it.

1. Is the change declared in writing? → No: stop. Nothing proceeds. (This is the gate.)
2. Is it on the "must be declared" list? → No: administrative only, close as Class 1.
3. Classify the change (1–4).
4. Does it affect certification or a product claim? → Yes: Class 4. Certification review is mandatory, not optional.
5. Does it affect fill, fabric, construction, or supplier? → Yes: Class 3 minimum. Full re-test and cut-and-verify required.
6. Does it affect a measured metric (firmness, height, weight)? → Yes: re-test against the tolerance band in the buyer's spec sheet.
7. Has the buyer's named approver signed off in writing? → No: production must not start. Verbal is not sign-off.
8. Has the golden sample been updated and re-sealed? → No: production must not start.
9. Is the BOM and spec sheet updated to the new revision? → No: production must not start.
10. Release to production — and log the CR against the batch records.

Steps 7, 8 and 9 are the three that get skipped under delivery pressure. They're also the three that protect the buyer most.

Re-Test Trigger Conditions

Not every change needs a full destructive test. These do. Treat this as the floor, then add anything your spec or certifier requires.

• Any new material supplier — even for a nominally identical material.
• Any lot with materially different measured characteristics at intake (weight, loft, thickness).
• Any change to layer thickness, order or count.
• Any change to tufting pattern or density.
• Any change touching a certified material (OEKO-TEX, GOTS) or a marketing claim.
• Any change after a customer complaint tied to a specific metric.
• Any process change (new crew, new line, changed conditioning) where consistency is unproven.

For each trigger, the re-test should, at minimum: build a first article to the new spec, measure firmness/height/weight against tolerance, cut-and-verify the layering against the new BOM, and — where a claim is involved — verify the certification still holds. Any specific sample sizes or test counts should be set in your spec sheet, in proportion to the risk.

Buyer Approval: One Named Person, One Signature

Approval authority should rest with a named individual, not a department, not a group chat. One signature, one account, one person who can say no. This sounds bureaucratic; it's actually the opposite. Diffuse approval is how changes get waved through.

Conditions on an approval are common and useful: "approved for this batch only," "approved pending updated certificate," "approved for SKU A but not SKU B." Write them down. A conditional approval that lives only in someone's memory has already expired.

Golden Sample Update: The Physical Truth

The golden sample is the reference every future unit is measured against. If a change is approved, the golden sample must be updated and re-sealed, or your entire reference point is now wrong.

Golden-sample discipline:

• Seal, label (SKU, CR number, date, spec revision), and store in climate-controlled conditions.
• Retain the previous golden sample; don't discard it. Old samples are how you diagnose "when did this drift?" complaints.
• Record the sample ID in the change request so the CR and the physical reference point at each other.
• Never modify an existing golden sample to match a new spec. Make a new one.

A program with an out-of-date golden sample is a program that will eventually ship the wrong product with a clean QC stamp — because QC was measuring against yesterday's truth.

Production Release and Traceability Records

Once approved, the change rolls into production under these conditions:

• Production release only after: written buyer approval + updated golden sample + updated BOM/spec revision. All three.
• Batch markings must reference the CR where relevant, so any unit can be tied back to the change that produced it.
• Traceability records retained: CR form, risk assessment, re-test results and photos, cut-and-verify data, updated certificate (if applicable), approval signature, new golden sample ID, and the affected batch numbers.

Retention matters because OEM/ODM relationships run long. Two years after a change, a buyer reordering "the same mattress" needs the record to reconstruct exactly what "the same" meant at that point in time.

Constraints and Honest Caveats

• Change control slows things down. It's supposed to. The cost of a fast unapproved change is a recall, a lost listing, or a hotel full of mismatched mattresses.
• Classification is judgement, not arithmetic. Reasonable people can disagree on Class 2 vs. Class 3. When in doubt, go up a class — the downside of over-testing is time; the downside of under-testing is the product.
• Certification rules are not yours to interpret loosely. If a change touches a certified material or claim, the certifier's rules and your obligations govern.
• A form doesn't create discipline. If the approver signs whatever lands on their desk, the process is theatre. The control lives in the person who is willing to say no.

FAQ: Why "Verbal Confirmation" Is Never Enough

1. The supplier says the substitute is "exactly the same." Isn't that enough? No. "Same" is a claim, not evidence. Different supplier, different lot behaviour — even nominally identical material can shift loft, retention and feel. Prove it with a re-test, then approve.

2. Can we approve a change retroactively if the goods are already made? You can formalise what already happened, but you cannot un-ship risk. If the change wasn't tested, you're accepting an untested product. In a hotel program, that's a bet on 400 rooms, not one mattress.

3. Do we need buyer approval for a change the supplier thinks is an "improvement"? Yes. The buyer owns the spec. An unapproved "improvement" is still an unapproved change — and it may break a certification, a claim, or a customer's expectation.

4. How long should we keep change records? For the life of the product line plus a tail, matching your batch-record retention. OEM/ODM relationships outlive individual orders; the records are the only way to reproduce "the same product" years later.

5. What if a change is urgent and there's no time for the full process? Then you have a scheduling problem, not a change-control exception. The minimum non-negotiables — written declaration, risk classification, buyer approval, golden-sample update — don't get waived for urgency. Re-test scope can be negotiated; the paper trail cannot.

6. Who should be the named approver? Someone with authority over the spec and accountability for the outcome — typically the buyer's technical/quality lead or the procurement owner, not the supplier's account manager. One person, one signature.

The Short Version

Declare every change in writing. Classify it. Re-test what the class requires. Get one named signature from the buyer. Update the golden sample and the BOM. Release to production only when all three are done. Keep the records. Do this every time, and "we thought it was the same" stops being a sentence anyone has to say.

About the author: Nancy Yu leads B2B project solutions at BONJOUR LUXE (佰仕禄), a Chinese manufacturer of hand-sewn, foam-free mattresses built from six natural fills (horse hair, wool, cotton, camel hair, alpaca hair, silk). She works with hotel operators, design firms and OEM/ODM buyers on procurement specifications, sample approval and delivery acceptance. Contact: nancy@bonjourluxe.com

Sources

• bonjourluxe.com — BONJOUR LUXE 佰仕禄 hand-sewn natural mattress
• home.compare2best.com — BONJOUR LUXE on Compare2Best