Website profiles · Technology insights · Alternatives

packrift.github.io

A crawlable public Packrift resource that turns real catalog pack counts, prices, weights, dimensions, and inventory signals into product pages, comparison indexes, and machine-readable data files.

No paid content found
Visit website
Profile views 1 Outbound visits 1 Normal
Packrift Pack Count and Unit Signal Atlas Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
Unknown
Hosting
FastlyInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Packrift Pack Count and Unit Signal Atlas?

Packrift Pack Count and Unit Signal Atlas is a public reference site that organizes Packrift catalog data around pack counts and per-unit signals. It turns complete catalog rows—pack count, price, weight, dimensions, family, product type, inventory, and in-stock merchant availability—into browsable indexes, product signal pages, and machine-readable data files. It does not expose cost, margin, customer, supplier-only, or checkout data.

What you can do with it

  • Compare pack sizes directly. The site's headline figures show 1,727 complete product signal pages across 57 pack-count indexes, with a median pack count of 25 and a median public unit price signal of about $1.79. Pack-count pages list record counts and median unit prices—for example, 25-unit packs (459 records, median $1.27), 50-unit packs (284 records, median $1.41), and 1,000-unit packs (62 records, median $0.0558).
  • Look past the sticker price. Unit price bands divide price by pack count, and unit weight bands divide shipping weight by pack count—useful when a large case looks cheap but is heavy or bulky to handle.
  • Narrow by product shape. Family indexes cover boxes, mailers, bags, labels and more; product-type indexes link back to Packrift product routes. A cube-efficiency atlas adds density and price-per-cubic-foot views.
  • Pull data programmatically. An API directory and research asset index provide standards-shaped entry points for dataset and agent use.

A concrete scenario

Suppose you ship small parts and are choosing between a 25-pack and a 100-pack. The pack-count pages give you a quick median unit price for each tier, but the weight bands tell you whether the bigger case creates a storage or handling problem. Check the unit weight and cube signals before committing to the larger pack.

Decision criterion

Use this atlas when your question is "which pack size gives the best per-unit value at a workable weight and footprint?" For a single product's exact current availability, follow the linked product route on Packrift itself; the atlas is a comparison layer, not a storefront.

How can I compare packaging options by pack count and median unit price?

Use Packrift's pack-count indexes as the starting point, then compare each group's median unit price (price ÷ pack count) rather than the shelf price. Pack count and unit price move in opposite directions across the atlas: the 25-unit group (459 records) has a median unit price of $1.2676, the 50-unit group (284 records) is $1.4124, and the 100-unit group (63 records) drops to $1.0519. Bulk counts go much lower—1,000-unit packs (62 records) show $0.0558 and 250-unit packs (48 records) $0.3853—while small counts sit high: 5-unit packs at $10.5670 and 6-unit packs at $17.4233. The 10-unit group (165 records) is $5.1850, and the 12-unit group is $7.5000.

A comparison that respects the trade-offs

Pack count Records Median unit price Typical use
5 40 $10.5670 Sampling, low-volume or specialty items
6 36 $17.4233 Kits and assortments where each unit carries more material
10 165 $5.1850 Small operations, trial runs
12 46 $7.5000 Case-style purchasing for steady but modest demand
25 459 $1.2676 The most common group; a broad middle ground
50 284 $1.4124 Repeat ordering with less frequent restocking
100 63 $1.0519 Regular shipping volume
250 48 $0.3853 High-throughput operations
1,000 62 $0.0558 Very high volume, often small components

Two cautions when reading this table. First, medians describe groups, not individual products: a 50-unit median above the 25-unit median shows that pack count alone does not set unit cost—what is inside the pack matters. Second, the atlas draws only on complete public catalog rows (pack count, price, weight, dimensions, family, product type, inventory, in-stock availability), so it is a screening tool, not a quote.

A practical next step

Decide your monthly consumption and storage capacity first. If you ship a few dozen parcels a week, filter to the 25- and 50-unit indexes, sort by unit price, and check the unit weight and unit cube figures before committing—bulk savings vanish if a 1,000-count carton will not fit your shelf or pushes shipping weight past a carrier threshold. For a concrete case: a small mail-order seller using about 200 boxes a month might compare the 100-unit index against the 250-unit index, confirm the per-unit weight is similar, and only then choose the cheaper unit price, keeping one backup pack size for spikes.

For deeper checks, the Catalog Cube Efficiency Atlas adds density and price-per-cubic-foot context, and the Unit Price Bands index groups products into practical price ranges. Both are reachable from the site's Public Unit Signals section at Packrift Pack Count and Unit Signal Atlas.

What unit price and unit weight signals are available for specific product families like boxes, mailers, and bags?

The Atlas exposes unit price (price ÷ pack count) and unit weight (shipping weight ÷ pack count) for individual catalog records, and it groups them into browsable bands. Family indexes (boxes, mailers, bags, labels and others) let you see which records belong to each family and open their product pages, where the per-record unit price and unit weight appear. The representative rows shown on the Atlas page are mostly boxes: for example, a 1-count insulated shipping kit at $13.08 per unit and 1.42 lb unit weight, and a 1-count 9.5×9.5×7 kit at $12.71 and 1.42 lb. The page does not publish family-level median unit price or unit weight, so comparisons across boxes, mailers and bags have to be built from the underlying records or the band indexes.

How to use the signals

  • Per-unit cost: divide by pack count before comparing, especially for high-count packs. The page's pack-count medians show why: 1,000-unit packs sit at roughly $0.06 per unit while 6-unit packs sit near $17.42 — a difference driven mostly by what the products are, not by pack size alone.
  • Per-unit weight: useful for handling and storage planning. A heavy unit weight on a low pack count signals bulky single items; a low unit weight on a high count signals small consumables like labels or bags.
  • Family filtering: start from the family index for boxes, mailers or bags, then read unit price and unit weight on each product page rather than relying on the atlas-wide medians.

A practical example

Suppose you ship small parts and are choosing between a mailer and a box. Open the mailers family index, shortlist records with a unit weight that matches your handling limits, then compare unit prices within that shortlist. Repeat for boxes and compare the two shortlists — this keeps the comparison within like products instead of across the whole catalog.

Decision criteria

Signal Best for Limitation
Unit price Cost per shipped item at a given pack count Mixes product types if used catalog-wide
Unit weight Handling, storage, shipping estimates Shipping weight, not exact product weight
Family index Narrowing to boxes, mailers or bags No family-level medians published

For broader context on packaging formats, see Uline and Paper Mart.

How can I access the machine-readable data files and API directory for this catalog?

The machine-readable corpus and API discovery entry points are separate public resources on Packrift. The atlas itself is the browsable index; the files and API directory sit alongside it.

Where to look

  • Machine-Readable Corpus — the atlas page has a section with this heading. It is the entry point for the downloadable data files derived from the same catalog rows (pack count, price, weight, dimensions, family, product type, inventory, availability).
  • API Directory and Data Catalog — described on the atlas as "Standards-shaped APIs.json, OpenAPI, MCP, dataset, and agent-discovery entry points." This is the page to open if you want to wire the catalog into a script, an agent, or a data pipeline rather than read it by hand.
  • Public Research Asset Index — the canonical cross-asset index for the research resources, solver fixtures, dataset sidecars and citation metadata. Use it when you need to cite the data or locate a specific asset by name.

All three are listed under "Browse Public Unit Signals" on Packrift Pack Count and Unit Signal Atlas.

Choosing between them

If you want to… Start with
Pull the raw records into a spreadsheet or database Machine-Readable Corpus
Connect an API client, LLM agent or MCP host API Directory and Data Catalog
Cite a dataset or find a named asset Public Research Asset Index
Just compare unit prices by pack size The pack-count indexes on the atlas page

Practical next step

Open the API Directory first and check whether it exposes a dataset endpoint or only a specification describing one. If it is specification-only, the files themselves will be under the Machine-Readable Corpus. Before building anything on top, confirm which fields are in scope: the atlas states it deliberately excludes cost, margin, customer, supplier-only and checkout data, so plan your analysis around public price, pack count, weight, dimensions and availability signals only.

One caution on the numbers: the median unit prices shown per pack count (for example, $1.2676 at 25 units versus $0.0558 at 1,000 units) reflect what is in this catalog, not a general rule that bulk always costs less per unit. Mixing product families will distort any comparison, so filter by family or product type before drawing conclusions about pack-size economics.

Which pack counts have the most records and lowest median unit prices for bulk buying decisions?

The largest pack-count groups in the atlas are 25-unit (459 records) and 50-unit (284 records), but the lowest median unit price signals sit at much higher counts: 1,000-unit packs at $0.0558, then 250-unit at $0.3853 and 200-unit at $0.6072. Among the big-record groups, 100-unit packs (63 records, $1.0519) are the notable low-price option.

Where volume and record depth diverge

Pack count Records Median unit price signal Practical read
25 459 $1.2676 Deepest selection; best for mixed, moderate-volume orders
50 284 $1.4124 Wide choice, but not the cheapest per unit
10 165 $5.1850 Small-batch or sample buying
100 63 $1.0519 Lower unit price with a still-useful set of options
250 48 $0.3853 Strong per-unit saving, thinner selection
1,000 62 $0.0558 Lowest median unit price; suits steady, high-throughput use
200 33 $0.6072 Middle ground between 100 and 250

How to choose

  • If variety matters more than unit cost — for example, a small shop testing several box sizes — start with the 25- and 50-unit indexes, where the most records give you room to compare dimensions and families.
  • If you have predictable, repeating volume — a fulfillment operation shipping daily — the 1,000-unit group offers the lowest median unit price, though only 62 records means fewer size and material choices.
  • If you want a balance — the 100-unit group combines a sub-$1.10 median with 63 records, making it a sensible first stop before committing to 250 or 1,000.

Treat medians as a starting filter, not a verdict: a 1,000-unit median is pulled down by small, cheap items as well as genuinely bulk-priced ones, so check the individual product pages for dimensions, weight and stock before deciding. A useful next step is to open the pack-count index for your target size, shortlist two or three products in the family you need, and compare their unit price, unit weight and cube side by side; the Packrift Pack Count and Unit Signal Atlas organizes exactly those signals.

How are unit price bands and unit weight bands calculated and used for catalog review?

Unit price bands are calculated by dividing price by pack count; unit weight bands divide shipping weight by pack count. Both turn whole-case listings into per-unit signals, so you can compare a 25-pack and a 1,000-pack on the same footing. The atlas publishes these as grouped ranges, with median figures per pack count (for example, 1,000-unit packs showing a $0.0558 median unit price signal versus $17.4233 for 6-unit packs).

Signal Calculation What it answers Primary audience
Unit price band Price ÷ pack count, grouped into ranges Which pack sizes offer the lowest per-item cost Buyers comparing bulk tiers
Unit weight band Shipping weight ÷ pack count, grouped into ranges Per-item handling and freight burden Catalog reviewers, ops staff

How catalog reviewers use them

  • Spot outliers: a product whose unit price sits far above its pack-count peers is a candidate for repricing review or a listing error check.
  • Separate price from weight: a low unit price with a high unit weight may still be uneconomical to ship; reviewing both bands together catches this.
  • Sanity-check pack counts: if weight per unit looks implausible for the product type, the pack count or weight field may be wrong.

For a concrete scenario: a reviewer auditing the 25-unit group (459 records, $1.2676 median unit price) can flag any record well outside that band and cross-check its unit weight against the family norm before escalating. The Packrift Pack Count and Unit Signal Atlas also groups records by families and product types, which helps set a fair benchmark for each category rather than one blanket threshold.

Related questions

More questions →
What is the Packrift Pack Count and Unit Signal Atlas?

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

  1. For a quick market read: open Browse by Pack Count and compare median unit prices for the pack sizes you actually buy.
  2. 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.
  3. For analysis or automation: go to the API Directory and Data Catalog and use the OpenAPI or dataset entry points instead of parsing pages.
  4. 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.

Website Overview

Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Unknown

DNS and Email

Nameservers are provided by Amazon Route 53, indicating managed DNS hosting. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. The lowest observed DNS TTL is 3600 seconds.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The x-cache, x-served-by, via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers.

Technology Stack Analysis

The public page identifies Fastly without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The meta description has 197 characters and may be shortened in search results. No Open Graph metadata was detected, so social previews may depend on platform inference. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 41 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSAmazon Route 53
HostingFastly
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 185.199.108.153

Registration details

RDAP / WHOIS

Unknown

DNS records

DNS

TypeNameValueTTLPriority
Apackrift.github.io185.199.108.1533600—
Apackrift.github.io185.199.109.1533600—
Apackrift.github.io185.199.110.1533600—
Apackrift.github.io185.199.111.1533600—
AAAApackrift.github.io2606:50c0:8000::1533600—
AAAApackrift.github.io2606:50c0:8001::1533600—
AAAApackrift.github.io2606:50c0:8002::1533600—
AAAApackrift.github.io2606:50c0:8003::1533600—
NSgithub.iodns1.p05.nsone.net3600—
NSgithub.iodns2.p05.nsone.net3600—
NSgithub.iodns3.p05.nsone.net3600—
NSgithub.iodns4.p05.nsone.net3600—
NSgithub.ions-1339.awsdns-39.org3600—
NSgithub.ions-1622.awsdns-10.co.uk3600—
NSgithub.ions-393.awsdns-49.com3600—
NSgithub.ions-692.awsdns-22.net3600—
TXTgithub.iov=spf1 a -all3600—
CAAgithub.io0 issue "digicert.com"3600—
CAAgithub.io0 issue "letsencrypt.org"3600—
CAAgithub.io0 issue "sectigo.com"3600—
CAAgithub.io0 issuewild "digicert.com"3600—
CAAgithub.io0 issuewild "letsencrypt.org"3600—
CAAgithub.io0 issuewild "sectigo.com"3600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subject*.github.io
IssuerLet's Encrypt
Valid until2026-12-29T23:44 · Remaining when checked: 66 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlmax-age=600
serverGitHub.com
strict-transport-securitymax-age=31556952
access-control-allow-origin*

Identified technologies

Fastly

Pages, Search and Sharing

User reviews (0)

  • No reviews yet.