The Article 14 early warning identifies, where applicable, the Member States where the manufacturer knows the product was made available. The coordinating CSIRT ordinarily uses that availability information when disseminating the notification to other relevant coordinating CSIRTs.
The field therefore needs a product-distribution record with evidence, not an improvised list assembled during the first hours of an incident.
Combine the distribution channels
Map direct sales, app or package distribution, licences, marketplaces, importers, distributors, and embedded-product channels. For each source, record the product, version coverage, territory, period, data owner, and extraction time.
Distinguish the place of a contracting entity from the territory where the product was made available. Avoid using billing addresses as the sole proxy when distribution records give a different answer.
Preserve source provenance
For every channel extract, record the system, query or selection rule, extraction time, owner, covered period, product identifiers, and known exclusions. Keep raw evidence under the organisation’s access controls and link the derived territory decision to it.
Reconcile overlapping channels. A direct sale and distributor record may describe the same unit or licence. Duplicates may distort a count used elsewhere even though this record ultimately needs a supported territory state.
Where a marketplace or download route lacks reliable location evidence, mark the limitation. An accessible global page does not supply a verified Member State list on its own.
Express what is known
Create three states for each Member State: supported by current evidence, reasonably excluded by current evidence, or unresolved. Give unresolved states an owner and a next check. The early warning can then reflect what the manufacturer knows without disguising missing data as certainty.
Freeze the evidence snapshot used for the submission. If later sales or channel records change the list, retain the original and add the corrected scope at the next reporting stage.
Require a reason for every change: newly received channel data, corrected product mapping, changed version scope, or an error in the earlier extract. Keep the former state and the reviewer who approved the correction.
Keep product granularity
Do not reuse a company-wide market footprint for every case. A particular product family, release, or distribution period may have a narrower or different territorial record. Link availability to the same canonical product identifiers used in the report.
Test the process with a product sold through more than one channel and a version distributed through an intermediary. The exercise should reveal who can access the underlying records within the early-warning window.
Add an unresolved-territory scenario. The reporter should be able to state what the manufacturer knows, preserve the gap, identify its owner, and continue the approved reporting handoff without inventing a complete market map.
The result is a controlled availability table that supports both the manufacturer’s statement and the authority routing that follows it.
Continue this workflow with the onward-dissemination map and the coordinating-CSIRT analysis.