Timezone and Distance Units
Understand the market-owned timezone and distance-unit context used by AutoCore.
Timezone and distance units are explicit market context. The current installation
and edition models support a timezone and a distance unit (km or mi); the
edition also carries related presentation units such as speed and volume where
the product surface needs them.
Why this is a domain concern
Listing mileage is stored as mileageKm in the current schema, while display and
input conventions can use the configured market unit. Timestamps such as
publication, reservation, expiry, acceptance, and payment events need a stable
timezone interpretation when presented to people. A unit label must not silently
change the stored meaning of a record.
| Setting | Belongs to | Documentation rule |
|---|---|---|
| Timezone | Primary market and edition defaults | Explain local display context; do not imply a universal server timezone. |
| Distance unit | Installation/market configuration | Make conversion visible and preserve canonical storage semantics. |
| Speed, volume, power | Edition/market presentation defaults | Treat as formatting context unless a source-backed validation rule applies. |
Changing units after data exists requires review of forms, search ranges, exports, and existing user-facing records. Detailed configuration and migration procedure belongs to the installation phase.