Selling packaging across the EU and GCC: a market-specific evidence matrix
A single packaging specification sold into several markets is subject to several sets of rules. The register that maps them is what keeps a portfolio saleable.

- Byline
- Gambit Reign analysis
- Period covered
- 2023–2026
- Reviewed
- 6 October 2026
- Topic
- Materials & packaging
- Reading time
- 5 min read
Key takeaways
- Requirements for packaging differ by where the product is placed, how it is used, what role the business plays in the chain, and what it contacts. A single specification cannot be assumed to satisfy several markets.
- The GCC is six jurisdictions with differing rules, not one regime, and EU requirements do not carry across to GCC markets. Each market's position must be established on its own terms.
- A requirement register is only useful if each line names its source, the evidence it depends on, the owner of that evidence, and the date by which it should be reviewed.
Why one specification is not enough
A packaging specification developed for one market encodes the requirements that applied there. When the same product is sold into a different market, the specification travels but the requirements do not — and the gap between them is where problems are found, usually late.
Several things differ between markets. The rules addressing the material, its recyclability, its recycled content and its labelling differ. The treatment of specific product categories differs. Whether a given chemical is restricted differs. The requirements attaching to food contact differ, and the qualification routes for recycled material differ with them.
What also differs is the business's own position. A business that manufactures packaging is in a different position from one that fills it, and both differ from an importer or a distributor. Requirements frequently attach to a role in the chain as well as to a product, and a business operating in several roles across several markets has several positions to establish. Food-contact and recycled-material requirements are a clear example: the qualification routes differ by market, [D] and the UAE has its own guidance on the products its measures address, [E] with the phased federal measures announced separately [F] — none of which can be read across to another jurisdiction.
The practical consequence is that the unit of analysis is not the product but the combination of product, market and role. That is a larger number of combinations than most businesses first assume, which is precisely why a register rather than a mental model is required.
The six GCC jurisdictions
It is worth stating plainly, because it is a recurring source of error: the GCC is six jurisdictions, not one regime. Approaches to packaging, plastics and waste differ between them, and they are developing at different rates and in different directions.
Treating the GCC as a single market leads to two mistakes. The first is assuming that a requirement established in one jurisdiction applies across the region, which may overstate the constraint. The second, and more dangerous, is assuming that compliance achieved in one jurisdiction satisfies the others, which may understate it. Both come from the same underlying error of treating a region as a regime.
The parallel error runs in the other direction, and it is equally common: assuming that EU requirements apply in GCC markets, or that a specification built for the EU will satisfy a GCC authority. It will not. The approaches are different in structure as well as in content, and a business selling into both must establish each on its own terms.
What can be transferred is the method: identify the requirement, find its source, establish what evidence demonstrates it, assign the evidence to an owner, and set a review date. That method works in any market. The findings do not transfer, and should not be assumed to.
| Field | What it records | Why it is needed |
|---|---|---|
| Market | The jurisdiction the requirement attaches to | Requirements are jurisdiction-specific and never assumed |
| Product and use | The specific item and how it is used and contacted | Requirements attach to products and applications |
| Business role | Manufacturer, filler, importer, distributor or other | Obligations often attach to a position in the chain |
| Applicability | Whether the requirement applies to this combination | Prevents both over- and under-compliance |
| Source | The instrument or authority the requirement comes from | An unsourced requirement cannot be verified or challenged |
| Evidence required | The document, test or declaration that demonstrates it | Defines what must exist before the product ships |
| Evidence owner | Named person or role responsible for holding it | Unowned evidence is evidence that does not exist when needed |
| Next review | The date the line should be re-checked | Requirements change; a static register goes out of date |
This register structure is our own working framework. It records what must be established; it states no requirement of any jurisdiction and makes no determination about any product's compliance.
Applicability is the hard part
Populating the register is mechanical once the structure exists. Deciding applicability is the part that requires judgement, and it is where the register earns its keep.
Applicability depends on the combination of factors described above, and the answers are frequently not obvious. A requirement addressed to a particular category of product may or may not reach a specific item, depending on how the item is used and where it sits in the market. A labelling obligation may attach to a particular role rather than to the product, which means a business in that role carries it even though it did not design the pack. A chemical restriction may apply to a material that is present only in a coating or a layer rather than in the main construction.
This is why the register is worth building even when the initial answers are uncertain. Recording uncertainty explicitly, with the specific question to be resolved and who will resolve it, is more useful than recording a confident answer that has not been checked. An entry that reads 'applies, pending confirmation of role in this market, owner X, review date Y' is a working entry; one that reads 'no requirement applies' with no source is a risk.
The register should also record what it does not know. Where a market's position is unclear, or where an instrument is in the process of changing, that should appear as an open item with an owner rather than being omitted. A register that only contains settled answers is misleading about the state of the analysis.
Keeping the register alive
Requirements change, and a register that is accurate on the day it is built decays from that point. The decay is slow and invisible: a product changes, a supplier substitutes a material, an instrument is revised, a market introduces a new measure, and the register drifts out of step with the position.
Two mechanisms limit the drift. The first is the review date on each line, which forces a periodic re-check rather than a one-off. The second is a change trigger — a route by which a change to a product, a material, a supplier, a pack specification or a market of sale causes the affected register lines to be re-examined. Both belong in the register's design, and both require an owner who is accountable for the register as a whole.
The alternative to maintaining the register is discovering the drift at the point where it matters most: a shipment held, a customer query, a retailer audit, or an issue with an authority. The cost of the discovery is far higher than the cost of the review that would have prevented it, which is the ordinary case for maintaining accurate records.
The boundary should be stated once more. Nothing in this article establishes what any jurisdiction requires, and nothing here determines whether any product complies. Those questions turn on the current instruments, on the specific product and its use, and on the business's own role — and they should be settled against the source, with qualified advice where the exposure is material, rather than by inference from a general article.
Limitations
- This article sets out a register structure for tracking market-specific requirements. It states no requirement of the EU, the GCC or any jurisdiction, and it makes no determination about the compliance of any product.
- It does not transpose EU law to GCC markets and does not treat the GCC as a single regime. The GCC comprises six jurisdictions with differing rules, all of which must be established individually.
- The register structure is our own working framework and does not reproduce the content of any instrument.
- Requirements, their applicability and their sources change over time. Each entry must be confirmed against its own current source, with qualified advice where the exposure is material.
The next decision
List the product–market–role combinations you actually sell into — every line without a named evidence owner is an open risk.
Discuss your projectTaking this into your own project?
Our scoping guide and worksheet walk through the questions that make a brief usable — the decision, the evidence, the options including doing nothing, and what still has to be established. No email required.
Sources
External sources are referenced above by letter. Our own recommendations are identified as such in the text and are not attributed to these sources.
- [D]European Commission — Plastic recycling and food contact materials (framework overview)https://food.ec.europa.eu/food-safety/chemical-safety/food-contact-materials/plastic-recycling_en
- [E]MOCCAE — UAE guide on the regulation of single-use plastic products (2 January 2025 announcement)https://www.moccae.gov.ae/Handlers/DownloadPDF.ashx?id=67608
- [F]WAM — MOCCAE announcement on the second phase of the nationwide ban on the import and trade of single-use plastic products (16 December 2025)https://www.wam.ae/en/article/bn8qxpm-second-phase-nationwide-ban-import-trade
