Skip to content
Novus Examples
csv432 B

Pine Assembly Workshop: Bill of lading register

Bill of lading register for Pine Assembly Workshop. 4 bills of lading, one per delivery round, covering all 16 shipments and all 56 pieces. The piece counts are 8, 12, 16, 20 and they sum to 56, which is the parcels column of shipments-export.csv. Freight terms are prepaid on every round.

csv

text/csv

432 B
Document Set
logistics
Industry
logistics
Source Kit
inventory-manufacturing
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
logistics
Industry
logistics
Source Kit
inventory-manufacturing
Synthetic
true
As Of
2026-09-08
Rows
4
Pieces
56
Weight Kg
683.200
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Join the register to the shipment export on route_id and compare the piece counts.
Expected result
The 4 bills account for every shipment exactly once: the shipments column sums to 16, the pieces column to 56 and gross_weight_kg to 683.200, all matching the shipment export grouped by route.

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

“Pine Assembly Workshop: Bill of lading register” 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("bill-of-lading-register.csv")
print(df.head())
print(df.dtypes)

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