A track and trace system that cannot be audited on demand is not a compliance system. It is a liability waiting to surface during an Inspectie Justitie en Veiligheid (IJenV) inspection.
Netherlands cannabis track and trace requirements apply to every licensed cultivator in the Wietexperiment from the moment a seed is planted to the moment dried flower is delivered to an authorised coffeeshop. Cultivators must integrate with the Track en Trace system operated by Justid (Justitiële Informatiedienst) on behalf of the Ministry of Justice and Security, a single mandatory government-provided platform. This article covers exactly what your system must record, which inspectorate oversees which obligations, how discrepancies trigger enforcement, and what record retention actually means in practice.
For the broader compliance landscape, the Wietexperiment Compliance Guide covers all six compliance areas in full, including Dutch cannabis cultivation laws and the NVWA quality testing requirements that run alongside the track and trace obligations. This article focuses specifically on the digital traceability and batch record layer.
What Does Netherlands Cannabis Track and Trace Require From Licensed Cultivators?
The Wietexperiment mandates a single government-provided Track en Trace platform, built and operated by Justid (Justitiële Informatiedienst) on behalf of the Ministry of Justice and Security. The Besluit (art. 33) and Regeling (art. 16) refer specifically to “het door Onze Ministers beschikbaar gestelde elektronische systeem”, the electronic system made available by Our Ministers. Cultivators do not choose a vendor from a marketplace of authorised ERPs. They onboard to the single mandatory system and integrate their operational software with it so that every material movement from seed or clone receipt through cultivation, harvest, processing, and distribution to coffeeshops is recorded in the Justid platform.
The core obligations are:
- Integration with the Justid Track en Trace platform – cultivators onboard to the single mandatory government-provided system, not a commercial ERP marketplace.
- Ongoing inventory reconciliation – the Regeling does not specify a daily frequency, but many cultivators reconcile daily as best practice; at minimum, reconciliation should occur at operationally sensible intervals so variances are caught contemporaneously.
- Full audit trail capabilities – every transaction, transfer, and adjustment should be individually traceable with timestamp, operator identifier, and reason code.
- Availability to regulators – data must be accessible to the Inspectie Justitie en Veiligheid (IJenV) for supply-chain and Track en Trace oversight, and to the NVWA for product-quality matters, on demand rather than reconstructed after the fact.
- Record retention throughout the experiment – Regeling art. 13(3) requires records to remain available throughout the entire experiment. Separately, Dutch general bookkeeping law (Burgerlijk Wetboek 2:10 and Algemene Wet inzake Rijksbelastingen art. 52) requires business records to be kept for 7 years, which applies to cultivators as Dutch companies.
- Batch-level traceability – every product tracked from seed or clone through cultivation, processing, and delivery to the named coffeeshop recipient.
- Stock discrepancy reporting – any unresolved discrepancy between physical stock and system records can trigger enforcement and suspension from the experiment.
The closed supply chain rule is the enforcement context behind all of these. Every gram your facility produces must be accounted for within the authorised chain: cultivator to licensed transporter to coffeeshop. Anything that cannot be traced represents potential diversion to the illicit market, which is the outcome the experiment is specifically designed to prevent.
What Must Your Netherlands Cannabis Track and Trace System Record at Each Stage?
The requirement is batch-level traceability, which means the record starts at the beginning of the cultivation cycle, not at harvest. For each batch your track and trace system must be able to produce a complete chain of custody showing every material event from input through sale.
| Stage | What Your T&T System Must Record | Minimum Data Fields |
|---|---|---|
| Propagation | Seed or clone receipt, genetic source, variety identification | Date received, supplier, strain ID, cannabinoid profile, quantity |
| Cultivation | Environmental conditions, input applications, plant count changes | Temperature, humidity, CO2 logs; pest management entries with product names; plant mortality records |
| Harvest | Fresh weight per batch, harvest date, operator signature | Batch ID, wet weight, harvest location within facility, authorised signatory with timestamp |
| Drying and Processing | Dry weight, moisture content, processing conditions | Pre-drying weight, post-drying weight, moisture percentage, drying duration, process parameters |
| Packaging | Serial-number label applied, THC/CBD percentage from NVWA-approved test, package weights | Package ID, batch reference, test result date, labelled cannabinoid content, net weight |
| Transfer and Distribution | Quantities, dates, receiving coffeeshop, transporter details | Delivery note number, coffeeshop name and licence number, transport operator, transfer weight, receipt confirmation |
Reconciliation runs across all active batches. Whenever the cultivator closes out a reconciliation cycle (many operators choose daily as a best practice, though the Regeling does not specify a frequency), the system must show that physical stock on hand plus all transferred and destroyed quantities equals the starting inventory for that batch. Any variance should be logged with a reason code so the Track en Trace record reflects the physical reality of the facility at that moment.
How Should Electronic Signatures Work in the Wietexperiment Batch Record System?
A search of the Besluit and Regeling for “elektronische handtekening” returns no hits, so electronic signatures are not a specific Wietexperiment statutory mandate. They are, however, industry best practice drawn from EU GMP guidelines and strongly recommended for any cultivator operating under a closed supply chain. A compliant electronic signature is not a typed name in a text field or a scanned wet signature. It should carry a timestamp, a unique operator identifier tied to that specific person, and a record of what was being attested. If a signature is applied to the wrong record, or applied by a shared account, the integrity of the audit trail for that step is broken.
The practical consequence is that every person in your facility who performs a critical process step should have their own system account. Shared login credentials are one of the most common issues inspectors flag during facility audits, because shared accounts make it impossible to assign individual accountability when a discrepancy is investigated.
Critical process steps that benefit from a dated, named electronic signature include seed or clone receipt, each cultivation cycle stage completion, harvest weight entry, post-drying weight confirmation, NVWA quality test result linkage, packaging approval, and distribution release. Each signature should carry the operator’s name, their role, the date and time, and the specific batch record being attested.
When Does a Stock Discrepancy Trigger Enforcement?
Track and trace supervision sits with the Inspectie Justitie en Veiligheid (IJenV), not the NVWA. NVWA’s role in the Wietexperiment is limited to product-quality testing (THC/CBD content, heavy metals, pesticides, microbial contamination, aflatoxins). Supply-chain integrity, access to the Justid Track en Trace data, and stock-discrepancy enforcement belong to IJenV. The Wietexperiment regulations do not specify a threshold below which a discrepancy is acceptable. Any unresolved variance between physical count and system record is a reportable discrepancy. The enforcement trajectory from discrepancy to suspension follows a predictable pattern:
- Discovery. An IJenV inspector or internal reconciliation identifies that physical stock does not match the system record. The discrepancy is logged with the date, batch, and magnitude.
- Investigation window. The cultivator has a limited period to document the investigation. Acceptable explanations include moisture loss within documented parameters, package weight variance within stated tolerances, or a recording error with a correcting entry. Each must be supported by contemporaneous documentation, not retrospective recollection.
- Escalation. Unexplained discrepancies escalate within the Inspectie Justitie en Veiligheid, whose mandate is to confirm no experiment cannabis is entering the illicit supply chain. At this stage, the cultivator’s supply authorisation is at risk.
- Suspension. Persistent or large unexplained discrepancies can result in suspension from the experiment. With only 10 licensed cultivators, suspension does not mean a pause in operations, it means the coffeeshops that sourced from your facility lose their compliant supply.
The weight of the enforcement consequence is disproportionate to the size of the experiment. That is intentional. The Wietexperiment’s political durability depends on demonstrating that a legal regulated supply chain has zero leakage to the illicit market. A cultivator with unresolved discrepancies is not just a compliance problem, they are a political liability for the entire programme.
What Constitutes a Compliant Audit Trail Under the Wietexperiment?
A compliant audit trail means every change to a record is itself a record. Deleting a batch entry and re-entering a corrected figure undermines the original record. An append-only or versioned system, where the original entry, the correction, the correcting operator, and the reason all persist and are retrievable, is the design principle commonly implemented in compliant seed-to-sale platforms, even though these specific technical requirements are not written into the Besluit or Regeling as statutory mandates.
Inspectors from the Inspectie Justitie en Veiligheid expect to be able to sit at your system terminal, pick any batch from any date during the experiment, and see the complete chronological log of every entry and change made to that batch record. If your system has a “delete” or “overwrite” function that does not create a correcting entry, the audit trail for that record is compromised regardless of what else the system captures.
Practical design principles commonly implemented for audit trail integrity include:
- Every record creation logged with timestamp and operator identifier.
- Every record modification logged as a new entry with reference to the original, operator identifier, timestamp, and reason for change.
- No record can be deleted without a logged reason and authorisation from a second named operator.
- The audit log itself treated as read-only; it cannot be edited or deleted through the application.
- The complete log for any batch exportable in a human-readable format promptly on request from the Inspectie Justitie en Veiligheid.
The licensed cultivators who are furthest ahead operationally have implemented seed-to-sale platforms that treat audit trail integrity as a database constraint rather than a policy. When immutability is enforced at the software layer, the cultivation team cannot accidentally create a compliance gap even under harvest pressure.
How Must Distribution Records Satisfy the Closed Supply Chain Requirement?
Every delivery from your facility to a coffeeshop must generate a distribution record that closes the loop on both ends. The cultivator creates a dispatch record before the product leaves the facility. The coffeeshop creates a receipt record when the product arrives. Both records reference the same batch identifiers, quantities, and transport details. If the two records do not reconcile within the system, the transfer is an open loop, which is a discrepancy.
Distribution records must capture the following per delivery:
- Delivery note number and date of issue.
- Batch ID and lot numbers of every product in the delivery.
- Net weight per batch, confirmed by both cultivator and transporter before departure.
- Name, licence number, and municipal location of the receiving coffeeshop.
- Transporter name, vehicle identification, and authorisation to operate within the experiment.
- Departure timestamp from the cultivation facility.
- Arrival timestamp and receiving confirmation from the coffeeshop.
The closed supply chain integrity requirement also means your track and trace system must flag any coffeeshop that is not on the current authorised list before a delivery can be dispatched. The list of Wietexperiment municipalities and coffeeshops is managed by the government and subject to change. Delivering to a coffeeshop that has been suspended from the experiment, even if the coffeeshop was authorised at the time of the previous delivery, creates a supply chain breach.
Frequently Asked Questions
What counts as an audit trail in the Wietexperiment?
An audit trail in the Wietexperiment context is a complete, chronological log of every entry, modification, and deletion made to any record in your track and trace system. Each entry should carry a timestamp, the operator’s unique identifier, and for modifications, the original value and the reason for the change. The Inspectie Justitie en Veiligheid (IJenV), which supervises the Track en Trace platform operated by Justid, expects to access any batch’s full history on demand. A system that allows overwriting or deletion without creating a correcting record does not provide a defensible audit trail, regardless of what other data it captures.
How long must records be kept under the Wietexperiment?
Two distinct retention obligations apply. Regeling art. 13(3) requires Wietexperiment records to remain available throughout the entire experiment. Separately, Dutch general bookkeeping law (Burgerlijk Wetboek 2:10 and Algemene Wet inzake Rijksbelastingen art. 52) requires business records to be kept for 7 years, which applies to cultivators as Dutch companies. Besluit art. 32(3)(b) delegates retention specifics to ministerial rules, and the Regeling itself only specifies a 3-month sample retention numerically. The 7-year figure comes from general tax and bookkeeping law, not from the Wietexperiment regulations themselves. Cloud-based platforms with contractual data retention guarantees are the practical way to ensure continuity, since physical servers and on-premise databases create single points of failure for long-term retention.
What triggers enforcement action for track and trace violations?
Track and trace enforcement sits with the Inspectie Justitie en Veiligheid (IJenV), not the NVWA. NVWA’s remit within the Wietexperiment is limited to product-quality testing. Any unresolved stock discrepancy between physical inventory and system records can trigger IJenV enforcement; no published numerical tolerance applies. Beyond discrepancies, enforcement is also triggered by failure to provide records on demand during an inspection, records that cannot be reconciled across the supply chain (cultivator and coffeeshop records that do not match), evidence of system tampering or retroactive editing, and failure to maintain an operationally reasonable reconciliation cadence. IJenV’s oversight escalates quickly when discrepancies raise questions about product diversion, which moves the matter from an administrative compliance issue to a criminal supply chain integrity investigation.
Do digital batch records need to be signed for every process step?
Electronic signatures are not a specific Wietexperiment statutory requirement; a search of the Besluit and Regeling for “elektronische handtekening” returns no hits. They are, however, industry best practice drawn from EU GMP guidelines and strongly recommended for any cultivator operating under a closed supply chain. Where you implement them, each signature should be individual (no shared accounts), timestamped, and traceable to a specific named operator, covering steps such as seed or clone receipt, cultivation stage completions, harvest weight entry, post-drying weight, packaging approval, and distribution release. Shared login credentials undermine the individual accountability that both EU GMP guidance and good operational discipline assume.
Can a standard cannabis ERP platform be used for Wietexperiment track and trace?
There is no vendor marketplace for the Wietexperiment Track en Trace system. The Besluit (art. 33) and Regeling (art. 16) refer specifically to “het door Onze Ministers beschikbaar gestelde elektronische systeem”, the single electronic system made available by the Ministers. That system is the Track en Trace platform built and operated by Justid (Justitiële Informatiedienst) on behalf of the Ministry of Justice and Security. Cultivators do not choose an authorised ERP, they onboard to Justid’s platform and integrate their operational software with it. A commercial seed-to-sale ERP can be used alongside the Justid system to handle day-to-day cultivation operations, but the regulated T&T record of truth lives in the single government-provided platform.
Get the Full Wietexperiment Compliance Guide
The PDF goes beyond track and trace: it covers NVWA quality testing standards, packaging and labelling rules, facility security requirements, and the full cultivator priority action checklist for 2026.
Download Free Wietexperiment GuideRecommended For You
Saint Lucia Selects GrowerIQ to Power National Cannabis Traceability Programme
April 20, 2026Germany’s Cannabis Market Hits EUR 670M: How 900,000 Patients Are Reshaping Europe’s Largest Market
April 17, 2026Mexico’s Cannabis Gray Market: Legal Personal Use but No Commercial Framework in Sight
April 16, 2026About GrowerIQ
GrowerIQ is changing the way producers use software - transforming a regulatory requirement into a robust platform to learn, analyze, and improve performance.
To find out more about GrowerIQ and how we can help, fill out the form to the right, start a chat, or contact us.