Description
Compare a shaped container code's equipment-category character with a supplied category.
Identifier validation can involve several distinct questions: whether text has the expected shape, whether a checksum is consistent, and whether an authority actually assigned the identifier. Formatting and field extraction address narrower questions. Each result must be read according to the particular property the tool checks.
Compare a shaped container code's equipment-category character with a supplied category.
When to use this tool
Use ISO 6346 Equipment Category Source Match when you need the particular shape, formatting, field, or checksum property as one explicit stage in an identifier workflow.
How to use the tool and how it works
- Enter code, expectedCategory. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read matches, category. Inspect matches before interpreting the associated values.
Require the implemented uppercase container-code shape and expectedCategory U, J, or Z. Return the code's category and whether it equals the expected category.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| code | Code | Required. Text; maximum UTF-16 length 8192. |
| expectedCategory | Expected Category | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| matches | Whether the supplied values match under the particular stated rule. | Required. Boolean. |
| category | Category | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"code": "CSQU3054383",
"expectedCategory": "U"
},
"output": {
"matches": true,
"category": "U"
}
}Limitations and assumptions
- The expected category is supplied rather than inferred from equipment. The tool does not validate the checksum, owner registration, physical equipment, or a complete logistics record.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete format and checksum validator when required, then consult the issuing registry or verification process for assignment and identity. Preserve meaningful leading zeros as text.
References
Similar or alternative tools
- Validation: Iso6346 Category Character Check
Inspect one ISO6346 equipment-category letter U/J/Z, not an owner code, check digit or operational container certification.
- LEI Country Code Source Match
Compare a supplied LEI record country with supplied reference metadata; no country is decoded from the LEI itself.