What is the Packrift Pack Count and Unit Signal Atlas?
Updated
The Packrift Pack Count and Unit Signal Atlas is a public, crawlable research resource that reorganizes complete Packrift catalog rows into product pages, comparison indexes, and machine-readable data files. It is useful if you want to compare packaging supplies by pack count, unit price, unit weight, or cube size without opening each product listing, and if you only need catalog-level signals rather than cost, margin, customer, supplier, or checkout data.
What the Atlas contains
The site describes itself as covering 1,727 complete public product signal pages across 57 pack-count indexes, with a median pack count of 25 and a median public unit price signal of $1.7905.
A record only enters the atlas if the source catalog row is complete: canonical product URL, pack count, price, weight, dimensions, family, product type, inventory, approved catalog status, and in-stock merchant availability. Rows missing any of these are excluded, which is why the page count is smaller than a full catalog.
The site states plainly that it does not expose cost, margin, customer, supplier-only, or checkout data. Treat it as a comparison and research layer, not a storefront or a purchasing system.
How the data is organized
The atlas splits into four browsing paths, each answering a different question:
| Section | What it answers | Example entry |
|---|---|---|
| Browse by Pack Count | How do prices and weights differ across pack sizes? | 25 unit pack: 459 records, median unit price $1.2676 |
| Browse Public Unit Signals | Where are the derived indexes and data files? | Unit Price Bands, Unit Weight Bands, Families, Product Types |
| Representative Product Signals | What does a single record look like? | SKU 212C, 1-pack insulated shipping kit, $13.0800, 1.42 lb, 576 in³ |
| Machine-Readable Corpus | How do I pull the data programmatically? | APIs.json, OpenAPI, MCP, dataset and agent-discovery entry points |
Pack-count indexes
The pack-count pages are the most immediately useful part. Each index lists the number of records and the median unit price for that pack size, so you can see the shape of pricing across the catalog before drilling into individual products. The largest groups are 25-unit (459 records), 50-unit (284), 10-unit (165), 15-unit (142), and 20-unit (140). Very large packs behave differently: the 1,000-unit group has 62 records at a median unit price of $0.0558, while the 6-unit group has 36 records at $17.4233.
Derived signal indexes
Beyond raw pack counts, the atlas publishes calculated views:
- Unit Price Bands — price divided by pack count, grouped into practical ranges.
- Unit Weight Bands — shipping weight divided by pack count, for handling and catalog review.
- Catalog Cube Efficiency Atlas — dimension-backed cube, density, reference DIM weight, and price per cubic foot.
- Families and Product Types — indexes across boxes, mailers, bags, labels, and similar categories.
Representative records
Individual product pages carry the fields you would otherwise have to reconstruct: SKU, title, pack count, unit price, unit weight, unit cube, and family. For example, SKU 212C is an 8x6x12 EPS foam insulated shipping kit listed at $13.0800 for a 1-pack, with a unit weight of 1.42 lb and a unit cube of 576 in³, in the Boxes family.
Machine-readable access
The corpus is also published for programmatic use through an API directory and data catalog: standards-shaped apis.json, OpenAPI, MCP, dataset, and agent-discovery entry points, plus a canonical cross-asset index for solver fixtures, dataset sidecars, and citation metadata. If you are building a comparison tool or feeding a model, start there rather than scraping the HTML pages.
When this resource fits your task
Use the atlas when you need to:
- Compare unit economics across pack sizes before requesting quotes.
- Estimate shipping weight or cube per unit for a packaging family.
- Pull structured pack-count and price signals into an analysis or agent workflow.
- Cite a public, crawlable source for catalog-level packaging data.
Look elsewhere when you need live stock guarantees, negotiated pricing, supplier contacts, or checkout. The atlas is built from approved, in-stock catalog rows, but it is a snapshot resource, not a live inventory feed, and the site does not publish pricing or access terms for the data itself.
Practical starting points
- For a quick market read: open Browse by Pack Count and compare median unit prices for the pack sizes you actually buy.
- For a specific product: search the representative product pages by SKU or family to get pack count, unit price, weight, and cube in one place.
- For analysis or automation: go to the API Directory and Data Catalog and use the OpenAPI or dataset entry points instead of parsing pages.
- For shipping-cost modeling: use the Catalog Cube Efficiency Atlas, which already computes DIM weight and price per cubic foot.
One caveat worth planning around: because inclusion requires a complete row, the atlas under-represents products with missing dimensions or inventory status. If a product you expect to see is absent, that is more likely a data-completeness filter than a missing product.