Logistics · Shipment tracking

Shipment tracking for Logistics

For logistics teams, shipment tracking on KERNSTACK ends the three-portal reconciliation shift: carrier webhooks and polling workers feed raw scan events into the project, normalisers append them to each shipment’s canonical timeline, and reconciliation workers flag the shipments that need a human — stalled, returned, held — while customers read their tracking page from the same rows dispatch works from.

Functions (WASM)NoSQL Tables Container Workers Product Analytics

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

Domain Architecture for Logistics

The domain model is a timeline with provenance: the shipment row (order reference, carrier, service level, recipient), scan rows keyed by shipment and carrier timestamp in canonical states, and the raw events preserved beneath them. Expected-progress rules per carrier and lane (first scan within a day, delivery inside the promised window) turn absence into information: a missing scan is computed, flagged, and assigned rather than noticed by a customer first.

Compliance, Data Residency & Governance

When a delivery is disputed — by a customer, or by you against the carrier — the evidence is the stored raw events plus the normalisation that interpreted them, all timestamped in one European project. Proof of delivery is a record, claims evidence exports assemble from the timeline within the carrier’s claims window, and recipient personal data follows declared retention instead of ageing forever in a tracking spreadsheet nobody owns.

Logistics runs on evidence with deadlines: proof of delivery, claims windows with carriers, customs documentation, and data about recipients that obeys European residency and retention duties. On KERNSTACK the raw carrier events are kept beside their normalised states, so a disputed delivery replays from what the carrier actually sent; exception handling is timestamped work with owners; and recipient data follows the project’s declared retention in one European zone — demonstrable to enterprise customers who audit their carriers’ subcontractors, software included.

Operational Impact on the Software Lifecycle Cloud

Dispatchers work a queue instead of a browser full of carrier tabs: exceptions arrive ranked by age and value, customer service answers “where is it” from the same timeline (so the answer stops depending on who is asked), and carrier performance conversations start from scan-derived facts — first-scan latency, stall rates per lane — computed from your own records.

Key Domain Entities & Workflows

Primary Logistics Data Entities: shipments, scan events, carrier accounts, exceptions, proofs of delivery
Governed Lifecycle Workflows: exception review, carrier replay, proof of delivery, customs document intake, claims evidence export
Integrated Platform Services: functions, tables, workers, analytics

Compare this integrated blueprint with the general Shipment tracking reference architecture or explore our European Sovereign Cloud guarantees.

Logistics · Shipment tracking Flow

IngressCarrier scan stored rawshipment-tracking

StateNormaliser appends the timelineproject resource

ReviewExceptions flagged for dispatchdeclared in stack.json

stack.json — Logistics Shipment tracking plan · deploy

{
  "resources": {
    "functions": [{ "name": "receive-scan" }],
    "workers": [{ "name": "normalise", "runtime": "nodejs" }, { "name": "reconcile", "runtime": "python" }],
    "tables": [
      { "name": "shipments", "key_name": "shipment_id", "key_type": "S", "indexes": [] },
      { "name": "scans", "key_name": "shipment_id", "key_type": "S", "sortkey_name": "ts", "sortkey_type": "N", "indexes": [] },
      { "name": "exceptions", "key_name": "shipment_id", "key_type": "S", "indexes": [] }
    ],
    "workflows": [{ "name": "exception-sweep", "triggers": [{ "type": "cron", "cron": "0 * * * *" }],
      "steps": [{ "id": "reconcile", "worker": "reconcile" }] }]
  }
}

Estimated Footprint · Team Plan ~1.600 credits / mo

Assumes 50k shipments a month with a dozen scans each; ingestion compute plus storage at platform rates, exception checks on a schedule.

Metered from one shared balance across compute (0.01 cr/GiB-s), storage (0.04 cr/GB-hr), network (9.00 cr/GiB), and catalog models. See full credit reference →

FAQ

Frequently asked questions

How are carriers without webhooks handled?

With a polling worker on a schedule, writing into the same raw-event intake. The downstream world — normalisation, timelines, exceptions — cannot tell the difference, which is the point of storing raw first.

What if the carrier never scans?

That becomes a computed exception: expected-scan rules per carrier and lane flag the silence inside the window where a call can still change the outcome. The customer hears it from you, which is the entire reputational difference.

Can customers track without accounts?

Yes — an unguessable tracking key on the shipment row gates a read-only route over the canonical timeline. Internal notes stay on fields the public handler never returns.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →