Skip to content
Novus Examples
json337.3 KB

E-commerce Orders (JSON, 2000 records)

The e-commerce orders table as a JSON array — the format twin of the CSV, for import and conversion testing.

Data importConversion testing
Preview — first 50 linesjson
[
  {
    "order_id": 1,
    "customer_id": 150,
    "product_id": 171,
    "quantity": 2,
    "total": 705.98,
    "status": "paid",
    "order_date": "2025-10-19"
  },
  {
    "order_id": 2,
    "customer_id": 174,
    "product_id": 36,
    "quantity": 1,
    "total": 25.59,
    "status": "refunded",
    "order_date": "2025-06-09"
  },
  {
    "order_id": 3,
    "customer_id": 31,
    "product_id": 1,
    "quantity": 2,
    "total": 444.46,
    "status": "shipped",
    "order_date": "2025-04-27"
  },
  {
    "order_id": 4,
    "customer_id": 293,
    "product_id": 51,
    "quantity": 4,
    "total": 881.44,
    "status": "delivered",
    "order_date": "2025-08-22"
  },
  {
    "order_id": 5,
    "customer_id": 431,
    "product_id": 127,
    "quantity": 3,
    "total": 1105.89,
    "status": "shipped",
    "order_date": "2025-03-12"
  },
  {
    "order_id": 6,
    "customer_id": 295,
    "product_id": 190,
… 3433 lines total — download for the full file.

Specifications

Records
2000
Schema
order_id, customer_id, product_id, quantity, total, status, order_date
Domain
e-commerce

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“E-commerce Orders (JSON, 2000 records)” is a deterministic Novus Examples fixture for Data import, Conversion testing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 2,000 records · schema: order_id, customer_id, product_id, quantity, total, status, order_date. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks — delimiters, encodings, null handling, schema, and row counts — in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import json

with open("orders.json") as f:
    data = json.load(f)
print(type(data), len(data))

Related files

Generated by generation/data_realworld.py. Free for any use, no attribution required — license.