Engineering Change Orders: How to Manage Product Modifications Without Destroying Your Supply Chain
Why ECOs Go Wrong (And Why Most Brands Don’t See Them Coming)
Engineering changes sound straightforward: you identify a problem or improvement, you communicate it to the factory, they implement it, production continues.
In practice, ECOs fail because:
The specification gap. Your written spec covers what you thought to specify. The factory interprets what you wrote. The change you intended and the change that gets implemented are often different.
The component ripple effect. Changing one component (LED wavelength bin) cascades into other variables (color temperature, power consumption, heat output, driver specifications). Brands that specify only the variable they care about miss the downstream effects.
The communication gap. ECOs communicated informally (email, WhatsApp, verbal conversation) get lost, misunderstood, or implemented inconsistently across different production batches.
The documentation gap. Without formal ECO documentation, there’s no record of what changed, when, and why. When problems emerge three months later, you can’t trace them back to the change.
The ECO Classification System
Not all changes are equal. We classify every ECO into three categories:
Minor ECO: No effect on fit, form, function, safety, or regulatory compliance. Example: changing packaging dimensions from 18cm × 15cm to 18.5cm × 15cm (still fits the same shipping box).
Moderate ECO: Affects function or appearance but not safety or regulatory compliance. Example: changing LED wavelength bin, changing button style, modifying housing color.
Major ECO: Affects safety, regulatory compliance, or fundamental function. Example: changing battery type, changing electrical specifications, adding a new wireless feature.
The ECO category determines the approval process, the documentation requirements, and the verification testing needed.
The Formal ECO Process
Step 1: Define the Change Request
Before communicating anything to the factory, document the change internally:
Change description: What exactly is changing?
Reason for change: Why is this change necessary? (Cost reduction, quality improvement, regulatory requirement, customer feedback, component availability)
Affected products: Which product SKUs does this change affect?
Affected components: Which components within the product does this change affect?
Risk assessment: What could go wrong if this change is implemented incorrectly?
Step 2: Evaluate Downstream Effects
Before submitting to the factory, evaluate how this change affects everything downstream:
Functional effects: Does this change affect any functional specifications beyond the one variable you’re changing?
Electrical effects: Does this change affect power consumption, battery life, charging behavior, EMC compliance?
Thermal effects: Does this change affect heat generation, thermal protection behavior, surface temperature?
Optical effects: Does this change affect light output, color temperature, LED uniformity?
Mechanical effects: Does this change affect fit, assembly, or structural integrity?
Regulatory effects: Does this change affect any certification or compliance requirements?
This is the step we skipped before our wavelength change disaster. We specified the wavelength change without evaluating the color temperature effect. Never skip this step.
Step 3: Factory Communication
Submit the ECO formally, not informally:
The ECO document should include:
- ECO number (sequentially assigned)
- Date of request
- Affected product SKU(s) and version(s)
- Detailed description of the change
- Reason for change
- Effective date (when production should switch to new specification)
- Disposition of existing inventory (use as-is, rework, scrap)
- Required documentation from factory (updated specifications, updated test reports)
- Approval signatures from both parties
- ECO acknowledgment and confirmation they understand the change
- Their implementation plan (how they’ll implement the change)
- Any concerns or questions about the change
- Timeline for first production run with new specification
- Updated Bill of Materials reflecting the change
- The changed specification meets the new requirement
- All downstream specifications that could be affected still pass
- New test results for any affected compliance requirements
- Updated documentation (BOM, spec sheets, test reports) is provided
Send the ECO document via email with read receipt and request a formal acknowledgment from the factory’s engineering or QC manager.
Step 4: Factory Implementation Confirmation
The factory should respond with:
Review the factory’s response carefully. If they don’t mention any downstream effects you identified, ask explicitly: “Confirm that the change from [old spec] to [new spec] does not affect [list downstream variables].”
Step 5: First Article Inspection After Change
Any ECO requires a new FAI before production continues. This is non-negotiable.
The FAI after an ECO should verify:
If the FAI fails, production stops until the problem is corrected and a new FAI passes.
The Common ECO Mistakes (And How to Avoid Them)
Mistake: ECOs communicated informally.
We sent an email: “Please change LED wavelength to tighter tolerance.” The factory implemented a different binning approach than we intended. The result: technically correct wavelength, unacceptable color shift.
Solution: Every ECO is a formal document. No exceptions.
Mistake: No inventory disposition plan.
We changed a component without specifying what to do with units already in production. The factory kept building with old components, knowing we were changing. Half the units that shipped had the old spec, half had the new.
Solution: Every ECO specifies what happens to existing inventory: scrap, rework, or sell-through with disclosure.
Mistake: Assuming the factory tests downstream effects.
The factory tests what you specify to test. They don’t test what you didn’t think to specify. Our wavelength change cascaded into color temperature issues because nobody specified that color temperature was a concern.
Solution: Create a comprehensive downstream effects checklist. Evaluate every variable before submitting the ECO. If you didn’t evaluate it, you didn’t think of it.
Mistake: No versioning system.
We changed a specification three times in six months without a formal versioning system. We ended up with products in the market that had three different versions of the same spec, and no way to track which was which.
Solution: Every product has a version number. Every specification change increments the version. All documentation references version numbers. Traceability is maintained through version history.
The ECO Cost You’re Not Counting
ECOs have hidden costs that most brands don’t budget for:
Production line downtime: Any change requires stopping production, retooling, and restarting. Factory downtime is expensive and often billed to the brand.
Component write-offs: Existing components that are no longer needed after a change may become scrap.
Rework costs: Units in process when a change takes effect often need to be reworked or scrapped.
Expediting costs: If a change disrupts your supply timeline, expedited production and shipping costs follow.
Customer communication costs: If the change affects already-shipped products, customer notification, return processing, and remediation costs apply.
Our $67,000 lesson from the wavelength change: we hadn’t budgeted for the customer replacement program. Never assume an ECO is cost-free.
The ECO Approval Thresholds
To balance agility with rigor, we use tiered approval:
Minor ECOs: Approved by our supply chain manager. No factory FAI required if downstream effects are confirmed as non-existent. Effective after 1 week.
Moderate ECOs: Approved by our supply chain director. Factory FAI required. Effective after 3-4 weeks.
Major ECOs: Approved by our CEO. Full FAI, regulatory review, and customer notification plan required. Effective after 6-8 weeks minimum.
This tiered system prevents minor changes from getting bogged down in unnecessary process while ensuring major changes get appropriate scrutiny.
Building ECO Management Into Your Culture
The most important change isn’t the process — it’s the mindset. In the two years since our wavelength incident, we’ve internalized three principles:
Changes are expensive until proven otherwise. Even minor-seeming changes have hidden costs. Always estimate the full cost before deciding to proceed.
Documentation prevents disputes. When a change goes wrong, the question is always “who is responsible?” With formal ECO documentation, this is clear. Without it, it’s a negotiation with no good outcome.
One change at a time. The temptation to bundle multiple changes into one ECO is real — it’s faster. It’s also a recipe for confusion about what caused what when problems emerge. One change, one ECO, full verification.
The brands that manage product development well treat ECOs as a discipline, not an interruption. The brands that don’t learn this lesson the hard way.