Skip to main content
Home
  • AI Mode
  • Supply Chain Orchestration
    fast
    Supply Chain Orchestration
    • Life Sciences Company
    • Direct Material Supplier
    • Contract Manufacturer
    • Third Party Logistics
    • Wholesale Distributor
    • Healthcare Provider
    • Retail Pharmacy
  • Network
  • Products
    fast
    Products
    • Multienterprise Information Network Tower (MINT)
    • Process Orchestration for Empowered Teams (POET)
    • Track-and-Trace
  • Resources
    fast
    Resources
    • Resource Center
    • TraceLink University
    • Partners
    • Community
    • Events
  • About
    fast
    About
    • Our Story
    • Newsroom
    • Culture and Careers
    • Leadership
    • Our Values
    • Corporate Social Responsibility
    • Contact Sales
  • Log In
    • Tracelink Classic
      TraceLink Classic app.tracelink.com
      Redirect
    • Opus Platform
      Opus Platform opus.tracelink.com
      Redirect
Log In
  • Tracelink Classic
    TraceLink Classic app.tracelink.com
    Redirect
  • Opus Platform
    Opus Platform opus.tracelink.com
    Redirect
Tracelink University

Breadcrumb

  1. Home
  2. Resources
  3. TraceLink University

Inventory balances (IDoc)

  • Download PDF
  • Share
    • LinkedIn
    • Facebook
    • Mail
    • Twitter

Table of contents

Inventory balances allow suppliers to communicate with their remote or third-party warehouses about their available and upcoming inventory levels. Inventory balances contain several types of inventory information such as physical product location within a warehouse, product category, and total available inventory. Communicating inventory levels ensures suppliers can keep the required amount of inventory stocked at their locations and enables them to perform other key activities like properly preparing to fulfill large orders. Inventory balances are usually sent at regular intervals or because the buyer requests inventory information.

Suppliers use inventory balances to communicate about available and upcoming inventory levels with their remote or third-party warehouses or buyers.

Contact your TraceLink Services representative for more information about integrating with this message.

  • Message Type: MPC_INVENTORY_BALANCE (Inventory Balance)
  • IDoc Format: INVRPT01
  • Transform Names:
    • B2B_IDoc_INVRPT_INVRPT01_InventoryBalance_IB_V4
    • B2B_IDoc_INVRPT_INVRPT01_InventoryBalance_OB_V3
ClosedGuidelines
Input Element Occurs Length Description Example
INVRPT01 [1…1]
– Required. XML IDoc DESADV root element. –
  IDOC [1…1]
– Required. IDoc root. –
    @BEGIN [1…1]
0/* Required. Begin of message attribute. 1
    EDI_DC40 [1…1]
– Required. IDoc control record. –
      @SEGMENT [1…1]
0/* Required. Begin of segment attribute. 1
      TABNAM [1…1]
0/* Required. IDoc table name. EDI_DC40
      MANDT [0…1]
0/3 Client. 300
      DOCNUM [0…1]
0/16 IDoc number. 0000000000619827
      STATUS [0…1]
0/* Current IDoc processing status. 03
      DIRECT [1…1]
0/* Required. Direction. 1
      OUTMOD [0…1]
0/1 Output mode. 2
      EXPRSS [0…1]
0/1 Overriding in inbound processing. –
      TEST [0…1]
0/1 Test flag. –
      IDOCTYP [1…1]
0/30 Required. IDoc basic type. INVRPT
      CIMTYP [0…1]
0/* Name of extension type. –
      MESTYP [0…1]
0/* Logical message type. INVRPT01
      MESCOD [0…1]
0/3 Logical message code. –
      MESFCT [0…1]
0/3 Logical message function. –
      STD [0…1]
0/1 EDI standard. –
      STDVRS [0…1]
0/6 Version of EDI standard. –
      STDMES [0…1]
0/6 EDI message type. –
      SNDPOR [1…1]
0/10 Required. Sender port (SAP System, EDI subsystem). SAPD11
      SNDPRT [1…1]
0/2 Required. Partner type of sender. LS
      SNDPFC [0…1]
0/2 Partner function of sender. –
      SNDPRN [0…1]
0/10 Partner number of sender. ERPCLNT302
      SNDSAD [0…1]
0/21 Sender address (SADR). –
      SNDLAD [0…1]
0/70 Logical address of sender mapping to fileSenderNumber. Require a value that concatenates party type with party identifier in party type format. 0010136941923
      RCVPOR [1…1]
0/10 Required. SAP receiver port. TRACELINK
      RCVPRT [0…1]
0/2 Partner type of receiver. LS
      RCVPFC [0…1]
0/2 Partner function of receiver. LS
      RCVPRN [0…1]
0/10 Partner number of receiver. TRACELINK
      RCVSAD [0…1]
0/21 Receiver address (SADR). –
      RCVLAD [0…1]
0/70 Logical address of receiver. Required for TraceLink. Identifies the receiver of the IDoc for the TraceLink system. 's location ID. Must match the value that the IDoc sender has configured for their receiver partner in TraceLink. 3333331013655
      CREDAT [1…1]
8/8 Required. Date IDoc was created in format YYYYMMDD. 20230511
      CRETIM [1…1]
6/6 Required. Time IDoc was created in format HHMMSS. 161000
      REFINT [0…1]
0/14 Reference to interchange file. –
      REFGRP [0…1]
0/14 Reference to message group. –
      REFMES [0…1]
0/14 Reference to message. –
      ARCKEY [0…1]
0/70 EDI archive key. –
      SERIAL [0…1]
0/20 EDI/ALE: Serialization field. –
    E1DRM01 [1…1]
– Required. Inventory balance report header segment. –
      @SEGMENT [1…1]
0/* Required. Begin of segment attribute. 1
      ACTION [0…1]
0/3

Processing action code for the whole IDoc message.

Valid values:

  • 000 – Original.
  • 001 – Reverse.
  • 002 – Change (header level) .

Not populated – Not applicable.

ORIGINAL
      EFF_DATE [0…1]
0/8 Effective date for inventory balance report. 20240228
      EFF_TIME [0…1]
0/6 Effective time. 12:40:34
      TRANSNO [0…1]
0/35 Inventory balance report document number. 0081426104
      TRANDATE [0…1]
0/8 Inventory balance report document date. 2024-03-08
      TRANTIME [0…1]
0/6 Inventory balance report document time. 1
    E1ADRM0 [0…10]
–

Mapping for bill-to party (customer) identifier and address information.

–
      @SEGMENT [1…1]
0/* Required. Begin of segment attribute. 1
      PARTNER_Q [0…1]
0/3

Qualifier identifying customer party location data.

Valid values:

  • AG – Sold to customer.
  • LF – Vendor, supplier.
  • MF – Manufacturer.
  • WE – Ship to location.
AG
      ADDRESS_T [0…1]
0/1 Address type. –
      PARTNER_ID [0…1]
0/17 SAP partner number. 0001307782
      JURISDIC [0…1]
0/17 Location for tax calculation - Tax Jurisdiction Code. –
      LANGUAGE [0…1]
0/2 Language key. EN
      NAME1 [0…1]
0/40 Party name or description. BLUE FERRET HEALTH
      NAME2 [0…1]
0/* Party name or description. –
      NAME3 [0…1]
0/* Party name or description. –
      STREET1 [0…1]
0/40 House number and street. 5995 COMMERCE CENTER DR
      STREET2 [0…1]
0/40 House number and street. –
      STREET3 [0…1]
0/40 House number and street. –
      POSTL_COD1 [0…1]
0/10 Postal code. 43125
      CITY1 [0…1]
0/40 Town or city. GROVEPORT
      TELEPHONE1 [0…1]
0/30 Telephone number. 6144096700
      TELEFAX [0…1]
0/30 Telephone number. 6144096751
      COUNTRY1 [0…1]
0/3 Country indicator (ISO alphanumeric). US
      REGION [0…1]
0/3 Region, state code. OH
    E1DRM02 [0…*]
– Inventory balance report line item details. –
      @SEGMENT [1…1]
0/* Required. Begin of segment attribute. 1
      POSEX [0…1]
0/6 Line item number for inventory balance report. 000010
      ACTION [0…1]
0/3

Processing function, transaction set purpose code.

Valid values:

  • 001 – Item added.
  • 002 – Item changed.
  • 003 – Cancel (item).
  • 005 – Item locked.

Not populated – Not applicable.

–
      STQTY [0…1]
0/15 Line item quantity. 1000
      MEASUNIT [0…1]
0/3

Unit of measure for total line item quantity.

ClosedValid values
  • 02 – Statute Mile
  • 4G – Microliter
  • AM – Ampoule
  • AV – Capsule
  • BD – Bundle
  • BG – Bag
  • BO – Bottle
  • BX – Box
  • C3 – Centiliter
  • C8 – Cubic decimeters
  • CA – Case
  • CC – Cubic Centimeter
  • CF – Cubic Feet
  • CG – Card Blister
  • CH – Container
  • CI – Cubic Inches
  • CL – Cylinder
  • CM – Centimeter
  • CN – Can
  • CP – Crate
  • CQ – Cartridge
  • CR – Cubic Meters
  • CT – Carton
  • DA – Day
  • DI – Dispenser
  • DK – Kilometers
  • DL – Deciliter
  • DM – Decimeter
  • DR – Drum
  • DS – Display
  • DZ – Dozen
  • EA – Each
  • FO – US Fluid Ounce
  • FT – Foot
  • GA – US Gallon
  • GL – Gram/Liter
  • GR – Gram
  • GS – Gross
  • H4 – Hectoliter
  • HF – Hundred Feet
  • HR – Hours
  • IN – Inch
  • K6 – Kiloliters
  • KG – Kilogram
  • KT – Kit
  • LB – US Pound
  • LF – Linear Foot
  • LO – Lot (unit of procurement)
  • LT – Liter
  • LY – Linear Yard
  • MC – Microgram
  • ME – Milligram
  • ML – Milliliter
  • MM – Millimeter
  • MO – Months
  • MQ – Cubic millimeter
  • MR – Meter
  • OZ – Ounce
  • P1 – Percent
  • PC – Piece
  • PF – Pallet
  • PK – Pack (Only supported Outbound)
  • PK – Package
  • PR – Pair
  • PT – Pint
  • QT – Quart
  • RL – Roll
  • SC – Square Centimeter
  • SF – Square Foot
  • SH – Sheet
  • SI – Square Inch
  • SM – Square Meter
  • SP – Self Package
  • ST – Set
  • SY – Square Yard
  • SZ – Syringe
  • T3 – Thousand Pieces
  • TB – Tube
  • TH – Thousands
  • TN – Tonne
  • TS – Thousands
  • TY – Tray
  • U2 – Tablet
  • UM – Million
  • UN – Unit
  • US – Dosage Form
  • V2 – Pouch
  • VI – Vial
  • WK – Week
  • YD – Yard
  • YR – Years
EA
      EFF_DATE [0…1]
0/8 Effective date. 20240308
        E1DRM04 [0…*]
– On hand quantity at storage locations for product at line item level. –
          @SEGMENT [1…1]
0/* Required. Begin of segment attribute. 1
          QUALF [0…1]
0/3

Qualifier identifying quantity type recorded in IDoc. Valid value for IDoc is 079 – ONHAND.

079
          STOCK_LOC [0…1]
0/10 Quantity Details for storage locations. 4578
          QTY [0…1]
0/15 On hand quantity at storage location. 500
          UOM [0…1]
0/3

Unit of measure for on hand quantity.

ClosedValid values
  • 02 – Statute Mile
  • 4G – Microliter
  • AM – Ampoule
  • AV – Capsule
  • BD – Bundle
  • BG – Bag
  • BO – Bottle
  • BX – Box
  • C3 – Centiliter
  • C8 – Cubic decimeters
  • CA – Case
  • CC – Cubic Centimeter
  • CF – Cubic Feet
  • CG – Card Blister
  • CH – Container
  • CI – Cubic Inches
  • CL – Cylinder
  • CM – Centimeter
  • CN – Can
  • CP – Crate
  • CQ – Cartridge
  • CR – Cubic Meters
  • CT – Carton
  • DA – Day
  • DI – Dispenser
  • DK – Kilometers
  • DL – Deciliter
  • DM – Decimeter
  • DR – Drum
  • DS – Display
  • DZ – Dozen
  • EA – Each
  • FO – US Fluid Ounce
  • FT – Foot
  • GA – US Gallon
  • GL – Gram/Liter
  • GR – Gram
  • GS – Gross
  • H4 – Hectoliter
  • HF – Hundred Feet
  • HR – Hours
  • IN – Inch
  • K6 – Kiloliters
  • KG – Kilogram
  • KT – Kit
  • LB – US Pound
  • LF – Linear Foot
  • LO – Lot (unit of procurement)
  • LT – Liter
  • LY – Linear Yard
  • MC – Microgram
  • ME – Milligram
  • ML – Milliliter
  • MM – Millimeter
  • MO – Months
  • MQ – Cubic millimeter
  • MR – Meter
  • OZ – Ounce
  • P1 – Percent
  • PC – Piece
  • PF – Pallet
  • PK – Pack (Only supported Outbound)
  • PK – Package
  • PR – Pair
  • PT – Pint
  • QT – Quart
  • RL – Roll
  • SC – Square Centimeter
  • SF – Square Foot
  • SH – Sheet
  • SI – Square Inch
  • SM – Square Meter
  • SP – Self Package
  • ST – Set
  • SY – Square Yard
  • SZ – Syringe
  • T3 – Thousand Pieces
  • TB – Tube
  • TH – Thousands
  • TN – Tonne
  • TS – Thousands
  • TY – Tray
  • U2 – Tablet
  • UM – Million
  • UN – Unit
  • US – Dosage Form
  • V2 – Pouch
  • VI – Vial
  • WK – Week
  • YD – Yard
  • YR – Years
EA
          E1EDP19 [0…*]
– On hand quantity at storage locations for product at line item level. –
            @SEGMENT [1…1]
0/* Required. Begin of segment attribute. 1
            QUALF [0…1]
0/3

Qualifier identifying type of material identifier.

Valid values:

  • 001 – Customer
  • 002 – Supplier
  • 003 – GTIN14
  • 004 – Manufacturer
  • 010 – Batch
001
            IDTNR [0…1]
0/35 Product code identifier value. 00015874962358
            KTEXT [0…1]
0/70 Product name or description. PHARMA PRODUCT NAME
ClosedExample
<INVRPT01>
    <IDOC BEGIN="1">
        <EDI_DC40 SEGMENT="1">
            <TABNAM>EDI_DC40</TABNAM>
            <MANDT>999</MANDT>
            <DOCNUM>DOCNUM</DOCNUM>
            <STATUS>03</STATUS>
            <DIRECT>1</DIRECT>
            <OUTMOD>2</OUTMOD>
            <EXPRSS>1</EXPRSS>
            <TEST>X</TEST>
            <IDOCTYP>INVRPT01</IDOCTYP>
            <CIMTYP></CIMTYP>
            <MESTYP>INVRPT</MESTYP>
            <MESCOD>COD</MESCOD>
            <MESFCT>s5</MESFCT>
            <STD>s</STD>
            <STDVRS>s7</STDVRS>
            <STDMES>s8</STDMES>
            <SNDPOR>s9</SNDPOR>
            <SNDPRT>s1</SNDPRT>
            <SNDPFC>s1</SNDPFC>
            <SNDPRN>s92</SNDPRN>
            <SNDSAD>SenAdd</SNDSAD>
            <SNDLAD>Sender</SNDLAD>
            <RCVPOR>s13</RCVPOR>
            <RCVPRT>LS</RCVPRT>
            <RCVPFC>LS</RCVPFC>
            <RCVPRN>s93</RCVPRN>
            <RCVSAD></RCVSAD>
            <RCVLAD>Receiver</RCVLAD>
            <CREDAT>20240103</CREDAT>
            <CRETIM>091013</CRETIM>
            <REFINT>s17</REFINT>
            <REFGRP>s18</REFGRP>
            <REFMES>s19</REFMES>
            <ARCKEY>s20</ARCKEY>
            <SERIAL>s21</SERIAL>
        </EDI_DC40>
        <E1DRM01 SEGMENT="1">
            <ACTION>000</ACTION>
            <EFF_DATE>20240101</EFF_DATE>
            <EFF_TIME>110123</EFF_TIME>
            <TRANSNO>s25</TRANSNO>
            <TRANDATE>20231229</TRANDATE>
            <TRANTIME>100001</TRANTIME>
        </E1DRM01>
        <E1ADRM0 SEGMENT="1">
            <PARTNER_Q>AG</PARTNER_Q>
            <ADDRESS_T>A</ADDRESS_T>
            <PARTNER_ID>BillTo</PARTNER_ID>
            <JURISDIC>Juris</JURISDIC>
            <LANGUAGE>EN</LANGUAGE>
            <NAME1>BillTo</NAME1>
            <NAME2>BillToName2</NAME2>
            <NAME3>BillToName3</NAME3>
            <STREET1>BillToStreet1</STREET1>
            <STREET2>BillToStreet2</STREET2>
            <STREET3>BillToStreet3</STREET3>
            <POSTL_COD1>BTPostal</POSTL_COD1>
            <CITY1>BTCity</CITY1>
            <TELEPHONE1>BTPhone</TELEPHONE1>
            <TELEFAX>BTFax</TELEFAX>
            <COUNTRY1>BT</COUNTRY1>
            <REGION>S1</REGION>
        </E1ADRM0>
        <E1ADRM0 SEGMENT="1">
            <PARTNER_Q>LF</PARTNER_Q>
            <ADDRESS_T>A</ADDRESS_T>
            <PARTNER_ID>SUPPLIER</PARTNER_ID>
            <JURISDIC>Juris</JURISDIC>
            <LANGUAGE>EN</LANGUAGE>
            <NAME1>Supplier</NAME1>
            <NAME2>SupplierName2</NAME2>
            <NAME3>SupplierName3</NAME3>
            <STREET1>LFStreer1</STREET1>
            <STREET2>LFStreer2</STREET2>
            <STREET3>LFStreet3</STREET3>
            <POSTL_COD1>Post2</POSTL_COD1>
            <CITY1>LFCity</CITY1>
            <TELEPHONE1>LFPhone</TELEPHONE1>
            <TELEFAX>LFFax</TELEFAX>
            <COUNTRY1>LF</COUNTRY1>
            <REGION>LF</REGION>
        </E1ADRM0>
        <E1ADRM0 SEGMENT="1">
            <PARTNER_Q>MF</PARTNER_Q>
            <ADDRESS_T>A</ADDRESS_T>
            <PARTNER_ID>MANUFACTURER</PARTNER_ID>
            <JURISDIC>Juris</JURISDIC>
            <LANGUAGE>EN</LANGUAGE>
            <NAME1>Manufacturer</NAME1>
            <NAME2>ManufacturerName2</NAME2>
            <NAME3>ManufacturerName3</NAME3>
            <STREET1>MFStreet1</STREET1>
            <STREET2>MFStreet2</STREET2>
            <STREET3>MFStreet3</STREET3>
            <POSTL_COD1>MFPost</POSTL_COD1>
            <CITY1>MFCity</CITY1>
            <TELEPHONE1>MFPhone</TELEPHONE1>
            <TELEFAX>MFFax</TELEFAX>
            <COUNTRY1>MF</COUNTRY1>
            <REGION>MFR</REGION>
        </E1ADRM0>
        <E1ADRM0 SEGMENT="1">
            <PARTNER_Q>WE</PARTNER_Q>
            <ADDRESS_T>A</ADDRESS_T>
            <PARTNER_ID>SHIPTO</PARTNER_ID>
            <JURISDIC>Juris</JURISDIC>
            <LANGUAGE>EN</LANGUAGE>
            <NAME1>ShipTo</NAME1>
            <NAME2>ShipToName2</NAME2>
            <NAME3>ShipToName3</NAME3>
            <STREET1>WEStreet1</STREET1>
            <STREET2>WEStreet2</STREET2>
            <STREET3>WEStreet3</STREET3>
            <POSTL_COD1>WEPost</POSTL_COD1>
            <CITY1>WECity</CITY1>
            <TELEPHONE1>WEPhone</TELEPHONE1>
            <TELEFAX>WEFax</TELEFAX>
            <COUNTRY1>WE</COUNTRY1>
            <REGION>WER</REGION>
        </E1ADRM0>
        <E1ADRM0 SEGMENT="1">
            <PARTNER_Q>OSP</PARTNER_Q>
            <ADDRESS_T>A</ADDRESS_T>
            <PARTNER_ID>SHIPFROM</PARTNER_ID>
            <JURISDIC>Juris</JURISDIC>
            <LANGUAGE>EN</LANGUAGE>
            <NAME1>ShipFrom</NAME1>
            <NAME2>ShipFromName2</NAME2>
            <NAME3>ShipFromName3</NAME3>
            <STREET1>SFStreet1</STREET1>
            <STREET2>SFStreet2</STREET2>
            <STREET3>SFStreet3</STREET3>
            <POSTL_COD1>SFPost</POSTL_COD1>
            <CITY1>SFCity</CITY1>
            <TELEPHONE1>SFPhone</TELEPHONE1>
            <TELEFAX>SFFax</TELEFAX>
            <COUNTRY1>SF</COUNTRY1>
            <REGION>SFR</REGION>
        </E1ADRM0>
        <E1DRM02 SEGMENT="1">
            <POSEX>000010</POSEX>
            <ACTION>005</ACTION>
            <STQTY>1305750</STQTY>
            <MEASUNIT>CR</MEASUNIT>
            <EFF_DATE>20240101</EFF_DATE>
            <E1DRM04 SEGMENT="1">
                <QUALF>079</QUALF>
                <STOCK_LOC>A-100</STOCK_LOC>
                <QTY>1500</QTY>
                <UOM>BX</UOM>
                <E1EDP19 SEGMENT="1">
                    <QUALF>004</QUALF>
                    <IDTNR>MANUFACTURER</IDTNR>
                    <KTEXT>ProdName 1</KTEXT>
                </E1EDP19>
                <E1EDP19 SEGMENT="1">
                    <QUALF>002</QUALF>
                    <IDTNR>Supplier</IDTNR>
                    <KTEXT>Name 2</KTEXT>
                </E1EDP19>
                <E1EDP19 SEGMENT="1">
                    <QUALF>003</QUALF>
                    <IDTNR>GTIN14</IDTNR>
                    <KTEXT>Name 3</KTEXT>
                </E1EDP19>
                <E1EDP19 SEGMENT="1">
                    <QUALF>001</QUALF>
                    <IDTNR>CUSTOMER</IDTNR>
                    <KTEXT>Customer Desc 3</KTEXT>
                </E1EDP19>
            </E1DRM04>        
        </E1DRM02>
    </IDOC>
</INVRPT01>
Review TraceLink's API: Terms of Use

Table of contents

Related Content
Related content
Forecast plan (IDoc)
Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record.
View More
Related content
Forecast plan (X12)
Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record.
View More
Related content
Forecast plan response (IDoc)
Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with downstream supply chain Partners without giving these Partners access to their serialization system of record.
View More

Cookie Settings

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies or similar tracking technologies. Please see below for an overview of the categories of cookies and similar technologies used on this site. You can allow or deny some of all of them, except Strictly Necessary Cookies which are required to provide the site to you. However, blocking some types of cookies may impact your experience of the site and services we are able to offer.

Please see our Cookie Policy for more details, including a list of the cookies we use. You can change your consent options at any time by following the “Cookie Settings” link in the Cookie Policy.
'Strictly Necessary' cookies let you move around the Site and use essential features like secure areas, shopping baskets and online billing. Without these cookies you would not be able to navigate between pages or use certain vital features of our Site, so we do not require your consent for their use. These cookies don't gather any information about you that could be used for marketing or remembering where you've been on the internet. For example, we use these Strictly Necessary cookies to identify you as being logged in to the Site. You can set your browser to block or alert you about these cookies, but if you do so, some parts of the Site will not work.
'Performance' cookies collect information about how you use the Site, such as which pages you visit, the time spent on the Site and if you experience any errors. We use performance cookies to provide aggregated statistics on how the Site is used and help us improve the Site including by measuring any errors that occur.
'Functional' cookies are used to provide services or to remember settings to improve your visit. We use 'Functionality' cookies to remember your settings and choices and show you when you're logged in to the Site.
‘Targeting' cookies are linked to services provided by third parties, such as 'Like' buttons and 'Share' buttons. The third party provides these services in return for recognizing that you have visited the Site. We also use 'Targeting' cookies to gather information that could be used to display content that we think may interest you.

Footer

  • Quick Links
    Get a Demo
    TraceLink Network Directory
    The Network
    OPUS Platform
    Technical Support
    Open Jobs
    API: Terms of Use
  • Products
    Multienterprise Information Network Tower
    U.S. DSCSA Compliance
    Targeted Recalls
    Process Orchestration for Empowered Teams
    Serialization
    Global Compliance
  • Resources
    Resource Center
    Events
    TraceLink University
    Partners
    Community
  • About TraceLink
    Our Story
    Newsroom
    Culture & Careers
    Leadership
    Our Values
    Corporate Social Responsibility
  • Hot Topics
    Transaction Integration
    Supply Chain Visibility
    DSCSA Compliance
    Process Orchestration
    Kazakhstan Compliance for Pharmaceuticals
    Kyrgyzstan Compliance for Pharmaceuticals
Follow Us on Social
Facebook
Linkedin
X
Legal & Trust.
© TraceLink Inc. 2009-2026 All Rights Reserved
Contact Us Today
Contact us today to begin your journey toward agentic supply chain orchestration — digitalize your end-to-end supply chain with intelligence, flexibility, and collaborative orchestration.
Contact Us
Stay Up-to-Date
Subscribe to receive industry insights and stay at the forefront of evolving trends.
Subscribe