Skip to content
Novus Examples
csv523 B

Fieldnote Supply Shop: Customer export with tax jurisdiction

Customer export with tax jurisdiction for Fieldnote Supply Shop. 6 fictional customers at example.test addresses, each with the jurisdiction that set the tax rate on their orders. Every customer placed 2 orders and merchandise_total sums to 922.00.

csv

text/csv

523 B
Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Rows
6

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
6
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Join the customer export to the order export on customer_id.
Expected result
All 6 customer_id values appear in orders-export.csv, each with exactly 2 orders, and the tax_jurisdiction column matches the jurisdiction recorded on both of that customer's orders. merchandise_total sums to 922.00.

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: Customer export with tax jurisdiction” 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: 6 rows · 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("customer-export.csv")
print(df.head())
print(df.dtypes)

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