Private label packaging control

Multi-SKU Private Label Tissue Launch Checklist

A coordinated tissue-range launch needs a common project record and a separate release decision for each SKU. Share reusable artwork and commercial assumptions where they genuinely match, but keep dimensions, counts, identifiers, packaging proofs and quantities visible by variant. GS1 GTIN management covers changes such as declared net content, case quantity and predefined assortments. The matrix below is a procurement planning tool for avoiding one unfinished variant delaying or contaminating the whole launch.

Include these records in your tissue RFQ Browse product formats ↗

Last reviewed: 10 October 2026
Reviewed by: VELUPLY editorial guidance
Evidence rule: SKU and market matched

BUYER CHECKLIST

Variant matrix: keep one column or row set per SKU

Product definition: SKU ___; intended use/channel ___; product format ___; fiber declaration ___; ply ___; sheet dimensions ___; sheets or pulls per pack ___; pack dimensions ___. Select the minimum launch range that covers distinct buyer needs. A new front-panel color without a differentiated use or offering should be justified before adding operational work.
Pack and identity: Dieline revision ___; artwork revision ___; consumer identifier ___; case identifier if required ___; pack/case quantity ___; assortment identity where relevant ___. When counts or configurations change, review the applicable GTIN rule with the responsible owner. Do not let a shared design template imply that every variant can share the same commercial identity.
Evidence and approvals: Paper sample reference ___; filled-pack sample ___; barcode evidence ___; claim-dossier reference ___; destination-copy approval ___; accepted specification revision ___. Mark each field approved, conditional or open with an owner. A signature on the range cover sheet should not silently override an open field in one variant.
Commercial dependencies: Quoted quantity by SKU ___; packaging minimum or setup item from supplier ___; shared setup allocation ___; production availability confirmation ___; release deadline agreed with supplier ___. Keep supplier-confirmed terms separate from buyer targets. A total range quantity does not establish that each printed pack meets its own commercial requirement.
Shipment and receiving: Cartons by SKU ___; case dimensions ___; packed gross weight ___; shipment split proposal ___; receiving master-data reference ___; label mapping ___; stock destination ___. Recalculate the shipment using actual approved case data. A visual range presentation cannot establish carton utilization or available warehouse space.

BUYER CHECKLIST

Resolve launch dependencies without losing control

Common component changes: Identify every SKU using the changed board, film, language panel or shared claim. Review the affected records together and carry the corrected revision into each variant. Keep unaffected approvals visible so a small common change does not accidentally erase decisions already supported by evidence.
One variant remains open: Compare a partial launch with waiting for the full range. Record incremental freight, separate receiving work, packaging commitments and commercial acceptance from the buyer. Release ready SKUs only when their records and the revised shipment plan are accepted; do not promise a split schedule without supplier confirmation.
Retail assortment differs from shipment mix: Decide whether mixed cartons are shipping arrangements or predefined sellable assortments. Their orderable identities and receiving data may differ. Ask the identifier owner to review the applicable GS1 assortment and hierarchy rules before printing a bundle label or treating a mixed pallet as a retail product.

DECISION POINTS

What to align before the next commitment.

Illustrative range release decision

Consider a flat facial tissue box, a cube box and a pocket pack with one visual brand family. The cube artwork may still lack a confirmed barcode location while the others are ready. A useful decision records whether the buyer accepts a two-SKU launch and what that does to shipment economics. It is not a promise that such a split is available.

Allocate setup costs transparently

Ask the supplier to itemize shared and variant-specific setup costs. Record the allocation method used for your comparison, such as equal allocation or allocation by ordered units, and show its effect on each SKU. Do not hide a low-volume variant’s packaging expense inside the strongest seller merely to make every unit price look similar.

Keep a launch packet for replenishment

Archive the approved matrix, each specification, artwork, reference sample and shipment record after release. At reorder, start from those versions and list changes rather than rebuilding from memory. The packet is especially useful when one range contains different pack structures whose suppliers or proof routes do not change together.

WORKING SEQUENCE

A clearer route from question to decision.

01
Define the commercial reason for each starting SKU and create a variant matrix. Confirm actual product specifications and packaging routes before committing to range-wide artwork.
02
Separate common tasks from variant-specific approvals and assign owners. Collect quoted quantities and dependency dates directly from the relevant supplier rather than generating a schedule from assumptions.
03
Review each SKU against sample, copy, barcode and shipment readiness. Work through partial-launch and full-launch options with explicit costs and buyer acceptance.
04
Freeze the accepted scope and release versions, then reconcile packed quantities and receiving records by SKU. Preserve the launch packet and reopen affected approvals when the next order changes configuration.

DIRECT ANSWERS

Questions buyers ask before moving forward.

01Can several SKUs share one packaging MOQ?+

Only if the supplier confirms that commercial arrangement for the actual print and packing route. Ask for minimums and setup charges by variant and any shared component. Do not infer a combined MOQ from the total order size.

02Should every variant be ready before shipping anything?+

Choose according to the buyer’s range requirements and the confirmed costs and feasibility of separate shipments. A staged release can be useful, but each released SKU and the revised shipment plan still need their own approval.

03How do we compare different case quantities?+

Convert quantities and prices onto a defined pack or finished-sheet basis, then keep freight, setup and other scope visible. Use the approved count for each SKU. Equal carton totals do not imply equal paper quantity or equivalent fulfilment work.

SOURCES & LIMITS

Trace the question and the verification.

The worksheets and release decisions are buyer planning recommendations, not records of a completed VELUPLY order. Confirm the applicable requirements with your trading partner and evidence provider.

01
GS1 Logistic Label Guideline, release 1.3
Standards verification · accessed 2026-10-10
02
GS1 GTIN Management Standard, release 1.1
Standards verification · accessed 2026-10-10