A battery-powered Android tablet sold into the EU in 2027 sits inside at least three regulatory clocks, and none of them starts on the same day. The firmest near-term date for a standard tablet SKU is 18 February 2027, when the removability and replaceability rules of the Battery Regulation (EU) 2023/1542 apply to portable batteries built into products. The Cyber Resilience Act’s vulnerability and incident reporting duty is already live — it has applied since 11 September 2026 — while the electronics Digital Product Passport under the ESPR has no dated obligation yet, because no delegated act for an electronics product group had been adopted as of October 2026. The EU AI Act milestones that matter for tablet hardware could not be verified from the public sources used for this page, so no date is printed for them here.
Before reading the calendar, answer three questions about the SKU. One: does it contain a portable battery, and is that battery sealed into the shell? Two: does it have any data connection — including a USB-C data port, not only a radio? Three: does it ship with on-device AI features, or with an AI application pre-installed by the factory? Those three answers decide which rows below apply, and each row translates into a document your OEM must be able to produce. That is the point of this page: a date you cannot evidence is a supplier-selection problem, not a calendar entry.
Two disclaimers, stated once and applying throughout. Every date below is attributed to a named public publisher and the date that publisher’s page carried when retrieved; this page is not legal advice and does not substitute for the consolidated legal text, which should be re-checked before a purchase order is signed. And where a dating step has not been taken, the row says so rather than offering a plausible-looking year.
The dated calendar: regulation, obligation, applies-to condition, deadline, document
| Regulation and article | Obligation | Applies to your tablet if… | Date (publisher, publication date) | Document to hold on file |
|---|---|---|---|---|
| CRA (Regulation (EU) 2024/2847), Articles 14 and 71 | Report actively exploited vulnerabilities and severe security incidents to the national CSIRT and ENISA; early warning within 24 hours of becoming aware | Any tablet whose intended or reasonably foreseeable use includes a data connection — USB counts, not just radio | In application since 11 September 2026 (EU hardware compliance calendar, published 19 October 2026) | Vulnerability-handling and coordinated-disclosure policy; named incident contact; component inventory (SBOM) |
| CRA, Article 69(3) | Reporting duty extends to in-scope products placed on the market before full application | Units already in your channel or a distributor’s warehouse | Same reporting regime as above (EU hardware compliance calendar, 19 October 2026) | Serial-range and ship-date list per SKU, so the reporting clock can be traced to a batch |
| CRA, full obligations | Essential cybersecurity requirements, conformity assessment, CE marking | In-scope tablets placed on the EU market from that date | 11 December 2027 (EU hardware compliance calendar, 19 October 2026) | Technical file index; EU Declaration of Conformity; the test report behind whatever standard route the OEM cites |
| Battery Regulation (EU) 2023/1542, Article 11 | Removability and replaceability of portable batteries incorporated in products | Sealed portable pack of 5 kg or less, not EV, LMT, SLI or specifically industrial | 18 February 2027 (Element, “Battery Regulation Compliance Deadlines”, retrieved without a stated publication date; corroborated by an ecocomply summary of Article 96(2)) | Battery design statement per SKU: end-user replaceable, service-replaceable, or derogation claimed with the article reference |
| Battery Regulation, Article 13(6) | QR code requirement | Tablet containing an in-scope battery | 18 February 2027 (Element) | Approved label artwork and the content the QR resolves to |
| Battery Regulation, Article 77 | Battery passport | LMT, EV and industrial batteries over 2 kWh — a standard tablet portable pack is not in that set; confirm your cell category in writing | 18 February 2027, for the categories the charge applies to (EU hardware compliance calendar, 19 October 2026; Element) | Written category statement from the cell maker and the pack assembler |
| Battery Regulation, Article 13(1) | General information labelling | In-scope batteries | 18 August 2026 — Element describes this date as contested and recommends planning for it as though fixed | Label artwork; supplier confirmation of the applied marking |
| Battery Regulation, Articles 7–10 | Carbon footprint, recycled content and related thresholds | In-scope batteries, moving with delegated and implementing acts | Recycled content minimums under Article 8(2) from 18 August 2031 (Element); other thresholds move with the acts | Cell-level supplier declarations and carbon data, requested now even though the date is distant |
| Battery Regulation, due diligence | Supply-chain due diligence obligations | Companies in scope of the chapter | Reported by one publisher as postponed to August 2027 — publisher-reported, verify against the Official Journal before relying on it | Supplier due-diligence questionnaire and sourcing map |
| ESPR (Regulation (EU) 2024/1781), Digital Product Passport for electronics | Passport requirements for the product group | Every tablet eventually — but only once a delegated act sets the requirement | No adopted act / date not verifiable. ESPR in force 18 July 2024; Working Plan 2025–2030 adopted 16 April 2025; no delegated act for an electronics product group adopted as of October 2026 (EU hardware compliance calendar, 19 October 2026) | Data spine: component-level BOM, material and recycled-content data, repairability and spare-part terms, supplier carbon data |
| ESPR Working Plan, repairability and displays measures | Indicative adoption years only | Tablets as a product group | 2027 indicated as an adoption year — indicative only and imposes no obligation (EU hardware compliance calendar, 19 October 2026) | Nothing dated; track the delegated acts instead |
| Toy Safety Regulation, electronic toys | Product passport for electronic toys | A kids tablet positioned and marketed as a toy | 1 August 2030 (EU hardware compliance calendar, 19 October 2026) | Positioning decision recorded; passport data plan if the SKU is sold as a toy |
| EU AI Act | Provider and deployer obligations depending on role and feature type | Only if the tablet ships AI features — see the scope section below | Date not verifiable from this research set — intentionally not printed. Check the consolidated text before quoting a date in a tender | Written statement of factory pre-installed AI features, provider identity for each, and on-device versus cloud execution |
| RoHS / REACH | Standing substance restrictions, re-checked on a cycle | All tablets | Standing requirement, not a single date (EU hardware compliance calendar, 19 October 2026) | Current material declarations per part family |
One footnote worth more than the table. Category matters more than the headline date. The 18 February 2027 battery passport charge applies to LMT, EV and industrial batteries over 2 kWh, so a standard tablet portable pack does not sit in it — but the Article 11 removability rule on the same date does reach a sealed pack at or under 5 kg. Two obligations, one date, different scope. Buyers who read only the date get the scope wrong in both directions.
CRA: your tablet was probably in scope before you read this
The scope test is narrower than most buyers assume, and wider than most sales decks admit. The CRA reaches hardware whose intended purpose or reasonably foreseeable use includes “a direct or indirect logical or physical data connection to a device or network” (Article 2(1), as summarised by the EU hardware compliance calendar dated 19 October 2026). A USB-C data line satisfies that; a Wi-Fi-only SKU with no data port still satisfies it through the radio. Medical devices, motor vehicles and several other sectors are carved out under their own legislation — a tablet used as a POS terminal accessory is not one of those carve-outs, and the PCI MPoC documentation path for payment devices is a separate track that does not replace CRA obligations (see the SoftPOS Android tablet PCI MPoC compliance checklist for that adjacent file).
What is already running is the reporting duty: since 11 September 2026, manufacturers must report any actively exploited vulnerability in their product and any severe security incident affecting its security to the national CSIRT designated as coordinator and to ENISA, through ENISA’s single reporting platform, with an early warning inside 24 hours of becoming aware (Articles 14 and 71, per the same calendar). Article 69(3) extends that duty to in-scope products placed on the market before December 2027 — which is the row that catches warehouse stock you already own.
What arrives on 11 December 2027 is the rest: essential cybersecurity requirements, conformity assessment and CE marking. The document request this implies is concrete. Ask for the vulnerability-handling and coordinated-disclosure policy as a controlled document, not a paragraph in a brochure. Ask who holds the incident-reporting clock and whether that person is reachable inside 24 hours on a weekend. Ask for the security update support window in years, written into the supply contract, because an updatable device and an abandoned device look identical at the quotation stage.
Does this apply to my tablet? If it has a USB data port or a radio and it will be on the EU market after 11 December 2027, yes — and the reporting duty already applies today.
Battery Regulation: 18 February 2027 is a tooling decision, not a paperwork decision
Article 11 removability and replaceability applies from 18 February 2027 to portable batteries incorporated in products — sealed cells of 5 kg or less that are not EV, LMT, SLI or specifically industrial (Element; ecocomply, citing Article 96(2) of Regulation (EU) 2023/1542). Element notes that the Regulation entered into force on 17 August 2023 and has applied since 18 February 2024 under Article 96, but that most substantive obligations arrive later and on different dates per battery category. There is no single compliance date.
Translated into tablet terms: an adhesive-bonded pack inside a sealed unibody shell is the design that gets questioned. The document to demand is a battery design statement per SKU that states, in writing, whether the pack is end-user replaceable, service-replaceable with tools, or claimed under a specific derogation — and if a derogation is claimed, which one. A verbal assurance is not a document. Public commentary notes that specific derogations and product rules can change who performs the replacement, which is precisely why the claim needs an article reference rather than a sentence.
Three obligations land on the same February date: Article 11 removability, the Article 13(6) QR code and the Article 77 battery passport. The passport charge is limited to LMT, EV and industrial batteries over 2 kWh, so the practical tablet question is not “how do I build a passport” but “can my suppliers prove which category my cell falls into.” Ask the cell maker and the pack assembler separately; the answers sometimes differ. For the current device families — the T616 11.97-inch business tablet, the T606 10.36-inch business tablet and comparable models — the correct starting point is a per-SKU statement, not a family-level one.
Does this apply to my tablet? If the battery is sealed in and the pack is at or under 5 kg, yes from 18 February 2027 — unless a specific derogation genuinely covers your design, which must be cited.
ESPR and the Digital Product Passport: the discipline is not building to a date nobody has set
This is where most compliance calendars quietly mislead. The ESPR entered into force on 18 July 2024 and its Working Plan 2025–2030 was adopted on 16 April 2025. DPP requirements for any given product group arrive only through later delegated acts — and as of the calendar dated 19 October 2026, none had been adopted for an electronics product group (EU hardware compliance calendar). The Working Plan’s 2027 indication for horizontal repairability requirements and displays is an indicative adoption year for those acts, not an obligation.
Public sources disagree, and the disagreement is worth showing rather than smoothing over. One DPP deadline tracker lists electronics as “expected 2028 to 2029” against the ESPR plus RoHS/WEEE. That is an expectation, not a compliance date, and it sits against a 2027 adoption indication elsewhere. Neither figure obliges anyone. Build to the delegated act, not to the tracker.
What to do instead is unglamorous and useful: assemble the data spine now so that whichever act lands first, the file already exists. Component-level bill of materials. Material and recycled-content data. Repairability and spare-part availability terms, which is where the Article 11 battery answer and the ESPR repair agenda converge. Supplier carbon data, because carbon-footprint obligations in the Battery Regulation already move with delegated and implementing acts.
One adjacent passport does have a date: electronic toys from 1 August 2030 under the new Toy Safety Regulation (same source). If a kids SKU such as the T1000 kids tablet is marketed as a toy rather than as an educational device, that row becomes live for you years before any tablet passport does. The positioning decision is a compliance decision.
Does this apply to my tablet? Not yet on a set date — no adopted act exists for electronics. Collect the data anyway, and record why: an obligation with no date is a data-readiness project, not a deadline.
EU AI Act: the scope questions you can answer now, and the dates you should not print
No primary source in the research used for this page supports a specific AI Act milestone date applicable to tablet hardware, so this page does not print one. If a supplier or a tender document quotes a date, verify it against the current consolidated text and the specific article, not against a summary slide. Stating a date you cannot source is a worse outcome than stating a gap.
The scope question that actually decides a purchase is answerable today, though. Ask whether the tablet ships with on-device features that infer, translate, assist or classify — a voice assistant, camera-based detection, on-device summarisation — and whether your organisation puts its name on the device. That second half matters because brand owners who place their name on a product can carry obligations that a bare-metal OEM does not, and the split is rarely discussed at quotation stage.
Three shipping models produce three different documentation footprints. First, bare Android with no added AI features: the file is thin, and the answer is a written negative statement. Second, OEM-supplied AI application pre-installed at the factory: you need the provider identity for that application and confirmation of whether inference runs on-device or calls a cloud endpoint. Third, AI features delivered by your own software on top of OEM hardware: the OEM’s obligation shrinks and yours grows, which is a commercial fact worth knowing before you sign.
The document to request is a short written statement covering which AI features are pre-installed at factory, who the provider of each is, where inference executes, and what logging or human-oversight artefacts the OEM can supply. Keep it in the same technical file as the CRA evidence — the same document is being asked to answer both questions, and a supplier who can only produce one of the two has a gap you can see before you buy.
Does this apply to my tablet? Only if it ships AI features or factory-installed AI software — and the applicable date is a gap in this page, deliberately.
The OEM document request list, mapped to dates rather than document types
Grouping by date is what makes a checklist usable in a sourcing meeting. Grouping by document type produces a folder nobody opens.
Already required (CRA reporting, live since 11 September 2026)
- Vulnerability-handling and coordinated-disclosure policy, as a controlled document with a version and an owner.
- Incident-reporting contact with a named individual and an out-of-hours route — the 24-hour early warning does not wait for a quarterly review.
- Component-level inventory the OEM can actually regenerate for a shipping SKU. Test: ask for one SBOM for a model you are buying, not a template.
- Security update end-of-support statement with a committed number of years.
Required before 18 February 2027 (Battery Regulation)
- Battery design statement per SKU: replaceable by end user, service-replaceable, or derogation claimed with the article reference.
- Cell specification and cell-maker declaration, including the battery category in writing.
- Statement of who performs replacement and with what tools, plus the spare-part availability term.
- Label artwork showing the Article 13(6) QR code, and confirmation of Article 13(1) general information labelling.
Required before 11 December 2027 (CRA full application)
- EU Declaration of Conformity and the technical file index per SKU.
- The test report behind whichever standard route the OEM intends to cite. A standard number in a sales deck is not evidence; the report is.
- Conformity assessment route documented, with the assessment body named where one is involved.
No date yet — collect anyway (ESPR DPP, AI Act)
- OEM statement of DPP readiness naming the data fields it can export per SKU today, and a commitment to supply them machine-readably on request.
- AI feature statement: pre-installed features, providers, on-device versus cloud, oversight artefacts.
- Supplier carbon and recycled-content data at cell and major-component level.
The test to apply on receipt. Does the DoC name the exact model designation and the standards cited, or only the product family? Does the battery statement name an article, or use the word “compliant”? Does the SBOM list components by version, or by category? Those three questions separate a file from a folder of assurances.
How to check a supplier’s compliance claim before you sign
Four checks work better than a questionnaire, because they cannot be answered with a template. Cross-read the DoC model designation against the purchase-order SKU — a mismatch is common and it invalidates the file for your shipment. Request one regenerated SBOM for a currently shipping SKU and compare it to the one you were given during the bid. Ask the OEM to walk through one hypothetical vulnerability report from discovery to the 24-hour early warning, naming who does what. And ask for the compliance document change log: a supplier whose technical file has not changed since 2025 has not read the 2026 dates.
Compare two quotations on documentation scope rather than unit price, and ask what is included at quotation stage versus after tooling payment. The honest caveat is that none of these checks transfers legal responsibility away from the EU importer or brand owner to the factory. They reduce the risk of discovering a gap in 2027; they do not remove it.
Stock already built, and stock in the warehouse
Two populations need separate plans. Units placed on the EU market before the CRA’s full application date remain caught by the reporting duty under Article 69(3) (EU hardware compliance calendar, 19 October 2026), so “old stock” is not a safe harbour. For the battery question, existing tooling with a bonded pack needs a written OEM position on service-replaceability, and a decision on whether to sell through before 18 February 2027 or fund a design change. If you are simultaneously planning 2027 build volumes, the memory-side sourcing question runs in parallel — see the tablet DRAM allocation strategy for 2027 — but compliance dates and allocation windows should not be managed by the same person in the same week.
Name the decision owner for each row before the end of the review. The reporting duty runs on a 24-hour clock and cannot route through a quarterly supplier meeting, which is the single most common structural gap we see in procurement-side compliance plans.
Turn the calendar into a purchase decision
The calendar produces three filters, and they are the ones to apply to every quote you receive. Battery replaceability: a design statement with an article reference, or the SKU is a 2027 write-off risk. CRA documentation depth: a regenerable SBOM and an owner on the reporting clock, or the reporting duty becomes your problem with no lever to pull. Honest handling of undated regimes: a supplier who invents a DPP year or an AI Act date to sound current is telling you something about every other document in the pack.
An OEM that cannot produce the first two is not shortlistable for an EU programme that ships past February 2027, regardless of unit price.
Request the OEM compliance document package and a dated compliance roadmap for your device program. The package should include the technical file index, an SBOM sample for a shipping SKU, the DoC draft, the battery design statement and the CRA readiness pack — mapped against the dates in your own launch plan. Start with the Snapdragon 685 11.97-inch business tablet as a reference platform, or send your SKU list and target EU markets and ask for the roadmap against those models specifically.




