CRA support period on the product page
Show the support-period end date at purchase — the duty file alone is not the offer
CRALedger Duty Records (Shopify App Store) is a Shopify app that tracks product roles, checklists and open record gaps, Article 14 incident deadlines, and encrypted ENISA SRP draft packs, with exportable record packs and chronological audit evidence. It does not display the support period on the storefront, does not file on ENISA, does not determine your legal role, and does not certify CRA compliance.
Related: EUDR Records Manager — DDS reference numbers on supplier lots.
Free check first: CRA role and scope self-check runs in your browser and sends nothing. Describe a product and your role and see which articles of Regulation (EU) 2024/2847 to read.
Job: put the support-period end date on the live product page at the time of purchase — at least the month and the year, clearly, in an easily accessible place. Keeping that date in a backend duty file is not the same as showing it on the offer.
What Art. 13(19) requires at the time of purchase
Manufacturers “shall ensure that the end date of the support period referred to in paragraph 8, including at least the month and the year, is clearly and understandably specified at the time of purchase in an easily accessible manner and, where applicable, on the product with digital elements, its packaging or by digital means” (Regulation (EU) 2024/2847, Art. 13(19)). For a Shopify distance sale, the practical place is the product page before Add to cart, for example “Security updates until 12/2031”.
Art. 13(8): manufacturers determine the support period so that it reflects the length of time the product is expected to be in use. “Without prejudice to the second subparagraph, the support period shall be at least five years. Where the product with digital elements is expected to be in use for less than five years, the support period shall correspond to the expected use time.”
These product obligations apply from 11 December 2027 (Art. 71(2)). Article 14 reporting already applies from 11 September 2026. Confirm the live articles, not this paraphrase. This page is not legal advice.
Sources: Regulation (EU) 2024/2847 on EUR-Lex (CELEX 32024R2847; consolidated 02024R2847-20241120) and the Commission’s Cyber Resilience Act page.
Who shows the date — manufacturers specify it; distributors verify it
Manufacturers ensure the end date is specified at purchase. Before making the product available on the market, distributors must verify that the manufacturer and the importer complied with Art. 13(19), among other obligations (Art. 20(2)(b) lists Art. 13(15), (16), (18), (19) and (20) and Art. 19(4)). A reseller should check that a date was supplied and is shown, and should not invent a support period.
That role analysis applies only to in-scope products with digital elements placed on the EU market — not to ordinary non-connected goods. For “does the CRA apply, and in which role?”, use the sibling Does the CRA apply to my store, and in which role?. This page does not expand into full role legal advice.
Native Shopify path — a metafield near price / Add to cart
No app is required to display the date. Store it as a product metafield (single-line text or date) and render it with the theme’s text / metafield block near the price.
- Settings → Custom data → Products → Add definition. Use single-line text or date, for example namespace/key
custom.security_updates_until, with a storefront label such as “Security updates until”. - Fill the field on each in-scope product. Use month and year at minimum (MM/YYYY). Do not invent a date the manufacturer never supplied.
- Online Store → Themes → Customize → Product template → add a Text or metafield block near the price / Add to cart, and connect the metafield as a dynamic source.
- Open the live product page. Confirm the line is visible before purchase, without opening a buried description tab.
Empty metafields should stay off the page so you do not publish a blank “until” line. Confirm the live PDP after you save the theme.
App path — record the date in the duty file, then check the live PDP
CRALedger keeps the duty file (role, support period, contact point, open gaps) and the Article 14 clocks. It does not push the support-period string to the theme. Record the same date you show on the offer, then confirm the live PDP still shows that date.
- Open the CRALedger Duty Records listing (
apps.shopify.com/craledger-duty-records) and install it on the store that sells in-scope products with digital elements. - Record the product role, support period, contact point, and open gaps. Track Article 14 clocks in the same file.
- Keep the storefront metafield / theme block in sync with that recorded date. The app does not write the theme string for you.
- Open the live product page and confirm the month-and-year line still matches the duty file.
The app stores duty records you enter. It does not display the date on the storefront, file on ENISA, or decide your role. This page is not legal advice.
What this page is not
- Not a full Article 14 / ENISA how-to. That path is CRA duty records before an incident.
- Not GPSR responsible-person fields. That job is GPSR manufacturer fields vs responsible person.
- Not an EUDR DDS lot registry. That job is DDS reference numbers on supplier lots.
- Not legal advice, a role determination, or a CRA compliance certification.
- Not “every Shopify SKU needs a CRA date.” Ordinary non-connected goods are outside this page’s job. Confirm Regulation (EU) 2024/2847 before you treat a product as in or out of scope.
Related pages
- Cyber Resilience Act duty records — Article 14 product file, roles, ENISA drafts; not this purchase-time display job
- CRA vulnerability forwarding vs Article 14 ENISA filing — importer/distributor manufacturer-notice, not the support-period offer
- CRALedger Duty Records — live App Store listing
- Shopify apps hub — CRALedger Duty Records
Not legal advice. Not a compliance guarantee. Confirm Regulation (EU) 2024/2847 Art. 13(8), 13(19), 20(2)(b) and 71(2) before you publish a support-period line. The app keeps the duty file you enter; it does not render the date on the storefront. You still file Article 14 notifications on ENISA’s platform.