Fragrance Product Expiry Dating: PAO, BBE, and Shelf Life Claims

Shelf life claims are one of the most common points of friction between fragrance suppliers and brand owners. A buyer wants the longest possible dating to protect retail margins; a regulator wants a defensible claim backed by data; a consumer wants a product that still performs when opened. This article explains the regulatory frameworks for expiry dating, the test methods that support them, and the documentation B2B buyers should require.

The Three Dating Concepts

• Minimum Durability Date (MDD) — the date until which the product, stored correctly, retains its declared properties. In the EU this is shown as “best before” with the hourglass symbol or “best before end” (BBE) followed by the date.
• Period After Opening (PAO) — the number of months a product remains safe and effective after first opening, shown as the open-jar symbol with a number, for example “12M.”
• Manufacture date / batch code — required for traceability even when an expiry date is not.

EU Rules (Regulation 1223/2009)

For cosmetic fragrance products sold in the EU:

• A Minimum Durability Date is mandatory when shelf life is below 30 months.
• When shelf life exceeds 30 months, the MDD is replaced by a PAO declaration, unless the product cannot deteriorate or has no realistic risk of harm after opening.
• The PAO must be supported by stability and preservative efficacy data.
• Single-use products, sealed aerosols, and products with no realistic post-opening deterioration may be exempt from PAO, with justification in the Product Information File (PIF).

For non-cosmetic fragrance products (candles, reed diffusers, household room sprays), dating is governed by general product safety and consumer information rules rather than Regulation 1223/2009, but BBE dating is still common practice and often required by retailers.

US and Other Markets

• The US FDA does not require expiry dating on cosmetics, with the exception of over-the-counter drug products, but recommends it for products with limited stability. California and Amazon impose their own de facto requirements.
• Canada requires expiry dating only for products with a shelf life below 30 days under the Cosmetic Regulations.
• China NMPA requires shelf life declaration on the label, expressed as either a production date plus shelf life or a single expiry date.
• Australia follows general consumer law; expiry dating is required where the product has a defined shelf life.

The Test Methods That Support a Claim

A defensible shelf life claim is built on three pillars:

1. Stability Testing (ICH Q1A-style)

• Long-term: 25 degrees Celsius / 60 percent RH for the proposed shelf life.
• Accelerated: 40 degrees Celsius / 75 percent RH for 6 months.
• Stress: 50 degrees Celsius, freeze-thaw, and UV per ICH Q1B.

Pass criteria typically include colour Delta E below 2.0, odour score within acceptance, density within plus or minus 1 percent, pH within plus or minus 0.5, and key marker degradation below 10 percent.

2. Preservative Efficacy / Challenge Test (ISO 11930)

For water-containing products such as room sprays, lotions, and emulsions:

• The product is inoculated with five reference organisms: Pseudomonas aeruginosa, Escherichia coli, Staphylococcus aureus, Candida albicans, and Aspergillus brasiliensis.
• Viable counts are measured at T0, T7, T14, and T28.
• Pass criteria (ISO 11930 Annex A): bacteria must reduce by at least 1 log at T7, 3 log at T14, and remain stable or further reduce at T28; fungi must remain stable or reduce throughout.

A product that fails the challenge test cannot support a multi-year shelf life claim, regardless of stability data.

3. Microbial Limit Testing (ISO 21149 / ISO 17516)

• General products: below 1000 CFU/g.
• Eye-area and children’s products: below 100 CFU/g.
• Specified pathogens absent in 1 g.

From Data to a Label Claim

A defensible dating decision follows this logic:

1. Run accelerated stability for 6 months.
2. Run long-term stability in parallel.
3. Run ISO 11930 challenge test on the finished product in its primary packaging.
4. If 6-month accelerated data is clean and challenge test passes, a 24-month provisional claim is supportable.
5. Confirm against 12-month and 24-month real-time data before extending to 36 months.
6. Set PAO based on the worst-case post-opening simulation, typically 6M, 12M, or 24M.

Pass/Fail Criteria at a Glance

Parameter	Acceptance
Accelerated 6-month stability	All parameters within specification
Long-term 12-month stability	All parameters within specification
ISO 11930 challenge test	Meets Annex A criteria for bacteria and fungi
Microbial limits at end of shelf life	Below 1000 CFU/g general; below 100 CFU/g sensitive
PAO simulation	No microbial growth, no sensory drift

Documentation Buyers Should Require

• Stability protocol and raw data, including accelerated and long-term tracks.
• ISO 11930 challenge test report from an accredited laboratory.
• Microbial limit reports at T0 and end of shelf life.
• A signed shelf life justification statement, naming the supported duration and storage conditions.
• PAO justification, including post-opening simulation data.
• Batch code system that allows traceability to the production date.

Common Buyer Mistakes

• Setting shelf life from accelerated data alone, without real-time confirmation.
• Skipping the challenge test for “natural” products, which often fail.
• Using a single PAO across an entire range without product-specific data.
• Printing a 36-month claim before the 36-month real-time data exists.
• Forgetting that primary packaging interacts with the formula and must be tested in-pack.

Closing Note

Shelf life claims are only as strong as the data behind them. Buyers who require stability, challenge test, and microbial data on the finished product in its actual packaging protect themselves against post-launch failures and regulatory challenge. Aromiso supports every custom programme with a stability protocol, ISO 11930 challenge testing where applicable, and a written shelf life and PAO justification, released to the buyer as part of the technical documentation package.