Trigger a POST request to the webhook.
const url = 'https://api.tradecloud1.com/v2/yourcompany.com/any/order/path';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"eventName":"OrderLinesAcceptedBySupplier","orderEvent":{"orderId":"cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189","buyerOrder":{"companyId":"deea1b30-64b6-4dbf-ad74-51895c4a7695","buyerParty":{"id":"COMPANY-123","idScheme":"KvK","names":["Blue Corp.","Ocean District"],"addressLines":["Main street 1","Building 6"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"buyerAccountingParty":{"id":"COMPANY-123","idScheme":"KvK","names":["Blue Corp.","Ocean District"],"addressLines":["Main street 1","Building 6"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"purchaseOrderNumber":"PO123456789","supplierAccountNumber":"SUPPLIER12345","supplierParty":{"id":"COMPANY-123","idScheme":"KvK","names":["Blue Corp.","Ocean District"],"addressLines":["Main street 1","Building 6"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"description":"Any custom text about this order","destination":{"locationType":"Supplier Premises","code":"LOC001","names":["Company Name Headquarters"],"addressLines":["Molengraaffsingel 12"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"terms":{"incotermsCode":"CIF","incoterms":"ECT Rotterdam","paymentTermsCode":"30D","paymentTerms":"30 days"},"indicators":{"autoConfirm":true},"properties":[{"key":"color","value":"red"}],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"notes":["Buyer note 1","Buyer note 2"],"labels":["first label for this buyer order","second label for this buyer order"],"contact":{"userId":"1ff0bd3b-9ee1-4b04-b6d0-f34de09aafce","email":"johndoe@test.com","userName":"john.d","status":"Assigned","firstName":"John","lastName":"Doe","position":"Supply Chain Manager","phoneNumber":"+31612345678"},"orderType":"Purchase","customLabels":[{"text":"Urgent","reason":"Out of stock"}],"erpIssueDateTime":"2019-12-31T10:11:12","erpIssuedBy":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"},"erpLastChangeDateTime":"2019-12-31T10:11:12","erpLastChangedBy":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"}},"supplierOrder":{"companyId":"d024bf02-7e33-427b-b4f5-a10a61761711","buyerAccountNumber":"BUYER12345","description":"Any custom text about this supplier order","properties":[{"key":"color","value":"red"}],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"notes":["Supplier note 1","Supplier note 2"],"contact":{"userId":"d024bf02-7e33-427b-b4f5-a10a61761711","email":"user@example.com","userName":"user","status":"Suggested","firstName":"John","lastName":"Doe","position":"Supply Chain Manager","phoneNumber":"+31612345678"},"customLabels":[{"text":"Urgent","reason":"Out of stock"}],"erpLastResponseDateTime":"2019-12-31T10:11:12","erpLastRespondedBy":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"}},"lines":[{"id":"ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010","lineType":"Item","chargeReasonCode":"FC","buyerLine":{"position":"00010","row":"1","description":"Anything about this buyer line","item":{"number":"12345","revision":"v2","name":"Round tube ø60x45","description":"Very nice round tube ø60 x 45","purchaseUnitOfMeasureIso":"PCE","supplierItemNumber":"67890","dimensions":[{"attribute":"Length","measure":50.5,"unitOfMeasureUnece":"m"}]},"itemDetails":{"countryOfOriginCodeIso2":"NL","combinedNomenclatureCode":"6406 10 10","netWeight":41.241,"netWeightUnitOfMeasureIso":"KG","dangerousGoodsCodeUnece":"0060","serialNumber":"0x0000000000028000","batchNumber":"#18001"},"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"deliverySchedule":[{"position":"0001","date":"2019-12-31","quantity":1234.56}],"chargeLines":[{"position":"001","chargeTypeCode":"FC","chargeDescription":"Additional coating","quantity":2,"price":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE"}],"deliveryHistory":[{"position":"0001","date":"2019-12-31","quantity":1234.56}],"requests":{"reopenRequest":{"deliverySchedule":[{"position":"0001","originalPosition":"0001","date":"2019-12-31","quantity":1234.56}],"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"chargeLines":[{"position":"001","chargeTypeCode":"FC","chargeDescription":"Additional coating","quantity":2,"price":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE"}],"reason":"We need to reconsider this.","status":"Open"},"reconfirmationRequest":{"status":"Open"}},"terms":{"contractNumber":"123456789","contractPosition":"0001"},"projectNumber":"PROJ12345","productionNumber":"PROD12345","salesOrderNumber":"SO123456789","indicators":{"noDeliveryExpected":true,"delivered":true,"shipped":true,"proposeWhenAccepted":true},"properties":[{"key":"color","value":"red"}],"notes":["First buyer line note","Second buyerr line note"],"labels":["First label for this buyer line","Second label for this buyer line"],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"certification":{"typeCode":"C","type":"Class Certificate","classificationSocietyCode":"LR","classificationSociety":"Lloyd & Boss Register"},"customLabels":[{"text":"Urgent","reason":"Out of stock"}]},"supplierLine":{"salesOrderNumber":"SO123456789","salesOrderLinePosition":"00010","description":"Anything about this supplier line","itemDetails":{"countryOfOriginCodeIso2":"NL","combinedNomenclatureCode":"6406 10 10","netWeight":41.241,"netWeightUnitOfMeasureIso":"KG","dangerousGoodsCodeUnece":"0060","serialNumber":"0x0000000000028000","batchNumber":"#18001"},"chargeLines":[{"position":"001","chargeTypeCode":"FC","chargeDescription":"Additional coating","quantity":2,"price":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE"}],"requests":{"proposal":{"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"deliverySchedule":[{"position":"0001","originalPosition":"0001","date":"2019-12-31","quantity":1234.56}],"chargeLines":[{"position":"001","chargeTypeCode":"FC","chargeDescription":"Additional coating","quantity":2,"price":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE"}],"reason":"Out of stock","status":"Open"},"reopenRequest":{"deliverySchedule":[{"position":"0001","originalPosition":"0001","date":"2019-12-31","quantity":1234.56}],"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"chargeLines":[{"position":"001","chargeTypeCode":"FC","chargeDescription":"Additional coating","quantity":2,"price":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE"}],"reason":"We need to reconsider this.","status":"Open"},"shipmentRescheduleRequest":{"deliverySchedule":[{"position":"0001","originalPosition":"0001","date":"2019-12-31","quantity":1234.56}],"reason":"Shipment needs to be rescheduled due to production delay.","status":"Open"}},"properties":[{"key":"color","value":"red"}],"notes":["First supplier line note","Second supplier line note"],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"customLabels":[{"text":"Urgent","reason":"Out of stock"}]},"confirmedLine":{"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"deliverySchedule":[{"position":"0001","originalPosition":"0001","date":"2019-12-31","quantity":1234.56}],"chargeLines":[{"position":"001","chargeTypeCode":"FC","chargeDescription":"Additional coating","quantity":2,"price":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE"}]},"deliverySchedule":[{"position":"01","date":"2019-12-31","quantity":1234.56,"status":"Open","indicators":{"deliveryOverdue":false},"transportMode":"Train","etd":"2019-12-31","eta":"2019-12-31"}],"deliveryScheduleIncludingRequests":[{"position":"01","date":"2019-12-31","quantity":1234.56,"status":"Open","indicators":{"deliveryOverdue":false},"transportMode":"Train","etd":"2019-12-31","eta":"2019-12-31"}],"shipmentHistory":[{"shipmentId":"0827f1b5-af43-4fbb-8f7e-6bc20c7dcd44-S12345","shipmentNumber":"S12345","deliverySchedulePosition":"D01","despatchQuantity":15.5}],"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"pricesIncludingRequests":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"indicators":{"deliveryOverdue":true},"eventDates":{"issuedAt":"2019-12-31T10:11:12.123Z","confirmedAt":"2019-12-31T10:11:12.123Z","shippedAt":"2019-12-31T10:11:12.123Z","deliveredAt":"2019-12-31T10:11:12.123Z","cancelledAt":"2019-12-31T10:11:12.123Z","completedAt":"2019-12-31T10:11:12.123Z"},"status":{"processStatus":"Issued","inProgressStatus":"OpenSupplierProposal","logisticsStatus":"Open"},"mergedItemDetails":{"countryOfOriginCodeIso2":"NL","combinedNomenclatureCode":"6406 10 10","netWeight":41.241,"netWeightUnitOfMeasureIso":"KG","dangerousGoodsCodeUnece":"0060","serialNumber":"0x0000000000028000","batchNumber":"#18001"},"totalAmount":{"value":1234.56,"currencyIso":"EUR"},"totalAmountIncludingRequests":{"value":1234.56,"currencyIso":"EUR"},"lastUpdatedAt":"2021-04-23T10:01:53.812Z","reason":"Production schedule changed.","portalUrl":"https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10"}],"status":{"processStatus":"Issued","logisticsStatus":"Open"},"reason":"Production schedule changed.","indicators":{"deliveryOverdue":true},"eventDates":{"issuedAt":"2019-12-31T10:11:12.123Z","confirmedAt":"2019-12-31T10:11:12.123Z","shippedAt":"2019-12-31T10:11:12.123Z","deliveredAt":"2019-12-31T10:11:12.123Z","cancelledAt":"2019-12-31T10:11:12.123Z","completedAt":"2019-12-31T10:11:12.123Z"},"amounts":{"total":{"value":1234.56,"currencyIso":"EUR"},"totalInclRequests":{"value":1234.56,"currencyIso":"EUR"}},"meta":{"messageId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","source":{"traceId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","userId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","companyId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","origin":"Portal"},"createdDateTime":"2019-12-08T10:11:12.123Z"},"lastUpdatedAt":"2021-04-23T10:01:53.812Z","version":3,"portalUrl":"https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189"},"singleDeliveryOrderEvent":{"orderId":"eaf0036d-63ec-4292-b4ca-d65df0a912cc","buyerOrder":{"companyId":"deea1b30-64b6-4dbf-ad74-51895c4a7695","buyerParty":{"id":"COMPANY-123","idScheme":"KvK","names":["Blue Corp.","Ocean District"],"addressLines":["Main street 1","Building 6"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"buyerAccountingParty":{"id":"COMPANY-123","idScheme":"KvK","names":["Blue Corp.","Ocean District"],"addressLines":["Main street 1","Building 6"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"purchaseOrderNumber":"PO123456789","supplierAccountNumber":"SUPPLIER12345","supplierParty":{"id":"COMPANY-123","idScheme":"KvK","names":["Blue Corp.","Ocean District"],"addressLines":["Main street 1","Building 6"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"description":"Any custom text about this order","destination":{"locationType":"Supplier Premises","code":"LOC001","names":["Company Name Headquarters"],"addressLines":["Molengraaffsingel 12"],"postalCode":"1234 AB","city":"Delft","countryCodeIso2":"NL","countryName":"The Netherlands"},"terms":{"incotermsCode":"CIF","incoterms":"ECT Rotterdam","paymentTermsCode":"30D","paymentTerms":"30 days"},"indicators":{"autoConfirm":true},"properties":[{"key":"color","value":"red"}],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"notes":["Buyer note 1","Buyer note 2"],"labels":["first label for this buyer order","second label for this buyer order"],"contact":{"userId":"1ff0bd3b-9ee1-4b04-b6d0-f34de09aafce","email":"johndoe@test.com","userName":"john.d","status":"Assigned","firstName":"John","lastName":"Doe","position":"Supply Chain Manager","phoneNumber":"+31612345678"},"orderType":"Purchase","customLabels":[{"text":"Urgent","reason":"Out of stock"}],"erpIssueDateTime":"2019-12-31T10:11:12","erpIssuedBy":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"},"erpLastChangeDateTime":"2019-12-31T10:11:12","erpLastChangedBy":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"}},"supplierOrder":{"companyId":"d024bf02-7e33-427b-b4f5-a10a61761711","buyerAccountNumber":"BUYER12345","description":"Any custom text about this supplier order","properties":[{"key":"color","value":"red"}],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"notes":["Supplier note 1","Supplier note 2"],"contact":{"userId":"d024bf02-7e33-427b-b4f5-a10a61761711","email":"user@example.com","userName":"user","status":"Suggested","firstName":"John","lastName":"Doe","position":"Supply Chain Manager","phoneNumber":"+31612345678"},"customLabels":[{"text":"Urgent","reason":"Out of stock"}],"erpLastResponseDateTime":"2019-12-31T10:11:12","erpLastRespondedBy":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"}},"lines":[{"id":"ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010","lineType":"Item","chargeReasonCode":"FC","buyerLine":{"position":"00010","originalPosition":"00010","row":"1","description":"Anything about this line","item":{"number":"12345","revision":"v2","name":"Round tube ø60x45","description":"Very nice round tube ø60 x 45","purchaseUnitOfMeasureIso":"PCE","supplierItemNumber":"67890","dimensions":[{"attribute":"Length","measure":50.5,"unitOfMeasureUnece":"m"}]},"itemDetails":{"countryOfOriginCodeIso2":"NL","combinedNomenclatureCode":"6406 10 10","netWeight":41.241,"netWeightUnitOfMeasureIso":"KG","dangerousGoodsCodeUnece":"0060","serialNumber":"0x0000000000028000","batchNumber":"#18001"},"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"terms":{"contractNumber":"123456789","contractPosition":"0001"},"projectNumber":"PROJ12345","productionNumber":"PROD12345","salesOrderNumber":"SO123456789","indicators":{"noDeliveryExpected":true,"delivered":true,"shipped":true,"proposeWhenAccepted":true},"properties":[{"key":"color","value":"red"}],"notes":["example"],"labels":["first label for this line","second label for this line"],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"certification":{"typeCode":"C","type":"Class Certificate","classificationSocietyCode":"LR","classificationSociety":"Lloyd & Boss Register"},"customLabels":[{"text":"Urgent","reason":"Out of stock"}]},"supplierLine":{"salesOrderNumber":"SO123456789","salesOrderLinePosition":"00010","description":"Anything about this line","itemDetails":{"countryOfOriginCodeIso2":"NL","combinedNomenclatureCode":"6406 10 10","netWeight":41.241,"netWeightUnitOfMeasureIso":"KG","dangerousGoodsCodeUnece":"0060","serialNumber":"0x0000000000028000","batchNumber":"#18001"},"properties":[{"key":"color","value":"red"}],"notes":["example"],"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"customLabels":[{"text":"Urgent","reason":"Out of stock"}]},"statusLine":{"scheduledDelivery":{"date":"2019-12-31","quantity":1234.56,"status":"ReadyToShip","indicators":{"deliveryOverdue":false},"transportMode":"Road transport","etd":"2019-12-31","eta":"2019-12-31"},"scheduledDeliveryInclRequests":{"date":"2019-12-31","quantity":1234.56,"status":"ReadyToShip","indicators":{"deliveryOverdue":false},"transportMode":"Road transport","etd":"2019-12-31","eta":"2019-12-31"},"prices":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"pricesInclRequests":{"grossPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"discountPercentage":50,"netPrice":{"priceInTransactionCurrency":{"value":1234.56,"currencyIso":"EUR"},"priceInBaseCurrency":{"value":1234.56,"currencyIso":"EUR"}},"priceUnitOfMeasureIso":"PCE","priceUnitQuantity":100},"totalQuantity":1234.56,"totalQuantityInclRequests":1234.56,"totalAmount":{"value":1234.56,"currencyIso":"EUR"},"totalAmountInclRequests":{"value":1234.56,"currencyIso":"EUR"}},"indicators":{"deliveryOverdue":true},"status":{"processStatus":"Issued","inProgressStatus":"OpenSupplierProposal","logisticsStatus":"Open"},"reason":"Production schedule changed.","eventDates":{"issuedAt":"2019-12-31T10:11:12.123Z","confirmedAt":"2019-12-31T10:11:12.123Z","shippedAt":"2019-12-31T10:11:12.123Z","deliveredAt":"2019-12-31T10:11:12.123Z","cancelledAt":"2019-12-31T10:11:12.123Z","completedAt":"2019-12-31T10:11:12.123Z"},"mergedItemDetails":{"countryOfOriginCodeIso2":"NL","combinedNomenclatureCode":"6406 10 10","netWeight":41.241,"netWeightUnitOfMeasureIso":"KG","dangerousGoodsCodeUnece":"0060","serialNumber":"0x0000000000028000","batchNumber":"#18001"},"lastUpdatedAt":"2021-04-23T10:01:53.812Z","portalUrl":"https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10"}],"status":{"processStatus":"Issued","logisticsStatus":"Open"},"reason":"Production schedule changed.","indicators":{"deliveryOverdue":true},"eventDates":{"issuedAt":"2019-12-31T10:11:12.123Z","confirmedAt":"2019-12-31T10:11:12.123Z","shippedAt":"2019-12-31T10:11:12.123Z","deliveredAt":"2019-12-31T10:11:12.123Z","cancelledAt":"2019-12-31T10:11:12.123Z","completedAt":"2019-12-31T10:11:12.123Z"},"amounts":{"total":{"value":1234.56,"currencyIso":"EUR"},"totalInclRequests":{"value":1234.56,"currencyIso":"EUR"}},"meta":{"messageId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","source":{"traceId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","userId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","companyId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","origin":"Portal"},"createdDateTime":"2019-12-08T10:11:12.123Z"},"lastUpdatedAt":"2021-04-23T10:01:53.812Z","version":3,"portalUrl":"https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189"},"orderDocumentsEvent":{"orderId":"eaf0036d-63ec-4292-b4ca-d65df0a912cc","buyerOrderDocument":{"companyId":"00f03b98-2511-489f-9695-13791b3f66b6","purchaseOrderNumber":"PO123456789","orderType":"Purchase","supplierAccountNumber":"12345","contact":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"}},"supplierOrderDocument":{"companyId":"d024bf02-7e33-427b-b4f5-a10a61761711","buyerAccountNumber":"BUYER12345","contact":{"userId":"00f03b98-2511-489f-9695-13791b3f66b6","email":"contact@yourcompany.com","userName":"username"}},"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}],"lines":[{"orderLineId":"ee99cd3f-c24c-4b60-84ea-8dcf889cc37b","buyerLineDocument":{"position":"00010"},"supplierLineDocument":{"salesOrderNumber":"SO123456789","salesOrderPosition":"00020"},"documents":[{"code":"123456789","revision":"B","name":"Tradecloud API Manual","objectId":"00f03b98-2511-489f-9695-13791b3f66b6","url":"https://my-company.com/storage/my_file.pdf","description":"General document","type":"General"}]}],"meta":{"messageId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","source":{"traceId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","userId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","companyId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","origin":"Portal"},"createdDateTime":"2019-12-08T10:11:12.123Z"}}}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.tradecloud1.com/v2/yourcompany.com/any/order/path \ --header 'Content-Type: application/json' \ --data '{ "eventName": "OrderLinesAcceptedBySupplier", "orderEvent": { "orderId": "cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189", "buyerOrder": { "companyId": "deea1b30-64b6-4dbf-ad74-51895c4a7695", "buyerParty": { "id": "COMPANY-123", "idScheme": "KvK", "names": [ "Blue Corp.", "Ocean District" ], "addressLines": [ "Main street 1", "Building 6" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "buyerAccountingParty": { "id": "COMPANY-123", "idScheme": "KvK", "names": [ "Blue Corp.", "Ocean District" ], "addressLines": [ "Main street 1", "Building 6" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "purchaseOrderNumber": "PO123456789", "supplierAccountNumber": "SUPPLIER12345", "supplierParty": { "id": "COMPANY-123", "idScheme": "KvK", "names": [ "Blue Corp.", "Ocean District" ], "addressLines": [ "Main street 1", "Building 6" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "description": "Any custom text about this order", "destination": { "locationType": "Supplier Premises", "code": "LOC001", "names": [ "Company Name Headquarters" ], "addressLines": [ "Molengraaffsingel 12" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "terms": { "incotermsCode": "CIF", "incoterms": "ECT Rotterdam", "paymentTermsCode": "30D", "paymentTerms": "30 days" }, "indicators": { "autoConfirm": true }, "properties": [ { "key": "color", "value": "red" } ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "notes": [ "Buyer note 1", "Buyer note 2" ], "labels": [ "first label for this buyer order", "second label for this buyer order" ], "contact": { "userId": "1ff0bd3b-9ee1-4b04-b6d0-f34de09aafce", "email": "johndoe@test.com", "userName": "john.d", "status": "Assigned", "firstName": "John", "lastName": "Doe", "position": "Supply Chain Manager", "phoneNumber": "+31612345678" }, "orderType": "Purchase", "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ], "erpIssueDateTime": "2019-12-31T10:11:12", "erpIssuedBy": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" }, "erpLastChangeDateTime": "2019-12-31T10:11:12", "erpLastChangedBy": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" } }, "supplierOrder": { "companyId": "d024bf02-7e33-427b-b4f5-a10a61761711", "buyerAccountNumber": "BUYER12345", "description": "Any custom text about this supplier order", "properties": [ { "key": "color", "value": "red" } ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "notes": [ "Supplier note 1", "Supplier note 2" ], "contact": { "userId": "d024bf02-7e33-427b-b4f5-a10a61761711", "email": "user@example.com", "userName": "user", "status": "Suggested", "firstName": "John", "lastName": "Doe", "position": "Supply Chain Manager", "phoneNumber": "+31612345678" }, "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ], "erpLastResponseDateTime": "2019-12-31T10:11:12", "erpLastRespondedBy": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" } }, "lines": [ { "id": "ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010", "lineType": "Item", "chargeReasonCode": "FC", "buyerLine": { "position": "00010", "row": "1", "description": "Anything about this buyer line", "item": { "number": "12345", "revision": "v2", "name": "Round tube ø60x45", "description": "Very nice round tube ø60 x 45", "purchaseUnitOfMeasureIso": "PCE", "supplierItemNumber": "67890", "dimensions": [ { "attribute": "Length", "measure": 50.5, "unitOfMeasureUnece": "m" } ] }, "itemDetails": { "countryOfOriginCodeIso2": "NL", "combinedNomenclatureCode": "6406 10 10", "netWeight": 41.241, "netWeightUnitOfMeasureIso": "KG", "dangerousGoodsCodeUnece": "0060", "serialNumber": "0x0000000000028000", "batchNumber": "#18001" }, "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "deliverySchedule": [ { "position": "0001", "date": "2019-12-31", "quantity": 1234.56 } ], "chargeLines": [ { "position": "001", "chargeTypeCode": "FC", "chargeDescription": "Additional coating", "quantity": 2, "price": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE" } ], "deliveryHistory": [ { "position": "0001", "date": "2019-12-31", "quantity": 1234.56 } ], "requests": { "reopenRequest": { "deliverySchedule": [ { "position": "0001", "originalPosition": "0001", "date": "2019-12-31", "quantity": 1234.56 } ], "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "chargeLines": [ { "position": "001", "chargeTypeCode": "FC", "chargeDescription": "Additional coating", "quantity": 2, "price": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE" } ], "reason": "We need to reconsider this.", "status": "Open" }, "reconfirmationRequest": { "status": "Open" } }, "terms": { "contractNumber": "123456789", "contractPosition": "0001" }, "projectNumber": "PROJ12345", "productionNumber": "PROD12345", "salesOrderNumber": "SO123456789", "indicators": { "noDeliveryExpected": true, "delivered": true, "shipped": true, "proposeWhenAccepted": true }, "properties": [ { "key": "color", "value": "red" } ], "notes": [ "First buyer line note", "Second buyerr line note" ], "labels": [ "First label for this buyer line", "Second label for this buyer line" ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "certification": { "typeCode": "C", "type": "Class Certificate", "classificationSocietyCode": "LR", "classificationSociety": "Lloyd & Boss Register" }, "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ] }, "supplierLine": { "salesOrderNumber": "SO123456789", "salesOrderLinePosition": "00010", "description": "Anything about this supplier line", "itemDetails": { "countryOfOriginCodeIso2": "NL", "combinedNomenclatureCode": "6406 10 10", "netWeight": 41.241, "netWeightUnitOfMeasureIso": "KG", "dangerousGoodsCodeUnece": "0060", "serialNumber": "0x0000000000028000", "batchNumber": "#18001" }, "chargeLines": [ { "position": "001", "chargeTypeCode": "FC", "chargeDescription": "Additional coating", "quantity": 2, "price": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE" } ], "requests": { "proposal": { "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "deliverySchedule": [ { "position": "0001", "originalPosition": "0001", "date": "2019-12-31", "quantity": 1234.56 } ], "chargeLines": [ { "position": "001", "chargeTypeCode": "FC", "chargeDescription": "Additional coating", "quantity": 2, "price": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE" } ], "reason": "Out of stock", "status": "Open" }, "reopenRequest": { "deliverySchedule": [ { "position": "0001", "originalPosition": "0001", "date": "2019-12-31", "quantity": 1234.56 } ], "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "chargeLines": [ { "position": "001", "chargeTypeCode": "FC", "chargeDescription": "Additional coating", "quantity": 2, "price": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE" } ], "reason": "We need to reconsider this.", "status": "Open" }, "shipmentRescheduleRequest": { "deliverySchedule": [ { "position": "0001", "originalPosition": "0001", "date": "2019-12-31", "quantity": 1234.56 } ], "reason": "Shipment needs to be rescheduled due to production delay.", "status": "Open" } }, "properties": [ { "key": "color", "value": "red" } ], "notes": [ "First supplier line note", "Second supplier line note" ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ] }, "confirmedLine": { "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "deliverySchedule": [ { "position": "0001", "originalPosition": "0001", "date": "2019-12-31", "quantity": 1234.56 } ], "chargeLines": [ { "position": "001", "chargeTypeCode": "FC", "chargeDescription": "Additional coating", "quantity": 2, "price": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE" } ] }, "deliverySchedule": [ { "position": "01", "date": "2019-12-31", "quantity": 1234.56, "status": "Open", "indicators": { "deliveryOverdue": false }, "transportMode": "Train", "etd": "2019-12-31", "eta": "2019-12-31" } ], "deliveryScheduleIncludingRequests": [ { "position": "01", "date": "2019-12-31", "quantity": 1234.56, "status": "Open", "indicators": { "deliveryOverdue": false }, "transportMode": "Train", "etd": "2019-12-31", "eta": "2019-12-31" } ], "shipmentHistory": [ { "shipmentId": "0827f1b5-af43-4fbb-8f7e-6bc20c7dcd44-S12345", "shipmentNumber": "S12345", "deliverySchedulePosition": "D01", "despatchQuantity": 15.5 } ], "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "pricesIncludingRequests": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "indicators": { "deliveryOverdue": true }, "eventDates": { "issuedAt": "2019-12-31T10:11:12.123Z", "confirmedAt": "2019-12-31T10:11:12.123Z", "shippedAt": "2019-12-31T10:11:12.123Z", "deliveredAt": "2019-12-31T10:11:12.123Z", "cancelledAt": "2019-12-31T10:11:12.123Z", "completedAt": "2019-12-31T10:11:12.123Z" }, "status": { "processStatus": "Issued", "inProgressStatus": "OpenSupplierProposal", "logisticsStatus": "Open" }, "mergedItemDetails": { "countryOfOriginCodeIso2": "NL", "combinedNomenclatureCode": "6406 10 10", "netWeight": 41.241, "netWeightUnitOfMeasureIso": "KG", "dangerousGoodsCodeUnece": "0060", "serialNumber": "0x0000000000028000", "batchNumber": "#18001" }, "totalAmount": { "value": 1234.56, "currencyIso": "EUR" }, "totalAmountIncludingRequests": { "value": 1234.56, "currencyIso": "EUR" }, "lastUpdatedAt": "2021-04-23T10:01:53.812Z", "reason": "Production schedule changed.", "portalUrl": "https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10" } ], "status": { "processStatus": "Issued", "logisticsStatus": "Open" }, "reason": "Production schedule changed.", "indicators": { "deliveryOverdue": true }, "eventDates": { "issuedAt": "2019-12-31T10:11:12.123Z", "confirmedAt": "2019-12-31T10:11:12.123Z", "shippedAt": "2019-12-31T10:11:12.123Z", "deliveredAt": "2019-12-31T10:11:12.123Z", "cancelledAt": "2019-12-31T10:11:12.123Z", "completedAt": "2019-12-31T10:11:12.123Z" }, "amounts": { "total": { "value": 1234.56, "currencyIso": "EUR" }, "totalInclRequests": { "value": 1234.56, "currencyIso": "EUR" } }, "meta": { "messageId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "source": { "traceId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "userId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "companyId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "origin": "Portal" }, "createdDateTime": "2019-12-08T10:11:12.123Z" }, "lastUpdatedAt": "2021-04-23T10:01:53.812Z", "version": 3, "portalUrl": "https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189" }, "singleDeliveryOrderEvent": { "orderId": "eaf0036d-63ec-4292-b4ca-d65df0a912cc", "buyerOrder": { "companyId": "deea1b30-64b6-4dbf-ad74-51895c4a7695", "buyerParty": { "id": "COMPANY-123", "idScheme": "KvK", "names": [ "Blue Corp.", "Ocean District" ], "addressLines": [ "Main street 1", "Building 6" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "buyerAccountingParty": { "id": "COMPANY-123", "idScheme": "KvK", "names": [ "Blue Corp.", "Ocean District" ], "addressLines": [ "Main street 1", "Building 6" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "purchaseOrderNumber": "PO123456789", "supplierAccountNumber": "SUPPLIER12345", "supplierParty": { "id": "COMPANY-123", "idScheme": "KvK", "names": [ "Blue Corp.", "Ocean District" ], "addressLines": [ "Main street 1", "Building 6" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "description": "Any custom text about this order", "destination": { "locationType": "Supplier Premises", "code": "LOC001", "names": [ "Company Name Headquarters" ], "addressLines": [ "Molengraaffsingel 12" ], "postalCode": "1234 AB", "city": "Delft", "countryCodeIso2": "NL", "countryName": "The Netherlands" }, "terms": { "incotermsCode": "CIF", "incoterms": "ECT Rotterdam", "paymentTermsCode": "30D", "paymentTerms": "30 days" }, "indicators": { "autoConfirm": true }, "properties": [ { "key": "color", "value": "red" } ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "notes": [ "Buyer note 1", "Buyer note 2" ], "labels": [ "first label for this buyer order", "second label for this buyer order" ], "contact": { "userId": "1ff0bd3b-9ee1-4b04-b6d0-f34de09aafce", "email": "johndoe@test.com", "userName": "john.d", "status": "Assigned", "firstName": "John", "lastName": "Doe", "position": "Supply Chain Manager", "phoneNumber": "+31612345678" }, "orderType": "Purchase", "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ], "erpIssueDateTime": "2019-12-31T10:11:12", "erpIssuedBy": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" }, "erpLastChangeDateTime": "2019-12-31T10:11:12", "erpLastChangedBy": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" } }, "supplierOrder": { "companyId": "d024bf02-7e33-427b-b4f5-a10a61761711", "buyerAccountNumber": "BUYER12345", "description": "Any custom text about this supplier order", "properties": [ { "key": "color", "value": "red" } ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "notes": [ "Supplier note 1", "Supplier note 2" ], "contact": { "userId": "d024bf02-7e33-427b-b4f5-a10a61761711", "email": "user@example.com", "userName": "user", "status": "Suggested", "firstName": "John", "lastName": "Doe", "position": "Supply Chain Manager", "phoneNumber": "+31612345678" }, "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ], "erpLastResponseDateTime": "2019-12-31T10:11:12", "erpLastRespondedBy": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" } }, "lines": [ { "id": "ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010", "lineType": "Item", "chargeReasonCode": "FC", "buyerLine": { "position": "00010", "originalPosition": "00010", "row": "1", "description": "Anything about this line", "item": { "number": "12345", "revision": "v2", "name": "Round tube ø60x45", "description": "Very nice round tube ø60 x 45", "purchaseUnitOfMeasureIso": "PCE", "supplierItemNumber": "67890", "dimensions": [ { "attribute": "Length", "measure": 50.5, "unitOfMeasureUnece": "m" } ] }, "itemDetails": { "countryOfOriginCodeIso2": "NL", "combinedNomenclatureCode": "6406 10 10", "netWeight": 41.241, "netWeightUnitOfMeasureIso": "KG", "dangerousGoodsCodeUnece": "0060", "serialNumber": "0x0000000000028000", "batchNumber": "#18001" }, "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "terms": { "contractNumber": "123456789", "contractPosition": "0001" }, "projectNumber": "PROJ12345", "productionNumber": "PROD12345", "salesOrderNumber": "SO123456789", "indicators": { "noDeliveryExpected": true, "delivered": true, "shipped": true, "proposeWhenAccepted": true }, "properties": [ { "key": "color", "value": "red" } ], "notes": [ "example" ], "labels": [ "first label for this line", "second label for this line" ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "certification": { "typeCode": "C", "type": "Class Certificate", "classificationSocietyCode": "LR", "classificationSociety": "Lloyd & Boss Register" }, "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ] }, "supplierLine": { "salesOrderNumber": "SO123456789", "salesOrderLinePosition": "00010", "description": "Anything about this line", "itemDetails": { "countryOfOriginCodeIso2": "NL", "combinedNomenclatureCode": "6406 10 10", "netWeight": 41.241, "netWeightUnitOfMeasureIso": "KG", "dangerousGoodsCodeUnece": "0060", "serialNumber": "0x0000000000028000", "batchNumber": "#18001" }, "properties": [ { "key": "color", "value": "red" } ], "notes": [ "example" ], "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "customLabels": [ { "text": "Urgent", "reason": "Out of stock" } ] }, "statusLine": { "scheduledDelivery": { "date": "2019-12-31", "quantity": 1234.56, "status": "ReadyToShip", "indicators": { "deliveryOverdue": false }, "transportMode": "Road transport", "etd": "2019-12-31", "eta": "2019-12-31" }, "scheduledDeliveryInclRequests": { "date": "2019-12-31", "quantity": 1234.56, "status": "ReadyToShip", "indicators": { "deliveryOverdue": false }, "transportMode": "Road transport", "etd": "2019-12-31", "eta": "2019-12-31" }, "prices": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "pricesInclRequests": { "grossPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "discountPercentage": 50, "netPrice": { "priceInTransactionCurrency": { "value": 1234.56, "currencyIso": "EUR" }, "priceInBaseCurrency": { "value": 1234.56, "currencyIso": "EUR" } }, "priceUnitOfMeasureIso": "PCE", "priceUnitQuantity": 100 }, "totalQuantity": 1234.56, "totalQuantityInclRequests": 1234.56, "totalAmount": { "value": 1234.56, "currencyIso": "EUR" }, "totalAmountInclRequests": { "value": 1234.56, "currencyIso": "EUR" } }, "indicators": { "deliveryOverdue": true }, "status": { "processStatus": "Issued", "inProgressStatus": "OpenSupplierProposal", "logisticsStatus": "Open" }, "reason": "Production schedule changed.", "eventDates": { "issuedAt": "2019-12-31T10:11:12.123Z", "confirmedAt": "2019-12-31T10:11:12.123Z", "shippedAt": "2019-12-31T10:11:12.123Z", "deliveredAt": "2019-12-31T10:11:12.123Z", "cancelledAt": "2019-12-31T10:11:12.123Z", "completedAt": "2019-12-31T10:11:12.123Z" }, "mergedItemDetails": { "countryOfOriginCodeIso2": "NL", "combinedNomenclatureCode": "6406 10 10", "netWeight": 41.241, "netWeightUnitOfMeasureIso": "KG", "dangerousGoodsCodeUnece": "0060", "serialNumber": "0x0000000000028000", "batchNumber": "#18001" }, "lastUpdatedAt": "2021-04-23T10:01:53.812Z", "portalUrl": "https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10" } ], "status": { "processStatus": "Issued", "logisticsStatus": "Open" }, "reason": "Production schedule changed.", "indicators": { "deliveryOverdue": true }, "eventDates": { "issuedAt": "2019-12-31T10:11:12.123Z", "confirmedAt": "2019-12-31T10:11:12.123Z", "shippedAt": "2019-12-31T10:11:12.123Z", "deliveredAt": "2019-12-31T10:11:12.123Z", "cancelledAt": "2019-12-31T10:11:12.123Z", "completedAt": "2019-12-31T10:11:12.123Z" }, "amounts": { "total": { "value": 1234.56, "currencyIso": "EUR" }, "totalInclRequests": { "value": 1234.56, "currencyIso": "EUR" } }, "meta": { "messageId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "source": { "traceId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "userId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "companyId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "origin": "Portal" }, "createdDateTime": "2019-12-08T10:11:12.123Z" }, "lastUpdatedAt": "2021-04-23T10:01:53.812Z", "version": 3, "portalUrl": "https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189" }, "orderDocumentsEvent": { "orderId": "eaf0036d-63ec-4292-b4ca-d65df0a912cc", "buyerOrderDocument": { "companyId": "00f03b98-2511-489f-9695-13791b3f66b6", "purchaseOrderNumber": "PO123456789", "orderType": "Purchase", "supplierAccountNumber": "12345", "contact": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" } }, "supplierOrderDocument": { "companyId": "d024bf02-7e33-427b-b4f5-a10a61761711", "buyerAccountNumber": "BUYER12345", "contact": { "userId": "00f03b98-2511-489f-9695-13791b3f66b6", "email": "contact@yourcompany.com", "userName": "username" } }, "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ], "lines": [ { "orderLineId": "ee99cd3f-c24c-4b60-84ea-8dcf889cc37b", "buyerLineDocument": { "position": "00010" }, "supplierLineDocument": { "salesOrderNumber": "SO123456789", "salesOrderPosition": "00020" }, "documents": [ { "code": "123456789", "revision": "B", "name": "Tradecloud API Manual", "objectId": "00f03b98-2511-489f-9695-13791b3f66b6", "url": "https://my-company.com/storage/my_file.pdf", "description": "General document", "type": "General" } ] } ], "meta": { "messageId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "source": { "traceId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "userId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "companyId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "origin": "Portal" }, "createdDateTime": "2019-12-08T10:11:12.123Z" } } }'If POST requests are configured in your company integration settings, Tradecloud will trigger a request to this address when an order (response) is new or has been changed.
Request Bodyrequired
Section titled “Request Bodyrequired”The request body that is sent to your webhook.
object
The name of the event that is included in this request. For buyer/supplier it could be one one of the following:
- CompletedOrderLinesRevertedByBuyer
- OrderChangesProposalApprovedByBuyer
- OrderChangesProposalRejectedByBuyer
- OrderChangesProposedBySupplier
- OrderContactReassignedByBuyer
- OrderContactReassignedBySupplier
- OrderCustomLabelsUpdatedByBuyer
- OrderCustomLabelsUpdatedBySupplier
- OrderDocumentsAttachedByBuyer
- OrderDocumentsAttachedBySupplier
- OrderIssuedByBuyer
- OrderLinesAcceptedBySupplier
- OrderLinesCancelledByBuyer
- OrderLinesCompletedByBuyer
- OrderLinesConfirmedByBuyer
- OrderLinesConfirmedBySupplier
- OrderLinesDeliveryHistoryAppendedByBuyer
- OrderLinesDeliveryHistorySetByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedBySupplier
- OrderLinesIssuedByBuyer
- OrderLinesItemDetailsChangedBySupplier
- OrderLinesMarkedAsDeliveredByBuyer
- OrderLinesMarkedAsDeliveredBySupplier
- OrderLinesMarkedAsOpenByBuyer
- OrderLinesMarkedAsOpenBySupplier
- OrderLinesReconfirmationRequestedByBuyer
- OrderLinesReconfirmedBySupplier
- OrderLinesReissuedByBuyer
- OrderLinesRejectedBySupplier
- OrderLinesReopenRequestApprovedByBuyer
- OrderLinesReopenRequestApprovedBySupplier
- OrderLinesReopenRequestRejectedByBuyer
- OrderLinesReopenRequestRejectedBySupplier
- OrderLinesReopenRequestRevertedByBuyer
- OrderLinesReopenRequestRevertedBySupplier
- OrderLinesReopenRequestedByBuyer
- OrderLinesReopenRequestedBySupplier
- OrderLinesShipmentRescheduleApprovedByBuyer
- OrderLinesShipmentRescheduleRejectedByBuyer
- OrderLinesShipmentRescheduleRequestedBySupplier
- OrderLinesShippedByBuyer
- OrderLinesUpdatedByBuyer
- OrderLinesUpdatedBySupplier
- OrderResentByBuyer
- OrderResentBySupplier
Example
OrderLinesAcceptedBySupplierIncludes the order data. Note that if “Single delivery per order line” is enabled in the connector settings, the singleDeliveryOrderEvent is provided instead. Only provided if eventName is one of the following:
- CompletedOrderLinesRevertedByBuyer
- OrderChangesProposalApprovedByBuyer
- OrderChangesProposalRejectedByBuyer
- OrderChangesProposedBySupplier
- OrderContactReassignedByBuyer
- OrderContactReassignedBySupplier
- OrderCustomLabelsUpdatedByBuyer
- OrderCustomLabelsUpdatedBySupplier
- OrderIssuedByBuyer
- OrderLinesAcceptedBySupplier
- OrderLinesCancelledByBuyer
- OrderLinesCompletedByBuyer
- OrderLinesConfirmedByBuyer
- OrderLinesConfirmedBySupplier
- OrderLinesDeliveryHistoryAppendedByBuyer
- OrderLinesDeliveryHistorySetByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedBySupplier
- OrderLinesIssuedByBuyer
- OrderLinesItemDetailsChangedBySupplier
- OrderLinesMarkedAsDeliveredByBuyer
- OrderLinesMarkedAsDeliveredBySupplier
- OrderLinesMarkedAsOpenByBuyer
- OrderLinesMarkedAsOpenBySupplier
- OrderLinesReconfirmationRequestedByBuyer
- OrderLinesReconfirmedBySupplier
- OrderLinesReissuedByBuyer
- OrderLinesRejectedBySupplier
- OrderLinesReopenRequestApprovedByBuyer
- OrderLinesReopenRequestApprovedBySupplier
- OrderLinesReopenRequestRejectedByBuyer
- OrderLinesReopenRequestRejectedBySupplier
- OrderLinesReopenRequestRevertedByBuyer
- OrderLinesReopenRequestRevertedBySupplier
- OrderLinesReopenRequestedByBuyer
- OrderLinesReopenRequestedBySupplier
- OrderLinesShipmentRescheduleApprovedByBuyer
- OrderLinesShipmentRescheduleRejectedByBuyer
- OrderLinesShipmentRescheduleRequestedBySupplier
- OrderLinesShippedByBuyer
- OrderLinesUpdatedByBuyer
- OrderLinesUpdatedBySupplier
- OrderResentByBuyer
- OrderResentBySupplier
object
The Tradecloud order ID
Example
cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189The buyer side header of the purchase order.
object
The buyers globally unique Tradecloud company identifier
Example
deea1b30-64b6-4dbf-ad74-51895c4a7695Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsIncludes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe purchase order number provided by the buyer. The number is unique and immutable within the buyer scope.
Example
PO123456789The supplier account code or number as known at the buyer.
Example
SUPPLIER12345Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsAn optional free format order description or reference added by the buyer
Example
Any custom text about this orderIncludes location code and address.
object
Optional type of the location, eg. Supplier Premises
Example
Supplier PremisesMandatory unique and immutable destination location code or number.
Example
LOC001One or more names used to described this location. Can be the company name, location name, department, etc.
One or more address lines of this location.
The postal code of this location.
Example
1234 ABThe city of this location.
Example
DelftMandatory ISO 3166-1 alpha-2 country code of this location.
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe order terms as agreed between buyer and supplier, provided by the buyer.
object
Optional incoterms code according to ICC Incoterms 2010.
Example
CIFThe incoterms named place (delivery, terminal, port or destination).
Example
ECT RotterdamThe payment terms code as provided by the buyer.
Example
30DThe payment terms text as provided by the buyer.
Example
30 daysobject
Indicates whether the autoConfirm feature was enabled by the buyer for this order.
Key-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the buyer. \n are used for a new line.
Example
[ "Buyer note 1", "Buyer note 2"]Optional value-added services labels on order level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "first label for this buyer order", "second label for this buyer order"]The buyer contact information of an order.
object
The Tradecloud user ID of the buyer contact.
Example
1ff0bd3b-9ee1-4b04-b6d0-f34de09aafceThe email of the buyer contact.
Example
johndoe@test.comThe username of the buyer contact in the buyer ERP system.
Example
john.dThe status of this buyer contact.
The first name of the buyer contact.
Example
JohnThe last name of the buyer contact.
Example
DoeThe position of the buyer contact within the buyer company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the buyer company.
Example
+31612345678The order type, one of:
Purchase- This is a purchase order (default).Forecast- This is a forecast order.RFQ- This is a request for quotation order.
Optional custom labels on order level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockOptional ISO local date and time at which the order was originally issued in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameOptional ISO local date and time at which the order was updated in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameThe supplier side header of the purchase order.
object
The suppliers globally unique Tradecloud company identifier
Example
d024bf02-7e33-427b-b4f5-a10a61761711The buyer account code or number as known at the supplier.
Example
BUYER12345An optional free format order description or reference added by the supplier
Example
Any custom text about this supplier orderKey-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the supplier. \n are used for a new line.
Example
[ "Supplier note 1", "Supplier note 2"]Supplier contact information.
object
User ID.
Example
d024bf02-7e33-427b-b4f5-a10a61761711Email address.
Example
user@example.comUsername.
Example
userThe first name of the supplier contact.
Example
JohnThe last name of the supplier contact.
Example
DoeThe position of the supplier contact within the supplier company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the supplier company.
Example
+31612345678Optional custom labels on order level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockISO local date and time at which the order response was updated in suppliers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameList of order lines, sorted by buyerLine.position.
Includes the order line data.
object
The globally unique Tradecloud order line identifier
Example
ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010The optional order line type set by the buyer or supplier, one of:
Item- This is an item line (default).Service- This is a service line.Charge- This is a charge line.
The optional charge reason code set by the buyer or supplier, in case of a charge line.
Example
FCA buyer purchase order line contains at least the position, item and delivery schedule.
object
The mandatory position identifier in the purchase order. The position is unique and immutable within the order.
Example
00010An optional row label for this position. Do NOT use row as identifier.
Example
1An optional free format line description or reference added by the buyer.
Example
Anything about this buyer lineThe buyer item (or article, goods) to be delivered.
object
The mandatory item code or number as known by the buyer. The number is unique and immutable within the buyer scope.
Example
12345The optional revision (or version) of this item as known by the buyer.
Example
v2The mandatory short name of this item as known by the buyer.
Example
Round tube ø60x45The optionally long description of this item as known by the buyer.
Example
Very nice round tube ø60 x 45The purchase unit of measure for this item, passed through as-is to the supplier. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
PCEThe optional item code or number as known by the supplier. Advised in case of wholesale suppliers.
Example
67890Array of dimensions related to the item
Defines measurable dimensions (length, width, area, weight or volume) of an item
object
Measurement type of item
Example
LengthMeasurement value
Example
50.5The unit of measure for this dimension, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
mThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The planned delivery schedule as requested by the buyer. One or more delivery lines will be provided.
A delivery line in the delivery schedule or history.
object
The optional position in the delivery schedule or history. The position is unique and immutable within the schedule.
Example
0001The mandatory local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The mandatory quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The charge lines for this order line as known by the buyer.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe historical actual delivery schedule as goods are received at the buyer. Zero, one or more delivery lines will be provided.
A delivery line in the delivery schedule or history.
object
The optional position in the delivery schedule or history. The position is unique and immutable within the schedule.
Example
0001The mandatory local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The mandatory quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Requests by the buyer.
object
Alternative delivery schedule and prices proposed by the buyer or supplier, after the order line was confirmed.
object
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEExample
We need to reconsider this.The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedReconfirmation request as requested by the buyer.
object
The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedOrder line terms set by the buyer.
object
The contract framework code or number associated with this line. The number is unique and immutable within the buyer scope.
Example
123456789Optional position in the framework contract associated with this line. The position is unique and immutable within the contract.
Example
0001Optional buyer project code or number associated with this line.
Example
PROJ12345Optional buyer production code or number associated with this line.
Example
PROD12345Optional buyer sales order code or number associated with this line.
Example
SO123456789Order line indicators set by the buyer.
object
No goods are expected to be delivered to the buyer.
Example
trueAll goods are delivered at the buyer.
Example
trueAll goods are shipped to the buyer.
Example
trueIf set to true, when supplier confirms a line then this line becomes a proposal
Example
trueKey-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the buyer. \n are used for a new line.
Example
[ "First buyer line note", "Second buyerr line note"]Optional value-added services labels on line level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "First label for this buyer line", "Second label for this buyer line"]Order line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
General3th party certification requirements by buyer.
object
Certification Type code
Example
CHuman readable Certification Type
Example
Class CertificateClassification Society code
Example
LRHuman readable Classification Society
Example
Lloyd & Boss RegisterOptional custom labels on order line level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockA supplier side order line may contain sales order number and position and a proposal.
object
Optional supplier sales order code or number associated with this line. The number is unique and immutable within the supplier scope.
Example
SO123456789Optional supplier sales order line position associated with this line. The position is unique and immutable within the sales order.
Example
00010An optional free format line description or reference added by the supplier.
Example
Anything about this supplier lineThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The charge lines for this order line as known by the supplier.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCERequests by the supplier.
object
Alternative delivery schedule and prices proposed by the supplier.
object
The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Alternative delivery schedule proposed by the supplier.
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The charge lines for this order line as proposed by the supplier.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEOptional reason for this proposal provided by the supplier.
Example
Out of stockThe line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedAlternative delivery schedule and prices proposed by the buyer or supplier, after the order line was confirmed.
object
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEExample
We need to reconsider this.The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedShipment reschedule request as requested by the supplier.
object
Requested delivery schedule for shipment reschedule.
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Optional reason for the shipment reschedule request.
Example
Shipment needs to be rescheduled due to production delay.The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedKey-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the supplier. \n are used for a new line.
Example
[ "First supplier line note", "Second supplier line note"]Order line document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralOptional custom labels on order line level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockThe agreed delivery schedule and prices between buyer and supplier. Available when the line has status ‘Confirmed’
object
The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The agreed delivery schedule between buyer and supplier. One or more delivery lines will be provided.
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The confirmed charge lines for this order line.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEAggregated delivery schedule with logistics info
An aggregated delivery schedule line with logistics info
object
The optional position in the delivery schedule.
Example
01The optional scheduled delivery local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery line. Quantity has a decimal format.
Example
1234.56The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
Openobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe mode of transportation
Example
TrainThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31Aggregated delivery schedule with logistics info and merged with requests
An aggregated delivery schedule line with logistics info
object
The optional position in the delivery schedule.
Example
01The optional scheduled delivery local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery line. Quantity has a decimal format.
Example
1234.56The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
Openobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe mode of transportation
Example
TrainThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31Information about the shipment lines that were created in the shipment module for this order line.
Information about a shipment line that was created in the shipment module for an order line.
object
The Tradecloud ID of the shipment in which the shipmentLine was included.
Example
0827f1b5-af43-4fbb-8f7e-6bc20c7dcd44-S12345The shipment number of the shipment in which the shipmentLine was included.
Example
S12345The position in the deliverySchedule that this shipmentLine applies to.
Example
D01The quantity that was dispatched.
Example
15.5The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100object
The goods of this line to be delivered are overdue according to the confirmed delivery schedule.
Example
trueKey line event date and times.
object
Mandatory ISO date and time, in UTC time zone, at which the order line was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe line process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedMore fine-grained status when an order line has processStatus InProgress, explaining why it is in progress:
OpenSupplierProposal- There is an open proposal from the supplier.RejectedSupplierProposal- The proposal from the supplier was rejected and no other requests are open.ApprovedDeliverySchedule- The order line delivery schedule was approved by the buyer.RejectedDeliverySchedule- The order line delivery schedule was rejected by the buyer.ReissuedRejectedLine- The rejected order line was reissued by the buyer.OpenBuyerReconfirmationRequest- The buyer has requested to reconfirmed the order line.OpenSupplierReopenRequest- There is an open reopen request from the supplier.OpenSupplierShipmentRescheduleRequest- There is an open shipment reschedule request from the supplier.OpenBuyerReopenRequest- There is an open reopen request from the buyer.RevertedCompletedLine- The completion of this line was reverted.
The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe ISO-8601 date and time in UTC time zone that denotes the latest date time the order line has been changed
Example
2021-04-23T10:01:53.812ZOptional reason for this order line event.
Example
Production schedule changed.The language independent Tradecloud portal URL of the order line.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10The order process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedThe order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenOptional reason for this order event.
Example
Production schedule changed.object
The goods of this order to be delivered are overdue according to the confirmed delivery schedule.
Example
trueOptional key order event date and times, on order header level. Only included on events that set one of these dates, such as OrderIssuedByBuyer, OrderLinesAcceptedBySupplier, OrderLinesConfirmedBySupplier, OrderLinesConfirmedByBuyer, OrderChangesProposalApprovedByBuyer, OrderLinesCancelledByBuyer, OrderLinesCompletedByBuyer, OrderLinesShippedByBuyer and the marked as delivered or marked as open events. Not included on events that do not set an order date, such as OrderLinesUpdatedByBuyer, OrderLinesRejectedBySupplier, OrderLinesReconfirmedBySupplier, OrderResentByBuyer and the reopen request events, including their approvals. The order line level eventDates is always included.
object
Mandatory ISO-8601 date and time in UTC time zone, at which the order was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe totalAmount and totalAmountInclRequests.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURIncludes meta information about this message.
object
Globally unique Tradecloud identifier of this message.
Includes meta information about the source of this message.
object
Globally unique Tradecloud trace identifier of this message. All related messages in a flow will have the same tradeId.
Globally unique Tradecloud user identifier which triggered the first message in a flow.
Globally unique Tradecloud company identifier which triggered the first message in a flow.
Mandatory ISO date and time, in UTC time zone, at which this message was created.
Example
2019-12-08T10:11:12.123ZThe ISO-8601 date and time in UTC time zone that denotes the latest date time the order has been changed.
Example
2021-04-23T10:01:53.812ZThe Tradecloud order version after the event. Some events, such as line updates, do not raise it, so two events can carry the same version and still differ. It does not identify a delivery; deduplicate a retry on meta.messageId.
Example
3The language independent Tradecloud portal URL of the order.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189Includes the order data, only if “Single delivery per order line” is enabled in the company’s connector settings. Only provided if eventName is one of the following:
- CompletedOrderLinesRevertedByBuyer
- OrderChangesProposalApprovedByBuyer
- OrderChangesProposalRejectedByBuyer
- OrderChangesProposedBySupplier
- OrderContactReassignedByBuyer
- OrderContactReassignedBySupplier
- OrderCustomLabelsUpdatedByBuyer
- OrderCustomLabelsUpdatedBySupplier
- OrderIssuedByBuyer
- OrderLinesAcceptedBySupplier
- OrderLinesCancelledByBuyer
- OrderLinesCompletedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedBySupplier
- OrderLinesIssuedByBuyer
- OrderLinesItemDetailsChangedBySupplier
- OrderLinesMarkedAsDeliveredByBuyer
- OrderLinesMarkedAsDeliveredBySupplier
- OrderLinesMarkedAsOpenByBuyer
- OrderLinesMarkedAsOpenBySupplier
- OrderLinesReconfirmationRequestedByBuyer
- OrderLinesReconfirmedBySupplier
- OrderLinesReissuedByBuyer
- OrderLinesRejectedBySupplier
- OrderLinesReopenRequestApprovedByBuyer
- OrderLinesReopenRequestApprovedBySupplier
- OrderLinesReopenRequestRejectedByBuyer
- OrderLinesReopenRequestRejectedBySupplier
- OrderLinesReopenRequestRevertedByBuyer
- OrderLinesReopenRequestRevertedBySupplier
- OrderLinesReopenRequestedByBuyer
- OrderLinesReopenRequestedBySupplier
- OrderLinesShipmentRescheduleApprovedByBuyer
- OrderLinesShipmentRescheduleRejectedByBuyer
- OrderLinesShipmentRescheduleRequestedBySupplier
- OrderLinesShippedByBuyer
- OrderLinesUpdatedByBuyer
- OrderLinesUpdatedBySupplier
- OrderResentByBuyer
- OrderResentBySupplier
object
The Tradecloud order ID
Example
eaf0036d-63ec-4292-b4ca-d65df0a912ccThe buyer side header of the purchase order.
object
The buyers globally unique Tradecloud company identifier
Example
deea1b30-64b6-4dbf-ad74-51895c4a7695Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsIncludes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe purchase order number provided by the buyer. The number is unique and immutable within the buyer scope.
Example
PO123456789The supplier account code or number as known at the buyer.
Example
SUPPLIER12345Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsAn optional free format order description or reference added by the buyer
Example
Any custom text about this orderIncludes location code and address.
object
Optional type of the location, eg. Supplier Premises
Example
Supplier PremisesMandatory unique and immutable destination location code or number.
Example
LOC001One or more names used to described this location. Can be the company name, location name, department, etc.
One or more address lines of this location.
The postal code of this location.
Example
1234 ABThe city of this location.
Example
DelftMandatory ISO 3166-1 alpha-2 country code of this location.
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe order terms as agreed between buyer and supplier, provided by the buyer.
object
Optional incoterms code according to ICC Incoterms 2010.
Example
CIFThe incoterms named place (delivery, terminal, port or destination).
Example
ECT RotterdamThe payment terms code as provided by the buyer.
Example
30DThe payment terms text as provided by the buyer.
Example
30 daysobject
Indicates whether the autoConfirm feature was enabled by the buyer for this order.
Key-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the buyer. \n are used for a new line.
Example
[ "Buyer note 1", "Buyer note 2"]Optional value-added services labels on order level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "first label for this buyer order", "second label for this buyer order"]The buyer contact information of an order.
object
The Tradecloud user ID of the buyer contact.
Example
1ff0bd3b-9ee1-4b04-b6d0-f34de09aafceThe email of the buyer contact.
Example
johndoe@test.comThe username of the buyer contact in the buyer ERP system.
Example
john.dThe status of this buyer contact.
The first name of the buyer contact.
Example
JohnThe last name of the buyer contact.
Example
DoeThe position of the buyer contact within the buyer company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the buyer company.
Example
+31612345678The order type, one of:
Purchase- This is a purchase order (default).Forecast- This is a forecast order.RFQ- This is a request for quotation order.
Optional custom labels on order level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockOptional ISO local date and time at which the order was originally issued in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameOptional ISO local date and time at which the order was updated in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameThe supplier side header of the purchase order.
object
The suppliers globally unique Tradecloud company identifier
Example
d024bf02-7e33-427b-b4f5-a10a61761711The buyer account code or number as known at the supplier.
Example
BUYER12345An optional free format order description or reference added by the supplier
Example
Any custom text about this supplier orderKey-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the supplier. \n are used for a new line.
Example
[ "Supplier note 1", "Supplier note 2"]Supplier contact information.
object
User ID.
Example
d024bf02-7e33-427b-b4f5-a10a61761711Email address.
Example
user@example.comUsername.
Example
userThe first name of the supplier contact.
Example
JohnThe last name of the supplier contact.
Example
DoeThe position of the supplier contact within the supplier company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the supplier company.
Example
+31612345678Optional custom labels on order level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockISO local date and time at which the order response was updated in suppliers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameList of order lines, sorted by buyerLine.position.
Includes the order line data for a particular scheduledDelivery
object
The globally unique Tradecloud order line identifier
Example
ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010The optional order line type set by the buyer or supplier, one of:
Item- This is an item line (default).Service- This is a service line.Charge- This is a charge line.
The optional charge reason code set by the buyer or supplier, in case of a charge line.
Example
FCA buyer purchase order line for a particular single delivery order line.
object
The position identifier in the purchase order. The position is unique and immutable within the order. Position is empty in case of a newly created or split line by the supplier.
Example
00010The original position in case this is a split line.
Example
00010An optional row label for this position. Do NOT use row as identifier.
Example
1An optional free format line description or reference added by the buyer.
Example
Anything about this lineThe buyer item (or article, goods) to be delivered.
object
The mandatory item code or number as known by the buyer. The number is unique and immutable within the buyer scope.
Example
12345The optional revision (or version) of this item as known by the buyer.
Example
v2The mandatory short name of this item as known by the buyer.
Example
Round tube ø60x45The optionally long description of this item as known by the buyer.
Example
Very nice round tube ø60 x 45The purchase unit of measure for this item, passed through as-is to the supplier. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
PCEThe optional item code or number as known by the supplier. Advised in case of wholesale suppliers.
Example
67890Array of dimensions related to the item
Defines measurable dimensions (length, width, area, weight or volume) of an item
object
Measurement type of item
Example
LengthMeasurement value
Example
50.5The unit of measure for this dimension, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
mThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Order line terms set by the buyer.
object
The contract framework code or number associated with this line. The number is unique and immutable within the buyer scope.
Example
123456789Optional position in the framework contract associated with this line. The position is unique and immutable within the contract.
Example
0001Optional buyer project code or number associated with this line.
Example
PROJ12345Optional buyer production code or number associated with this line.
Example
PROD12345Optional buyer sales order code or number associated with this line.
Example
SO123456789Order line indicators set by the buyer.
object
No goods are expected to be delivered to the buyer.
Example
trueAll goods are delivered at the buyer.
Example
trueAll goods are shipped to the buyer.
Example
trueIf set to true, when supplier confirms a line then this line becomes a proposal
Example
trueKey-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the buyer. \n are used for a new line.
Optional value-added services labels on line level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "first label for this line", "second label for this line"]Order line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
General3th party certification requirements by buyer.
object
Certification Type code
Example
CHuman readable Certification Type
Example
Class CertificateClassification Society code
Example
LRHuman readable Classification Society
Example
Lloyd & Boss RegisterOptional custom labels on order line level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockA supplier side order line may contain sales order number and position.
object
Optional supplier sales order code or number associated with this line. The number is unique and immutable within the supplier scope.
Example
SO123456789Optional supplier sales order line position associated with this line. The position is unique and immutable within the sales order.
Example
00010An optional free format line description or reference added by the supplier.
Example
Anything about this lineThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001Key-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the supplier. \n are used for a new line.
Order line document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralOptional custom labels on order line level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockThe order line values representing the current Issued or Confirmed status. The InclRequests fields include the InProgress status and open buyer or supplier request values.
object
The scheduled delivery line. This field is used as an alternative for the deliverySchedule field if your ERP system does not support a deliverySchedule within an order line natively and the delivery schedule is spread over multiple order lines instead. If you have One single delivery per order line enabled in your Order Webhook Connector settings, Tradecloud will transform the deliverySchedule into multiple order lines each containing a scheduledDelivery; one order line per delivery schedule line.
object
The optional scheduled delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The delivery schedule line logistics status according to your ERP system:
ReadyToShip- All goods of this delivery line are ready to be shipped by the supplier.Shipped- All goods of this delivery line are shipped by the supplier.Delivered- All goods of this delivery line are delivered at the buyer.
Example
ReadyToShipobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe Mode of Transport used for the delivery of goods. UNECE.org Recommendation 19 is advised for Mode of Transport values.
Example
Road transportThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The scheduled delivery line. This field is used as an alternative for the deliverySchedule field if your ERP system does not support a deliverySchedule within an order line natively and the delivery schedule is spread over multiple order lines instead. If you have One single delivery per order line enabled in your Order Webhook Connector settings, Tradecloud will transform the deliverySchedule into multiple order lines each containing a scheduledDelivery; one order line per delivery schedule line.
object
The optional scheduled delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The delivery schedule line logistics status according to your ERP system:
ReadyToShip- All goods of this delivery line are ready to be shipped by the supplier.Shipped- All goods of this delivery line are shipped by the supplier.Delivered- All goods of this delivery line are delivered at the buyer.
Example
ReadyToShipobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe Mode of Transport used for the delivery of goods. UNECE.org Recommendation 19 is advised for Mode of Transport values.
Example
Road transportThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The total scheduled quantity in the order line delivery schedule. Quantity has a decimal format.
Example
1234.56The total scheduled quantity in the order line delivery schedule including all requests.
Example
1234.56Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURobject
The goods of this line to be delivered are overdue according to the confirmed delivery schedule.
Example
trueThe line process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedMore fine-grained status when an order line has processStatus InProgress, explaining why it is in progress:
OpenSupplierProposal- There is an open proposal from the supplier.RejectedSupplierProposal- The proposal from the supplier was rejected and no other requests are open.ApprovedDeliverySchedule- The order line delivery schedule was approved by the buyer.RejectedDeliverySchedule- The order line delivery schedule was rejected by the buyer.ReissuedRejectedLine- The rejected order line was reissued by the buyer.OpenBuyerReconfirmationRequest- The buyer has requested to reconfirmed the order line.OpenSupplierReopenRequest- There is an open reopen request from the supplier.OpenSupplierShipmentRescheduleRequest- There is an open shipment reschedule request from the supplier.OpenBuyerReopenRequest- There is an open reopen request from the buyer.RevertedCompletedLine- The completion of this line was reverted.
The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenOptional reason for this order line event.
Example
Production schedule changed.Key line event date and times.
object
Mandatory ISO date and time, in UTC time zone, at which the order line was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001The ISO-8601 date and time in UTC time zone that denotes the latest date time the order line has been changed
Example
2021-04-23T10:01:53.812ZThe language independent Tradecloud portal URL of the order line.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10The order process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedThe order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenOptional reason for this order event.
Example
Production schedule changed.object
The goods of this order to be delivered are overdue according to the confirmed delivery schedule.
Example
trueOptional key order event date and times, on order header level. Only included on events that set one of these dates, such as OrderIssuedByBuyer, OrderLinesAcceptedBySupplier, OrderLinesConfirmedBySupplier, OrderLinesConfirmedByBuyer, OrderChangesProposalApprovedByBuyer, OrderLinesCancelledByBuyer, OrderLinesCompletedByBuyer, OrderLinesShippedByBuyer and the marked as delivered or marked as open events. Not included on events that do not set an order date, such as OrderLinesUpdatedByBuyer, OrderLinesRejectedBySupplier, OrderLinesReconfirmedBySupplier, OrderResentByBuyer and the reopen request events, including their approvals. The order line level eventDates is always included.
object
Mandatory ISO-8601 date and time in UTC time zone, at which the order was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe totalAmount and totalAmountInclRequests.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURIncludes meta information about this message.
object
Globally unique Tradecloud identifier of this message.
Includes meta information about the source of this message.
object
Globally unique Tradecloud trace identifier of this message. All related messages in a flow will have the same tradeId.
Globally unique Tradecloud user identifier which triggered the first message in a flow.
Globally unique Tradecloud company identifier which triggered the first message in a flow.
Mandatory ISO date and time, in UTC time zone, at which this message was created.
Example
2019-12-08T10:11:12.123ZThe ISO-8601 date and time in UTC time zone that denotes the latest date time the order has been changed.
Example
2021-04-23T10:01:53.812ZThe Tradecloud order version after the event. Some events, such as line updates, do not raise it, so two events can carry the same version and still differ. It does not identify a delivery; deduplicate a retry on meta.messageId.
Example
3The language independent Tradecloud portal URL of the order.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189Includes the order documents data. Only provided if eventName is one of the following:
- OrderDocumentsAttachedByBuyer
- OrderDocumentsAttachedBySupplier
object
The Tradecloud order ID
Example
eaf0036d-63ec-4292-b4ca-d65df0a912ccBuyer order data related to an OrderDocumentsEvent
object
The mandatory buyers globally unique Tradecloud company identifier
Example
00f03b98-2511-489f-9695-13791b3f66b6The purchase order number provided by the buyer. The number is unique and immutable within the buyer scope.
Example
PO123456789The order type, one of:
Purchase- This is a purchase order (default).Forecast- This is a forecast order.RFQ- This is a request for quotation order.
The mandatory supplier account code or number as known at the buyer.
Example
12345A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameSupplier order data related to an OrderDocumentsEvent
object
The mandatory suppliers globally unique Tradecloud company identifier
Example
d024bf02-7e33-427b-b4f5-a10a61761711The buyer account code or number as known at the supplier.
Example
BUYER12345A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameThe list of attached documents
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralA list of lines to which documents were attached.
Order line data related to an OrderDocumentsEvent
object
The globally unique Tradecloud order line identifier
Example
ee99cd3f-c24c-4b60-84ea-8dcf889cc37bBuyer order line data related to an OrderDocumentsEvent
object
The mandatory position in the purchase order. The position is unique and immutable within the order.
Example
00010Supplier order line data related to an OrderDocumentsEvent
object
Optional supplier sales order code or number associated with this line. The number is unique and immutable within the supplier scope.
Example
SO123456789Optional supplier sales order line position associated with this line. The position is unique and immutable within the sales order.
Example
00020Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralIncludes meta information about this message.
object
Globally unique Tradecloud identifier of this message.
Includes meta information about the source of this message.
object
Globally unique Tradecloud trace identifier of this message. All related messages in a flow will have the same tradeId.
Globally unique Tradecloud user identifier which triggered the first message in a flow.
Globally unique Tradecloud company identifier which triggered the first message in a flow.
Mandatory ISO date and time, in UTC time zone, at which this message was created.
Example
2019-12-08T10:11:12.123Zobject
The name of the event that is included in this request. For buyer/supplier it could be one one of the following:
- CompletedOrderLinesRevertedByBuyer
- OrderChangesProposalApprovedByBuyer
- OrderChangesProposalRejectedByBuyer
- OrderChangesProposedBySupplier
- OrderContactReassignedByBuyer
- OrderContactReassignedBySupplier
- OrderCustomLabelsUpdatedByBuyer
- OrderCustomLabelsUpdatedBySupplier
- OrderDocumentsAttachedByBuyer
- OrderDocumentsAttachedBySupplier
- OrderIssuedByBuyer
- OrderLinesAcceptedBySupplier
- OrderLinesCancelledByBuyer
- OrderLinesCompletedByBuyer
- OrderLinesConfirmedByBuyer
- OrderLinesConfirmedBySupplier
- OrderLinesDeliveryHistoryAppendedByBuyer
- OrderLinesDeliveryHistorySetByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedBySupplier
- OrderLinesIssuedByBuyer
- OrderLinesItemDetailsChangedBySupplier
- OrderLinesMarkedAsDeliveredByBuyer
- OrderLinesMarkedAsDeliveredBySupplier
- OrderLinesMarkedAsOpenByBuyer
- OrderLinesMarkedAsOpenBySupplier
- OrderLinesReconfirmationRequestedByBuyer
- OrderLinesReconfirmedBySupplier
- OrderLinesReissuedByBuyer
- OrderLinesRejectedBySupplier
- OrderLinesReopenRequestApprovedByBuyer
- OrderLinesReopenRequestApprovedBySupplier
- OrderLinesReopenRequestRejectedByBuyer
- OrderLinesReopenRequestRejectedBySupplier
- OrderLinesReopenRequestRevertedByBuyer
- OrderLinesReopenRequestRevertedBySupplier
- OrderLinesReopenRequestedByBuyer
- OrderLinesReopenRequestedBySupplier
- OrderLinesShipmentRescheduleApprovedByBuyer
- OrderLinesShipmentRescheduleRejectedByBuyer
- OrderLinesShipmentRescheduleRequestedBySupplier
- OrderLinesShippedByBuyer
- OrderLinesUpdatedByBuyer
- OrderLinesUpdatedBySupplier
- OrderResentByBuyer
- OrderResentBySupplier
Example
OrderLinesAcceptedBySupplierIncludes the order data. Note that if “Single delivery per order line” is enabled in the connector settings, the singleDeliveryOrderEvent is provided instead. Only provided if eventName is one of the following:
- CompletedOrderLinesRevertedByBuyer
- OrderChangesProposalApprovedByBuyer
- OrderChangesProposalRejectedByBuyer
- OrderChangesProposedBySupplier
- OrderContactReassignedByBuyer
- OrderContactReassignedBySupplier
- OrderCustomLabelsUpdatedByBuyer
- OrderCustomLabelsUpdatedBySupplier
- OrderIssuedByBuyer
- OrderLinesAcceptedBySupplier
- OrderLinesCancelledByBuyer
- OrderLinesCompletedByBuyer
- OrderLinesConfirmedByBuyer
- OrderLinesConfirmedBySupplier
- OrderLinesDeliveryHistoryAppendedByBuyer
- OrderLinesDeliveryHistorySetByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedBySupplier
- OrderLinesIssuedByBuyer
- OrderLinesItemDetailsChangedBySupplier
- OrderLinesMarkedAsDeliveredByBuyer
- OrderLinesMarkedAsDeliveredBySupplier
- OrderLinesMarkedAsOpenByBuyer
- OrderLinesMarkedAsOpenBySupplier
- OrderLinesReconfirmationRequestedByBuyer
- OrderLinesReconfirmedBySupplier
- OrderLinesReissuedByBuyer
- OrderLinesRejectedBySupplier
- OrderLinesReopenRequestApprovedByBuyer
- OrderLinesReopenRequestApprovedBySupplier
- OrderLinesReopenRequestRejectedByBuyer
- OrderLinesReopenRequestRejectedBySupplier
- OrderLinesReopenRequestRevertedByBuyer
- OrderLinesReopenRequestRevertedBySupplier
- OrderLinesReopenRequestedByBuyer
- OrderLinesReopenRequestedBySupplier
- OrderLinesShipmentRescheduleApprovedByBuyer
- OrderLinesShipmentRescheduleRejectedByBuyer
- OrderLinesShipmentRescheduleRequestedBySupplier
- OrderLinesShippedByBuyer
- OrderLinesUpdatedByBuyer
- OrderLinesUpdatedBySupplier
- OrderResentByBuyer
- OrderResentBySupplier
object
The Tradecloud order ID
Example
cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189The buyer side header of the purchase order.
object
The buyers globally unique Tradecloud company identifier
Example
deea1b30-64b6-4dbf-ad74-51895c4a7695Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsIncludes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe purchase order number provided by the buyer. The number is unique and immutable within the buyer scope.
Example
PO123456789The supplier account code or number as known at the buyer.
Example
SUPPLIER12345Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsAn optional free format order description or reference added by the buyer
Example
Any custom text about this orderIncludes location code and address.
object
Optional type of the location, eg. Supplier Premises
Example
Supplier PremisesMandatory unique and immutable destination location code or number.
Example
LOC001One or more names used to described this location. Can be the company name, location name, department, etc.
One or more address lines of this location.
The postal code of this location.
Example
1234 ABThe city of this location.
Example
DelftMandatory ISO 3166-1 alpha-2 country code of this location.
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe order terms as agreed between buyer and supplier, provided by the buyer.
object
Optional incoterms code according to ICC Incoterms 2010.
Example
CIFThe incoterms named place (delivery, terminal, port or destination).
Example
ECT RotterdamThe payment terms code as provided by the buyer.
Example
30DThe payment terms text as provided by the buyer.
Example
30 daysobject
Indicates whether the autoConfirm feature was enabled by the buyer for this order.
Key-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the buyer. \n are used for a new line.
Example
[ "Buyer note 1", "Buyer note 2"]Optional value-added services labels on order level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "first label for this buyer order", "second label for this buyer order"]The buyer contact information of an order.
object
The Tradecloud user ID of the buyer contact.
Example
1ff0bd3b-9ee1-4b04-b6d0-f34de09aafceThe email of the buyer contact.
Example
johndoe@test.comThe username of the buyer contact in the buyer ERP system.
Example
john.dThe status of this buyer contact.
The first name of the buyer contact.
Example
JohnThe last name of the buyer contact.
Example
DoeThe position of the buyer contact within the buyer company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the buyer company.
Example
+31612345678The order type, one of:
Purchase- This is a purchase order (default).Forecast- This is a forecast order.RFQ- This is a request for quotation order.
Optional custom labels on order level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockOptional ISO local date and time at which the order was originally issued in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameOptional ISO local date and time at which the order was updated in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameThe supplier side header of the purchase order.
object
The suppliers globally unique Tradecloud company identifier
Example
d024bf02-7e33-427b-b4f5-a10a61761711The buyer account code or number as known at the supplier.
Example
BUYER12345An optional free format order description or reference added by the supplier
Example
Any custom text about this supplier orderKey-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the supplier. \n are used for a new line.
Example
[ "Supplier note 1", "Supplier note 2"]Supplier contact information.
object
User ID.
Example
d024bf02-7e33-427b-b4f5-a10a61761711Email address.
Example
user@example.comUsername.
Example
userThe first name of the supplier contact.
Example
JohnThe last name of the supplier contact.
Example
DoeThe position of the supplier contact within the supplier company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the supplier company.
Example
+31612345678Optional custom labels on order level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockISO local date and time at which the order response was updated in suppliers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameList of order lines, sorted by buyerLine.position.
Includes the order line data.
object
The globally unique Tradecloud order line identifier
Example
ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010The optional order line type set by the buyer or supplier, one of:
Item- This is an item line (default).Service- This is a service line.Charge- This is a charge line.
The optional charge reason code set by the buyer or supplier, in case of a charge line.
Example
FCA buyer purchase order line contains at least the position, item and delivery schedule.
object
The mandatory position identifier in the purchase order. The position is unique and immutable within the order.
Example
00010An optional row label for this position. Do NOT use row as identifier.
Example
1An optional free format line description or reference added by the buyer.
Example
Anything about this buyer lineThe buyer item (or article, goods) to be delivered.
object
The mandatory item code or number as known by the buyer. The number is unique and immutable within the buyer scope.
Example
12345The optional revision (or version) of this item as known by the buyer.
Example
v2The mandatory short name of this item as known by the buyer.
Example
Round tube ø60x45The optionally long description of this item as known by the buyer.
Example
Very nice round tube ø60 x 45The purchase unit of measure for this item, passed through as-is to the supplier. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
PCEThe optional item code or number as known by the supplier. Advised in case of wholesale suppliers.
Example
67890Array of dimensions related to the item
Defines measurable dimensions (length, width, area, weight or volume) of an item
object
Measurement type of item
Example
LengthMeasurement value
Example
50.5The unit of measure for this dimension, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
mThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The planned delivery schedule as requested by the buyer. One or more delivery lines will be provided.
A delivery line in the delivery schedule or history.
object
The optional position in the delivery schedule or history. The position is unique and immutable within the schedule.
Example
0001The mandatory local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The mandatory quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The charge lines for this order line as known by the buyer.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe historical actual delivery schedule as goods are received at the buyer. Zero, one or more delivery lines will be provided.
A delivery line in the delivery schedule or history.
object
The optional position in the delivery schedule or history. The position is unique and immutable within the schedule.
Example
0001The mandatory local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The mandatory quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Requests by the buyer.
object
Alternative delivery schedule and prices proposed by the buyer or supplier, after the order line was confirmed.
object
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEExample
We need to reconsider this.The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedReconfirmation request as requested by the buyer.
object
The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedOrder line terms set by the buyer.
object
The contract framework code or number associated with this line. The number is unique and immutable within the buyer scope.
Example
123456789Optional position in the framework contract associated with this line. The position is unique and immutable within the contract.
Example
0001Optional buyer project code or number associated with this line.
Example
PROJ12345Optional buyer production code or number associated with this line.
Example
PROD12345Optional buyer sales order code or number associated with this line.
Example
SO123456789Order line indicators set by the buyer.
object
No goods are expected to be delivered to the buyer.
Example
trueAll goods are delivered at the buyer.
Example
trueAll goods are shipped to the buyer.
Example
trueIf set to true, when supplier confirms a line then this line becomes a proposal
Example
trueKey-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the buyer. \n are used for a new line.
Example
[ "First buyer line note", "Second buyerr line note"]Optional value-added services labels on line level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "First label for this buyer line", "Second label for this buyer line"]Order line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
General3th party certification requirements by buyer.
object
Certification Type code
Example
CHuman readable Certification Type
Example
Class CertificateClassification Society code
Example
LRHuman readable Classification Society
Example
Lloyd & Boss RegisterOptional custom labels on order line level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockA supplier side order line may contain sales order number and position and a proposal.
object
Optional supplier sales order code or number associated with this line. The number is unique and immutable within the supplier scope.
Example
SO123456789Optional supplier sales order line position associated with this line. The position is unique and immutable within the sales order.
Example
00010An optional free format line description or reference added by the supplier.
Example
Anything about this supplier lineThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The charge lines for this order line as known by the supplier.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCERequests by the supplier.
object
Alternative delivery schedule and prices proposed by the supplier.
object
The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Alternative delivery schedule proposed by the supplier.
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The charge lines for this order line as proposed by the supplier.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEOptional reason for this proposal provided by the supplier.
Example
Out of stockThe line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedAlternative delivery schedule and prices proposed by the buyer or supplier, after the order line was confirmed.
object
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEExample
We need to reconsider this.The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedShipment reschedule request as requested by the supplier.
object
Requested delivery schedule for shipment reschedule.
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Optional reason for the shipment reschedule request.
Example
Shipment needs to be rescheduled due to production delay.The line reopen request or proposal status:
- Open - Requested by either buyer or supplier. To be approved or rejected by the other party.
- Approved - The request is approved by the other party.
- Rejected - The request is rejected by the other party.
- Closed - The request is closed because it is not relevant anymore.
Example
ApprovedKey-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the supplier. \n are used for a new line.
Example
[ "First supplier line note", "Second supplier line note"]Order line document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralOptional custom labels on order line level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockThe agreed delivery schedule and prices between buyer and supplier. Available when the line has status ‘Confirmed’
object
The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The agreed delivery schedule between buyer and supplier. One or more delivery lines will be provided.
A delivery line in the proposed or confirmed delivery schedule.
object
The position of the delivery schedule line. The position is unique and immutable within the schedule. Omitted/null in case of a split delivery schedule line.
Example
0001The original position of the delivery schedule line in case of a split delivery schedule line.
Example
0001Required local delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31Required quantity of this delivery position. Quantity has a decimal format.
Example
1234.56Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The confirmed charge lines for this order line.
Deprecated: Use lineType with value ‘Charge’ and chargeReasonCode on the order line instead. The Charge Line that is included in an order line.
object
The position used to identify a Charge Line.
Example
001The reason code of this Charge Line.
Example
FCThe description of this Charge Line.
Example
Additional coatingThe quantity ordered of this Charge Line
Example
2A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEAggregated delivery schedule with logistics info
An aggregated delivery schedule line with logistics info
object
The optional position in the delivery schedule.
Example
01The optional scheduled delivery local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery line. Quantity has a decimal format.
Example
1234.56The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
Openobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe mode of transportation
Example
TrainThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31Aggregated delivery schedule with logistics info and merged with requests
An aggregated delivery schedule line with logistics info
object
The optional position in the delivery schedule.
Example
01The optional scheduled delivery local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery line. Quantity has a decimal format.
Example
1234.56The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
Openobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe mode of transportation
Example
TrainThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31Information about the shipment lines that were created in the shipment module for this order line.
Information about a shipment line that was created in the shipment module for an order line.
object
The Tradecloud ID of the shipment in which the shipmentLine was included.
Example
0827f1b5-af43-4fbb-8f7e-6bc20c7dcd44-S12345The shipment number of the shipment in which the shipmentLine was included.
Example
S12345The position in the deliverySchedule that this shipmentLine applies to.
Example
D01The quantity that was dispatched.
Example
15.5The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100object
The goods of this line to be delivered are overdue according to the confirmed delivery schedule.
Example
trueKey line event date and times.
object
Mandatory ISO date and time, in UTC time zone, at which the order line was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe line process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedMore fine-grained status when an order line has processStatus InProgress, explaining why it is in progress:
OpenSupplierProposal- There is an open proposal from the supplier.RejectedSupplierProposal- The proposal from the supplier was rejected and no other requests are open.ApprovedDeliverySchedule- The order line delivery schedule was approved by the buyer.RejectedDeliverySchedule- The order line delivery schedule was rejected by the buyer.ReissuedRejectedLine- The rejected order line was reissued by the buyer.OpenBuyerReconfirmationRequest- The buyer has requested to reconfirmed the order line.OpenSupplierReopenRequest- There is an open reopen request from the supplier.OpenSupplierShipmentRescheduleRequest- There is an open shipment reschedule request from the supplier.OpenBuyerReopenRequest- There is an open reopen request from the buyer.RevertedCompletedLine- The completion of this line was reverted.
The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe ISO-8601 date and time in UTC time zone that denotes the latest date time the order line has been changed
Example
2021-04-23T10:01:53.812ZOptional reason for this order line event.
Example
Production schedule changed.The language independent Tradecloud portal URL of the order line.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10The order process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedThe order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenOptional reason for this order event.
Example
Production schedule changed.object
The goods of this order to be delivered are overdue according to the confirmed delivery schedule.
Example
trueOptional key order event date and times, on order header level. Only included on events that set one of these dates, such as OrderIssuedByBuyer, OrderLinesAcceptedBySupplier, OrderLinesConfirmedBySupplier, OrderLinesConfirmedByBuyer, OrderChangesProposalApprovedByBuyer, OrderLinesCancelledByBuyer, OrderLinesCompletedByBuyer, OrderLinesShippedByBuyer and the marked as delivered or marked as open events. Not included on events that do not set an order date, such as OrderLinesUpdatedByBuyer, OrderLinesRejectedBySupplier, OrderLinesReconfirmedBySupplier, OrderResentByBuyer and the reopen request events, including their approvals. The order line level eventDates is always included.
object
Mandatory ISO-8601 date and time in UTC time zone, at which the order was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe totalAmount and totalAmountInclRequests.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURIncludes meta information about this message.
object
Globally unique Tradecloud identifier of this message.
Includes meta information about the source of this message.
object
Globally unique Tradecloud trace identifier of this message. All related messages in a flow will have the same tradeId.
Globally unique Tradecloud user identifier which triggered the first message in a flow.
Globally unique Tradecloud company identifier which triggered the first message in a flow.
Mandatory ISO date and time, in UTC time zone, at which this message was created.
Example
2019-12-08T10:11:12.123ZThe ISO-8601 date and time in UTC time zone that denotes the latest date time the order has been changed.
Example
2021-04-23T10:01:53.812ZThe Tradecloud order version after the event. Some events, such as line updates, do not raise it, so two events can carry the same version and still differ. It does not identify a delivery; deduplicate a retry on meta.messageId.
Example
3The language independent Tradecloud portal URL of the order.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189Includes the order data, only if “Single delivery per order line” is enabled in the company’s connector settings. Only provided if eventName is one of the following:
- CompletedOrderLinesRevertedByBuyer
- OrderChangesProposalApprovedByBuyer
- OrderChangesProposalRejectedByBuyer
- OrderChangesProposedBySupplier
- OrderContactReassignedByBuyer
- OrderContactReassignedBySupplier
- OrderCustomLabelsUpdatedByBuyer
- OrderCustomLabelsUpdatedBySupplier
- OrderIssuedByBuyer
- OrderLinesAcceptedBySupplier
- OrderLinesCancelledByBuyer
- OrderLinesCompletedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedByBuyer
- OrderLinesDeliveryScheduleLogisticsUpdatedBySupplier
- OrderLinesIssuedByBuyer
- OrderLinesItemDetailsChangedBySupplier
- OrderLinesMarkedAsDeliveredByBuyer
- OrderLinesMarkedAsDeliveredBySupplier
- OrderLinesMarkedAsOpenByBuyer
- OrderLinesMarkedAsOpenBySupplier
- OrderLinesReconfirmationRequestedByBuyer
- OrderLinesReconfirmedBySupplier
- OrderLinesReissuedByBuyer
- OrderLinesRejectedBySupplier
- OrderLinesReopenRequestApprovedByBuyer
- OrderLinesReopenRequestApprovedBySupplier
- OrderLinesReopenRequestRejectedByBuyer
- OrderLinesReopenRequestRejectedBySupplier
- OrderLinesReopenRequestRevertedByBuyer
- OrderLinesReopenRequestRevertedBySupplier
- OrderLinesReopenRequestedByBuyer
- OrderLinesReopenRequestedBySupplier
- OrderLinesShipmentRescheduleApprovedByBuyer
- OrderLinesShipmentRescheduleRejectedByBuyer
- OrderLinesShipmentRescheduleRequestedBySupplier
- OrderLinesShippedByBuyer
- OrderLinesUpdatedByBuyer
- OrderLinesUpdatedBySupplier
- OrderResentByBuyer
- OrderResentBySupplier
object
The Tradecloud order ID
Example
eaf0036d-63ec-4292-b4ca-d65df0a912ccThe buyer side header of the purchase order.
object
The buyers globally unique Tradecloud company identifier
Example
deea1b30-64b6-4dbf-ad74-51895c4a7695Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsIncludes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe purchase order number provided by the buyer. The number is unique and immutable within the buyer scope.
Example
PO123456789The supplier account code or number as known at the buyer.
Example
SUPPLIER12345Includes an unique party identifier and scheme. Without idSchema an accountNumber is assumed.
object
The identifier for the party
Example
COMPANY-123The scheme, providing context to the identifier. Eg. KvK, GLN, etc.
Example
KvKThe names of this company
Example
[ "Blue Corp.", "Ocean District"]The address lines where this company is located.
Example
[ "Main street 1", "Building 6"]The postal code of this company
Example
1234 ABThe city where this company is located
Example
DelftISO 3166-1 alpha-2 country code of this company
Example
NLOptional country name, preferable in English.
Example
The NetherlandsAn optional free format order description or reference added by the buyer
Example
Any custom text about this orderIncludes location code and address.
object
Optional type of the location, eg. Supplier Premises
Example
Supplier PremisesMandatory unique and immutable destination location code or number.
Example
LOC001One or more names used to described this location. Can be the company name, location name, department, etc.
One or more address lines of this location.
The postal code of this location.
Example
1234 ABThe city of this location.
Example
DelftMandatory ISO 3166-1 alpha-2 country code of this location.
Example
NLOptional country name, preferable in English.
Example
The NetherlandsThe order terms as agreed between buyer and supplier, provided by the buyer.
object
Optional incoterms code according to ICC Incoterms 2010.
Example
CIFThe incoterms named place (delivery, terminal, port or destination).
Example
ECT RotterdamThe payment terms code as provided by the buyer.
Example
30DThe payment terms text as provided by the buyer.
Example
30 daysobject
Indicates whether the autoConfirm feature was enabled by the buyer for this order.
Key-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the buyer. \n are used for a new line.
Example
[ "Buyer note 1", "Buyer note 2"]Optional value-added services labels on order level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "first label for this buyer order", "second label for this buyer order"]The buyer contact information of an order.
object
The Tradecloud user ID of the buyer contact.
Example
1ff0bd3b-9ee1-4b04-b6d0-f34de09aafceThe email of the buyer contact.
Example
johndoe@test.comThe username of the buyer contact in the buyer ERP system.
Example
john.dThe status of this buyer contact.
The first name of the buyer contact.
Example
JohnThe last name of the buyer contact.
Example
DoeThe position of the buyer contact within the buyer company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the buyer company.
Example
+31612345678The order type, one of:
Purchase- This is a purchase order (default).Forecast- This is a forecast order.RFQ- This is a request for quotation order.
Optional custom labels on order level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockOptional ISO local date and time at which the order was originally issued in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameOptional ISO local date and time at which the order was updated in the buyers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameThe supplier side header of the purchase order.
object
The suppliers globally unique Tradecloud company identifier
Example
d024bf02-7e33-427b-b4f5-a10a61761711The buyer account code or number as known at the supplier.
Example
BUYER12345An optional free format order description or reference added by the supplier
Example
Any custom text about this supplier orderKey-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redOrder document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralString based custom fields added by the supplier. \n are used for a new line.
Example
[ "Supplier note 1", "Supplier note 2"]Supplier contact information.
object
User ID.
Example
d024bf02-7e33-427b-b4f5-a10a61761711Email address.
Example
user@example.comUsername.
Example
userThe first name of the supplier contact.
Example
JohnThe last name of the supplier contact.
Example
DoeThe position of the supplier contact within the supplier company.
Example
Supply Chain ManagerThe phone number of the buyer contact within the supplier company.
Example
+31612345678Optional custom labels on order level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockISO local date and time at which the order response was updated in suppliers ERP system.
Example
2019-12-31T10:11:12A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameList of order lines, sorted by buyerLine.position.
Includes the order line data for a particular scheduledDelivery
object
The globally unique Tradecloud order line identifier
Example
ee99cd3f-c24c-4b60-84ea-8dcf889cc37b-PO012345789-00010The optional order line type set by the buyer or supplier, one of:
Item- This is an item line (default).Service- This is a service line.Charge- This is a charge line.
The optional charge reason code set by the buyer or supplier, in case of a charge line.
Example
FCA buyer purchase order line for a particular single delivery order line.
object
The position identifier in the purchase order. The position is unique and immutable within the order. Position is empty in case of a newly created or split line by the supplier.
Example
00010The original position in case this is a split line.
Example
00010An optional row label for this position. Do NOT use row as identifier.
Example
1An optional free format line description or reference added by the buyer.
Example
Anything about this lineThe buyer item (or article, goods) to be delivered.
object
The mandatory item code or number as known by the buyer. The number is unique and immutable within the buyer scope.
Example
12345The optional revision (or version) of this item as known by the buyer.
Example
v2The mandatory short name of this item as known by the buyer.
Example
Round tube ø60x45The optionally long description of this item as known by the buyer.
Example
Very nice round tube ø60 x 45The purchase unit of measure for this item, passed through as-is to the supplier. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
PCEThe optional item code or number as known by the supplier. Advised in case of wholesale suppliers.
Example
67890Array of dimensions related to the item
Defines measurable dimensions (length, width, area, weight or volume) of an item
object
Measurement type of item
Example
LengthMeasurement value
Example
50.5The unit of measure for this dimension, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
mThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100Order line terms set by the buyer.
object
The contract framework code or number associated with this line. The number is unique and immutable within the buyer scope.
Example
123456789Optional position in the framework contract associated with this line. The position is unique and immutable within the contract.
Example
0001Optional buyer project code or number associated with this line.
Example
PROJ12345Optional buyer production code or number associated with this line.
Example
PROD12345Optional buyer sales order code or number associated with this line.
Example
SO123456789Order line indicators set by the buyer.
object
No goods are expected to be delivered to the buyer.
Example
trueAll goods are delivered at the buyer.
Example
trueAll goods are shipped to the buyer.
Example
trueIf set to true, when supplier confirms a line then this line becomes a proposal
Example
trueKey-value based custom fields added by the buyer.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the buyer. \n are used for a new line.
Optional value-added services labels on line level. Please note the practicable number of labels is dependent on the supplier.
Example
[ "first label for this line", "second label for this line"]Order line document references and meta data added by the buyer
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
General3th party certification requirements by buyer.
object
Certification Type code
Example
CHuman readable Certification Type
Example
Class CertificateClassification Society code
Example
LRHuman readable Classification Society
Example
Lloyd & Boss RegisterOptional custom labels on order line level added by buyer, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockA supplier side order line may contain sales order number and position.
object
Optional supplier sales order code or number associated with this line. The number is unique and immutable within the supplier scope.
Example
SO123456789Optional supplier sales order line position associated with this line. The position is unique and immutable within the sales order.
Example
00010An optional free format line description or reference added by the supplier.
Example
Anything about this lineThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001Key-value based custom fields added by the supplier.
A key-value based custom field.
object
The key of the custom field.
Example
colorThe value of the custom field. Use \n for a new line.
Example
redString based custom fields added by the supplier. \n are used for a new line.
Order line document references and meta data added by the supplier
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralOptional custom labels on order line level added by supplier, to make supply or quality issues visible.
Custom label to make supply or quality issues visible.
object
Free format label text.
Example
UrgentFree format label reason.
Example
Out of stockThe order line values representing the current Issued or Confirmed status. The InclRequests fields include the InProgress status and open buyer or supplier request values.
object
The scheduled delivery line. This field is used as an alternative for the deliverySchedule field if your ERP system does not support a deliverySchedule within an order line natively and the delivery schedule is spread over multiple order lines instead. If you have One single delivery per order line enabled in your Order Webhook Connector settings, Tradecloud will transform the deliverySchedule into multiple order lines each containing a scheduledDelivery; one order line per delivery schedule line.
object
The optional scheduled delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The delivery schedule line logistics status according to your ERP system:
ReadyToShip- All goods of this delivery line are ready to be shipped by the supplier.Shipped- All goods of this delivery line are shipped by the supplier.Delivered- All goods of this delivery line are delivered at the buyer.
Example
ReadyToShipobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe Mode of Transport used for the delivery of goods. UNECE.org Recommendation 19 is advised for Mode of Transport values.
Example
Road transportThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The scheduled delivery line. This field is used as an alternative for the deliverySchedule field if your ERP system does not support a deliverySchedule within an order line natively and the delivery schedule is spread over multiple order lines instead. If you have One single delivery per order line enabled in your Order Webhook Connector settings, Tradecloud will transform the deliverySchedule into multiple order lines each containing a scheduledDelivery; one order line per delivery schedule line.
object
The optional scheduled delivery date of this delivery position. Date has ISO 8601 date format.
Example
2019-12-31The optional scheduled quantity of this delivery position. Quantity has a decimal format.
Example
1234.56The delivery schedule line logistics status according to your ERP system:
ReadyToShip- All goods of this delivery line are ready to be shipped by the supplier.Shipped- All goods of this delivery line are shipped by the supplier.Delivered- All goods of this delivery line are delivered at the buyer.
Example
ReadyToShipobject
True if this delivery line is not Delivered yet and its date is in the past.
Example
falseThe Mode of Transport used for the delivery of goods. UNECE.org Recommendation 19 is advised for Mode of Transport values.
Example
Road transportThe optional logistics Estimated Time of Departure local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The optional logistics Estimated Time of Arrival local date (without time zone) of this delivery line. Date has ISO 8601 date format.
Example
2019-12-31The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The gross price, discount percentage and net price. Advised is to use net price only or alternatively gross price together with discount percentage.
object
A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe discount percentage. Use together with grossPrice.
Example
50A price in the transaction currency, like CNY and, if available, a price in your base currency, like EUR in the EU.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURThe price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation N°20 is recommended if you want a standard. The purchase unit and price unit may be different.
Example
PCEThe item quantity at which the price applies. Typically this is 1 (unit price) or 100 (the price applies to 100 items).
Example
100The total scheduled quantity in the order line delivery schedule. Quantity has a decimal format.
Example
1234.56The total scheduled quantity in the order line delivery schedule including all requests.
Example
1234.56Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURobject
The goods of this line to be delivered are overdue according to the confirmed delivery schedule.
Example
trueThe line process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedMore fine-grained status when an order line has processStatus InProgress, explaining why it is in progress:
OpenSupplierProposal- There is an open proposal from the supplier.RejectedSupplierProposal- The proposal from the supplier was rejected and no other requests are open.ApprovedDeliverySchedule- The order line delivery schedule was approved by the buyer.RejectedDeliverySchedule- The order line delivery schedule was rejected by the buyer.ReissuedRejectedLine- The rejected order line was reissued by the buyer.OpenBuyerReconfirmationRequest- The buyer has requested to reconfirmed the order line.OpenSupplierReopenRequest- There is an open reopen request from the supplier.OpenSupplierShipmentRescheduleRequest- There is an open shipment reschedule request from the supplier.OpenBuyerReopenRequest- There is an open reopen request from the buyer.RevertedCompletedLine- The completion of this line was reverted.
The order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenOptional reason for this order line event.
Example
Production schedule changed.Key line event date and times.
object
Mandatory ISO date and time, in UTC time zone, at which the order line was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO date and time, in UTC time zone, at which the order line became completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe buyer may send item details to inform the supplier about part information. The supplier may check, change and add item details if they are not correct or incomplete.
object
The country of manufacture, production, or growth where an article or product comes from
Example
NLA tool for classifying goods, set up to meet the requirements both of the Common Customs Tariff and of the EU’s external trade statistics
Example
6406 10 10Net weight of one item
Example
41.241The net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation N°20 (Codes for Units of Measure) is recommended if you want a standard.
Example
KGUN numbers or UN IDs are four-digit numbers that identify dangerous goods, hazardous substances and articles in the framework of international transport.
Example
0060Unique identifier assigned incrementally or sequentially to an item, to uniquely identify it
Example
0x0000000000028000Identification number assigned to a particular quantity or lot of material from a single manufacturer
Example
#18001The ISO-8601 date and time in UTC time zone that denotes the latest date time the order line has been changed
Example
2021-04-23T10:01:53.812ZThe language independent Tradecloud portal URL of the order line.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189/line/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189-10The order process status and logistics status.
object
The order or line process status:
Issued- (Re)issued by the buyerInProgress- Under negotiation between buyer and supplierConfirmed- Agreed between buyer and supplierRejected- Rejected by supplierCompleted- Completed at the buyerCancelled- Cancelled by buyer
Example
IssuedThe order, line or delivery line logistics status:
Open- No or partial quantity Produced, ReadyToShip, Shipped or DeliveredProduced- Full quantity produced by the supplierReadyToShip- Full quantity ready to be shipped by the supplierShipped- Full quantity shipped by the supplierDelivered- Full quantity delivered at the buyerCancelled- Cancelled by buyer
Example
OpenOptional reason for this order event.
Example
Production schedule changed.object
The goods of this order to be delivered are overdue according to the confirmed delivery schedule.
Example
trueOptional key order event date and times, on order header level. Only included on events that set one of these dates, such as OrderIssuedByBuyer, OrderLinesAcceptedBySupplier, OrderLinesConfirmedBySupplier, OrderLinesConfirmedByBuyer, OrderChangesProposalApprovedByBuyer, OrderLinesCancelledByBuyer, OrderLinesCompletedByBuyer, OrderLinesShippedByBuyer and the marked as delivered or marked as open events. Not included on events that do not set an order date, such as OrderLinesUpdatedByBuyer, OrderLinesRejectedBySupplier, OrderLinesReconfirmedBySupplier, OrderResentByBuyer and the reopen request events, including their approvals. The order line level eventDates is always included.
object
Mandatory ISO-8601 date and time in UTC time zone, at which the order was issued in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely confirmed in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely shipped in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely delivered in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely cancelled in Tradecloud.
Example
2019-12-31T10:11:12.123ZOptional ISO-8601 date and time in UTC time zone, at which the order became completely completed in Tradecloud.
Example
2019-12-31T10:11:12.123ZThe totalAmount and totalAmountInclRequests.
object
Mandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURMandatory price value and currency fields.
object
Mandatory price value has a decimal format. Typically a precision from 2 to 5 decimal digits is used, also depending on the purchase unit quantity.
Example
1234.56Mandatory 3-letter currency code according to ISO 4217.
Example
EURIncludes meta information about this message.
object
Globally unique Tradecloud identifier of this message.
Includes meta information about the source of this message.
object
Globally unique Tradecloud trace identifier of this message. All related messages in a flow will have the same tradeId.
Globally unique Tradecloud user identifier which triggered the first message in a flow.
Globally unique Tradecloud company identifier which triggered the first message in a flow.
Mandatory ISO date and time, in UTC time zone, at which this message was created.
Example
2019-12-08T10:11:12.123ZThe ISO-8601 date and time in UTC time zone that denotes the latest date time the order has been changed.
Example
2021-04-23T10:01:53.812ZThe Tradecloud order version after the event. Some events, such as line updates, do not raise it, so two events can carry the same version and still differ. It does not identify a delivery; deduplicate a retry on meta.messageId.
Example
3The language independent Tradecloud portal URL of the order.
Example
https://portal.accp.tradecloud1.com/orders/cb0cef0b-6538-4828-b45e-5ad8ea69b5cd-PO2189Includes the order documents data. Only provided if eventName is one of the following:
- OrderDocumentsAttachedByBuyer
- OrderDocumentsAttachedBySupplier
object
The Tradecloud order ID
Example
eaf0036d-63ec-4292-b4ca-d65df0a912ccBuyer order data related to an OrderDocumentsEvent
object
The mandatory buyers globally unique Tradecloud company identifier
Example
00f03b98-2511-489f-9695-13791b3f66b6The purchase order number provided by the buyer. The number is unique and immutable within the buyer scope.
Example
PO123456789The order type, one of:
Purchase- This is a purchase order (default).Forecast- This is a forecast order.RFQ- This is a request for quotation order.
The mandatory supplier account code or number as known at the buyer.
Example
12345A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameSupplier order data related to an OrderDocumentsEvent
object
The mandatory suppliers globally unique Tradecloud company identifier
Example
d024bf02-7e33-427b-b4f5-a10a61761711The buyer account code or number as known at the supplier.
Example
BUYER12345A buyer or supplier contact.
object
Optional globally unique Tradecloud user identifier.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional contact email as known in your ERP system.
Example
contact@yourcompany.comOptional contact username as known in your ERP system.
Example
usernameThe list of attached documents
Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralA list of lines to which documents were attached.
Order line data related to an OrderDocumentsEvent
object
The globally unique Tradecloud order line identifier
Example
ee99cd3f-c24c-4b60-84ea-8dcf889cc37bBuyer order line data related to an OrderDocumentsEvent
object
The mandatory position in the purchase order. The position is unique and immutable within the order.
Example
00010Supplier order line data related to an OrderDocumentsEvent
object
Optional supplier sales order code or number associated with this line. The number is unique and immutable within the supplier scope.
Example
SO123456789Optional supplier sales order line position associated with this line. The position is unique and immutable within the sales order.
Example
00020Either use objectId and the Tradecloud object-storage API or url to download the document.
object
Optional document code or number. The code is unique and immutable within a company.
Example
123456789Optional document revision (or version) code or number
Example
BOptional document short name
Example
Tradecloud API ManualThe globally unique Tradecloud object identifier as known by the Tradecloud Object Storage, if this document stored in Tradecloud.
Example
00f03b98-2511-489f-9695-13791b3f66b6Optional location of the document if is not stored in Tradecloud.
Example
https://my-company.com/storage/my_file.pdfOptional description of the attached document.
Example
General documentOptional type of the attached document. Eg. General, Class Product Certificate, Manual, Packing Instructions, etc…
Example
GeneralIncludes meta information about this message.
object
Globally unique Tradecloud identifier of this message.
Includes meta information about the source of this message.
object
Globally unique Tradecloud trace identifier of this message. All related messages in a flow will have the same tradeId.
Globally unique Tradecloud user identifier which triggered the first message in a flow.
Globally unique Tradecloud company identifier which triggered the first message in a flow.
Mandatory ISO date and time, in UTC time zone, at which this message was created.
Example
2019-12-08T10:11:12.123ZResponses
Section titled “Responses”Success
Bad Request. Tradecloud will retry sending the request.
Internal Server Error. Tradecloud will retry sending the request.
