Purchasing desk email and PO change threads, industrial equipment maker
Summary
Fifteen years of purchasing and planning mail from one maker of industrial pumps and fluid handling skids, joined to the purchase orders, receipts and vendor records each thread is about. It captures expediting, PO change negotiations, supplier delay notices, substitutions and first article disputes as they really happen. Suppliers, customers, people and all prices are replaced with placeholders. The archive closes in 2025 and is not refreshed.
Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.
Pricing on request
Request scope and pricingAt a glance
- Planned scope. Volume, sources and timing are confirmed in writing before you sign.
- Records
- 3.9Memails, purchase orders, receipts and documents
- Size
- 10.4 GB
- Tokens, estimated
- 1.1B
- Years
- 2011 to 2025
- Firms
- 1
- Owner profile
- One US industrial equipment manufacturer, 150 to 300 staff
- Industry
- Manufacturing
- Data type
- Logistics and supply chain
- Headcount
- 150 to 300 staff
- Region
- United States
- Languages
- English
- Formats
- JSONL, Parquet
- Updated
Sources
| System | Kind | Records |
|---|---|---|
| Microsoft 365 mail | 3.1M messages | |
| NetSuite | Accounting and ERP | 164K purchase orders, 590K receipts |
| Shared drives | Shared files | 38K supplier agreements and first article reports |
Good for
- training procurement agents to expedite late purchase orders and negotiate dates
- extracting promised dates, quantities and change requests from supplier email into PO updates
- evaluating supplier risk reasoning across years of delivery history
- testing long-context retrieval over threads that span quotes, POs and receipts
Fields
| Field | Type | Description |
|---|---|---|
| thread_id | string | Email thread id |
| po_number | string | Purchase order the thread is about |
| vendor_code | string | Placeholder for the supplier |
| topic | enum | expedite, PO change, delay notice, substitution, quality issue or invoice question |
| messages | int | Messages in the thread |
| first_message_at | timestamp | First message in the thread |
| last_message_at | timestamp | Last message in the thread |
| promised_date_changes | array<string> | Each promised date the supplier gave, in order |
| excerpt | string | Body of the latest message, quoted text stripped |
Example record
{
"thread_id": "TH-2021-044817",
"po_number": "PO-118862",
"vendor_code": "[COMPANY_31]",
"topic": "delay notice",
"messages": 9,
"first_message_at": "2021-09-02T08:14:00-05:00",
"last_message_at": "2021-10-12T15:51:00-05:00",
"promised_date_changes": [
"2021-09-24",
"2021-10-15",
"2021-11-05"
],
"excerpt": "[PERSON_8], the 6 in ANSI 300 flanged ball valves now show 11/5 ship from the factory. That puts the [SITE_3] skid past its ship date. Can you split the order and send the 4 in valves you already have on the shelf? Please also confirm the WCB bodies come with 3.1 material certs, our customer rejects without them."
}Licenses available
Exclusive
One buyer. Nobody else can license it during the exclusive term, usually 2 years.
Non-exclusive
Licensed to more than one buyer.
First look
One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.
What ships with it
- Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
- Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
- Manifest with a hash for every file.
- QC report and de-identification report.
- Your own copy, with unique canary records.
How it is de-identified
Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.