Answer first
Retail teams should make a drawing board planogram input sheet a controlled, SKU-level record for testing a proposed shelf placement. Start with the exact sellable configuration, item identity, retail-pack dimensions, proposed orientation, channel, destination, and known fixture or replenishment limits. Give each important field a source and date. Then separate verified facts from assumptions that still need a decision.
The sheet is an input to a planogram, not proof that a product will fit every fixture, sell, remain available, satisfy a destination requirement, or be accepted for ranging. It should end with one visible status: ready for planogram test, usable with named assumptions, waiting for clarification, or not suitable for this placement.
For a drawing board, “how large is it?” is not enough. The planner needs to know which retail pack was measured, whether it stands or lies flat, whether an observed hanger matters to the proposed fixture, where the barcode sits, and how the shelf could be replenished. A family name, old image, or related sample does not establish those facts for the current configuration.
Give every row one configuration key: internal SKU, supplier reference where available, variant, retail-pack or artwork revision, and sample or record date. This is the basis for matching later data to the reviewed pack.
Define the decision and record boundary
State the decision before collecting data. The team may be asking whether one drawing-board SKU can be tested in a named bay, whether variants can be compared, or whether a draft layout has enough inputs to move to review. Do not blend those questions. A sheet that mixes a retail-pack fact, a case-level figure, and a future assortment assumption may look complete while being unreliable.
At the top, add a version date, review owner, retailer or channel, destination if known, and fixture context. Label important values by source: physical sample, approved artwork, supplier specification, retailer master-data extract, carton record, or planner assumption. A source also needs a date and configuration link. A blank source is not neutral; it means the value has not been established for this record.
Name retail, shelf, and replenishment units separately
First define the sellable unit, the unit the channel expects to scan or sell. Then define the shelf presentation unit, the physical unit that occupies the fixture. Finally, define the replenishment unit, such as a case, inner, tray, or other level used to supply the shelf. They may be identical, but do not assume they are.
A retail pack may sit one by one on a shelf while replenishment arrives in a case. Another configuration may remain in a tray only when that presentation is supported and accepted for the channel. Record the reviewed arrangement, not a presumed one. A carton photo does not establish that a tray is display-ready, and a related SKU with a hang tab does not establish that the reviewed drawing board has one.
Use a name colleagues can reconcile: family, internal SKU, retailer item number if assigned, variant, pack revision, and image or artwork reference. If identity is uncertain, mark the row “hold—identity not reconciled.”
Keep product facts separate from retail choices
Pack height, width, depth, barcode face, and a hanger observed on the reviewed pack are product inputs. Number of facings, shelf level, adjacent items, ticketing, security method, and promotional space are retailer choices. Use different columns or sections for them.
Measure retail-pack data in a repeatable way
The most useful drawing board merchandising dimensions come from the exact retail package in the stated measurement orientation. Record whether the pack is unopened, whether a tab, handle, blister edge, or overwrap is included, and whether it was undamaged. Capture any protrusion that changes the outer extent; do not measure only the central panel.
GS1’s package and product measurement standard aims to provide a consistent, repeatable process for nominal measurements across retail and non-retail packaging levels. It also notes that the measurement might not represent the “as merchandised” or shelf orientation. [1] Preserve the physical retail-pack data, then add a separate field for the proposed shelf-facing orientation and usable fixture space.
Declare one unit system and label the order, for example height × width × depth. For a conventional base, GS1 describes height from base to top, width as the shorter side, and depth or length as the longer side. [1] Keep the physical measure separate from the shelf-facing measure.
Use a short measurement protocol
Lay the exact retail pack in the stated orientation and capture the maximum outer extent. Record the configuration key, method, date, observer, and whether the value came from a physical sample or another controlled source.
Never copy outer-case dimensions into a retail row. If no physical pack is available, enter supplier-provided data as provided but unverified. Do not let a system calculate definitive facings from it until the retailer decides that the evidence is adequate. A calculation can be mathematically correct and still be based on the wrong pack.
| Input type | What the record should show | Suitable planogram use | Do not assume |
|---|---|---|---|
| Measured retail pack | Configuration key, method, date, unit, outer dimensions, source | Preliminary shelf-fit and facing work, subject to fixture rules | The proposed display method is approved |
| Approved artwork or technical record | Revision, date, stated dimensions, identity link | Identity cross-check and pending-data row | The physical pack matches an older file |
| Retailer master-data extract | Item identifier, field date, owner, validation status if known | Matching the retailer’s item record | It reflects the latest packaging revision |
| Case or inner-pack record | Packaging level, quantity, outer dimensions, source | Replenishment discussion | Case values describe the retail unit |
| Planner estimate | Assumption owner, reason, date, review deadline | Clearly labelled scenario work | It can become a product specification |
Use a written source and date. Do not silently compare an estimate with a sample measurement.
Capture identity, barcode, and shelf-facing information
A planogram row should let store, replenishment, e-commerce, and buying teams locate the same item. Include the internal SKU, retailer item number where assigned, retail-pack code or GTIN where used, pack or artwork revision, and image reference. GS1 defines a GTIN as an identifier for trade items that may be priced, ordered, or invoiced in the supply chain. [2] Use a neutral descriptor, not shopper claims or feature assumptions.
Record barcode location as a field, not a guess. State the face that carries the code, whether it would remain accessible in the proposed placement, and whether that observation comes from a sample, artwork, or record. The sheet should expose a handling question early; it does not certify scanning performance. Link any retailer-specific barcode rule rather than presenting it as universal.
For a U.S. children’s-product route, tracking-label requirements can be relevant to the exact product and packaging. CPSC says required distinguishing marks are visible and legible, permanently affixed to product and packaging to the extent practicable, and contain identifying information. [4] A planogram sheet can record an observed label location and assign a compliance owner. It cannot decide whether the item is in scope or meets applicable obligations.
Describe the front face operationally
Record the proposed front-facing side, shelf or hook orientation, visible window if present, and barcode side. Do not treat that description as a claim about appeal, suitability, safety, or demand.
Treat standing, hanging, and angled presentation as configuration- and fixture-specific. A tab may be folded, revised, absent on the sample, or unsuitable for a retailer’s fixture. Write “hanger observed on reviewed sample,” not “hook-ready,” unless the retailer has confirmed the fixture application.
At this stage, teams can email Toywink at info@toywink.com for configuration-specific inputs needed for an internal planogram review. Include the SKU or available reference, variant, channel, destination, shelf or fixture context, and requested dimensions, pack images, or documents. Request clarification only; do not assume price, MOQ, availability, production timing, features, market approval, or final packaging.
Build shelf-space calculations from declared assumptions
A planogram needs a product dimension, fixture constraint, proposed orientation, and stated allowance. Make all four visible. Clearance for dividers, ticket strips, or fixture geometry is a retailer scenario input, not a product specification.
For shelf placement, record usable width, depth, and height; shelf level; fixture type; proposed orientation; and clearance assumption. For a hook or peg, record the retailer’s fixture rule, observed hanging feature, proposed hanging point, and permitted depth where known. If only product data is available, the appropriate result is “awaiting fixture confirmation.”
A simple internal scenario can calculate tentative facings as usable shelf width divided by stated front-facing width, then round under the retailer’s rule. Do not round up automatically. If a pack is angled, overlapped, placed in a tray, or held behind a divider, simple division may not represent usable space. Flag it for a mock-up or visual-merchandising review.
Add replenishment context without creating an order plan
Keep replenishment separate. Record a case or inner quantity, outer dimensions, and case identifier only when configuration and source are known. Ask whether staff can replenish in single units, whether the shelf unit depends on a tray, and whether retail and case identities reconcile. A case quantity is not a forecast or order recommendation.
| Planogram choice | Inputs needed before review | Useful output | Hold or escalate when |
|---|---|---|---|
| Single upright shelf unit | Retail-pack dimensions, natural base, proposed face, usable shelf space | Tentative facing width and physical-fit question | Pack cannot stand as proposed or clearance is unknown |
| Flat shelf stack | Pack depth, retailer stacking rule, shelf height, review owner | Scenario for shelf footprint | Stacking or stability basis is not established |
| Peg or hook placement | Observed hanger, pack width/depth, fixture rule, barcode face | Fixture-compatibility question | Hanger or fixture application is unconfirmed |
| Tray or display presentation | Retail and tray identities, display approval, outer dimensions, replenishment route | Separate display-unit scenario | Tray status or included quantity is uncertain |
| Mixed-variant block | Each variant’s identity, dimensions, front face, source status | Comparable SKU-level rows | A family name is substituting for data |
This LCD tablet retail shelf data comparison is a decision aid, not a fixture specification. It shows what should be known before a layout moves beyond an idea.
Include destination and governance fields without overclaiming
A planogram input is not a compliance file, but it should preserve destination context. Record the intended market or mark it “not confirmed,” the channel, and the owner for product and packaging review. The European Commission explains that the EU General Product Safety Regulation aims to ensure only safe products are available on the market and points businesses to product-safety obligations. [3] That is a reason to link a shelf-data record to responsible review, not to make a regulatory conclusion in the sheet.
Use neutral fields: “destination stated by buyer,” “label or artwork reference supplied,” “document request routed,” and “review owner.” Do not state that an item is compliant, approved, tested, or certified; link to a controlled conclusion if one is available for the exact configuration and market. Keep shopper claims outside the layout record.
Resolve conflicts with a small exception log
Common issues are an old pack measurement, barcode on another face, conflicting dimensions, case quantity that no longer matches the pack, or an image from another revision. Do not overwrite a discrepancy. Create an exception line with the affected field, competing sources, configuration scope, owner, date raised, and evidence requested.
Use a restrained status vocabulary: verified for this record, provided but not physically verified, assumption for scenario, conflict open, and not supplied. Close a conflict only when the source is reconciled for the exact configuration. If packaging changes, issue a new sheet version or change record. This preserves history without suggesting that an earlier planogram describes a current SKU.
Planogram input sheet checklist
Use this toy planogram buyer checklist before sending a row to a planner or retail partner:
- Confirm scope, channel, destination, fixture context, owner, date, and version.
- Identify one retail configuration with SKU, available retailer item number, variant, pack or artwork revision, and relevant trade-item code where used.
- Name sellable, shelf-presentation, and replenishment units separately.
- Record height, width, depth, unit, method, date, source, and any protrusion affecting the outer extent.
- State shelf-facing orientation separately from measurement orientation, and label it as a planning choice.
- Capture barcode face and observed label location where relevant; route questions to the responsible owner.
- Link the current image or artwork revision as a reference, not proof that it matches the pack.
- Record usable fixture dimensions, clearance assumptions, proposed facings, and the calculation or mock-up requirement.
- Keep case or inner quantity and outer dimensions in a separate replenishment field with their own source.
- Mark material fields as verified, provided but unverified, assumption, conflict, or not supplied; assign owners for gaps.
- Add destination and governance owners without declaring compliance or copying claims into the sheet.
- Record one release state: ready for planogram test, usable with assumptions, waiting for clarification, or not suitable for this placement.
The checklist controls information quality. It is not a declaration that a drawing board has passed product, commercial, market, or fixture review. A documented hold is better than a confident-looking layout based on unknown identity or dimensions.
Keep the record current through short reviews
Review the sheet before layout, after a sample or artwork update, before channel release, and when configuration changes. Keep prior dated versions. Ask whether the configuration remains the same, dimensions are comparable, fixture constraints are confirmed, and destination questions have owners. A family can share a name while variants have different footprints, so make placement decisions by SKU or explicitly linked configuration.
FAQ
What is the minimum data for an educational toy shelf planning sheet?
Record an exact configuration identifier, retail-pack dimensions with units and source, proposed orientation, shelf or fixture context, barcode-face information where known, and an explicit status. Add channel, destination, owner, date, and open assumptions. This supports a planning discussion; it does not establish approval for sale, fit, or a market.
Should a team use supplier dimensions or measure a drawing-board sample?
Use both where possible and label them differently. Supplier-provided data can support early comparisons. A measurement of the exact retail pack offers a stronger physical-fit input when its method, date, and configuration are recorded. If figures differ, open an exception rather than silently replacing one with the other.
Can one row cover several drawing-board variants?
Only if the relevant retail-pack configuration is evidenced as the same and the retailer accepts the grouping. Colour, artwork, included items, barcode, packaging revision, and dimensions can differ. In most cases, create a row for each sellable configuration and use a family field only for navigation.
What happens if fixture information is unknown?
Enter the available product facts, leave fixture-dependent calculations unresolved, and mark the row “waiting for fixture context.” Do not invent shelf depth, peg type, clearance, or facings. The planner can attach the retailer’s fixture data or arrange a physical test under its own process.
Does this sheet prove destination compliance?
No. It can record the intended market, an artwork or label reference, document-request status, and the responsible reviewer. It cannot conclude that a SKU is compliant, safe, approved, certified, or lawful for a market. Those conclusions depend on the exact configuration, intended route, applicable rules, evidence, and responsible review.
Make the handoff usable, not overconfident
Good B2B shelf planning information gives a planner identity, physical data, orientation, source quality, fixture assumptions, replenishment context, and unresolved issues in one concise record. It does not turn a supplier description into a store instruction, or a sample into a permanent specification.
Before release, check the version date, source labels, calculation assumptions, and exception owners. If the retailer changes the shelf map, log that as a retailer scenario rather than changing product facts. The result keeps “what was observed” distinct from “what the channel chose to test.”
For a configuration-specific discussion, contact Toywink by email. Include the drawing-board reference, available pack or artwork version, target destination and channel, shelf or fixture context, and unresolved fields. An inquiry is not a quotation, product approval, compliance conclusion, MOQ, availability, production date, or delivery commitment unless separately confirmed in writing for the relevant configuration.