pdf2.7 KB

Pine Assembly Workshop: Proof of delivery PDF

Proof of delivery PDF for Pine Assembly Workshop. A one-page delivery confirmation for SHIP-07. The record table states 4 pieces delivered against 4 expected, 48.800 kg gross and 16 actual minutes against 15 planned.

Data import

Rendered preview of Pine Assembly Workshop: Proof of delivery PDF

Rendered preview of the pdf file (2.7 KB). Download above for the original.

Specifications

Document Set: logistics
Industry: logistics
Source Kit: inventory-manufacturing
Synthetic: true
As Of: 2026-09-08
Pages: 1
Shipment Id: SHIP-07
Pieces Delivered: 4

Testing contract

Expected to pass

Scenario: Extract the record table and reconcile it with the shipment export and the POD register.
Expected result: Pieces expected 4, pieces delivered 4 and the minute figures all match the SHIP-07 row of shipments-export.csv, and the proof of delivery number POD-2026-0007 is the proof-of-delivery.csv row whose shipment_id is SHIP-07.

What is a .pdf file?

PDF (Portable Document Format) is a page-oriented format that fixes layout, fonts, and vector and raster graphics so a page renders identically anywhere. A `%PDF-` header is followed by numbered objects, a cross-reference table mapping each to a byte offset, and a trailer; edits append incremental updates rather than rewrite the file. Page content is a stream of drawing operators, so a PDF holds no words or paragraphs, only positioned glyph runs. Adobe released it in 1993 and gave it to ISO as ISO 32000-1 in 2008.

How to use this file

Use an example PDF to test text extraction, rendering, metadata parsing, AcroForm handling, and OCR pipelines: checking that extraction reconstructs reading order from glyph positions, that a scanned page yields no text, and that an incremental update leaves earlier revisions in the file.

How to use this file for testing

“Pine Assembly Workshop: Proof of delivery PDF” 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: 1 pages. 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.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import pdfplumber  # pip install pdfplumber

with pdfplumber.open("proof-of-delivery-SHIP-07.pdf") as pdf:
    print(len(pdf.pages), "pages")
    print(pdf.pages[0].extract_text())