randarium
Datasets

Fake Logistics Dataset

Create reproducible synthetic logistics and package tracking records with shipment IDs, statuses, carriers, locations, and event timelines. This data is fictional and should not be used for real tracking or shipping purposes.

Also known as: package tracking · shipment data · delivery tracking

seeded · synthetic data

Presets

Output

No output yet — set your options and hit .
About this tool, tips & examples

What it does

The Fake Logistics Dataset generator produces synthetic package-tracking records: shipment IDs, delivery statuses, carriers, origin and destination cities, and event timelines with timestamps. Generate up to 10,000 shipments from a chosen start date, seeded for exact reproducibility, and export as CSV, JSON, NDJSON, TSV, or Markdown.

Common use cases

  • Tracking UI development — status timelines and progress indicators populated with realistic multi-event shipment histories.
  • Supply-chain dashboards — carrier mix, delivery-time distributions, and exception rates with plausible demo data.
  • Logistics platform testing — bulk imports, webhook simulations, and status-transition logic against varied reproducible records.
  • Training and onboarding — safe example data for support teams learning a shipping tool.

Settings

  • How many — 1 to 10,000 shipments (presets for typical, large, and recent batches).
  • Start date — anchors the event timelines.
  • Seed — the same seed and settings regenerate the identical dataset.

Privacy note

Records are generated locally in your browser and never uploaded. Everything is fictional — the tracking numbers resolve nowhere, the addresses ship nothing — so it must never be used for real tracking or customer communication.

FAQ

Do the tracking events tell a coherent story? Each shipment’s events follow a sensible progression (created → in transit → delivered/exception), which is what tracking UIs and state machines need to render meaningfully.

Will these tracking numbers work on carrier sites? No — they’re format-plausible but not issued by any carrier. Perfect for UI work, useless (by design) for real lookups.

Can I stress-test with a big batch? Yes — 10,000 shipments per run, and NDJSON export streams cleanly into most ingestion pipelines. Regenerate the identical batch anywhere with the seed.