TATMEEN integration steps:

1. Register your company on the portal
2. Obtain API credentials
3. Implement EPCIS message generation
4. Configure secure connection (HTTPS)
5. Test in sandbox environment
6. Go live after certification

Common reasons for EPCIS file rejection:

• Schema validation errors: Check XML/JSON syntax
• Invalid identifiers: Verify check digits
• Missing required fields: Ensure all mandatory elements are present
• Unregistered products/locations: Register master data first

Use our EPCIS Analyzer to identify specific issues.

RSD integration steps:

1. Register with SFDA
2. Obtain RSD portal access
3. Implement EPCIS capture interface
4. Configure API authentication
5. Complete testing phase
6. Receive production approval

A duplicate serial number error occurs when the same serial is used twice. Causes:

• System generating non-unique serials
• Re-using previously commissioned serials
• Data synchronization issues

Solution: Implement proper serial number management and validation.

To print GS1 DataMatrix barcodes:

1. Use a printer capable of 300+ DPI resolution
2. Ensure proper quiet zones around the barcode
3. Follow GS1 size recommendations (minimum X-dimension)
4. Verify print quality with a barcode verifier

Consider using Continuous Ink Jet (CIJ), Thermal Inkjet (TIJ), or laser marking.

When EPCIS events fail:

1. Check error response from portal
2. Validate XML/JSON syntax
3. Verify all identifiers (GTIN, GLN, SSCC)
4. Ensure master data is registered
5. Check business rules compliance
6. Retry after fixing issues

A parent-child mismatch occurs when aggregation data is inconsistent:

• Child already in another parent
• Parent doesn't exist
• Unpacking before packing was reported

Solution: Ensure proper event sequencing and aggregation management.

Check digit errors occur when the last digit of a GTIN or SSCC doesn't match the calculated value:

1. Use the GS1 Modulo 10 algorithm
2. Recalculate the check digit
3. Compare with the actual last digit
4. Correct the barcode or data entry

Use our Barcode Decoder to validate check digits.

The typical EPCIS events required for pharmaceutical track and trace are:

• ObjectEvent (Commissioning): Serial number assignment
• AggregationEvent: Packing/unpacking
• ObjectEvent (Shipping): Products leaving a location
• ObjectEvent (Receiving): Products arriving at a location
• ObjectEvent (Dispensing): Products given to patients

Specific requirements vary by country.

A product not found error means the GTIN is not registered in the portal master data. Solution:

1. Verify GTIN format and check digit
2. Register product master data first
3. Wait for approval before sending events

Master data is foundational reference data required before sending events:

• Product master: GTIN, description, NDC
• Location master: GLN, address, type
• Trading partner: Company information

Master data must be registered before transactional events.

Common reasons for barcode read failures:

• Poor print quality (low contrast, defects)
• Wrong scanner type (laser vs imager)
• Scanning angle or distance issues
• Damaged or dirty barcode
• Inadequate lighting

Use a barcode verifier to check quality.

A location not found error means the GLN is not registered. Solution:

1. Verify GLN format and check digit
2. Register location master data
3. Ensure GLN is approved before use

A schema validation error means the EPCIS message doesn't match expected format:

• Invalid XML/JSON structure
• Missing required elements
• Incorrect data types

Use an EPCIS validator to check message format before submission.

Barcode verification is the process of grading barcode quality using ISO standards. Verification checks:

• Symbol contrast
• Modulation
• Decodability
• Defects

Grades range from A (best) to F (fail). Grade C or better is typically required.

API (Application Programming Interface) enables system-to-system communication. In track and trace:

• Submit EPCIS events to portals
• Query product status
• Retrieve master data

REST and SOAP APIs are common.

Serial number validation involves:

1. Format validation: Check length and character set
2. Check digit validation: Verify GTIN check digit using Modulo 10
3. Uniqueness check: Ensure no duplicates exist
4. Database lookup: Verify against regulatory portal

Use our Barcode Decoder tool to validate barcodes.

A sandbox environment is a testing system that mimics production without affecting real data. Use it to:

• Test EPCIS message format
• Validate integration
• Train users
• Debug issues

Always test thoroughly in sandbox before production.

Disaggregation is the reverse of aggregation - breaking parent-child relationships:

• Unpacking cases from pallets
• Unpacking units from cases
• Reported with AggregationEvent action DELETE

Required when products are repackaged or split.

GS1 DataMatrix is a 2D barcode format used for pharmaceutical serialization. It can encode the GTIN, serial number, batch/lot number, and expiry date in a small space.

DataMatrix barcodes are required on pharmaceutical packaging in most regulated markets.

Learn about DataMatrix requirements

For pharmaceutical serialization:

• Unit level: GS1 DataMatrix 2D barcode
• Case level: GS1-128 linear barcode or GS1 DataMatrix
• Pallet level: GS1-128 linear barcode

The barcode must encode: GTIN (AI 01), Serial (AI 21), Batch (AI 10), and Expiry (AI 17).

DataMatrix size depends on the application:

• X-dimension: Minimum 0.254mm recommended
• Module size: Based on scanning distance
• Overall size: Varies with encoded data

Follow GS1 General Specifications for exact requirements.

Decommissioning removes a serial from active status:

1. Send ObjectEvent with action DELETE
2. Set appropriate disposition (destroyed, sample, etc.)
3. Include reason code if required

Decommissioned serials cannot be used for further transactions.

Common authentication methods:

• OAuth 2.0: Token-based authentication
• Certificate-based: Digital certificates
• API Keys: Unique access keys
• Username/Password: Basic authentication

Check specific portal documentation for requirements.

For product returns:

1. Receive products with receiving event
2. Verify serial numbers against expected data
3. Update disposition (returned, sellable, destroyed)
4. Report appropriate events to portal

Returns workflow depends on country regulations.

Aggregation is the process of recording parent-child relationships between packaging levels - for example, which unit-level products are packed into which case, and which cases are on which pallet.

Aggregation is recorded using EPCIS AggregationEvents with ADD (packing) or DELETE (unpacking) actions.

Read aggregation best practices

A line-level system manages serialization on the production line:

• Serial number assignment
• Barcode printing
• Verification and inspection
• Aggregation at packaging

It interfaces with enterprise systems for data exchange.

A barcode scanner reads and decodes barcode data. Types include:

• Handheld: Portable, manual operation
• Fixed mount: Automated line scanning
• Camera-based: 2D barcode capability

For DataMatrix, you need an imager (2D scanner), not a laser scanner.

In EPCIS events:

• readPoint: The specific location where the event observation occurred (e.g., a scanner at dock door 3)
• bizLocation: The business location where objects are after the event (e.g., the warehouse)

Both are typically identified by GLN.

Key differences between EPCIS versions:

• EPCIS 1.2: XML format, widely adopted, CBV 1.2
• EPCIS 2.0: Adds JSON-LD support, sensor data, CBV 2.0

Most MENA portals currently accept EPCIS 1.2, with 2.0 support being added progressively.

An enterprise serialization system manages track and trace at the company level:

• Serial number pool management
• Aggregation data storage
• EPCIS event generation
• Regulatory portal connectivity
• Reporting and analytics

EPCIS queries retrieve event data from repositories:

• SimpleEventQuery: Search events by criteria
• SimpleMasterDataQuery: Retrieve master data

Query parameters: eventTime, GTIN, serial number, location, etc.

For product recalls:

1. Identify affected serial numbers
2. Query EPCIS repository for current locations
3. Send ObjectEvent with disposition 'recalled'
4. Track return/destruction events
5. Report to regulatory portals as required

EPCIS provides full traceability for efficient recall execution.

To obtain a GS1 Company Prefix:

1. Contact your local GS1 Member Organization
2. Complete the membership application
3. Pay the membership fee
4. Receive your unique Company Prefix

MENA GS1 offices: GS1 UAE (gs1.ae), GS1 Saudi Arabia (gs1sa.org), GS1 Egypt (gs1eg.org)

Aggregation inference means deducing child contents from parent events without explicit disaggregation:

• Scan pallet → infer all cases and units inside
• Reduces scanning requirements
• Requires accurate aggregation data

Not all portals support inference.

No. While technically the SGTIN (GTIN + Serial) would be unique, best practice is to use unique serial numbers across all products to avoid confusion and simplify tracking.

Most serialization systems generate globally unique serial numbers.

EPCIS events should be reported in chronological order. Reporting out of order may cause:

• Validation errors on some portals
• Inconsistent product status
• Failed aggregation relationships

If events arrive late, ensure eventTime reflects actual occurrence time, not submission time.