Tradecloud API v2 manual
  • Introduction
    • Welcome
      • Checklist
      • Support
    • API
      • Rules
      • Requests
      • JSON versus XML
      • Environments
      • Standards
      • Compatibility
      • Tools
        • Swagger UI
        • Postman
        • .NET SDK
      • Webhook versus polling
        • Polling usage
        • Polling echo
      • Delivery schedule
    • Security
      • Security overview
      • Authentication
      • Authorization
      • Encryption
      • Document storage
  • Guide
    • 1. Getting an Account
    • 2. Sending your first order
      • Option A: Sending a Delivery Schedule per order line
      • Option B: Sending a Single Delivery per order line
  • Processes
    • Forecasts
      • Issue a new forecast
      • Issue a new Slimstock forecast
    • Orders
      • Buyer order process
        • Issue a new order
          • Delivery schedule
          • Indicators
          • No delivery expected
          • Propose when accepted
          • Attach a document to an order
          • Choose attach document API
        • Update an existing order
        • Receive an order response
          • Download a document attached to an order response
          • Single delivery order response
        • Receive goods
        • Complete an order
        • Reopen an order
        • Cancel an order
      • Supplier order process
        • Receive an order
          • Download a document attached to an order
          • Single delivery order
        • Send order response
          • Attach a document to an order response
        • Reopen an order
        • Cancel an order
    • Shipments
      • Supplier shipment process
        • Send despatch advice
      • Buyer shipment process
        • Receive a shipment event
          • Download a document attached to a shipment
Powered by GitBook
On this page
  • Choose the appropriate API to receive a shipment event
  • ShipmentEvent
  • Shipment state
  • Shipment identifiers
  • Supplier shipment header
  • Buyer shipment header
  • Load carrier
  • Container fields
  • Generic package fields
  • Lines
  • Shipment line
  • Shipment item
  • Supplier shipment line
  • Shipment line meta information
  • Shipment locations
  • Shipment departure
  • Shipment destination
  • Shipment location
  • Shipment meta information
  • Message meta information
  1. Processes
  2. Shipments
  3. Buyer shipment process

Receive a shipment event

How to receive a shipment event

PreviousBuyer shipment processNextDownload a document attached to a shipment

Last updated 1 year ago

Tradecloud will send a shipment event to the buyer when a shipment event has been triggered.

At this moment a shipment event will only be triggered when the supplier issues or updates a despatch advice.

The shipment module is under development. The API and documentation may change.

Choose the appropriate API to receive a shipment event

First choose either the webhook API or the polling API to receive shipment messages:

ShipmentEvent

  • eventName: the event name, currently ShipmentIssuedBySupplier, ShipmentApprovedByBuyer, ShipmentRejectedByBuyer or ShipmentResentByBuyer.

Event names may be extended by other shipment events in the future.

  • shipment: the shipment state, see

  • meta: the message meta information, see

Shipment state

The shipment data:

  • id: the Tradecloud shipment identifier

  • identifiers: the identifiers related to this shipment, see

  • transportMode: the Mode of Transport name used for the delivery of goods. is advised for Mode of Transport names.

  • supplierShipment: the supplier side header of the shipment, see

  • buyerShipment: the buyer side header part of the shipment, see

  • loadCarriers: a list of all the load carriers in this shipment, each load carrier containing shipment lines, see

  • lines: a list of all the shipment lines, not loaded in a load carrier, see

  • locations: the departure and destination locations with arrival and departure date/times, see

  • status: the shipment status

    • processStatus: the shipment process status, currently Issued, Approved or Rejected, and may be extended with other values in the future

    • processStatusReason: the optional reason of the current process status, for example the reason why the shipment is rejected

  • meta: meta information about the shipment, see

Shipment identifiers

The identifiers related to this shipment:

  • billOfLadingNumber: the bill of lading number as provided by the carrier

  • carrierShipmentNumber: the shipment number as provided by the carrier

  • trackingNumber: the tracking number as provided by the carrier or courier

Supplier shipment header

The supplier side header of this shipment:

  • companyId: the mandatory Tradecloud company identifier of the supplier

  • buyerAccountNumber: the buyer account code or number as used by the supplier

  • shipmentNumber: the related shipment number as known in the supplier's ERP system

  • invoiceNumbers: the related invoice numbers as known in the supplier's ERP system

Buyer shipment header

The buyer side header of this shipment:

  • companyId: the mandatory Tradecloud company identifier of the buyer

  • supplierAccountNumber: the supplier account code or number as known at the buyer

Contact

A contact person related to this shipment:

  • userId: the Tradecloud user identifier

  • email: the contact email as known in Tradecloud

  • firstName: the personal name of the contact person

  • lastName: the family name of the contact person

  • position: the business role of the contact person within the company

  • phoneNumber the phone number of the contact person

Document

  • code: the unique identifier of the document as provided by the supplier or buyer

  • revision: the revision of the document

  • name: the short name of the document

  • description: the description of the document

  • type: the type of the document. Eg. General, Invoice, Packing List, etc...

  • objectId: the object ID as known by the Tradecloud Object Storage, if this document is stored in Tradecloud, see also:

  • url: the location of the document if is not stored in Tradecloud

  • meta: meta information about the shipment document

    • lastUpdatedAt: ISO date and time with timezone at which the shipment document was last updated in Tradecloud. A document has been added or changed if the document.meta.lastUpdatedAt is equal to the shipment.meta.lastUpdatedAt

Purchase order terms

The purchase order terms, as agreed between buyer and supplier, related to this shipment:

  • incoterms: the incoterms named place (delivery, terminal, port or destination)

  • paymentTermsCode: the payment terms code as defined in the buyers ERP system

  • paymentTerms: the payment terms text as defined in the buyers ERP system

Load carrier

Container fields

When the load carrier is a container:

Generic package fields

When the load carrier is NOT a container:

Lines

Shipment line

A shipment line containing identifiers, item and supplier data including quantities. A line has been added to either a shipment directly or to a load carrier.

  • purchaseOrderNumber: the mandatory related purchase order number as provided by the buyer

  • purchaseOrderLinePosition: the mandatory line position in the purchase order as provided by the buyer

  • deliverySchedulePosition: the related delivery schedule position in the purchase order line as provided by the buyer

Shipment item

The item (article, goods) that is being shipped:

  • buyerItemNumber: the item number as provided by the buyer

  • buyerItemRevision: the revision of the item as provided by the buyer

  • buyerItemName: the short name of this item as provided by the buyer

  • supplierItemNumber: the supplier item code or number as provided by the buyer or supplier

  • supplierItemRevision: the revision (or version) as provided by the supplier

  • supplierItemName: the short name of this item as provided by the supplier

  • purchaseUnitOfMeasureIso: the the 3-letter purchase unit according to ISO 80000-1 which applies to this item

Supplier shipment line

The supplier side of the shipment line:

  • despatchAdviceNumber: the mandatory unique despatch advice number as provided by the supplier

  • despatchAdviceLinePosition the mandatory position in the despatch advice as provided by the supplier. The position is unique within the despatch advice and immutable.

  • despatchQuantity the mandatory despatch quantity of this purchase order line or delivery schedule position.

  • backorderQuantity: the backorder quantity of this purchase order line or delivery schedule position.

Shipment line meta information

  • lastUpdatedAt: ISO date and time with timezone at which the shipment line was last updated in Tradecloud. A line has been added or changed if the lines.meta.lastUpdatedAt is equal to the shipment.meta.lastUpdatedAt

Shipment locations

The departure and destination locations together with arrival and departure date/times of a shipment:

Shipment departure

A shipment departure location with ETD and ATD dates:

  • etdDate: the Estimated Time of Departure of this shipment from this location

  • atdDate: the Actual Time of Departure of this shipment from this location

Shipment destination

A shipment place, port or final destination with location, ETA time window, ATA, ETD and ATD dates:

Estimated start and end date/times indicate the scheduled time window of arrival:

  • etaStartDate: the Estimated Time of Arrival period start date of this shipment at this destination

  • etaStartTime: the Estimated Time of Arrival period start time of this shipment at this destination

  • etaEndDate: the Estimated Time of Arrival period end date of this shipment at this destination

  • etaEndTime: the Estimated Time of Arrival period end time of this shipment at this destination

  • ataDate: the Actual Time of Arrival of this shipment at this destination

  • etdDate: the Estimated Time of Departure of this shipment from this location

  • atdDate: the Actual Time of Departure of this shipment from this location

Shipment location

    • AgreedPlace (used with EXW, FCA)

    • PortOfLoading (used with FAS, FOB)

    • PortOfDestination (used with CFR, CIF)

    • PlaceOfDestination (used with CPT, CIP)

    • FinalDestination (used with DAP, DPU, DDP)

  • id: the required identifier for the location, in context of idSchema

  • names: one or more location names. It is recommended to provide at least one name.

  • addressLines: one or more location address lines

  • postalCode: location postal code

  • city: location city

Shipment meta information

  • lastUpdatedAt: ISO date and time with timezone at which the shipment was last updated in Tradecloud, useful for polling shipments.

  • supplierErpMeta the supplier's ERP meta information about this shipment

    • despatchAdviceErpIssueDateTime: local date and time at which the despatch advice of this shipment was issued in the supplier's ERP system

Message meta information

  • messageId: the Tradecloud identifier of this message.

  • source: includes meta information about the source of this message:

    • traceId: the Tradecloud trace identifier of this message. All related messages in a flow will have the same tradeId.

    • userId: the Tradecloud user identifier which triggered the first message in a flow

    • companyId: the Tradecloud company identifier which triggered the first message in a flow

  • createdDateTime: date and time with time zone, at which this message was created

imoNumber: the IMO as provided by the carrier

supplierParty: the unique party identifier and scheme, like , of the supplier

documents: the supplier documents attached to this shipment, see

contacts: the supplier contacts related to this shipment, see

buyerParty: the unique party identifier and scheme, like , of the buyer

documents: the buyer documents attached to this shipment, see

contacts: the buyer contacts related to this shipment, see

purchaseOrderTerms: the purchase order terms as agreed between buyer and supplier, see

incotermsCode: the incoterms code according to ICC

A load carrier containing shipment lines. Either use the or the together with .

containerNumber: the BIC ISO 6346

containerSizeAndType: the BIC ISO 6346

packageSSCC: the package GS1

packageType: the package type, is advised

lines: a list of all the shipment lines, loaded in this load carrier, see

item: the item that is shipped, see

supplierLine: the supplier side of the shipment line, see

meta: meta information about the shipment line, see

departure: the departure location and dates, see

destinations: one or more destination locations with arrival and departure date/times, see

location: the departure location, see

location: the location where the shipment should arrive next, see

locationType: a location type according to ICC :

idScheme: scheme, providing context to the location identifier, like

countryCodeIso: country code

ship identification number
GLN
GLN
Download a document attached to a shipment
Incoterms 2020
Container Identification Number
Container Size & Type Code
Serial Shipping Container Code (SSCC)
Unece Code List Recommendation 21
Incoterms 2020
GLN
ISO 3166-1 alpha-2
Webhook versus polling
Unece Code List Recommendation 19
Shipment state
Message meta information
Shipment identifiers
Supplier shipment header
Buyer shipment header
Load carrier
Shipment line
Shipment locations
Shipment meta information
Document
Contact
Document
Contact
Purchase order terms
container fields
generic package fields
lines
Shipment line
Shipment item
Supplier shipment line
Shipment line meta information
Shipment departure
Shipment destination
Shipment location
Shipment location