The commissioning decision
A repair studio receives reference 00218 but the follow-up spreadsheet shows 218. Commission the enquiry field as an identifier from input through delivery, rather than fixing its appearance with padding after information has already been lost. Agree whether letters, spaces and leading zeroes are meaningful before choosing a field type.
Source and claim boundary
MDN distinguishes incrementable quantities from digit-only identifiers and recommends a text input where number semantics do not apply. A numeric keyboard hint is separate from preserving a string. MDN · Checked 16 October 2026.
Filled synthetic acceptance cases
Synthetic teaching data, not client records. Review the inputs and expected outcomes before running the isolated browser exercise. On narrow screens, scroll the table.
| Input | Check | Expected |
|---|---|---|
| 00218 → text field | FormData reference | 00218, unchanged |
| 218 → text field | Different original identifier | 218; do not invent zeroes |
| A-0218 → text field | Agreed alphanumeric format | A-0218, unchanged |
How to verify beyond appearance
- Agree the identifier grammar with the receiving team; do not use a real customer record.
- Run the reference case in the browser fixture and inspect the submitted string.
- Compare that value with the receiving test record and exported cell, without numeric conversion.
Interpret the result
The fixture proves browser-side string retention only. In the handover, retain the original input, request field and final test record as three separate observations. A spreadsheet that displays 00218 using a number format is not proof that the original identifier survived. Treat 00218 and 218 as different until the business owner explicitly defines otherwise.
What this does not prove
No payment-card collection, identity verification or production CRM test is provided. Actual mobile keyboards and downstream spreadsheet imports still need device and integration checks.
Runnable fixture and handover record
Open the browser acceptance fixture · Read the test source。The fixture creates temporary elements with synthetic values inside the browser. It reads no account, uploads no file, and sends no email or form. Record the browser version, check name, observed value and pass state. Keep real integration evidence separate: a local pass is not a live delivery result.