EPCIS 1.2 – SOM Void Shipment

Overview

The SOM Void Shipment transaction is an XML-based message used to cancel or reverse a previously recorded serialized shipment. This transaction is triggered when a shipment must be halted due to a QA rejection, pick/pack/ship error, or operational issue before or after physical dispatch.

Executed by TraceLink’s Serialized Operations Manager (SOM) platform, the transaction adheres to GS1 EPCIS 1.2 standards and provides a traceable, auditable record of the voided shipment. It ensures that serialization repositories, trading partners, and compliance systems are updated with the corrected shipment status and that non-compliant or flagged products are not allowed to move downstream.
 

Key Use Cases

• Cancel a serialized shipment due to QA rejection, shipment processing or operational error.
• Reverse a shipment that was mistakenly recorded or prematurely dispatched.
• Maintain DSCSA, DEA, and global compliance by correcting shipment records.
• Support exception handling, rework, or re-release workflows.
• Provide audit-ready documentation of voided serialized shipments.
   

Data Elements Included

An EPCIS 1.2 – SOM Void Shipment transaction includes:

• Event Type: ObjectEvent with business step "shipping" and action "delete" to indicate reversal of a previously recorded shipment.
• Serialized Product Identifiers (EPCs): SGTINs or SSCCs of the serialized units being voided.
• Event Time and Time Zone: Timestamp when the void event was executed.
• Read Point: Location where the void event was recorded (e.g., QA terminal, ERP system, warehouse).
• Business Location: GLN or internal identifier of the site initiating the void.
• Disposition: Typically "shipment_cancelled", "voided", or "error_in_shipment".
• Original Shipment Reference: Identifier linking to the original EPCIS shipment event being voided.
• Void Reason Code (optional): Code indicating the reason for the void (e.g., “QA_REJECTION”, “CUSTOMER_REQUEST”).
• Transaction ID (optional): Unique identifier for the void transaction.
• Digital Signature (optional): Ensures data integrity and non-repudiation.
• Comments or Notes (optional): Free-text field for additional context or exception handling.
   

Benefits of EPCIS 1.2 – SOM Void Shipment

• Prevents unauthorized or non-compliant product movement.
• Corrects shipment data across serialization, ERP, and partner systems.
• Ensures compliance with DSCSA, DEA, and global serialization regulations.
• Supports exception workflows for rework, re-release, or quarantine.
• Enhances audit readiness with full traceability of voided events..
   

Business Process: EPCIS 1.2 – SOM Void Shipment

The SOM Void Shipment transaction supports:

• Order Management & Fulfillment: Cancels previously approved product shipments before or after dispatch.
• Inventory Management: Returns serialized units to inventory or quarantine.
• Product Serialization & Traceability: Updates shipment status to reflect voided movement.
• Quality, Risk, and Recall Management: Supports corrective actions tied to QA or recall alerts.
• Track and Trace & Government Compliance: Ensures accurate serialized records for regulatory compliance.
   

How TraceLink Supports EPCIS 1.2 – SOM Void Shipment

TraceLink’s OPUS Platform, powered by B2N Integrate-Once™, supports secure and compliant void shipment processing by:

• Capturing EPCIS 1.2-compliant “shipping delete” events with full serialization context.
• Linking void events to original shipment transactions for complete traceability.
• Transmitting updated shipment status to serialization repositories, ERP, and trading partners.
• Logging all void actions for audit readiness and regulatory reporting.
• Supporting exception workflows for reprocessing, re-release, or return.
• Ensuring secure communication with optional digital signatures and encryption.
   

Explore More Serialization & Compliance Capabilities

• EPCIS 1.2 – SOM ESM Sales Shipment: Record serialized product shipments.
• EPCIS 1.2 – SOM ESM Receipt: Confirm serialized product receipt and verification.
• EPCIS 1.2 – SOM Take Product Sample: Record serialized product removal for QA events.
• EPCIS 1.2 – SOM Aggregation Update: Modify parent-child relationships.

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 void shipment workflows, ensure serialization compliance, and maintain traceability across your pharmaceutical supply chain.