TL XML – SOM Void Shipment

Overview

The SOM Void Shipment transaction is an XML-based message used to cancel or reverse a previously recorded serialized shipment that had been cleared through Suspicious Order Monitoring (SOM). This transaction is triggered when a shipment must be invalidated due to a SOM alert, QA rejection, customer request, or operational error—either before or after physical dispatch.

Executed within TraceLink’s Enterprise Serialization Management (ESM) platform, the transaction ensures that serialization repositories, ERP systems, and downstream partners are updated with the corrected shipment status. It helps prevent unauthorized product movement, supports regulatory compliance, and maintains traceability of all serialized units involved in the voided shipment.
 

Key Use Cases

• Trigger shipment cancellation directly from enterprise systems (e.g., ERP, WMS, QA) using TraceLink’s flexible TL XML format.
• Integrate SOM void logic into custom exception workflows, such as QA hold, customer cancellation, or warehouse mispick resolution.
• Automate updates to internal serialization and inventory systems when a SOM-cleared shipment is invalidated.
• Support real-time communication with TraceLink’s Opus Platform to ensure shipment status is updated before physical dispatch or invoicing.
• Enable rapid partner notification of voided shipments without requiring EPCIS 1.2 event modeling—ideal for early-stage or hybrid serialization environments.
• Maintain audit-ready documentation for voided shipments using TraceLink’s native transaction logging and reporting capabilities.
• Facilitate reprocessing or re-release workflows by retaining serialized unit history within the TraceLink network.
   

Data Elements Included

A TL XML – SOM Void Shipment transaction includes:

• Transaction Type: SOMVoidShipment
• Serialized Product Identifiers (EPCs): SGTINs or SSCCs of the serialized units being voided.
• Original Shipment Reference: Identifier linking to the shipment being voided (e.g., ASN or delivery number).
• Void Timestamp: Date and time when the void action was performed.
• Read Point: Location where the void event was recorded (e.g., QA terminal, ERP system).
• Business Location: GLN or internal identifier of the facility initiating the void.
• Disposition: Typically "voided", "shipment_cancelled", or "error_in_shipment".
• Void Reason Code (optional): Coded reason for the void (e.g., “QA_REJECTION”, “SOM_ALERT”, “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, such as corrective actions or exception notes.
   

Benefits of TL XML – SOM Void Shipment

• Prevents the movement of non-compliant or incorrectly shipped serialized products.
• Maintains compliance with DSCSA, DEA, and global serialization mandates.
• Provides traceable, auditable records of voided shipments.
• Supports exception handling workflows across QA, SOM, and logistics teams.
• Ensures serialization data integrity across internal and partner systems.
• Scales globally via TraceLink’s B2N Integrate-Once™ model.
   

Business Process: TL XML – SOM Void Shipment

The SOM Void Shipment transaction supports:

• A sales order is SOM-cleared, and serialized units are prepared for shipment.
• A QA issue, customer cancellation, or system error is detected before or after dispatch.
• A void request is triggered from ERP, WMS, or QA systems and sent to TraceLink via TL XML.
• TraceLink processes the TL XML transaction, voids the shipment, and updates internal serialization status.
• Serialized units are returned to inventory, quarantined, or flagged for reprocessing.
• Shipment records are updated across connected systems (ERP, serialization repository, partner platforms).
• TraceLink logs the void event for audit, compliance, and reporting purposes.
   

How TraceLink Supports TL XML – SOM Void Shipment

TraceLink’s Opus Platform, powered by B2N Integrate-Once™, supports flexible and exception-driven void shipment processing through TL XML by:

• Accepting void requests from ERP, WMS, QA, or SOM systems using TraceLink’s TL XML schema — without requiring full EPCIS event modeling.
• Supporting early-stage exception handling, including shipment cancellation before physical dispatch or EPCIS generation.
• Processing void transactions independently of EPCIS, allowing for hybrid serialization environments.
• Automatically updating internal serialization records and shipment status in TraceLink’s ESM platform.
• Triggering inventory updates or product quarantine workflows based on the void result.
• Logging all TL XML void transactions for audit readiness, compliance, and traceability.
• Providing APIs and integration toolkits to simplify connection with enterprise systems and automation of exception workflows.
   

Explore More Serialization & Compliance Capabilities

• TL XML – SOM Product Release: Authorize serialized units for shipment after SOM clearance.
• TL XML – SOM ESM Sales Shipment: Record serialized shipments after SOM approval.
• TL XML – SOM ESM Receipt: Confirm serialized product receipt and verification.
• EPCIS 1.2 – SOM Aggregation Update: Modify parent-child relationships post-SOM.

See All Serialization and EPCIS Capabilities

Need Help Implementing TL XML Transactions?

Contact TraceLink 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.