Skip to content
Novus Examples
csv2.1 KB

Fieldnote Supply Shop: Order line export CSV

Order line export CSV for Fieldnote Supply Shop. 24 order lines, two per order, each naming the variant actually sold. quantity times unit_price equals line_total on every row and the line totals sum to 942.00, which is the merchandise_subtotal column of orders-export.csv before discounts.

csv

text/csv

2.1 KB
Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Rows
24

Binary csv: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Rows
24
Columns
10
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Join the line export to the order export on order_id and recompute each order subtotal.
Expected result
All 24 lines multiply out exactly and group into 12 orders whose summed line_total equals the merchandise_subtotal column of orders-export.csv for every order_id.

What is a .csv file?

CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.

How to use this file

Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.

How to use this file for testing

“Fieldnote Supply Shop: Order line export CSV” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 24 rows · 10 columns · UTF-8. 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 pandas as pd

df = pd.read_csv("order-lines-export.csv")
print(df.head())
print(df.dtypes)

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