Egypt EDA Track and Trace: A Practical Guide for Indian Pharmaceutical Exporters

Picture a consignment of tablets leaving an Indian plant for Cairo. The cartons are clean, the batch documents are in order, and every pack carries a 2D code. Then the Egyptian importer discovers the data on the packs doesn’t match what the national system expects. Because stock can’t be re-coded once it arrives, the whole lot is stuck.

For Indian exporters, this is the real risk in Egypt’s new traceability regime. The rules are not especially exotic, but they are unforgiving, and mistakes made on your packaging line in India can’t be corrected on the other side. This guide explains what the Egyptian Drug Authority (EDA) expects and how to build it into your export process.

First, who is responsible for what?

This is the most important point, and it is easy to get wrong. The EDA’s Phase 1 technical FAQ draws a clear line: the importing entity is legally accountable for reporting commissioning, aggregation, shipping and receiving events to the system, and manufacturers and CMOs may generate the data but submission accountability stays with the importer. 

In practice, that means a two-sided relationship:

• You (the Indian manufacturer) generate the serial numbers, print the codes, build the aggregation hierarchy and prepare the data.
• Your Egyptian importer reports that data into the national system and answers to the EDA for it.

If your data is late, wrong or incomplete, your importer carries the regulatory risk, and you will feel it in your commercial relationship. Treat the importer as a partner in the process, not just a customer.

The EDA’s Phase 1 rules, in plain English

The FAQ states it covers the mandatory requirements for Phase 1 and applies to all pharmaceutical products manufactured locally or imported into Egypt. It applies to shipments sent on or after 1 February 2026, plus the stock packed together with those shipped drugs. Here is what matters most for exporters. 

Serial numbers come from you, not the EDA

The EDA does not issue serial numbers. Manufacturers must generate globally standard-compliant serial numbers (AI 21), which must be globally unique, never reused, and tied to approved GTINs registered with the EDA before importation. So GTIN registration comes first. 

Serialize the saleable pack only

Serialization is mandatory at secondary Packaging Level only, defined as the smallest saleable unit dispensed to patients. Strips and blisters inside don’t need their own serial numbers. 

Use a Data Matrix with specific content

 The code must be a GS1 Data Matrix ECC 200 carrying the GTIN (01), serial number (21), expiry date (17) and batch or lot (10). 

Two details deserve special care: 

• Expiry date format  -: The EDA says expiry must be encoded in a YYYY-MM-DDT format, a deliberate departure from the standard GS1 YYMMDD. If your line is set up for normal GS1 dates, you will need to change that. Confirm the exact format string with your importer and test it before production. 
• Separators  -:  FNC1/GS (ASCII 29) separators are required after variable-length elements such as batch and serial number. Human-readable text is mandatory. HRI must follow GS1 General Specifications Release 26, with AI prefixes in parentheses; data titles like GTIN, EXPIRY and BATCH/LOT are acceptable. 
• Aggregation must keep its hierarchy  -: The system supports aggregation from SGTIN up to SSCC at bundle, carton, pallet and container levels. No packing method is mandated, but parent-child integrity must be preserved. Disaggregation requires decommissioning the SSCC, and partial unpack or partial receive events must be reported immediately 

Phase 1 data goes in as CSV, not through an API

 This surprises many exporters who expect EPCIS. CSV is the mandatory format in Phase 1, XML and API integration come later, and manual uploads are required initially. The EDA says Phase 1 CSV formats deviate from the standard EPCIS and that future releases will align with EPCIS 2.0. 

The CSV rules are strict -: A file may contain at most 50,000 serial numbers and 5 batches per commissioning file, and processing is atomic, so a single error rejects the whole file. VOID events are supported before custody transfer.

Timing is tight  -: Only products physically shipped to Egypt may be reported, reporting must be completed before arrival, and timelines run on calendar hours, not business hours.

No fixing it in Egypt -: Barcode printing within Egypt is allowed only at EDA-licensed facilities after batch approval, and distribution centres may not serialize or reprint barcodes. This is the rule that makes your packaging line in India the point of no return. 

How this differs from what Indian exporters already know

Many Indian manufacturers learned traceability through India’s own export barcoding scheme. In 2011 the DGFT announced a GS1-based track and trace system for exported drugs, requiring serialization at secondary packaging level and data submission to a central portal. One vendor now notes that the DGFT has withdrawn the mandated system for export consignments of drug formulations, so confirm the current position with Pharmexcil or DGFT. 

Even if you have experience with that regime, Egypt is different in four ways: the data goes to a foreign regulator’s system, an importer is legally accountable for submission, the encoding rules include Egypt-specific details such as the expiry format, and the Phase 1 data exchange runs on CSV files.

If you also export to the EU or US, don’t assume one setup covers all three. Keep a separate, tested configuration for Egypt.

Where Indian shipments are most likely to go wrong

1. GTIN not registered before shipment -: The EDA ties serial numbers to approved, registered GTINs, so the product cannot be reported until that is done.
2. Wrong expiry format -: A line running standard GS1 dates will produce codes that don’t match the EDA’s requirement.
3. Missing separators -:  A code that looks right but lacks the correct GS characters can fail verification.
4. Reusing or duplicating serials -: Serial numbers must never repeat, including across re-runs and reprints.
5. Aggregation mismatches -: Cartons packed manually without scanning break parent-child links for the whole pallet.
6. Reporting what you didn’t ship -:  The system only accepts products that physically went to Egypt, so keep reporting consistent with the actual dispatch.
7. One bad row in a CSV -: Because processing is atomic, a single error rejects the full file, delaying everything in it.
8. Late data -: Reporting must finish before arrival, so your data pack must reach the importer before the truck reaches the port.

A step-by-step export workflow

Step 1: Align with your importer 

Agree who generates, who validates and who uploads the data. Share timelines in calendar hours.

Step 2: Register GTINs 

Make sure every product’s GTIN is registered with the EDA before the first shipment.

Step 3: Configure your serialization software 

Set up the Egyptian encoding profile: the data elements, expiry format, separators and HRI layout.

Step 4: Print and verify inline

Print on the secondary pack, then verify every code for readability, content and format before it leaves the line.

Step 5: Aggregate with scanning

Build bundles, cartons, pallets and containers with scanned links, and keep the SSCC hierarchy intact.

Step 6: Prepare the CSV files

Respect the 50,000-serial and 5-batch limits, and run an internal validation before sending anything.

Step 7: Hand over data before dispatch

Give your importer the files in time for reporting to finish before arrival.

Step 8: Reconcile after shipping 

Compare what was commissioned, aggregated and physically shipped. Fix discrepancies with a VOID event before custody transfers, where applicable.

If you ship bulk to be packed in Egypt

Some Indian companies export bulk product for local packaging. Under the decree, bulk imported and locally manufactured, packaged and repackaged products came into scope from 1 August 2026. If this is your model, remember that printing in Egypt can only happen at an EDA-licensed facility after batch approval, so choose your packing partner carefully and agree responsibilities for serialization and data in writing. 

Pre-shipment checklist

• GTINs registered with the EDA
• Serials generated, unique and never reused
• Data Matrix contains GTIN, serial, expiry and batch with correct separators
• Expiry date in the EDA’s required format
• HRI printed per the specification, with AI prefixes in parentheses
• Every pack verified inline; rejects removed
• Aggregation scanned end to end, with SSCC hierarchy intact
• CSV files within size limits and validated
• Data delivered to the importer before dispatch
• Shipment and reported data reconciled

Why inline verification is your safety net

The rules above are detailed, and the cost of a mistake is high. An inline vision system that reads every Data Matrix code, checks its content and print quality, confirms the human-readable text, and rejects non-conforming packs is the most reliable way to stop errors before they ship. It can also check labels, cartons and print defects in the same pass. Jekson Vision supplies Vision Inspection and track and trace solutions for pharmaceutical packaging, designed to help exporters verify codes and packaging quality at line speed.

How Jekson Vision can help

Jekson Vision provides vision inspection and track and trace solutions for pharmaceutical packaging. Our systems verify every 2D Data Matrix code on your secondary packs, so errors are caught on the line in India and not at the Egyptian port. Write to us at marketing@jeksonvision.com to know more.