3PL Use Cases

TraceLink Roles

TraceLink API Guides group messages by application. Each API Guide contains all messages available within that application. Your company's business type (e.g. CMO, Wholesale Distributor, 3PL) and role in the TraceLink Network (Owner or Partner1) determine which of these messages to develop (i.e. not all messages within this guide may fulfill your business or compliance needs).

See below to confirm which messages you should develop based on your role in the supply chain and/or the TraceLink Network.

Configure and exchange (send or receive) each message separately as a best practice.

 

A 3PL acting on behalf of a Pharmaceutical Manufacturer can enable asynchronously notifying the relevant Pharmaceutical Manufacturer of successful Set Event requests. This requires the 3PL to own Smart Event Manager, Master Data Exchange, and Serialized Operations Manager applications. The 3PL uses this feature by enabling the Smart Event Manager Notification Workflow and the Serialized Operations Manager Update Serial Number Status Workflow in Company Administration, and by specifying the Product Master Data, including the Pharmaceutical Manufacturer ID at the target market level, only for products that require Pharmaceutical Manufacturer notification.

 

Smart Event Manager Owners

3PLs send the Set Event Request to TraceLink to record events (e.g. verification, shipping, receiving)(i.e. verification) and observations, as well as to record "undo" operations when events or observations are submitted in error. TraceLink sends he Set Event Response is sent by TraceLink and includes the original Request data, plus additional response fields that include the assigned eventId and processing result information (i.e. status, message, and state).
3PLs send the Get Event Request to TraceLink returning the Request and Response from a single previously reported Set Event for a specific eventId. TraceLink generates the eventId when processing the initial Set Event Request. The Get Event Response is sent by TraceLink and includes the complete Request and Response contents from the original Set Event. The response fields vary based on the information included in each specific event.
3PLs send the Get Result Request to TraceLink using the eventQueryResponseId to determine if a bulk serial number request has been processed and what the result of the request is.
3PLs send the Query Event Request to TraceLink to retrieve previously submitted events and their results using a broad set of search criteria. The Query Event Response is sent byTraceLink and includes all of the event data from the Set Event Request and Response relating to the search criteria.