EPCIS 1.2 – SOM ESM Void Shipment

Overview

The SOM ESM Void Shipment transaction (Transaction Code: EPCIS 1.2) is an XML-based message used to cancel or void a previously recorded serialized shipment event. This transaction is typically triggered when a shipment is halted due to a QA rejection, or logistical error, and ensures that serialized product movement is accurately reversed in compliance with DSCSA, global track and trace, and internal SOPs.

Working in conjunction with Enterprise Serialization Management (ESM) platforms, this transaction complies with GS1 EPCIS 1.2 standards and ensures that all downstream systems and partners are updated with the corrected shipment status.
 

Key Use Cases

• Cancel a previously recorded serialized shipment due to a shipment operational error or QA rejection.
• Prevent unauthorized or non-compliant product movement before it leaves the facility.
• Update serialization repositories and downstream systems with corrected shipment status.
• Maintain DSCSA and global track and trace compliance by ensuring accurate serialized movement records.
• Support internal SOPs for shipment cancellation, rework, or re-release.
• Provide a traceable, auditable record of voided shipment activity.
   

Data Elements Included

An EPCIS 1.2 – SOM ESM Void Shipment transaction includes:

• Event Type: ObjectEvent with business step "shipping" and action "delete" to indicate the cancellation or reversal of a previously recorded shipment.
• Serialized Product Identifiers (EPCs): SGTINs of the serialized items that were originally shipped but are now being voided from the shipment record.
• Event Time and Time Zone: The exact timestamp when the void action was performed, including time zone offset.
• Read Point: The physical or logical location where the void event was captured (e.g., shipping station, ERP system, or QA terminal).
• Business Location: The site (GLN or internal code) responsible for initiating the void shipment transaction.
• Disposition: Typically set to "voided", "shipment_cancelled", or "error_in_shipment" to denote the nature of the reversal.
• Void Reason Code (optional): A coded explanation for why the shipment was voided (e.g., "DUPLICATE_SHIPMENT", "QA_REJECTION", "CUSTOMER_REQUEST").
• Original Shipment Reference (optional): Identifier or linkage to the original EPCIS shipment event being voided, providing traceability and auditability.
• Transaction ID (optional): A unique identifier for the void transaction, useful for system reconciliation and tracking.
• Digital Signature (optional): Applied for data integrity and non-repudiation, especially in regulated environments.
• Comments or Notes (optional): Free-text field for additional context, such as corrective actions, system user notes, or exception handling details.
   

Benefits of EPCIS 1.2 – SOM ESM Void Shipment

• Ensures regulatory compliance by accurately reversing invalid shipment events.
• Prevents downstream product movement of flagged or non-compliant serialized units.
• Maintains serialization integrity by updating all systems with corrected shipment status.
• Improves audit readiness and traceability with a complete record of voided shipments.
• Supports exception handling and reprocessing workflows across QA, and logistics teams.
   

Business Process: EPCIS 1.2 – SOM ESM Void Shipment

The SOM ESM Void Shipment transaction is used during exception handling in the serialized distribution process. It typically fits into the following workflow (other workflows may apply):

• A serialized shipment is created and recorded using EPCIS 1.2.
• A QA issue, or operational error is identified.
• SOM ESM Void Shipment (EPCIS 1.2) is triggered to cancel the original shipment event.
• Serialized units are returned to inventory, quarantined, or reprocessed.
• TraceLink logs the voided shipment for full traceability and audit readiness.
   

How TraceLink Supports EPCIS 1.2 – SOM ESM Void Shipment

TraceLink’s OPUS Platform, powered by B2N Integrate-Once™, enables secure and compliant shipment cancellation by:

• Triggering void actions directly from QA or logistics workflows.
• Capturing EPCIS 1.2-compliant void shipment events with full serialization context.
• Transmitting cancellation updates to serialization repositories, ERP, and downstream partners.
• Providing dashboards and audit logs to monitor voided shipments and corrective actions.
• Ensuring secure, traceable communication with optional digital signatures.
   

Explore More Serialization & Compliance Capabilities

• SOM ESM Sales Shipment (EPCIS 1.2) – Record serialized shipments.
• SOM ESM Sales Shipment (TL XML) – Record serialized shipments.
• SOM ESM Receipt (EPCIS 1.2) – Confirm serialized product receipt.
• SOM ESM Receipt (TL XML) – Confirm serialized product receipt.
• SOM ESM Decommission (EPCIS 1.2) – Deactivate flagged serialized units.

See All Serialization and EPCIS Capabilities

Need Help Implementing EPCIS 1.2?

Contact Us to learn how our OPUS Platform and B2N Integrate-Once™ model can help you automate shipment cancellations, maintain serialization accuracy, and ensure full compliance across your life sciences and healthcare supply chain.