WooCommerce Orders Export Sample Dataset
WooCommerce's native order export from the admin panel generates UTF-8 CSV files with exact production headers: Order ID, Date Created, Status, Currency, Total, Billing First Name, Billing Last Name, Billing Email, Line Items, Order Notes, and Shipping Method. This dataset contains 6,300 synthetic order records. The WooCommerce export quirk that causes CSV structural collapse is that the Line Items and Order Notes fields frequently contain raw HTML markup (<br>, <p>, <strong>) and embedded CRLF line breaks from product descriptions and checkout notes. When a customer leaves a multi-paragraph order note or a product description contains HTML tags, the entire CSV row structure fractures — naive parsers split a single order into 3-5 invalid rows at every unescaped newline. The structural dirty data inventory includes: 2,100 Order Notes cells with embedded CRLF line breaks and raw HTML tags, 890 Line Items cells containing quoted commas within product names (e.g., 'Widget A, Large, Blue'), and missing UTF-8 BOM causing accented customer names (Müller) to display as mojibake. Expected Output: Yields 6,300 clean order records with intact multiline content. Ideal for: ETL testing, DuckDB demos, Power BI, Excel Power Query, CI pipelines. Process this file through the woocommerce-cleaner tool to strip HTML artifacts and collapse multiline order notes.
This dummy dataset simulates a standard export from Other, containing realistic yet fully anonymized records that mirror the structure and common data quality issues found in real production environments. The CSV file includes typical problems such as inconsistent formatting, missing values, duplicate entries, and non-standardized categorical fields.
It is designed to be used as a safe sandbox for testing data cleaning workflows directly in your browser — no uploads, no server round-trips, no third-party data exposure. Whether you are validating a transformation pipeline, benchmarking a cleaning tool, or simply exploring common data quality patterns, this sample provides a representative starting point without risking any sensitive business data.
Data Schema
| Column Name | Data Type | Description |
|---|---|---|
| id | string | Unique record identifier |
| created_at | timestamp | Record creation date and time |
| status | string | Current status of the record |