  

 

Orchestration Integration &amp; Transactions

 ## Breadcrumb

1. [Home](/)
2. [Orchestration Integration &amp; Transactions](/orchestration-integration-transactions)
 
  

 

 

# TL XML – SOM Sales Shipment

 

 

 

 

 

 ![banner-image](https://www.tracelink.com/sites/default/files/2024-03/For%20Internal%204.png) 

 

 

 

 

#### Table of contents

 

 

 

### Overview

The SOM Sales Shipment transaction is an XML-based message used to rrecord and communicate the shipment of serialized products between companies and their trading partners. It allows for the exchange of important shipment information without granting partners direct access to the serialization system of record. The message supports various use cases, including commission and shipping events, and can handle both aggregated and non-aggregated product data.

Triggered at the point of shipment, the SOM Sales Shipment transaction shipping events and serialization data, including product identifiers, aggregation hierarchy, shipping location, and recipient details. It provides downstream systems, trading partners, and regulatory authorities with a verifiable and auditable record of compliant serialized product movement. It integrates follows the TL XML schema to support secure and standards-based data exchange between systems and trading partners.

### Key Use Cases

- Record the shipment of serialized product.
- Ensure DSCSA and global track and trace compliance by tracking shipments.
- Provide serialized shipment data to downstream systems and trading partners.
- Trigger post-shipment processes such as invoicing, customs clearance, and product verification.
- Maintain audit-ready documentation of serialized shipments.
- Integrate with ERP, WMS, and logistics systems for automated fulfillment.

### Data Elements Included

A TL XML – SOM Sales Shipment includes:

- **Serialized Product Identifiers (EPCs):** SGTINs or SSCCs of the serialized units or containers being shipped.
- **Shipment ID:** Unique identifier for the shipment (e.g., ASN or delivery number).
- **Sales Order Reference:** Identifier linking the shipment to the originating sales order.
- **Event Timestamp:** Date and time when the shipment was initiated.
- **Read Point:** Physical or logical location where the shipment was recorded (e.g., warehouse, dock).
- **Business Location:** GLN or internal site code of the shipping facility.
- **Destination Party:** GLN or identifier of the receiving customer.
- **Disposition:** Typically set to "shipped" or "in\_transit".
- **Carrier and Tracking Info (optional):** Logistics provider and tracking number.
- **Transaction ID (optional):** Unique ID for traceability and audit purposes.
- **Digital Signature (optional):** Ensures data integrity and regulatory compliance.
- **Comments or Notes (optional):** Free-text field for shipping context or exceptions.

### Benefits of TL XML – SOM Sales Shipment

- Identifies and confirms the serialized products that are shipped.
- Ensures compliance with DSCSA, global track and trace regulations, and internal SOPs.
- Provides traceable, auditable shipment records for regulatory inspections.
- Automates data exchange with partners and internal systems.
- Reduces manual errors and accelerates order-to-cash processes.

### Business Process: TL XML – SOM Sales Shipment

The SOM Sales Shipment transaction may fit into the serialized order fulfillment and compliance workflow as follows:

- A customer order is created and evaluated.
- Serialized units are picked, packed, and staged for shipment.
- SOM Sales Shipment (TL XML) is triggered.
- Shipment data is sent to downstream systems for tracking and verification.
- Products are physically shipped, and receiving parties use the data for confirmation.
- TraceLink logs the transaction for traceability, compliance, and audit readiness.

### How TraceLink Supports TL XML – SOM Sales Shipment

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

- Capturing serialized shipment events from ERP, WMS, or logistics systems.
- Automatically generating TL XML-compliant shipment messages.
- Transmitting shipment data to downstream partners, regulators, and serialization repositories.
- Providing dashboards and logs to monitor shipment status.
- Supporting exception handling for partial shipments, rejected orders, or re-shipments.
- Ensuring secure communication with optional digital signatures and encryption.

### Explore More Serialization &amp; Compliance Capabilities

- [**EPCIS Serialization**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-serialization): Capture and transmit commissioning events at the unit, case, or pallet level.
- [**SOM Product Release**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-product-release): Digitally authorize serialized product movement
- [**SOM Country Clearance**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-country-clearance): Confirm compliance with destination market customs rules prior to export or distribution.
- [**SOM Receipt**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-receipt): Confirm serialized product delivery and reconcile with shipments.

[See All Serialization and EPCIS Capabilities](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration)



### Need Help Implementing TL XML Transactions?

[**Contact us**](/contact-us) to learn how our OPUS Platform and B2N Integrate-Once™ model can help you automate shipments, ensure serialization compliance, and enable secure, interoperable data exchange 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) 

 

 [ ![network](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/recovery%20banner%20network.png.webp?itok=YHW_jjzV) ](/orchestration-integration-transactions) 

#####  Transaction Integrations for Orchestration 

 Unlock the full power of your supply chain with TraceLink’s Integrate-Once capability part of our Business Network (B2N) platform. 

 

 [View More](/orchestration-integration-transactions) 

 

 [ ![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)