Load Data Points

Practical ops definitions with developer behavior for Krane's Load schema.

Schema v1Production

Search fields

Find fields by name, purpose, or behavior.

1) Core Identity

Immutable anchors to join data across systems and documents.

load_id

uuid

Field

Ops: Internal unique ID for the load.

Dev: Primary key. Never re-used. Emitted by DB.

load_number

string

Field

Ops: Human-facing load identifier.

Dev: Unique per tenant recommended. Used on UI and exports.

customer_ref

string

Field

Ops: Customer/Broker reference.

Dev: Parsed from rate con / tender; used to match external systems.

external_ref

string

Field

Ops: External TMS/portal reference.

Dev: Optional. Comes from EDI/API portals.

bol_number

string

Field

Ops: Bill of Lading number.

Dev: Usually set at pickup; used for docs & claims.

pro_number

string

Field

Ops: LTL tracking number (if applicable).

Dev: Optional; used when shipper/broker issues a PRO.

ratecon_number

string

Field

Ops: Broker rate confirmation ID.

Dev: Extracted from RC PDF or email subject.

tender_id

string

Field

Ops: Digital tender identifier.

Dev: EDI/API field. Useful for dedupe on intake.

Field Patterns & Conventions

How indexed stop fields and units work system-wide.

Indexed Stops

Fields ending with _# repeat per stop index (1–6). Example: pickup_date_1 … pickup_date_6.

Units

Weights use weight_unit (lb|kg). Pieces use pieces_unit. Dimensions use dimensions_unit (in|cm).

Timestamps

All timestamps are stored as UTC. UI renders in company/user timezone.