# `Sscc`

A serial shipping container code (GS1), 18 digits, its check digit passing: `106141412345678908`.

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

## Make one

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

`text.parse(raw, as: Sscc)` reads one from its text; text that isn't one at all fails `malformed`, such as `106141412345678909`, `10614141234567890` or `(00)106141412345678908`.

## 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 |
|---|---|
| `106141412345678908` | `"106141412345678908"` |
| `350123450000000016` | `"350123450000000016"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `106141412345678908` | `106141412345678908` |
| `350123450000000016` | `350123450000000016` |

## 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.