Send order response

As a supplier, you can send a purchase order response to your buyer.

Order process

As a supplier, you have three possible ways to respond to an order:

Detailed response: Send an order response with lines containing their position, confirmed delivery schedule, and prices
Line-level acceptance: Send an order response with lines containing their position and line-level accept or reject indicators
Header-level acceptance: Send an order response with header-level accept or reject indicators, and lines containing only their positions

After sending an order response, the order line process status may change based on the current status:

The order line will become:

Confirmed if:
- The accepted indicator is set, OR
- Responded delivery schedule and prices match the requested values
Rejected if the rejected indicator is set
InProgress if responded values differ from requested values (creates a proposal task for the buyer)

The order line will become:

Confirmed if:
- The accepted indicator is set, OR
- Responded delivery schedule and prices match the requested values, OR
- The line has an open supplier reopen request and responded values match the confirmed values again (reverts the reopen) – see Revert a reopen request
Rejected if the rejected indicator is set
Stays InProgress if responded values still differ from requested values

The order line will:

Become InProgress if responded values differ from confirmed values (creates a reopen request task for the buyer)
Stay Confirmed if responded values match the confirmed values

The process status will not change.

Use the Send order response endpoint to send an order response to Tradecloud.

HTTP status code 200 or 202 means the order response was successfully verified or queued.

Processing typically takes less than a second, after which:

buyerAccountNumber: your buyer’s account number as known in your ERP system
- Must be set in the Tradecloud portal after the connection is accepted
- Must be unique within your company
purchaseOrderNumber: the purchase order number sent by the buyer
lines: Each order response must contain one or more lines

companyId: Tradecloud company identifier
- Only needed if your integration user has multiple company authorizations
contact.email: email of the supplier employee responsible for this order
- The user must be active in Tradecloud
description: additional description of this order
indicators.accepted: accept all lines in this response as-is.
- Order lines with positions are required.
- Delivery schedule and prices will be ignored for these lines
- Line-level indicators override this header indicator when present
indicators.rejected: reject all lines in this response
- Order lines with positions are required.
- Delivery schedule and prices will be ignored for these lines
- Line-level indicators override this header indicator when present
properties: key-value custom fields
- use \n for new lines
notes: simple text notes
- use \n for new lines

At least one delivery schedule line is required:

position: optional position in the delivery schedule
- Echo the position from the buyer, OR leave empty
- For new split delivery lines:
  - Leave the position empty - the buyer will assign it
  - Append new delivery lines at the end
  - Provide a reason
date: delivery date in ISO 8601 format (yyyy-MM-dd)
- Can be left empty if unknown
- Provide a reason if different from the requested date
quantity: delivery quantity in decimal format (e.g., 1234.56)
- Can be left empty if unknown
- Provide a reason if different from the requested quantity

Recommended: Use netPrice for simplicity, or use grossPrice + discountPercentage.

netPrice OR grossPrice + discountPercentage:
- priceInTransactionCurrency: required
  - value: decimal format (e.g., 1234.56)
  - currencyIso: 3-letter ISO 4217 code (e.g., EUR, USD, CNY)
- priceInBaseCurrency: optional
  - value: decimal format (e.g., 1234.56)
  - currencyIso: 3-letter ISO 4217 code
priceUnitOfMeasureIso: price unit of measure, passed through as-is. No standard is enforced; UN/ECE Recommendation No. 20 is recommended if you want a standard
- Copied from buyer if empty
priceUnitQuantity: quantity at which price applies (typically 1 or 100)
- Copied from buyer if empty

description: additional description of this line
indicators.accepted: accept the line as-is
- Delivery schedule, prices, and header indicators are ignored
indicators.rejected: reject the line
- Delivery schedule, prices, and header indicators are ignored
reason: explanation when:
- The line is rejected
- Responded values differ from requested or confirmed values
- Splitting in the delivery schedule
properties: key-value custom fields
- use \n for new lines
notes: simple text notes
- use \n for new lines

You can check, change, or add item details if the buyer’s information is incorrect or incomplete:

countryOfOriginCodeIso2: ISO 3166-1 alpha-2 country code of origin
combinedNomenclatureCode: goods classification code for customs and trade statistics
netWeight: net weight of one item
netWeightUnitOfMeasureIso: net weight unit of measure, passed through as-is. Mandatory when netWeight is provided. No standard is enforced; UN/ECE Recommendation No. 20 is recommended if you want a standard
dangerousGoodsCodeUnece: UN number for dangerous goods (4-digit)
serialNumber: unique sequential identifier for the item
batchNumber: identification number for a quantity/lot from a manufacturer

erpResponseDateTime: date/time the order was responded in your ERP (ISO 8601 format: yyyy-MM-ddTHH:mm:ss)
erpRespondedBy: email or username of the person who responded to this order in your ERP