
Storage EOL: How Many Units Should an OEM Buy Last?
- Confirm the latest notice for the exact orderable part and keep the last order date separate from the last delivery date.
- Estimate production, loss, service and test needs in pieces, then subtract only usable stock, firm receipts and demand covered by an approved alternative.
- Run low, base and high cases before accepting shortage or excess-stock risk.
Estimate a last-time buy in pieces of the exact discontinued storage part. Add the units needed for remaining production, expected production losses, field service and approved test work. Subtract usable stock, firm incoming units and the demand an already-approved replacement can actually cover. Calculate low, base and high cases before committing to an order. A forecast alone is neither a supplier allocation nor a purchase commitment.
This guide concerns quantity. The flash-storage PCN and EOL guide covers notification review and requalification decisions.
Fix the part number and two deadlines first
Check the latest discontinuance notice against the full orderable part number, not only a product family or marketing capacity. Record its revision and ask the supplier to confirm which code and configuration the notice covers. A replacement listed on a notice still needs approval for the target host before it can remove demand from the old part.
Record the last order date and last delivery or shipment date separately. NXP's lifecycle definitions and Micron's PCN/EOL policy distinguish these events in their respective processes. An NXP notice with corrected dates shows why the latest version matters. These vendors' dates and policies are examples, not a deadline or promise for a Kalstor part. Delkin likewise describes EOL notices with last-buy and shipment information for its products.
Ask what an order must contain by the cutoff, when it is accepted, whether scheduled deliveries are possible and what terms apply to cancellation or returns. Confirm who will hold any stock and how its lot and approved revision will be identified. None of those arrangements should be assumed from the EOL notice alone.
Calculate gross need, then remove confirmed coverage
Keep every input in pieces of the EOL storage part. If each finished device uses two units, multiply the number of planned devices by two before adding other needs.
Gross need = remaining production consumption
+ expected production loss or rework units
+ service spares not already counted elsewhere
+ approved pilot or qualification units
Net last-buy target = max(0, gross need
− usable on-hand EOL units
− firm EOL receipts arriving in time
− demand covered by an approved alternative)
Apply loss estimates only to the activity that produces those losses; do not inflate field-service stock with an assembly yield factor. Check whether a warranty reserve is already part of the production plan before adding service spares. Count on-hand material only if its identity, condition and availability fit this project. Count incoming units when the order and delivery are confirmed for the needed period, rather than treating a supplier forecast as inventory.
A proposed replacement in validation is an uncertain scenario, not confirmed coverage. Only subtract the devices or service units it can cover after the required application approval and supply plan are in place.
For a hypothetical arithmetic example, an OEM plans 8,000 devices using one EOL part each. It adds 200 pieces for production loss/rework, 500 distinct service spares and 100 pilot/test pieces: 8,000 + 200 + 500 + 100 = 8,800 gross pieces. It has 1,000 verified usable pieces, 400 firm receipts due in time and 800 devices that an already-approved alternative will serve. The net EOL target is 8,800 − 1,000 − 400 − 800 = 6,600 pieces. These are teaching figures, not Kalstor inventory, a customer forecast or an offer to supply.
Put uncertainty into a planning worksheet
Make one row per planning period and configuration. Keep service demand separate from production so the same unit is not counted twice.
| Field to record | Source or question |
|---|---|
| Period and exact EOL part | Which months and orderable code does this row cover? |
| Planned finished devices × EOL units per device | Which orders or approved forecast support the build plan? |
| Production losses and rework | What process history or test plan supports the extra units? |
| Service spares | Which installed base and support obligation create demand, and is it already reserved elsewhere? |
| Pilot or qualification pieces | Which approved activity will consume them? |
| Usable stock and firm receipts | Which lots are available, and which supplier-accepted deliveries arrive when needed? |
| Approved alternate coverage | For which devices, date and volume is a replacement released? |
| Low, base and high net need | What changes in the forecast, transition date or service rate? |
| Owner and confidence | Who signed off each assumption, and what remains unknown? |
The low case may leave excess old stock if production ends early or replacement approval moves forward. The high case may cause shortages if builds, service demand or qualification delays increase. Show both in pieces and money using actual purchasing terms, then decide with the teams that own production, service and budget. Do not hide a high case inside an unexplained “safety factor.”
If the last buy will be stored for a long period, ask for the exact part's storage, handling and data-retention conditions, especially when media is preloaded. Confirm how inventory will be identified and checked before use. There is no universal shelf-life number for all flash products, packages and storage environments; an overbuy can become unusable stock as well as tied-up capital.
For a quote request, send the notice and revision, full part number, low/base/high quantities, desired delivery dates and configuration requirements. Ask for a written response on availability, acceptance, delivery and commercial conditions. A last-time-buy calculation is a planning input; the supplier's confirmation determines what can actually be ordered and delivered.
References
We publish measured usable capacity and define trial-batch verification against the quoted product and agreed test scope.