What Should Be on a Pre-Rolled Cone Specification Sheet?

A pre-rolled cone specification sheet should identify the exact product revision, physical dimensions, paper and tip construction, pack quantities, permitted variation and inspection method. It should also connect the approved sample to the purchase order and explain what happens if the received lot differs.

This guide concerns empty paper products and procurement records. It does not provide filling instructions, consumption amounts or controlled-substance guidance.

Quick answer

  • Use one sheet per SKU and revision; do not rely on a size nickname.
  • Separate total length, body length, tip length and named diameters.
  • Record paper and tip facts only when the supplier can verify them.
  • Define units per pack, packs per case and total units separately.
  • Add tolerances, sampling and accept/review/hold rules before ordering.
Specification block Minimum useful fields Why it matters
Identity Buyer SKU, supplier SKU, revision, approval date Prevents an old sample or similar variant from becoming the reference
Geometry Total length, body length, tip length, wide and narrow diameters Makes size comparisons reproducible
Materials Paper description, declared GSM, tip material, adhesive declaration Separates verified composition from appearance
Packaging Units per pack, packs per case, cases per shipment Prevents count and packaging-level confusion
Quality Tolerances, inspection method, sample plan, disposition Turns observations into repeatable decisions

Lock identity, revision and dimensions

The sheet must first answer which product it describes. A neat table is not useful if it can quietly migrate between variants.

Record:

  • buyer SKU and supplier SKU;
  • plain product name;
  • supplier and manufacturing source, when relevant;
  • sample or drawing identifier;
  • specification revision and effective date;
  • approval owner and date; and
  • linked purchase-order line.

Use an explicit revision field and retain the superseded version.

Good identity record

“SKU CB-Example-01; supplier item ABC-123; specification revision 3; approved sample S-2026-10; effective for purchase orders issued after [date].”

Bad identity record

“King-size brown cone — same as last time.”

The examples are formatting illustrations, not ConeBarn product identifiers or claims.

Define dimensions and measurement points

A size name should never replace the dimensions a buyer actually checks. For a tapered paper form, one “length” cell hides too much.

Include the relevant fields:

  1. total length;
  2. paper-body length;
  3. paper-tip length;
  4. wide-opening diameter;
  5. narrow-end or tip-interface diameter; and
  6. inside or outside measurement convention.

Every controlled dimension needs a unit, reference points and method. State whether the sample is measured along a centerline, whether an opening is treated as round or checked across two axes, and how light contact is maintained without flattening the paper.

The pre-rolled cone measurement guide provides a worksheet for those fields. The dimension-tolerance guide explains why nominal values, permitted ranges and actual measurements should remain separate.

Describe materials without guessing

Record what the supplier declares and what the buyer can verify; leave unsupported claims out. Color alone does not establish fibre source, bleaching status, certification or paper weight.

A practical material block can include:

  • supplier paper description;
  • declared grammage in g/m²;
  • paper color or finish as a visual identifier;
  • tip material and construction;
  • adhesive or seam declaration supplied by the manufacturer;
  • certification name, scope, certificate holder and validity, when applicable; and
  • source document and date for every formal claim.

GSM is a mass-per-area field, not a synonym for thickness, stiffness or performance. Use the cone-paper GSM guide to keep those properties separate.

Likewise, “paper tip” does not automatically mean a filtration component. The paper-tip versus filter guide explains which component questions belong on the sheet.

> Selection boundary: A supplier declaration can populate the specification when its scope is clear. It should not be promoted into an independent test result unless a suitable test and report actually exist.

Map every packaging level

Count must be attached to a packaging level. “200 count” is incomplete if one team means units per retail pack and another means packs per shipping case.

Use a packaging hierarchy:

Level Identifier Quantity fields Dimensions and weight
Each Individual empty cone 1 unit Product dimensions
Inner or retail pack Pack SKU and label version Units per pack Pack dimensions and gross weight, if verified
Case Case SKU and label version Packs per case and total units Case dimensions and gross weight
Shipment or pallet Logistics reference Cases and total units Declared shipment data

GS1 guidance treats product information by packaging level because data from an each, inner pack, case and pallet are not interchangeable. The same discipline helps a smaller buyer even without a formal data-exchange program.

The 200-count guide shows how to distinguish units per pack, number of packs and total units.

Add quality and receiving rules

A specification becomes operational when it says how conformity will be checked. Otherwise the buyer has a product biography, not an acceptance plan.

For each critical feature, add:

  • nominal requirement and permitted range;
  • inspection tool and method;
  • sample-selection rule;
  • approved visual reference, when appropriate;
  • accept, review and hold criteria;
  • documentation required for exceptions; and
  • agreed remedy or escalation route.

Do not mix visible damage, dimensional variation and quantity shortage into one “quality” checkbox. A crushed carton, lifted seam, out-of-range diameter and missing pack require different evidence and next actions.

The purchase order should point to the specification revision rather than paste a partial copy of it. Shopify’s current wholesale guidance similarly recommends aligning specifications, quantities, pricing, delivery dates and special conditions before payment, then checking the received order against the agreed record.

Specification-sheet checklist

  • [ ] Exact buyer and supplier SKUs are listed.
  • [ ] Revision, effective date and approved sample are linked.
  • [ ] Dimensions have units, reference points and conventions.
  • [ ] Paper and tip statements are source-scoped.
  • [ ] GSM is not presented as thickness or performance.
  • [ ] Units per pack, packs per case and total units are separate.
  • [ ] Labels and packaging levels use matching identifiers.
  • [ ] Critical fields include tolerances and inspection methods.
  • [ ] Sample size and lot selection are defined.
  • [ ] Accept, review and hold outcomes are documented.
  • [ ] The purchase order cites the current specification revision.
  • [ ] Changes require a new revision rather than a silent overwrite.

FAQ

Is a product page enough for a bulk specification?

Usually not. A product page can summarize the offer, but a bulk specification should define revision, measurement methods, tolerances, packaging hierarchy and acceptance rules.

Should capacity be on the sheet?

Only with a defined basis. Keep geometric dimensions separate from a nominal or measured capacity, and record the method, material, sample and revision behind the capacity value.

Can one specification cover several cone sizes?

A shared template can cover the same fields, but each SKU or size should have its own controlled values and revision. Do not assume a tolerance or material claim transfers automatically.

Who should approve a specification change?

The buyer and supplier should identify authorized approvers in their purchasing process. Record the revised fields, effective date and which open or future orders use the change.

References

If you are comparing a current ConeBarn option, start with the live 200-count product entry, then request the specification revision and fields needed for your exact buying decision.

Back to blog