Exporting to the GCC: Tatmeen, RSD and Where Their Requirements Diverge

Sun Teknovation is a leading manufacturer of serialization, aggregation and track and trace systems for pharmaceutical packaging lines.

Most exporters approach the Gulf as one market. The packaging looks alike, the GS1 standards are shared, and the sales team treats Dubai and Riyadh as two lines on the same forecast. Then a consignment holds at a UAE port because the packs were never commissioned before customs, or a Saudi distributor cannot move stock because the case hierarchy does not match what was reported. Both systems use GS1. That is exactly why the differences catch people out.

Where the Two Systems Agree

Before the gaps, the common ground. Both Tatmeen (UAE, operated for the Ministry of Health and Prevention) and RSD (Saudi Arabia, operated by the SFDA) are built on the same foundations:

• A GS1-compliant 2D Data Matrix on each saleable pack, carrying GTIN, serial number, batch or lot and expiry date
• A unique serial against the GTIN, not a batch code alone
• Aggregation using SSCCs to link packs into cases and pallets
• EPCIS-format event reporting to a national platform
• A valid GLN for registered supply chain locations

If your line already produces compliant GS1 codes and commissions serials cleanly, you have the base for GCC Pharmaceutical Serialization in place. The divergence sits in what happens after the code is printed.

Divergence 1: When Reporting Has to Happen

This is the difference that stops shipments.

UAE. Products must be commissioned to Tatmeen before import customs clearance into the local market. The data has to exist in the platform ahead of the goods arriving, not after.

Saudi Arabia. RSD does not gate customs clearance in the same way. Reporting obligations apply after shipments are received.

The practical effect is that Tatmeen Serialization Requirements put the deadline before the port, while RSD Serialization Compliance places it after receipt. An exporter who plans the UAE consignment on the Saudi rhythm will find the goods sitting at customs with no record to clear against.

Worth noting: Tatmeen applies to products intended for the local UAE market. Goods moving through purely for export are treated differently, which is a distinction free zone shippers should confirm for their specific route.

Divergence 2: How Deep the Aggregation Goes

Both markets require aggregation, but the shape differs.

UAE. Manufacturers must aggregate using SSCCs across at least two levels of packaging. There is also an obligation further down the chain — distributors or trade partners who break a hierarchy must re-aggregate at least one level using their own SSCCs.

Saudi Arabia. Full aggregation at case and pallet level is required for products in the market.

That re-aggregation obligation in the UAE is often missed at the planning stage, because it sits with the partner rather than the manufacturer. If your local distributor cannot generate their own SSCCs and report the new hierarchy, the chain breaks after your responsibility technically ends — and the product still stops moving.

For any GCC Drug Track and Trace project, this means aggregation cannot be inferred. Contextual logic based on known case counts is not accepted where regulators require recorded parent-child links, so packs must be physically read into their case on the line.

Divergence 3: Master Data and Platform Architecture

UAE. Products are registered in the MoHAP system and in GS1 BrandSync, with supply chain entities registered under valid GLNs. Traceability events are submitted in GS1 EPCIS format as individual files per event.

Saudi Arabia. Each SFDA-licensed warehouse requires its own GLN and separate registration, and the Saudi ecosystem involves more than one portal, with commissioning and aggregation files exchanged between stakeholders rather than submitted through a single channel.

Master data errors are the most common cause of rejection in both markets — a wrong GLN for a CMO or importer, or a mismatch between printed serials and reported data. These are not machine faults. They are set-up faults, and they surface only when the file is rejected.

What This Means on Your Line

A single system can serve both markets, but it has to be specified for the harder case rather than the easier one:

• Can it commission serials and generate export-ready EPCIS files ahead of shipment, not after?
• Does it record true parent-child aggregation on the line, at every level required?
• Can it hold separate master data profiles for different destination markets on the same product?
• Does the audit trail show what was read, when, and what the system decided?

Teams comparing suppliers for GCC Drug Track and Trace should put their full destination list on the table at the first meeting. A line specified for one Gulf market and retrofitted for the second usually costs more than one specified for both from the start.

Why Choose Us

Sun Teknovation Pvt Ltd., builds machine vision hardware and serialization software in-house, and that single-owner structure is what keeps a project moving when something needs attention on the line. Our systems run in more than 60 countries, so multi-market packaging — where the same product carries different reporting obligations by destination — is familiar territory for us. We handle GS1 Data Matrix generation and grading, OCR and OCV verification, and multi-level aggregation from unit through to pallet, with the parent-child link committed on the line rather than assembled afterwards. Our engineers tune camera positions and lighting to your actual pack format instead of a demo carton, work alongside your team through integration, and stay reachable after commissioning. We are equally straightforward about what a format will not support, because an honest specification at the start costs far less than rework against a regulatory deadline.

Conclusion

Tatmeen and RSD share a standard but not a workflow. The UAE front-loads the obligation, with commissioning required before customs and a re-aggregation duty carried down the chain. Saudi Arabia places reporting after receipt but demands full case and pallet aggregation and per-location registration. Treating them as one requirement is what causes held consignments and stalled distributor stock. Specify your line for both destinations from the outset, confirm master data before the first shipment rather than after a rejection, and keep aggregation real rather than inferred. That is what keeps Gulf market access predictable.

Shipping to the UAE, Saudi Arabia or wider GCC and planning your serialization and aggregation setup? Talk to Sun Teknovation about the right system for your pack formats and destination markets. Call +91 98982 45695 or email connect@sunteknovation.com .

Frequently Asked Questions