Orchestration Integration & Transactions ## Breadcrumb 1. [Home](/) 2. [Orchestration Integration & Transactions](/orchestration-integration-transactions) # EPCIS 1.2 – SOM Void Shipment ![banner-image](https://www.tracelink.com/sites/default/files/2024-02/For%20Internal%202.png) #### Table of contents ### 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**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-esm-sales-shipment): Record serialized product shipments. - [**EPCIS 1.2 – SOM ESM Receipt**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-esm-receipt): Confirm serialized product receipt and verification. - [**EPCIS 1.2 – SOM Take Product Sample**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-take-product-sample): Record serialized product removal for QA events. - [**EPCIS 1.2 – SOM Aggregation Update**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-aggregation-update): Modify parent-child relationships. [See All Serialization and EPCIS Capabilities](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration) ### Need Help Implementing EPCIS 1.2? [**Contact Us**](/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. #### Table of contents Contact us to learn more about B2B Integration. Fill out the form to contact us now. document.addEventListener("DOMContentLoaded", function() { // Delay the execution by 2 seconds (2000 milliseconds) setTimeout(function() { (function() { 'use strict'; // Load Marketo form MktoForms2.loadForm("//go.tracelink.com", "776-BAW-230", 2259); })(); // Wait until the Marketo form is loaded MktoForms2.whenReady(function(form) { var formElement = document.getElementById('mktoForm_2259'); if (!formElement) { console.error("Form with id 'mktoForm_2259' not found."); return; } var formLocation = formElement.querySelector("input[name=formLocation]"); // Get the current URL and set the formLocation field if (formLocation) { var currentURL = window.location.href; formLocation.value = currentURL; } // Add onSuccess handler form.onSuccess(function(values, followUpUrl) { var formElem = form.getFormElem()[0]; if (formElem) { formElem.style.display = 'none'; } else { console.warn("Form element could not be found to hide it."); } var confirmMessage = document.getElementById('confirmform'); if (confirmMessage) { confirmMessage.style.display = 'block'; } else { console.warn("Confirmation message with id 'confirmform' not found."); } return false; // Prevent the form from submitting normally }); }); }, 2000); // Delay for 2 seconds }); **Thank you for contacting us; we’ll be in touch shortly.** ##### Related Content [ ![wholesale distributor](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-03/wsd-2.png.webp?itok=Q0nGUO1Y) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-hda-advance-ship-notice) ##### EPCIS 1.2 – HDA Advance Ship Notice The EPCIS 1.2 – HDA ASN (Advance Ship Notice) is an XML-based electronic message that provides detailed, serialized shipment information from pharmaceutical manufacturers or distributors to downstream trading partners in compliance with Healthcare Distribution Alliance (HDA) and DSCSA (Drug Supply Chain Security Act) guidelines. [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-hda-advance-ship-notice) [ ![CMO](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/LifeScience-CMO8%20%281%29.png.webp?itok=3ZnAZMLd) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-dscsa-advance-ship-notice) ##### EPCIS 1.2 – DSCSA Advance Ship Notice The EPCIS 1.2 – DSCSA ASN (Advance Ship Notice) is an XML-based electronic message used to transmit serialized product shipment data in compliance with the Drug Supply Chain Security Act (DSCSA). [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-dscsa-advance-ship-notice) [ ![Wholesale-Distributor](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/For%20Internal%2055.png.webp?itok=0K8agZX1) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-serialization) ##### EPCIS 1.2 – Serialization The EPCIS 1.2 – Serialization transaction is an XML-based message used to capture and share commissioning (serialization) events for pharmaceutical products. [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-serialization) [ ![Brazil Pharmaceuticals](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/LifeScience%20CMO-1.png.webp?itok=8qEXci20) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-esm-update-lot-information) ##### EPCIS 1.2 – SOM ESM Update Lot Information The EPCIS 1.2 – SOM ESM Update Lot Information transaction is an XML-based message used to update or correct lot-level information for serialized pharmaceutical products. [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-esm-update-lot-information) [ ![crypto code](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/crypto%20code.png.webp?itok=hDYDa49u) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-receipt) ##### TL XML – SOM Receipt The SOM Receipt transaction is an XML-based message used to record the receipt and transfer serialized products between warehouses and trading partners. [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-receipt) [ ![digitalising order management](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2025-04/GettyImages-1299660112.jpg.webp?itok=qNA8FTp4) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-product-release) ##### TL XML – SOM Product Release The SOM Product Release transaction is an XML-based message used to indicate that a serialized pharmaceutical product or batch has successfully passed quality review and other product release processes and is now authorized for downstream processing—such as shipment, aggregation, or inventory movement. [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-product-release)