Ribbon OEM Change Order Control: Scope, Cost and Approval Governance for Brand Buyers (2026)
Core principle: a change order is not an exception to the production plan. It is a formal transfer of cost, capacity and delivery risk from one party to another. If the transfer is not written down, priced, and signed by a named person, the brand owner pays for it in margin anyway — just later, less visibly, and without the right to refuse.
Every ribbon programme accumulates changes. A decoration is moved. A width is adjusted by two millimetres. A packing format is revised because a retailer asked for a different shelf presentation. A colourway is re-approved after a dye lot drifts. On their own these are small. Accumulated across a year of repeat orders, unmanaged changes become the single largest driver of margin leakage in a trim programme — and they are almost invisible in the per-unit cost, because they are spread across thousands of units and reordered every season.
This guide sets out the governance structure that experienced brand buyers put in place: how to classify changes by scope tier, how to attribute cost fairly, which gates require written approval before work starts, and how to keep a change log that remains defensible two years later when someone asks why the last price was higher than the first.
Ribbon OEMB2B ProcurementSmith Ribbon since 2004
Why unmanaged change is the quietest margin leak in a trim programme
Ribbon programmes have a peculiar property: the unit cost of a ribbon looks almost identical from season to season, while the cost of getting it made drifts steadily upward. The buyer compares last quarter’s price with this quarter’s price, sees a small increase, and concludes that the supplier has raised prices. Sometimes that is true. More often, what has changed is the scope of what is being bought.
Consider a typical private-label hair accessory programme. The opening order is genuinely simple: 38 mm grosgrain in one Pantone colour, printed with a logo, wound on a 25 mm core, packed into 500-piece cartons. The launch cost is high because of setup, but the per-unit cost is low and the specification is short. Twenty four months later, the same programme contains a 38 mm grosgrain in three Pantone colours, one of them with a metallic foil stripe, wound on 25 mm cores for two SKUs and on spool cards for a third, with printed header cards, EAN labelling, and a different carton count per market. The ribbon itself has not become more expensive. The programme has become a different programme.
Nothing about this is dishonest or unusual. What is avoidable is discovering the cost of the change after it has been incurred. A change that has not been priced before work starts is a change the mill absorbs, and a mill that absorbs changes indefinitely does one of three things: quietly raises the price of the next release, slows its response to the next genuine change, or both.
From the brand owner’s side, the risk is different but equally real. A scope change that nobody formally approved is difficult to recover. You cannot claim the setup cost was unauthorised if the production was delivered and accepted. You cannot argue the specification was breached if the receiving team signed the carton without checking. Changes that are not governed become, by default, the buyer’s problem — because the evidence trail shows acceptance rather than objection.
Scope tiering: classifying a change by what it actually consumes
The first governance decision is classification. Most change-control frameworks fail because they offer only two categories — “minor” and “major” — which are decided by whoever is arguing hardest. A workable framework classifies changes by what they consume at the mill, because consumption determines cost and therefore who should approve.
Three tiers cover almost all ribbon programmes in practice:
Tier 1 — Documentation only. The specification does not change. What changes is a document: a packaging insert is reworded, a label artwork is corrected for a typo, a country of origin note is added, a packing list format is updated. No machine is re-set, no material is consumed differently, no new setup occurs. Cost impact is typically zero. Tier 1 changes are approved by the relevant programme contact in writing, and the production plan is not re-opened.
Tier 2 — In-plan, costed, no capacity impact. The specification changes in a way that consumes a small amount of additional material or labour, but does not require re-sequencing the production plan or displacing other work. Examples: a 10 % increase in print coverage on the same artwork; a small quantity of additional ribbon bundled into the carton; a minor adjustment to cut length that stays within existing tolerance bands. Tier 2 changes are priced as a line item, approved by the buyer, and scheduled into the next available production slot without renegotiating the delivery date.
Tier 3 — Out-of-plan, capacity-affecting, contractually material. The change requires a new setup, consumes additional capacity that was reserved for other work, invalidates an already-approved sample, or changes the delivery commitment. Examples: a new decoration method on an existing construction; a change in base material; a change to packing format; a change that moves the article from an in-stock construction to a made-to-order one. Tier 3 changes require a written quote, a revised delivery date, and signature from a person with authority to commit the brand to the new date and cost.
The tier is determined by evidence, not by assertion. A mill that proposes a Tier 3 change should say which of the four capacity-affecting conditions applies. A buyer that receives a Tier 2 proposal should check whether a new setup is genuinely avoidable — in many cases it is not, and the change has been mis-tiered in the buyer’s favour. Both directions of error are common, and both are corrected by asking for the specific operational basis of the classification.
| Tier | What it changes | Cost impact | Approval required | Delivery impact |
|---|---|---|---|---|
| Tier 1 | Documents only | Nil | Programme contact, written | None |
| Tier 2 | Material or labour, in-plan | Quoted line item | Buyer, written | None; next slot |
| Tier 3 | Setup, capacity or commitment | Re-quoted, full basis | Authorised signatory, written | Revised date required |
Cost attribution: four rules that keep the arithmetic honest
Once a change is classified, the next question is who pays. The rule that feels obvious — the party requesting the change bears the incremental cost — is correct, but it is not sufficient on its own. Attribution gets complicated because a single change can carry both a requester-driven component and a supplier-driven component. Four rules handle most cases cleanly.
Rule 1: The requesting party bears direct incremental cost. If the brand asks for 20 metres of extra ribbon bundled into the carton, the brand pays for 20 metres of ribbon at the agreed rate, plus the incremental packing labour. The mill does not absorb it, and the brand does not get it free because the carton was already going to be packed. This rule is uncontroversial in principle and frequently violated in practice, usually because nobody wrote the extra quantity down and the cost simply appeared in the next invoice.
Rule 2: Setup cost follows the first order that triggers it, amortised explicitly. If a new printing plate or new colourway setup is required, that setup belongs to the order that caused it. The cost can be quoted as a one-off line item, or spread across a stated quantity, or amortised over the contract year with a defined break point. What is not acceptable is a setup charge that appears without explanation, or one that is quietly folded into the unit price so that it recurs forever. If it is amortised, the amortisation must have an end, and the end must be stated.
Rule 3: Supplier-driven changes are supplier-borne, unless the buyer elects to pay for speed. If a change is required because a mill process was retooled, a dye lot failed, a machine was replaced, or a sub-supplier discontinued a material, the cost of adapting the programme to the new reality sits with the mill. The buyer may choose to pay a premium to retain the original specification — that is a legitimate commercial decision — but it should be recorded as the buyer’s election, not presented as the only way forward. The framing matters because it determines who is solving the problem.
Rule 4: Value-adding changes are quoted at the agreed rate, not at a penalty rate. If the buyer asks for a longer roll length that reduces handling at their own warehouse, or a packing format that improves shelf presentation, the mill should quote it as ordinary commercial work. Penalising a buyer for a change that improves their own operation trains them to stop asking. The question to ask is narrower: does this change consume more capacity than the original scope, and does it create work that displaces other customers?
One practical refinement: ask for the cost breakdown, not just the number. A change quote that separates material, labour, setup, and freight impact can be checked against the original quote’s structure. A change quote that presents a single number cannot. The difference is not cosmetic — it is the difference between auditing a change and merely reading it.
Approval gates: what must be written, by whom, and before what
Governance only works if the evidence exists. A change that was discussed, agreed verbally, and then executed has no audit trail — and when the cost appears on the invoice six weeks later, the discussion is no longer available to either party. Four gates close that gap.
Gate 1 — Request completeness. Before the mill prices a change, the request must contain the information required to price it: what changes, from what baseline, effective from which order, and whether it is permanent or reversible. A mill that prices an underspecified change is not obliged to hold the quote. Requests arriving as “can you also change the packing?” generate quotes that cannot be compared and commitments nobody can audit.
Gate 2 — Costed proposal with an explicit basis. The mill returns a written proposal stating the tier, the incremental cost with its breakdown, the capacity effect, and the revised delivery date. The proposal states what happens if the change is declined — because sometimes the honest answer is that the programme cannot proceed without it, and discovering that late is expensive.
Gate 3 — Written approval before work starts. Approval is a written instruction to proceed, from a named person, referencing the proposal. “Go ahead” in a meeting, followed by silence, is not approval. For Tier 3 changes the approval should also state the revised date, so that both parties are committed to the same schedule rather than assuming the original one survives.
Gate 4 — Execution evidence at despatch. When the changed goods ship, the despatch documentation should identify the change and reference the approval. This closes the loop: the invoice, the packing list, the delivery date and the approval record all describe the same transaction. It also protects the buyer, because the despatch evidence is what makes a legitimate cost claim substantiable rather than speculative.
Two details are worth insisting on. First, approval authority should be defined once and circulated: who can approve Tier 1, who can approve Tier 2, who can sign a Tier 3 change that moves a delivery date. Without a published authority matrix, every change becomes a negotiation about authority rather than about the work. Second, an approval should never be retrospective. A change executed and then approved retrospectively has a much weaker position on both cost and delivery, and should be treated as a process incident rather than quietly normalised.
The change log: the artefact that survives the programme
Most programmes generate change records scattered across email threads, chat messages, spreadsheets, and meeting notes. Each is a fragment. The change log is a single, chronological, append-only record that makes the programme’s actual history legible. Its value compounds over time.
A usable change log carries, for every entry: a sequential reference; the date raised; the requesting party and the person who requested it; the baseline specification and the revised specification, stated as differences rather than as full documents; the scope tier; the cost impact and how it was attributed; the capacity and delivery impact; the approver and the approval date; the production order or lot in which the change was executed; and the reversal status, if the change was temporary.
The last field deserves attention. A great many changes are provisional: a single-market packaging test, a seasonal colourway, a temporary promotion format. Without a reversal flag, temporary changes accumulate silently and become the baseline — and the next quotation is built on a structure nobody consciously chose. This is one of the quietest forms of scope creep in the industry, because each individual decision was reasonable.
Because the log is append-only and referenceable, it also serves a pricing function. When a new quotation is requested, the log supplies the actual basis for comparing this programme’s current scope against a baseline: not what the original spec sheet said, but what is actually being produced now, and what each difference costs. Quoting from the log rather than from the original brief is materially more accurate, and materially harder to argue with.
| Field | Why it belongs in the log |
|---|---|
| Change reference | Links invoice, despatch note and approval into one traceable chain |
| Baseline vs revised specification | Prevents later reconstruction from memory |
| Scope tier | Shows the classification applied at the time, not a later rationalisation |
| Cost impact and attribution basis | Makes the invoice line auditable rather than arguable |
| Capacity and delivery impact | Records the schedule consequence that was accepted |
| Approver and date | Establishes that approval preceded execution |
| Reversal status | Stops temporary changes becoming an unnoticed permanent baseline |
Implementing the framework without slowing the programme
The legitimate objection to change control is that it makes a programme slower. That is true of change control designed badly, and false of change control designed well. The distinction is entirely in where the effort sits.
Badly designed change control puts the burden at the front: every request requires a form, a form requires a cost estimate, the cost estimate requires a conversation with production, and the conversation happens after the production slot has been committed elsewhere. The programme slows and the mill is annoyed.
Well-designed change control puts the burden in the middle, where it is cheap. A published tier definition means the requester can classify the change themselves. A pre-agreed pricing basis means the mill can quote Tier 2 changes without escalation. A standing approval matrix means the right person signs without a search. A structured request format means the mill receives the information needed to price without a round of emails. None of these steps is slower than a normal email exchange; they are simply less ambiguous.
Two implementation habits matter most. First, agree the authority matrix before the first change arrives, not after the first dispute. Second, review the change log quarterly for patterns. A programme that generates four or more Tier 3 changes in a quarter has a specification problem, not a change-control problem, and the log is the evidence that lets both parties say so without argument.
There is also a commercial benefit worth stating plainly. Brand buyers who run a clean change process tend to receive better proposals, because the mill knows the scope is stable enough to quote firmly. The mill spends less time speculating about what is actually wanted, and can commit to a date with more confidence. That confidence is worth more than the cost of the governance itself, and it is one of the reasons experienced buyers treat documentation maturity as a signal of supplier quality rather than as administrative overhead.
Finally, a note on how this interacts with the supply agreement. Change governance is far more effective when the contract itself references it. A clause that requires written approval before execution of a costed change, that identifies the authorised approver by role, and that sets a window in which a Tier 3 change may be declined without penalty, converts a management practice into an enforceable obligation. Where no such clause exists, the framework still works — but it depends on goodwill, and goodwill is not a control.
Frequently Asked Questions
What counts as a change order in ribbon OEM production?
Any deviation from the approved specification that is executed in production. That includes changes to material, width, decoration, colour, packing format, roll configuration, labelling and documentation. The common mistake is treating only large changes as change orders. Small changes accumulate, and it is the accumulation, rather than any single change, that produces margin erosion over a programme year.
Who should approve a change order in a ribbon supply programme?
Authority should be defined once, published, and mapped to scope tier. In practice the programme or merchandising contact approves Tier 1 and Tier 2 changes in writing, while Tier 3 changes — those affecting setup, capacity or the delivery commitment — require a signatory with authority to commit the brand to a revised date and cost. The named individual should be recorded against every approval.
How should cost be attributed when a change is requested by the buyer?
The requesting party bears the direct incremental cost: the additional material at the agreed rate, plus incremental labour, setup and freight impact. Setup cost is either quoted as a one-off line item or amortised across a stated quantity with a defined end. The underlying principle is that the request is priced transparently before work begins, so that no cost is discovered after the fact on an invoice.
Can a change order be approved after the work has started?
It should not be, and a retrospective approval is treated as a process incident rather than a routine administrative step. Approval given after execution weakens the position on both cost recovery and delivery commitment, because it cannot demonstrate that the buyer had the option to decline. A revised date should be stated explicitly in the approval for any change that affects the schedule.
How do you stop temporary changes from becoming the permanent baseline?
Record a reversal status on every change, and schedule a review date for provisional changes. When the programme is re-quoted, build the comparison from the change log rather than from the original brief, so that what is actually being produced is visible. This prevents single-market tests, seasonal colourways and temporary promotion formats from quietly becoming the standard specification.
How many change orders are normal in a repeat ribbon order programme?
For a stable programme with an established construction, a small number per year is normal — typically a handful of Tier 1 and Tier 2 items such as updated documents or minor packaging adjustments. A programme generating repeated Tier 3 changes is usually experiencing an unresolved specification or artwork problem, and the change log is the evidence needed to identify it. The volume itself is the diagnostic.
Ready to source ribbons and bows with a mill that answers the hard questions?
Smith Ribbon & Bow has supplied woven, printed, velvet, satin, organza and RPET ribbons to brand buyers in over 50 countries since 2004 — from a 15,000 m² plant with 200+ staff and 100,000 m daily capacity, holding OEKO-TEX®, GRS, FSC, BSCI, SEDEX, ISO 9001 and SMETA.
Request a quotation or a sample pack → | Browse the ribbon product range →