Table of contents
Overview
The SOM ESM Sales Shipment transaction is an XML-based message used to record the shipment of serialized products with Enterprise Serialization Management (ESM) platform and communicate important information regarding the shipment to trading partners.
The transaction captures EPCIS-compliant shipping events and serialization data, including product identifiers, aggregation hierarchy, shipment details, and destination information. It provides a verifiable, auditable record of serialized product movement from the point of shipping to the receiving partner.
The SOM ESM Sales Shipment transaction follows the GS1 EPCIS 1.2 standard and integrates seamlessly with internal systems and downstream partners to automate compliance, improve traceability, and streamline operations.
Key Use Cases
- Record detailed information about serialized product shipments.
- Provide downstream partners with serialized shipment data for verification and receipt without requiring their direct access to internal serialization systems.
- Enable full traceability and auditability of serialized units.
- Integrate with ERP, WMS, and regulatory systems for end-to-end compliance.
- Automate shipping workflows using EPCIS 1.2 standards.
Data Elements Included
An EPCIS 1.2 – SOM ESM Sales Shipment transaction includes:
- Event Type: ObjectEvent with business step "shipping" and action "observe" to indicate serialized product movement.
- Serialized Product Identifiers (EPCs): Serialized GTINs (SGTINs) or container codes (SSCCs) of shipped units.
- Event Time and Time Zone: Timestamp of the shipment event, including time zone offset.
- Read Point: Physical or logical location where the shipment was recorded (e.g., shipping dock, ERP system).
- Business Location: GLN or internal identifier of the shipping facility.
- Destination Party: GLN or customer ID of the receiving partner.
- Disposition: Typically set to "in_transit" or "shipped".
- Aggregation Hierarchy (optional): Parent-child relationships between units, cases, and pallets.
- Sales Order Reference: Identifier linking the shipment to the originating order.
- Shipment ID (optional): Unique identifier for the shipment (e.g., ASN or delivery number).
- Carrier and Tracking Info (optional): Logistics provider and tracking number.
- Transaction ID (optional): Unique identifier for the EPCIS transaction.
- Digital Signature (optional): Ensures data integrity and regulatory compliance.
- Comments or Notes (optional): Free-text field for shipping context or exceptions.
Benefits of EPCIS 1.2 – SOM ESM Sales Shipment
- Automates product shipment recording using EPCIS 1.2 standards.
- Ensures compliance with DSCSA, DEA, and global regulatory frameworks.
- Provides traceable, auditable records of serialized product movement.
- Enables downstream verification and receipt confirmation.
- Reduces manual errors and accelerates order-to-cash processes.
Business Process: EPCIS 1.2 – SOM ESM Sales Shipment
The SOM ESM Sales Shipment transaction fits into the serialized order fulfillment and compliance workflow as follows (other use cases are possible):
- A sales order is created.
- Serialized units are picked, packed, and staged for shipment.
- The EPCIS 1.2 – SOM ESM Sales Shipment transaction is triggered by Serialized Operations Manager (SOM).
- Serialized shipment data is transmitted.
- Products are shipped, and receiving partners verify EPCs upon delivery.
- TraceLink logs the transaction for traceability, compliance, and audit readiness.
How TraceLink Supports EPCIS 1.2 – SOM ESM Sales Shipment
TraceLink’s OPUS Platform, powered by B2N Integrate-Once™, supports secure, compliant product shipment processing by:
- Capturing EPCIS 1.2-compliant shipping events from the ESM platform.
- Integrating with ERP, WMS, and material handling systems to automate shipment authorization.
- Transmitting serialized shipment data to trading partners and regulatory endpoints.
- Providing dashboards and audit logs for monitoring shipment status and compliance.
- Supporting exception handling for rejections, partial shipments, or re-shipments.
- Ensuring secure communication with optional digital signatures and encryption.
Explore More Serialization & Compliance Capabilities
- SOM ESM Void Shipment: Cancel previously recorded shipments.
- SOM ESM Receipt: Confirm serialized product receipt.
- SOM ESM Decommission: Deactivate flagged serialized units.
- SOM Product Release: Communicate products are ready to be released into the supply chain.
Need Help Implementing EPCIS 1.2?
Contact Us to learn how our OPUS Platform and B2N Integrate-Once™ model can help you automate shipments processes, improve operational efficiency for trading partners, ensure serialization compliance, and enable secure, interoperable data exchange across your pharmaceutical supply chain.
