BOM Consolidation
3 Years Warranty
PCBA Build Support
PCB Fabrication
Traceability Review
Responsive Delivery

Intel 13th Gen Mobile CPU Last-Time Buy Ends Today: What BOM Owners Must Lock Now


The short answer: Intel PCN 913512-00 identifies September 25, 2026 as both the last standard product-discontinuance order date and the non-cancelable, non-returnable cutoff for 31 affected 13th Generation Intel Core mobile processor ordering codes. Procurement teams with an exposed BOM should match the exact ordering code, obtain written order acceptance and a committed shipment schedule, and freeze the commercial assumptions today. An RFQ, forecast, or unacknowledged purchase order is not the same evidence as an accepted order.

By Feifei Deng · Source review completed September 25, 2026 · Evidence grade: A, based on Intel primary sources.

Generic mobile processor packages in an antistatic tray beside a procurement checklist
Lifecycle action starts with the exact ordering code, not the processor family name.

What happened on September 25, 2026?

Intel published Product Change Notification 913512-00 on March 2, 2026. The notice covers selected 13th Generation Intel Core i9, i7, i5 and i3 processors plus an Intel Processor U-series device. It sets June 5, 2026 as the date for customers to provide remaining discontinuance demand to their local Intel representative, September 25, 2026 as the last standard discontinuance order date, and March 26, 2027 as the last standard shipment date.

The same September 25 date is also the NCNR boundary. Intel explains that new orders and unfilled backlog become non-cancelable after that date, while affected products become non-returnable. The notice also makes an important qualification: a superseding written agreement with Intel may specify different dates. That exception is why the governing commercial document must be identified rather than assumed.

The PCN lists 31 affected Intel ordering codes. It does not provide a recommended replacement-code column. A project using an affected device therefore has two separate decisions: secure the remaining quantity under an accepted commercial arrangement, and decide whether a future platform migration needs to begin. Those decisions should not be compressed into a single “find an alternative” request.

Who is affected?

The immediate audience is any OEM, contract manufacturer, repair program, industrial computer supplier or embedded-system team whose released BOM contains one of the 31 exact ordering codes in the PCN. Searching only for “13th Gen Core i9” is too broad for a purchasing decision. Intel binds the lifecycle notice to ordering codes, and each code carries its own marketing name, spec code and shipping configuration.

Two examples show the level of precision required. Intel's ordering page identifies FJ8071505204101 as the Core i9-13900HK in FC-BGA16F tray form with spec code SRMJ3. A separate ordering page identifies CM8071505151708 as the Core i9-13980HX in FC-BGA16F tray form with spec code SRME9. Both pages link back to PCN 913512, but they are different orderable items. The two examples are representative checks, not a substitute for screening the full affected table.

Teams should also check service BOMs, repair depots, long-warranty commitments and configured-to-order variants. A processor may be absent from the current production build yet still be required for field replacement or a contractual spare pool. Conversely, a family name in an internal specification does not prove that every associated ordering code is affected. The released BOM and approved manufacturer list remain the controlling internal records.

A generic processor, BOM review checklist and deadline marker on a bright engineering desk
Separate the BOM match, accepted quantity, NCNR exposure and delivery commitment.

Why an RFQ or purchase order is not enough evidence

A last-time-buy deadline describes the manufacturer's standard ordering window; it does not prove that a particular request has been accepted. A quotation request may still be unanswered. A purchase order may be on hold for price, allocation, credit, terms, minimum quantity or an incomplete customer acknowledgement. Even an ERP status such as “PO sent” can describe transmission rather than supplier acceptance.

For an affected BOM, the useful evidence is a written acknowledgement that ties together the exact Intel ordering code, accepted quantity, commercial terms, NCNR status and committed or acknowledged shipment schedule. If supply is routed through an authorized distributor, the acknowledgement should distinguish distributor acceptance from an upstream Intel commitment. If a separate written agreement governs the account, record its identifier and confirm which milestone replaces the standard PCN date.

The March 26, 2027 last-shipment milestone should also be read carefully. It is the final date in Intel's standard discontinuance process, not a customer-specific delivery promise. Production scheduling, allocation and the terms of an accepted order still determine what a buyer can rely on. Treating the final shipment date as automatic availability would turn a lifecycle fact into an unsupported supply assumption.

Five actions BOM and procurement teams should take today

  1. Screen every released and service BOM against all 31 ordering codes. Match the complete Intel code, including every digit. Keep the marketing name and spec code as supporting fields, not as the primary join key.
  2. Reconcile remaining demand by build and service horizon. Separate firm production, realistic upside, repair obligations, engineering samples and safety stock. Document the assumptions behind the quantity instead of rolling them into one opaque lifetime-buy figure.
  3. Obtain written acceptance. Ask the Intel representative or authorized channel to confirm the exact code, accepted quantity, NCNR treatment and shipment schedule. Escalate any order that is merely submitted, quoted or pending review.
  4. Record the financial exposure. NCNR material can convert a forecast error into stranded inventory. Confirm internal approval, storage requirements, moisture and ESD handling, traceability, warranty horizon and ownership of unused stock.
  5. Open a controlled engineering path for future builds. If the product will continue beyond secured supply, define a platform review with firmware, thermal, power, mechanical, BIOS, compliance and production-test owners. Do not present an unvalidated CPU or board redesign as an approved replacement.

A practical decision record can fit on one page: affected assembly, exact ordering code, current stock, accepted open orders, remaining demand, service reserve, responsible buyer, governing agreement and engineering disposition. That record is more useful than a long email thread because it exposes missing evidence immediately.

Engineering review: no automatic replacement is established

PCN 913512-00 is a discontinuance notice, not a cross-reference approval. It does not state that FJ8071505204101 and CM8071505151708 replace one another, nor does it name a successor ordering code. Any alternative processor, module or board platform is therefore a candidate that requires validation.

Even when two processors share a broad package description, a safe change assessment can include chipset and board support, BIOS or firmware enablement, power limits, cooling capacity, memory configuration, graphics and I/O behavior, mechanical constraints, regulatory evidence and production test coverage. The required scope depends on the product architecture. The sourcing team should not promise a form-fit-function substitution before the engineering owner defines and closes that scope.

A bright component laboratory prepared for BGA processor inspection and engineering validation
Any successor platform is a validation project, not an assumed drop-in replacement.

If your team needs an updated quotation, send the exact processor ordering code, BOM revision, build quantities, delivery country and required dates. For a PCBA or platform change, add the current board documentation and the engineering-review boundary. Informic can then separate confirmed supply, commercial assumptions and candidate alternatives in the response. Request a BOM and engineering review.

Facts, judgment and recommendations: keep the boundary visible

Type What this article states Boundary
Verified facts PCN publication and milestone dates; the 31-code affected table; exact mappings for FJ8071505204101 and CM8071505151708. Drawn from the Intel PCN and Intel ordering pages.
Professional judgment A submitted RFQ or PO is weaker evidence than written acceptance tied to quantity, code and schedule. A procurement-control interpretation, not a statement that Intel rejected any specific order.
Recommendations Screen all BOM variants, reconcile demand, document NCNR exposure and begin a controlled platform review where required. Actions should be adapted to the buyer's contracts, product architecture and risk tolerance.

This article does not claim public inventory, price movement or guaranteed ATP for any affected code. No customer forecast, private quotation or factory allocation statement was available. Supply decisions should use a current written response from Intel or the authorized channel serving the actual delivery region.

Frequently Asked Questions

What is the Intel 13th Gen mobile processor deadline?

Intel PCN 913512-00 lists September 25, 2026 as both the last standard product-discontinuance order date and the NCNR date for the affected ordering codes. It lists March 26, 2027 as the last standard shipment date.

Does submitting an RFQ or purchase order secure supply?

No. Submission alone does not prove acceptance. Obtain written confirmation covering the exact ordering code, accepted quantity, NCNR treatment and acknowledged shipment schedule from Intel or the authorized channel.

Are FJ8071505204101 and CM8071505151708 interchangeable?

No interchangeability is established by the PCN. They are distinct Intel ordering codes with different processor names and spec codes. Any proposed substitution or platform change is a candidate that requires engineering validation.

Does the March 26, 2027 last-shipment date guarantee delivery?

No. It is an Intel program milestone, not a customer-specific delivery commitment. Buyers should rely on the governing written agreement and the accepted order acknowledgement for their schedule.

What if our BOM uses another 13th Generation mobile processor?

Check the complete ordering code against all 31 entries in the PCN. The two codes discussed here are verified examples, not the full affected set. Contact the local Intel representative for code-specific questions.

Sources

  1. Intel Product Change Notification 913512-00 — published March 2, 2026; lifecycle milestones and 31 affected ordering codes.
  2. Intel ordering page for FJ8071505204101 — Core i9-13900HK, FC-BGA16F tray, spec code SRMJ3.
  3. Intel ordering page for CM8071505151708 — Core i9-13980HX, FC-BGA16F tray, spec code SRME9.

Choose the long-term lifecycle response

This notice is one part-specific event. Use the obsolete and EOL components decision framework to compare a calculated last-time buy, replacement qualification and redesign using the same demand, inventory, timing and approval evidence.

Table of Contents

Translate »

Get Component Availability Updates

Receive periodic availability notes, BOM sourcing guidance and supply-chain updates.