Can You Promise the Ship Date Before Material, Capacity and WIP Agree?
EMS delivery commitments are reliable only when component readiness, constrained capacity, current WIP, test and outside-processing dependencies support the date. Customer service needs an operational promise, not only an ERP due date.
The short answer
An EMS ship date is credible only when the current evidence supports it. Critical material, approved sources, constrained capacity, WIP position, test readiness, rework and outside-processing return all need to align closely enough that the order has a realistic path to shipment.
A due date stored in ERP is important, but it is not the same as an operational promise.
Customer service needs both: the commercial commitment and the latest evidence that production can still meet it.
The same question belongs to the wider High-Mix EMS Changes Every Day. How Do You Keep Production Under Control? operating picture: delivery-promise control has to remain connected to the decisions made before and after it, rather than becoming a separate local control.
Separate requested, committed and current forecast dates
A customer can request one date.
The business may commit to another.
Execution may later predict a third if risk develops.
Keep these meanings clear.
Overwriting one field repeatedly destroys the history of the commitment. Start with critical material. Ask whether the order has the components that can truly stop the build.
Do not treat all shortages equally.
A missing low-value connector can be just as decisive as a missing processor if there is no approved alternate. Use approved-source reality. A market search may show components available.
If the source or manufacturer is not approved, the material is not yet a valid recovery plan.
Delivery promise should use executable supply, not theoretical availability.
Include material allocation. A component can be on hand but assigned to another urgent order.
Customer service needs a view of whether the current promise depends on allocation that management has not secured. Include constrained capacity. A fully kitted order can still be late if the required SMT line, test station or skilled operation is overloaded.
Promise should reflect the critical route, not average plant capacity. Include WIP position. If production has started, use actual WIP state.
A job at functional test is different from one waiting for first operation.
The remaining route matters.
Include rework exposure
A large rework queue can delay completion even when main production is finished.
Use current quality and repair state when assessing ship date. Include outside processing. If coating, programming or another external step is still outstanding, the supplier due-back date becomes part of the customer promise.
Do not ignore off-site WIP. Include final quality and release. Completed quantity may still need final inspection, documentation or customer-specific release.
Shipment readiness is not identical to production completion. Use confidence, not false certainty. Some orders have strong evidence.
Others depend on a supplier recovery or an unapproved alternate.
Customer service can benefit from a risk indicator such as:
- on track;
- at risk;
- blocked.
The status should have a reason underneath it.
Trigger review when assumptions move. The promise should be rechecked when:
- critical component slips;
- priority allocation changes;
- ECN affects the job;
- line breakdown occurs;
- test fails materially;
- subcontract return moves;
- rework rises.
This makes customer communication earlier. Avoid promising from spreadsheets disconnected from execution. When ERP dates are not trusted, teams often create local promise trackers.
That can produce a second planning system.
The better fix is to connect customer-date review with actual material, WIP and shop-floor evidence.
Give sales/customer service the right level of detail
They do not need every feeder or defect record.
They need the operational reasons that affect the customer decision.
For example:
- waiting for approved component;
- in test;
- subcontract due back Friday;
- partial shipment possible.
This supports clear communication without overwhelming the commercial team. Support partial shipment decisions. If 80% of the order can ship, management may choose to release it.
The system should show the quantity complete and the cause of the balance.
Split shipment is a commercial decision supported by production evidence. Preserve promise-change history. Track how often dates change and why.
Repeated movement caused by the same issue can identify:
- weak supplier lead times;
- unstable allocation;
- test bottleneck;
- excessive expedite;
- unrealistic original commitment.
This feeds continuous improvement.
Use the promise in priority decisions. If an order is already at risk, the production team may prioritize it.
But priority should consider whether recovery is actually possible.
Moving a job ahead without its critical material does not protect delivery. Use delivery-risk reason codes consistently. If one team records “material issue” and another records “supplier late,” the same problem can look like two different causes.
Use a small shared set of delivery-risk categories.
Detailed notes can remain underneath.
This helps management see recurring sources of promise failure. Review promise stability by customer. Some customers frequently change required dates.
Others receive date changes because the factory is unstable.
Separate these patterns.
Commercial action differs from operational improvement.
Connect promise to available-to-ship quantity
A customer may not need the entire order at once.
If finished, released quantity is available, customer service can discuss partial shipment.
The system should distinguish produced quantity from quality-released quantity. Include documentation readiness. Some shipments require certificates, test data, labels or customer portal updates.
A physically finished product may still be blocked.
Where these requirements are material, include them in shipment readiness. Close the loop after missed promise. When an order ships late, classify the primary cause using evidence.
Then ask whether the original commitment was unrealistic or execution failed later.
This distinction improves both quoting and production control. Use promise accuracy as a cross-functional metric. Delivery reliability belongs to sales, planning, purchasing, production, quality and suppliers together.
Avoid using the measure only to judge the final shipping department.
The customer promise is the output of the whole operating model.
Use promise confidence levels. A date supported by fully ready material and active WIP has different confidence from a date depending on an unconfirmed component shipment.
Represent that difference.
For example:
- committed/on track;
- committed/at risk;
- recovery pending;
- blocked.
The exact terms can vary.
The point is to make uncertainty visible before the due date is missed.
Identify the critical dependency
An order can have many open items.
Customer service needs to know which one actually controls the date.
That might be:
- one component;
- SMT capacity;
- functional test;
- customer approval;
- external coating.
Focus recovery on the critical dependency. Review promise after priority changes. If a scarce component or SMT slot is reassigned to another order, recheck the displaced customer's date immediately.
Allocation and sequencing decisions should flow through to promise risk.
Otherwise the customer-facing view remains stale. Include yield risk near completion. An order may have enough gross production to meet quantity but still depend on expected test yield.
If final good quantity is uncertain, show that risk.
Do not promise from gross WIP as though every unit will pass.
Use customer promise history to improve planning assumptions. If dates repeatedly move because one supplier or test process is late, update the planning model.
Promise review should generate learning, not only customer communication. Make late reason evidence-based. Avoid generic “production delay” explanations internally.
Classify whether the cause was demand change, material, allocation, capacity, quality, rework, subcontract, or original promise error.
This supports meaningful improvement.
What management should measure
Useful indicators include:
- promised date changes;
- orders at risk by reason;
- material-driven lateness;
- capacity-driven lateness;
- WIP/test-driven lateness;
- subcontract-driven lateness;
- partial shipments;
- customer expedites;
- difference between requested and committed date;
- orders whose promise depended on unapproved recovery.
These measures show whether the business is promising from evidence or optimism.
A practical review
Choose ten orders shipping in the next two weeks.
For each one, confirm:
1. critical material;
2. approved source;
3. allocation;
4. next constrained operation;
5. current WIP state;
6. test/rework status;
7. outside processing;
8. final release requirement.
Then ask whether the customer date is still supported.
Where Epicor Mars fits in delivery-promise control
For delivery-promise control, the key system-design question is how to keep enterprise control and electronics-specific execution on the same operating thread. Epicor provides the enterprise-grade ERP foundation for customer orders, purchasing, inventory, planning, costing, finance, approvals and governance. Epicor Mars extends that foundation with the EMS industry context needed at the point of work, including material identity and readiness.
That connection is directly relevant to Can You Promise the Ship Date Before Material, Capacity and WIP Agree?. EMS delivery commitments are reliable only when component readiness, constrained capacity, current WIP, test and outside-processing dependencies support the date. Customer service needs an operational promise, not only an ERP due date. When the Epicor Mars execution record stays tied to the Epicor work order, material and customer context, management can compare the business commitment with what the factory actually executed without maintaining a second source of truth.
For delivery-promise control, that complementary positioning is the point: Epicor remains the enterprise-grade foundation, while Epicor Mars adds the EMS workflows needed to make this particular control operational on the factory floor. Explore Epicor Mars for electronics manufacturing.
Frequently asked questions
Is a planned ERP due date the same as capable-to-promise?
No. A planned date becomes more credible when current material, capacity and execution evidence support it.
Should customer service see detailed factory data?
Only the detail needed to understand risk and communicate accurately.
Can partial shipment protect the customer promise?
Sometimes. It is a commercial decision that should use current completion and remaining-risk evidence.
How often should delivery promises be reviewed?
When important assumptions change, with exception reporting to focus attention on at-risk orders.