Answer first
Buyers should plan a carton assortment brief as a controlled instruction set, not as a list of colours or a final purchase-order attachment. It should state which exact sellable SKUs are in scope, how many of each belong in every carton or shipment, which item and case identifiers apply, and who may approve a substitution. It should also separate three decisions that are often blurred: the consumer-facing range, the inbound shipping configuration, and the retailer’s receiving or replenishment rule.
Begin with the retailer’s intended sales unit and work upwards: approved SKU record, inner pack if used, shipping case, then pallet or shipment allocation. For every level, record confirmed identifiers, counts, dimensions and weights. GS1 describes a trade-item hierarchy as linked GTINs for specific units, packs, cases and pallets; each is a distinct packaging level [1].
The goal is not to predict which variant will sell best. The goal is to make the buyer’s current allocation decision visible, measurable and changeable without creating an undocumented mix. A strong lcd writing tablet assortment brief therefore names the commercial objective, allocates quantities by SKU, identifies allowed and prohibited mixes, shows carton arithmetic, and attaches a versioned approval record. Product wording, labels, instructions, warnings and market documentation must still be reviewed for the exact SKU, destination and retailer requirements.
Treat assortment, packaging and allocation as separate layers
A range can contain several variants while the warehouse receives one case format. The brief should label each layer explicitly.
- Sellable SKU layer: the individual item record that a consumer-facing channel, school buyer or retailer will list, scan or replenish. It needs its own confirmed identifier and approved product information.
- Pack layer: an optional intermediate grouping. It may be used for handling, merchandising or an agreed order unit, but it is not automatically a consumer unit.
- Case layer: the inbound case used for shipping and receiving. It can be a homogeneous case or, if agreed, a mixed case with a stated composition.
- Shipment layer: cases allocated to a purchase order, destination, store cluster, fulfilment route or pallet pattern.
Do not infer these layers from a colour name, artwork file or sample photo. GS1 US distinguishes an “each,” inner pack, case and mixed case, and explains that a mixed case contains more than one type of each and more than one GTIN [2]. Confirm the retailer’s own data, label and receiving rules.
The practical implication is simple: write “mixed case permitted: yes/no” near the case configuration, not only in an email comment. If the answer is yes, supply the exact count of every contained SKU. If the answer is no, state whether cases may be mixed only on a pallet, at a shipment level, or not at all. Ambiguous phrases such as “assorted colours” or “send a balanced mix” cannot tell a receiving team what is inside a carton.
Define a variant without assuming its attributes
For this guide, a variant is a separately managed SKU. Its difference—such as an approved size, finish, pack presentation, language or accessory configuration—must be documented, not inferred from category terminology. A different identifier, retail pack, instruction set or market label can create a separate operational record.
Use a neutral internal SKU code and approved short description. Link the current specification, artwork, product-data sheet, label proof and approved sample reference so a mismatch can be spotted before packing.
Start with the buying decision, not the carton capacity
Carton capacity should not decide the range by itself. First describe the destination and uncertainty the allocation must absorb. A retailer may need store replenishment, an e-commerce team a warehouse split, an educational publisher a defined set, and a distributor a channel-neutral master case. These uses only determine the information the buyer needs to request; they do not prove product suitability.
Write a testable objective: “Allocate approved SKUs for the specified channel while preserving the retailer’s receiving rule and traceability record.” Identify the owner, destination, channel, order status, planning horizon and demand unit. Consumer units, inner packs, cases and pallets are different units.
Then rank each SKU’s role before selecting its quantity. A useful role set is:
- Core: required in the initial range under the buyer’s current plan.
- Support: included to complete an agreed choice set or channel requirement.
- Test: deliberately limited, with a defined review point.
- Hold: documented but excluded from this order.
These are planning statuses, not claims about demand, quality or ranking. Note whether a variant is required in every destination, selected destinations or a later order; this keeps a “test” item from entering every carton by default.
Convert preference into an explicit allocation rule
The buyer may assign quantities by forecast, store count, shelf capacity, campaign allocation or an agreed proportional split. Whichever rule is selected, state it in a way that another person can recalculate. For a proportional approach, use:
planned units for SKU = total planned sellable units × approved SKU share
Decide the rounding method, reconcile it to case quantity, and name any adjusted SKU and reason. Do not silently change a planned split to fill a carton.
At this point, distinguish range share from case composition. A range share might be 60/40 across a complete purchase order, while each homogeneous case contains only one SKU. By contrast, a mixed case could have a fixed 3/3 composition yet be ordered in unequal numbers of cases. Both methods can produce the same total units, but the receiving, data and replenishment consequences differ.
Build a single source of truth for every SKU
Before carton math, compile a controlled SKU matrix from approved records. Use it to check the purchasing file, carton markings, warehouse instructions and product-information review.
Include buyer and supplier SKU; identifiers where assigned; approved description; destination; role; language/artwork version; selling-unit and case dimensions and gross weights; units per case; documentation/sample reference; owner; and a timestamped status. Leave unknown fields blank rather than guess.
Add an exception column as well. It should distinguish a missing value from a commercial decision still awaiting approval, such as an unconfirmed destination split or a proposed mixed-case composition. Assign an owner and a next action to every exception. This prevents a preliminary spreadsheet from being mistaken for a release-ready packing instruction. Where a retailer provides a product-information management template, map its field names to the buyer’s working matrix before an order is issued. Do not overwrite a retailer-required value with a supplier shorthand simply because the descriptions look similar. Retain the source file and date for values that may change, including dimensions, gross weight, pack count and artwork version.
Where relevant, make product and packaging traceability a review item, not a generic carton note. The U.S. CPSC says children’s-product tracking labels must be visible and legible and, to the extent practicable, permanently affixed to product and packaging; information includes the manufacturer, importer or private labeler, production location/date and batch/run or other source information [3]. This is not a universal template: the importer, category, market and SKU determine the review.
Apply the same discipline to warnings, instructions and online content. EU toy rules address economic-operator duties and require appropriate warnings and safe-use instructions to be legible, visible and intelligible; they also address online offers [4]. Check the current framework for the destination: a carton label does not replace SKU documentation.
| Decision point | Homogeneous case | Fixed mixed case | Mixed pallet of homogeneous cases |
|---|---|---|---|
| Contents | One confirmed SKU per case | More than one confirmed SKU, with stated count per SKU | Several confirmed case SKUs allocated at pallet level |
| Best fit to consider | One SKU per received case is preferred | Buyer wants a set assortment in each case | Several SKUs are needed but cases stay single-SKU |
| Data instruction needed | SKU/case relationship and count | Every SKU count and mixed-case identifier | Case counts by SKU and destination allocation |
| Main control question | Can the receiver handle this case quantity? | Can teams recognise composition and identifier? | Can cases and allocations stay separated? |
| Do not assume | That one case equals one sellable unit | That a colour ratio is enough to identify contents | That a mixed pallet is acceptable to every receiver |
Pause for a documented B2B review
Before release, retailers, schools, importers, distributors, educational publishers, e-commerce teams and private-label buyers can ask Toywink to review their brief against exact SKU records and an approved sample: email info@toywink.com. Include destination, channel, candidate SKUs, case rule and retailer template. This email-only request does not confirm availability, pricing, delivery or approval.
Turn the range into carton arithmetic
A writing tablet carton plan should show the arithmetic in a form a purchasing manager and packing team can both test. Start from the total required sellable units by SKU. Divide each SKU quantity by units per case for its approved case configuration. The result may be a whole number, a remainder, or an instruction to use a separately approved mixed case. Never solve a remainder by adding another variant without the buyer’s recorded approval.
For a homogeneous case, the core calculation is:
cases for SKU A = approved units of SKU A ÷ confirmed units per case of SKU A
For a fixed mixed case, calculate complete cases from every component. If it requires A×4 and B×2, the count is limited by the lower of A units ÷ 4 and B units ÷ 2, rounded down. Revise the total, use another approved route or hold the remainder.
Record the unit beside every quantity: “12” may mean eaches, packs, cases or pallets. If inner packs are used, list both inner packs per case and sellable units per inner pack. Totals must reconcile across levels.
A compact calculation block can include:
- total sellable units requested, by SKU and destination;
- units per inner pack, if an inner pack is used;
- inner packs per case or sellable units per case;
- full-case quantity and any approved remainder route;
- confirmed cases per pallet or layer pattern; and
- total cases, gross weight and cubic measurements.
Do not estimate logistics fields from a photo. They require a confirmed configuration. GS1 notes that orderable and shipping units need not be the same [1], so capture both flags or retailer equivalents.
Make mixed-case composition auditable
A mixed case needs an unambiguous line: “Case MC-01: 4 × SKU A, 2 × SKU B; total 6 sellable units.” Repeat it in the required order/data record and packing instruction, with the version. A 4/2-to-3/3 change is a new composition decision.
A useful controls block answers five questions: What may be mixed? At which level may it be mixed? What is the exact count of each SKU? What identifier refers to that configured case? Who may authorise a change? The responsibility must be named, because supplier, buyer, importer and retailer roles may differ by contract and market.
Keep display-ready configurations separate unless their construction and identifiers are approved. GS1 recognises a display shipper as a self-contained display shipping unit that may contain one or multiple types of eaches [2]. This does not establish any specific carton’s retail suitability; its data and pack-out need their own record.
Carton assortment brief checklist
Use this concise checklist before submitting or revising the order instruction:
- Scope: destination, channel, buyer entity, order reference, status and revision date are named.
- SKU identity: buyer SKU, supplier SKU and applicable sellable/case identifiers are matched to the approved record.
- Variant boundary: every differentiating attribute comes from the exact SKU specification, approved artwork or sample record; no feature is inferred.
- Range roles: each SKU is marked core, support, test or hold, with the decision owner.
- Allocation rule: total units, share or other rule, rounding method and final adjustment are visible.
- Case route: homogeneous case, fixed mixed case or mixed pallet is selected explicitly; prohibited mixes are stated.
- Carton math: quantities reconcile from sellable units through inner packs, cases and shipment totals where applicable.
- Data and markings: dimensions, weights, identifiers and carton marks are sourced from current confirmed packaging data.
- Product-information review: instructions, warnings, labels, traceability and documentation are reviewed for the SKU and destination by the responsible parties.
- Approval and change control: named approvers, version, effective date and procedure for shortages, substitutions or artwork changes are included.
This checklist does not certify a product, label, shipment or market placement; it exposes decisions for the responsible reviewers.
Approve, freeze and change the brief deliberately
The LCD writing tablet SKU mix should be frozen only after relevant owners check composition, identifiers, labels and routing. Name the commercial allocation, product-data, packaging/operations, market/importer and purchase-order owners.
Give the brief a version and effective date. A change request needs old/new SKU, quantity, carton configuration, reason, documentation impact, owner and written approval. Route replacement SKUs, changed ratios, units per case, artwork or destination through it. Mark unconfirmed fields pending.
At goods receipt, compare agreed identifiers and composition to the receiving record, then log discrepancies by SKU and carton. This separates an allocation decision from an execution mismatch.
FAQs
What is the minimum information for a retail order brief?
It should identify buyer and destination, exact SKUs, requested units, case route, units per case, identifiers where assigned, allocation, documentation status, version and approver. Add retailer receiving, labelling and data fields. A total order quantity alone cannot communicate pack-out.
Should every variant receive the same number of units?
Not necessarily. Equal allocation is one rule; others may use store group, catalogue selection, existing stock or pilot scope. Show the rule and final SKU quantities, including any complete-case adjustment.
Is a mixed carton the same as a product variant assortment?
No. It is the selected range and quantities; a mixed carton is one physical route for multiple SKUs. The range may use homogeneous cases, fixed mixed cases, mixed pallets or approved combinations. Do not mistake an assortment ratio for a packing ratio.
Can the supplier choose substitutions when one SKU is unavailable or incomplete?
No substitution should occur without named buyer approval for a specific alternative. A substitute can affect identifiers, packaging, artwork, instructions, labels, destination review and receiving data.
How should a buyer handle a partial carton quantity?
Verify whether the retailer accepts the existing case rule, an approved mixed case, another approved orderable unit or a deferred remainder. Do not create a ratio merely to divide evenly. Record the route and approved quantity adjustment.
Do carton markings make a product compliant for every market?
No. Carton markings support logistics and identification, but do not establish that an SKU, pack, instructions, warnings or documentation meet every destination’s requirements. Review obligations with responsible parties. EU toy rules include economic-operator duties and requirements related to warnings and instructions [4].
Make the next order easier to execute
A reliable brief traces the range decision to the physical carton without assuming a variant’s contents, pack-out or market status. Exact SKU records, visible arithmetic, clear case composition and approvals give downstream teams the same instruction.
Retailers, schools, importers, distributors, educational publishers, e-commerce teams and private-label buyers can email info@toywink.com with SKU list, destination, case preference and retailer template. Toywink can discuss the B2B brief against exact documentation and approved samples; no pricing, availability, delivery or approval outcome is implied.
