A farm may already have GACP in hand and still submit the wrong dossier. The processor is reading a different file: methods, records, formats, deviations, traceability, and release logic.[2][3][8]
That file matters because EU-GMP toll processing is the mandatory gate for flower entering Germany today.[4][7] The route can only move if the processor accepts the batch into its own controlled system.
The practical question is simple. Can the farm produce a package that the processor can read without rebuilding it first?[2][3]
GACP records are necessary and still incomplete for intake
GACP covers cultivation discipline, hygiene, records, and traceability at the farm.[8] Processor intake asks a narrower and harder question. Can the batch enter a manufacturing file that will later support QP release, importer review, and German market movement?[3]
That is why farms often discover the gap late. They prepared around the certificate they already had rather than the processor file they still had to enter.
"The batch file has to survive a processor before it ever reaches Germany."— EudraLex documentation and release rules, BfArM trader guidance
Method alignment is usually the first hard gate
A certificate of analysis is only useful if the target processor and the downstream importer accept the methods behind it.[1][4] Method names, validation status, quantification limits, sample handling, and lab format all matter when the file leaves the farm.
This is one reason readiness work begins before the first batch. The farm has to know which tests are being run, how they are being run, and whether the results can survive outside review.
The COA has to speak the processor language
Processors and importers are not reading a COA as marketing collateral. They are reading it as a controlled record that sits beside the batch history.[2][3] Identity, cannabinoid content, microbial status, impurities, and any product-specific limits have to line up with the route that follows.[1]
A farm can have strong cultivation practice and still present a COA that arrives in the wrong structure, with the wrong reference points, or without the supporting context the processor expects.
Traceability has to survive the tolling step
The intake file has to connect cultivation records, post-harvest records, retained samples, testing results, and the batch identity that will later pass through processing.[2][3] If one identifier changes without explanation, the route slows down fast.
That is why the batch package has to be designed early. The farm file is preparing to move into another company, another jurisdiction, and another release standard.
Format is part of quality
Chapter 4 of EudraLex treats documentation as part of quality assurance itself.[2] In practice, that makes format a live issue. Current versions, signatures, change history, and record structure affect whether the processor can use the document at all.
Good farms still lose time here. The content may be sound. The package arrives in a form that does not fit the receiving quality system.
Stability and retention questions arrive later than most farms expect
Readiness work often starts with cultivation and COAs. The file later widens toward stability, retained samples, document retention, and the evidence needed when a batch is read months after harvest.[2][3]
That is where a farm begins preparing for more than the first batch. The same controlled habits that support processor intake also support later on-site EU-GMP site preparation.
Processors usually read in an order
They start with admissibility. Then they test whether the batch identity, methods, and records hold together. Then they decide whether the intake package can sit inside the manufacturing and release file without being rebuilt.[2][3]
That order matters because a farm can answer the right question too late. A strong method summary does not rescue a weak traceability file. A clean batch record does not rescue a COA the processor cannot use.
The same package later supports the German side
BfArM's trader guidance asks the German participant to stand behind named products, origin, source, and the medical state-control basis for cultivation.[4] The import leg under § 72 AMG then sits on top of that route.[7]
The processor file therefore does not end at the processor. It becomes part of the German importer file later in the chain.
A processor-ready batch package is a serious operating asset
The farms that move cleanly into Germany are usually the farms that learned to produce the same batch package every time, in the same structure, with the same discipline.[2][3] That is what readiness looks like in practice.
It also explains why later on-site EU-GMP site preparation does not begin from zero. The document habits are already being built while the toll-processing route is still doing the market-entry work.[4][7]
Primary Sources
- EDQM / European PharmacopoeiaCannabis flower monograph and related quality standards2025
- European CommissionEudraLex Volume 4 - Chapter 4 Documentation↗
- European CommissionEudraLex Volume 4 - Annex 16 Certification by a Qualified Person and Batch Release↗
- BfArMHinweise fuer Haendler nach § 4 MedCanG (Stand 09/25)2025-09↗
- BfArMMedizinalcannabisverkehr – Ein-/Ausfuhr↗
- Gesetze im InternetMedizinal-Cannabisgesetz (MedCanG)↗
- Gesetze im InternetArzneimittelgesetz § 72 - Einfuhrerlaubnis↗
- Silk LegalGACP export documentation guidance2025-12↗