Skip to content
Novus Examples
csv599 B

Fieldnote Supply Shop: Refund and partial-refund export

Refund and partial-refund export for Fieldnote Supply Shop. 4 refunds: 2 return the whole line and 2 return one unit of a multi-unit line. merchandise_refund totals 80.00 and matches the refunded column of the shop payments table; tax_refund totals 7.46 and is charged at the order jurisdiction rate on the merchandise refunded.

csv

text/csv

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

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
4
Full Line Refunds
2
Partial Line Refunds
2
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Import the refunds and check each one against the order line it reverses.
Expected result
Every refund_id resolves to a line_id in order-lines-export.csv, refunded_quantity never exceeds line_quantity, merchandise_refund sums to 80.00 and total_refund sums to 87.46.

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: Refund and partial-refund export” 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: 4 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("refunds.csv")
print(df.head())
print(df.dtypes)

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