Carrier Despatch Advice

As a carrier: get your despatch advice from Solventum in the agreed format.

Formats available:

  • GS1 Transport Instruction (GS1-TI), version 3.2.1
  • GS1-Transport Capacity Booking (GS1-TCB)
  • IFTMIN D96A / D01B

If you have your own standard that can be used to support the Solventum business, please let us know so we can identify if that can be implemented.

How go get connected

Since integrations can be challenging our team is here to assist you. Please reach out to us at servicedesk@shipitsmarter.com.
These specific messages are exchanged through SFTP, where our team can configure to which folders to push the files.

How to identify Solventum?

As Viya is a multi-tenant platform, we support sharing the same SFTP server for multiple shippers, although we typically advice against it for security & privacy reasons.

Our main separator for the identification is a separate SFTP user for each shipper. We made it easy for the shipper to create a new user for each carrier, and to provide the necessary information to the carrier.

If you want to separate the files for each shipper based on the contents of the file, following identifiers are available:

  • GS1-TI: Transport_instruction.transportInstruction.logisticServicesBuyer.additionalPartyIdentification additionalPartyIdentificationTypeCode="BUYER_ASSIGNED_IDENTIFIER_FOR_A_PARTY" contains the identifier for the shipper.
<?xml version="1.0" encoding="UTF-8"?>
  <transport_instruction:transportInstructionMessage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:transport_instruction="urn:gs1:ecom:transport_instruction:xsd:3">
  <StandardBusinessDocumentHeader xmlns="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" />
  <transportInstruction>
    <creationDateTime/>
    <documentStatusCode/>
    <transportInstructionIdentification/>
    <transportInstructionFunction/>
    <logisticServicesSeller/>
    <logisticServicesBuyer>
      <additionalPartyIdentification additionalPartyIdentificationTypeCode="BUYER_ASSIGNED_IDENTIFIER_FOR_A_PARTY">{shipper identifier here}</additionalPartyIdentification>
    </logisticServicesBuyer>

Note: The StandardBusinessDocumentHeader\DocumentIdentification\instanceIdentifier is VIYA for all GS1-TI messages.

  • GS1-TCB: transport_capacity_booking.transportCapacityBooking.logisticServicesBuyer.additionalPartyIdentification additionalPartyIdentificationTypeCode="BUYER_ASSIGNED_IDENTIFIER_FOR_A_PARTY" contains the identifier for the shipper.
<transport_capacity_booking:transportCapacityBookingMessage xmlns:sh="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:transport_capacity_booking="urn:gs1:ecom:transport_capacity_booking:xsd:3">
  <sh:StandardBusinessDocumentHeader/>
  <transportCapacityBooking>
    <creationDateTime/>
    <documentStatusCode/>
    <documentActionCode/>
    <transportCapacityBookingIdentification/>
    <transportServiceCategoryCode/>
    <transportServiceConditionTypeCode/>
    <logisticServicesBuyer>
      <additionalPartyIdentification additionalPartyIdentificationTypeCode="BUYER_ASSIGNED_IDENTIFIER_FOR_A_PARTY">{shipper identifier here}</additionalPartyIdentification>
  </logisticServicesBuyer>
  • IFTMIN D96A / D01B: The NAD+CZ segment contains the identifier for the shipper.
NAD+CZ+{shipper identifier here}++Shipper Name+Street+City+Postal Code+Country Code'

For Solventum the identifier for the shipper is 0707387103026