Description
Record explicitly supplied shipment notify-party and consignee roles as distinct ordered fields.
Cross-border business records combine named parties, contract versions, currencies, fees, shipment terms and local-time transcriptions. A supplied rate direction or fee currency determines arithmetic, while an authentic-language or trade-rule label remains a record assertion. Local calculations do not establish actual settlement or governing obligations.
Record explicitly supplied shipment notify-party and consignee roles as distinct ordered fields.
When to use this tool
Use Shipment Notify Consignee Role Pair when you already have shipmentId, notifyPartyId, consigneeId and need to record explicitly supplied shipment notify-party and consignee roles as distinct ordered fields.
How to use the tool and how it works
- Enter shipmentId, notifyPartyId, consigneeId. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter shipmentId, notifyPartyId, consigneeId using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| shipmentId | Shipment Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| notifyPartyId | Notify Party Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| consigneeId | Consignee Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"shipmentId": "S17",
"notifyPartyId": "N4",
"consigneeId": "C2"
},
"output": {
"token": "[\"S17\",\"N4\",\"C2\"]"
}
}Limitations and assumptions
- The result records supplied values without identity inference. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Review the original agreement, invoice, shipment and payment records with their stated editions and currency bases. Use complete contractual and valuation rules for actual obligations; supplied shares, labels and conversions are auditable components of that review.
References
Similar or alternative tools
- Trade Invoice Country Currency Pair
Record explicit invoice country and currency codes.
- Shipment Document Reference Token
Associate an explicitly identified shipment document with its shipment.