# `UpcA`

A GTIN-12, the universal product code (GS1), its check digit passing and its leading zero kept: `036000291452`.

[Commerce and logistics](types.md#commerce-and-logistics); not ordered; since Jadpo 0.1.0.

## Make one

Build one from its text, `UpcA("036000291452")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: UpcA)` reads one from its text; text that isn't one at all fails `malformed`, such as `036000291453`, `36000291452` or `4006381333931`.

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `036000291452` | `"036000291452"` |
| `614141000036` | `"614141000036"` |

It is stored in one column named for the field, of type `text`. `614141000036` is stored as `'614141000036'`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `036000291452` | `036000291452` |
| `614141000036` | `614141000036` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It isn't ordered, so `<` and sorting don't take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.