Description
Preserve a supplied field verbatim while checking numeric fixed width and counting its leading zeros.
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.
Preserve a supplied field verbatim while checking numeric fixed width and counting its leading zeros.
When to use this tool
Use GS1 AI Fixed Field Leading Zero Preserver 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 field, width. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, preserved, leadingZeros. Inspect valid before interpreting the associated values.
Require width from one through 128. Return valid for an exactly width-sized nonempty digit field, preserved as the original text, and leadingZeros as its initial-zero count.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| field | Field | Required. Text; maximum UTF-16 length 8192. |
| width | Width | Required. Safe integer; minimum 1; maximum 128. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
| preserved | Preserved | Required. Text; maximum UTF-16 length 8192. |
| leadingZeros | Leading Zeros | Required. Safe integer. |
{
"input": {
"field": "000123",
"width": 6
},
"output": {
"valid": true,
"preserved": "000123",
"leadingZeros": 3
}
}Limitations and assumptions
- Preserved is returned even when valid is false; no cleanup, truncation, or padding occurs. The width is supplied, without application-identifier lookup or semantic and checksum validation.
- 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
- GS1 AI Date Day Zero Policy
Validate a supplied-century YYMMDD token and optionally interpret day 00 as the final day of its month.
- GS1 AI Fixed Length Padding Check
Check a digit field's supplied fixed length and report any missing character count without padding it.