SmartPack
Never receive the same SmartPack twice.
Every normal production file contains approximately 50,000 records and receives a unique pack ID. Your account remembers previously delivered pack IDs. Future purchases automatically exclude them while other packs remain available.
- Step 1
Numbered files
Each production file holds approximately 50,000 records and gets a permanent ID such as UK-0007.
- Step 2
Reserved while you pay
Starting checkout reserves the lowest-numbered packs you have not received, until the invoice expires.
- Step 3
Allocated on payment
When the payment provider confirms payment, those packs are recorded against your account with version and checksum.
- Step 4
Excluded next time
Every later order skips pack IDs already in your account while unseen packs remain.
A worked example
A dataset has six packs, UK-0001 to UK-0006. Two customers buy 100K (two packs) at a time:
| Order | Result |
|---|---|
| Customer A — 1st 100K | UK-0001 UK-0002 |
| Customer A — 2nd 100K | UK-0003 UK-0004 |
| Customer A — 3rd 100K | UK-0005 UK-0006 |
| Customer A — 4th 100K | Not allowed: no unseen packs remain. Customer A can ask to be notified when new packs arrive. |
| Customer B — 1st 100K | UK-0001 UK-0002 (uniqueness is per customer) |
Quantities and packs
| 30K trial | 1 dedicated trial file |
| 50K | 1 pack |
| 100K | 2 packs |
| 250K | 5 packs |
| 500K | 10 packs |
| 1M | 20 packs |
What SmartPacks are not
Packs are not exclusive: other customers may buy the same pack IDs. A pack is only exclusive when its product page explicitly says so. We also never oversell: if fewer unseen packs remain than you ask for, checkout tells you exactly how many new records are available to your account.
Every allocation is traceable
For each pack delivered we record:
- Pack ID
- Dataset version
- Your order number
- Allocation date
- SHA-256 file checksum
- Record count
If a delivered file ever changes on the server, its checksum no longer matches and downloads pause until an administrator reviews it. How versioning works