How did the Palo Alto SKU index move from 15,309 to 15,846 on September 30, 2026?

Quick Take

Quick Take: Palo Alto on the public index moves from catalog date 2026-08-22 (15,309 SKUs) to 2026-09-30 (15,846 SKUs). Net change is +537 / 0 removed. About 490 of the new lines are PAN-PA-* subscription rows, concentrated on Advanced IP Defense (AIPD). The rest cover ELA modifiers, Cortex Data Security, a few XDR and XSIAM data SKUs, five power supplies, and one FIPS kit. The public index does not show LIST. This refresh is separate from the October 3, 2026 list-surcharge notice.

For a China enterprise buyer the practical reading is simple. The index grew because more subscription and accessory codes are now orderable. It did not publish a new price table, and it did not delete last month’s chassis codes. If a bid ceiling was set on hardware list, do not spend that ceiling on 537 new rows you did not design.

• Cite: catalog date 2026-09-30, public count 15,846.
• Heaviest new block: Advanced IP Defense on PA-52R (86 rows), then PA-54R (28), PA-450R (24), and PA-455 (24).
• Also new: about 23 ELA modifiers, 10 data-security lines, five PAN-PWR-* supplies (including 1200 W AC and DC), and PAN-FIPS-KIT-56R.
• Removed: 0. There is no rename pair to search-replace from this diff.
• Price event to keep separate: the October 3, 2026 list surcharge.

What this Palo Alto catalog delta is

Quick Answer: A Palo Alto catalog delta is a part-number set change between two dated public indexes. August 22 held 15,309 public SKUs. September 30 holds 15,846. Five hundred thirty-seven codes are new. None dropped. Buyers use the index to confirm a code exists, then price it on a quote.

Definition: The live Palo Alto part-number index covers appliances, subscriptions, and related orderable codes. The catalog date printed for an RFQ is the revision the bid should cite. The September 30 refresh is a subscription-heavy expansion. It is a catalog add, and it is separate from a chassis replacement wave and from a published list-price table.

Keep it separate from the October 3, 2026 Palo Alto list surcharge (Gen 4 temporary surcharge, Gen 5 base-list move, CVP waiver window). A new AIPD row on the index does not mean every PA-400 or PA-5400 list price already moved. Channel registration (deal registration / CVP) is a commercial path you confirm in writing. It is not proved by the SKU count alone.

China enterprise use cases sit on three desks. The operations lead asks whether a branch firewall keeps forwarding if a new subscription code appears. The procurement lead asks whether the bid ceiling and the 13% VAT special invoice still match the old chassis lines. The integrator asks which AIPD, HA2, and GB rows the tender technical clause actually names. TaoHan reads the clause against the table on this page, then returns a deviation note before the quote.

• Fit this page: open Palo Alto BOMs that must match catalog date 2026-09-30; AIPD, Data Security, or ELA modifier lines that failed a code check last month; power-supply and PA-56R FIPS kit checks; tender deviation tables that must not auto-load unused subscriptions.
• Unfit: readers who want one percentage that says everything went up on September 30. That claim is not what this index shows. Use the October 3 notice for surcharge scope.

Start with TaoHan security deployment and send the clause pack to contact.html?intent=security.

Catalog numbers: 15,309 to 15,846

Quick Answer: Previous public index: 2026-08-22, 15,309 SKUs. New public index: 2026-09-30, 15,846 SKUs. Added 537. Removed 0. The public index has no LIST column, so this page does not report a list-price month-over-month move.

Metric	Value	Buyer note
Previous catalog date	2026-08-22	15,309 public SKUs
New catalog date	2026-09-30	15,846 public SKUs
Net SKU change	+537	Part-number growth
Removed SKUs	0	No rename cleanup in this diff
Public LIST column	Not shown	Quote-oriented index

Counts are the public totals buyers should cite. Channel net stays industry estimate / pending confirmation until a dated quote lands. TaoHan does not print a public net on this page. For a domestic bid, ask the quote face to show catalog date 2026-09-30, the 13% VAT special invoice line, and a separate column if the October 3 surcharge also applies.

A state-owned or public-institution reviewer often scores a deviation when the bid BOM cites an older catalog date than the one named in the technical specification. Stamping 2026-08-22 after the index moved to 2026-09-30 is an easy deduction even when the chassis SKU itself is unchanged. The fix is a date stamp, not a blanket reprice.

August 22 vs September 30 index

Quick Answer: Versus August 22, September 30 mainly adds Advanced IP Defense subscription variants on existing PA platforms, plus a smaller set of data-security, ELA, power, and one FIPS kit SKUs.

Bucket	New lines	What to do on an RFQ
PAN-PA-* subscriptions	490	Mostly AIPD, including 3-year, 5-year, HA2, and 5G tails. Heaviest on PA-52R (86), PA-54R (28), PA-450R (24), PA-455 (24). Midrange 1400 / 3400 / 5400 families add about a dozen to 15 rows each.
ELA / modifier add-ons	about 23	FedRAMP-mod and SD-WAN ELA add-on codes (1/3/5 year), including PAN-*-ELA-FMOD patterns. Attach only on an ELA quote, not a one-box BOM.
Cortex Data / XDR / XSIAM	10	PAN-DATA-*, PAN-XDR-DATA-SECURITY, PAN-XSIAM-DATA-SECURITY, plus PAN-XDR-XTI and PAN-XSIAM-XTI.
Power supplies	5	PAN-PWR-1200W-AC-A (1200 W AC), PAN-PWR-1200W-DC-A (1200 W DC), PAN-PWR-530W-54V-AC-B (530 W), PAN-PWR-66W-12V-AC-A and PAN-PWR-66W-12V-AC-R (66 W).
FIPS kit	1	PAN-FIPS-KIT-56R for PA-56R. Hardware kit, not a subscription.

Limitation: Region, deal registration, and bundle eligibility can hide a code from a specific quote even when the public index lists it. Confirm the code, then confirm the commercial path. A code that is orderable on the September 30 index can still be outside a China enterprise agreement if the registration was filed against a different subscription set.

Compared with the August 22 catalog add, this September refresh is larger and subscription-heavy. August was a smaller part-number add. September’s +537 is mostly AIPD depth on platforms you may already own. Read the two dates as two index revisions, and read October 3 as the list-surcharge date.

What was added

Quick Answer: Do not paste all 537 lines onto a purchase order. Add AIPD when the security design names Advanced IP Defense. Add Data Security GB SKUs when ingestion and retention are in scope. Add power and the PA-56R FIPS kit only against the matching chassis.

Representative new codes (not the full list):

SKU	Read
PAN-PA-1410-AIPD	Advanced IP Defense, year 1, PA-1410 — the same pattern repeats across many PA models and terms
PAN-DATA-SECURITY	Cortex Data Security with DSPM, DLP orchestration, and DDR
PAN-DATA-PRO-GB	Daily ingested GB with stated hot/cold retention windows — size GB, do not guess
PAN-XDR-DATA-SECURITY / PAN-XSIAM-DATA-SECURITY	Data-security attach for XDR and XSIAM — match the platform you actually run
PAN-FIPS-KIT-56R	FIPS hardware kit for PA-56R
PAN-PWR-1200W-AC-A	1200 W AC supply — pair to the chassis power budget, not as a spare-by-default

PA-52R alone accounts for 86 of the new subscription rows. A branch refresh that does not include PA-52R should ignore that block. PA-54R adds 28, PA-450R adds 24, and PA-455 adds 24. If the tender names PA-450R and the incumbent subscription does not include Advanced IP Defense, leave the new AIPD tails off the bid. Loading them “because they are new” inflates the price and can fail a limited-price review.

Power supplies are hardware, not a subscription year. PAN-PWR-1200W-AC-A and PAN-PWR-1200W-DC-A are 1200 W. PAN-PWR-530W-54V-AC-B is 530 W. The two 66 W codes, PAN-PWR-66W-12V-AC-A and PAN-PWR-66W-12V-AC-R, belong on the small-platform power budget. PAN-FIPS-KIT-56R belongs on PA-56R only. A PA-450R site does not inherit that kit.

Data lines are quantity-sensitive. PAN-DATA-PRO-GB should carry a written GB assumption on the RFQ. PAN-XDR-XTI and PAN-XSIAM-XTI follow the detection platform you run. Mixing an XDR data SKU onto an XSIAM tenant is a line error, not a catalog error.

Removals

Quick Answer: Zero part numbers left the index between August 22 and September 30. There is no rename pair to search-replace in ERP from this diff.

Absence of a removal is not a promise that every old quote line is still the commercial default. Subscription term (1-year vs 3-year vs 5-year) and HA2 vs standalone still have to match the design. If a distributor quote uses a code that cannot be resolved, treat that as a mismatch. This diff deleted nothing, so an unresolved code is not evidence that September removed it.

For a renewal that already runs on the August 22 index, keep the incumbent subscription family unless the security design or the tender clause names Advanced IP Defense, Cortex Data Security, or a new power or FIPS kit. Operations can keep forwarding on the existing subscription set while procurement checks the new codes. A new row on the index does not force a cutover window.

RFQ how-to steps

Quick Answer: Cite 2026-09-30, validate the codes, add AIPD only if required, keep October 3 surcharge work on its own checklist, then send one BOM. TaoHan targets a mapped reply within 1 business day.

1. Step 1 — Stamp the catalog date. BOMs and comparison sheets should say Palo Alto catalog 2026-09-30, 15,846 SKUs. Drop 2026-08-22 as the active date.
2. Step 2 — Validate codes. Send the part-number list to TaoHan via contact.html?intent=security. Bulk paste is part numbers only. The public index confirms existence. It does not show LIST.
3. Step 3 — Decide AIPD per platform. New rows cluster on PA-52R, PA-54R, PA-450R, PA-455, and smaller sets on 1400 / 3400 / 5400. Match model, term, and HA2 flag. See the HA2 vs non-HA2 note before you copy an HA pair SKU onto a single firewall.
4. Step 4 — Size data SKUs in GB. PAN-DATA-PRO-GB and retention add-ons are quantity-sensitive. Write the GB assumption on the RFQ.
5. Step 5 — Split the October 3 track. If the quote also hits the October 3 surcharge, say so explicitly. Do not bury it inside “catalog +537.”
6. Step 6 — Attach the tender clause. Send the technical specification lines that name Advanced IP Defense, HA2, Data Security, power, or FIPS. TaoHan marks comply / deviate before the price column is filled, so a limited-price bid is not scored down for an unrequired row.
7. Step 7 — Lock the quote face. Ask for quantities, subscription years, China ship-to, need-by date, deal-registration status, and a 13% VAT special invoice on the confirmed lines. Until that quote is issued, any channel figure is an industry estimate / pending confirmation.

Common traps

• Catalog date vs surcharge date. September 30 is the part-number index. October 3 is the list-surcharge effective date for named families. They are separate events. Mixing them makes a bid look like every appliance rose because 537 codes appeared.
• Auto-adding AIPD. Listing a code does not mean the renewal must include it. Attach Advanced IP Defense only when the design or the incumbent subscription includes it. Extra rows can push a bid over a ceiling and draw a deviation penalty.
• HA2 vs standalone. Many new tails are -HA2 or -R. A single-firewall site should not inherit an HA pair SKU. Order quantity still follows nodes when an HA pair is real.
• ELA modifiers on a transactional quote. PAN-*-ELA-FMOD and GOV ELA add-ons belong on an enterprise agreement, not a one-chassis spare order.
• Expecting LIST on the public index. The public Palo Alto index does not publish a LIST column. A missing price is normal. It is not a broken row. Channel net stays pending confirmation.
• PA-52R volume. Eighty-six new rows on one branch model can dominate an export. Filter by the models you actually buy.
• Invoice and registration shortcuts. A 13% VAT special invoice follows the confirmed China delivery. Deal registration is a written commercial status. Neither is created by citing +537 on the bid cover.

Quality gate before you send the RFQ: the sheet should show catalog date 2026-09-30, the models in scope, AIPD yes or no per model, HA2 yes or no, GB if data SKUs are in scope, and a separate October 3 flag. Without those markers, a soft channel figure must not enter approved CapEx as a fixed number.

FAQ

References

• TaoHan Palo Alto RFQ — send part numbers for a catalog-date 2026-09-30 line check.
• Security deployment — firewall and subscription delivery for China sites.
• Palo Alto October 3, 2026 list surcharge — separate from this catalog delta.
• Palo Alto catalog delta August 22, 2026 — the prior public index date.
• Palo Alto Networks documentation — platform and subscription descriptions.

Key Takeaway

Related reading