Toy Store POS: Age-Range Categories, Brands and Collectibles

To organize a toy store, pick one main category by product type (building sets, plush, games, arts and crafts), then record age range and brand as separate fields on each item instead of building a category for every combination. That keeps the list short for staff and still lets you answer the two questions customers ask most: “What is good for a 6-year-old?” and “Do you have anything from this brand?”

This post covers two angles that matter for toy shops: age-range and brand categories, and collectibles and limited releases. For the holiday rush, back-room counts, layaway and switching from an older EPOS, read our earlier post on toy store POS and holiday rush prep. Where Retailer OS does something about a topic, I say so. Where it does not, the advice applies to any POS you evaluate.

How should a toy store organize categories by age range and brand?

A category is the group an item belongs to for shelving, reporting and ordering decisions. In a toy store the temptation is to make a category for every combination, like “Building Sets, Ages 6–8, Brand X.” With 8 product types, 5 age bands and 40 brands, that is 1,600 possible categories, and most would hold three items.

Use a simple split instead:

• Product type is the main category. Aim for 8 to 12: building sets, plush, dolls and action figures, games and puzzles, arts and crafts, outdoor and active, STEM and science, baby and toddler, collectibles, seasonal.
• Age range is a second field with fixed bands, such as 0–2, 3–5, 6–8, 9–12 and 13+. Use the age printed on the box, not your own guess.
• Brand or license is a third field, spelled one way. “Brand X,” never “BrandX” in one place and “Brand-X” in another.

Why product type first? Because your ordering, markdown and shelving decisions follow it. You reorder building sets as a group, mark down seasonal as a group, and plan floor space in product types. Age range and brand help the customer and your reports, but they should not carve up your shelves.

One honest note about the product. Retailer OS has items with SKUs, barcodes, variants and per-location stock, plus dashboards, reports and saved views. It does not list a dedicated age-range field. If you want age bands, put them in the item name or the field your POS offers, and in a demo ask exactly how a report splits by category, brand and age. If the answer takes more than a minute, the report will not get used.

Name items so a gift shopper can be helped fast

A parent at the counter says “something for a 5-year-old who likes dinosaurs.” Your cashier types “dino” and needs the right items to come up with the age band visible. A pattern that works is brand, product, theme, age band: “Brand X Dino Excavation Kit, 5+.” Keep it the same on every item, and put the item’s age warning in the name only when it is a safety issue, such as small parts for under 3s.

Which numbers should you read by category in the holiday season?

Three numbers do most of the work. Check them by product type every week from mid-November and every two weeks after New Year.

• Sell-through: units sold ÷ (units sold + units on hand), over the same period. If you received 100 plush toys, sold 60 and have 40 left, sell-through is 60%. Anything under 40% by mid-December needs a decision.
• Weeks of supply: units on hand ÷ weekly units sold. If you have 90 puzzles and sell 15 a week, you have 6 weeks of supply. In December, anything over 8 weeks is probably overbought; anything under 2 is about to run out.
• GMROI: gross margin dollars ÷ average inventory at cost. It tells you how hard each inventory dollar worked.

Here is a worked example for two categories over a quarter. Building sets: sales $18,000, cost $10,800, so gross margin is $7,200 (40%). Average inventory at cost was $6,000, so GMROI is 7,200 ÷ 6,000 = 1.2. Plush: sales $9,000, cost $4,500, gross margin $4,500 (50%). Average inventory at cost was $2,500, so GMROI is 4,500 ÷ 2,500 = 1.8. Building sets sell more dollars, but plush works each inventory dollar harder. That is information you can use when deciding where to put next year’s open-to-buy.

Retailer OS has dashboards and reports, saved views and scheduled email digests, so you can save the product-type view you read every Monday and have the numbers arrive in your inbox. Reorder points are set per item. With a Messaging & AI plan (from $39.99 a month), demand forecasting and reorder suggestions are also available, and you make the buying decision.

How do you handle collectibles and limited releases?

Collectibles are a different business from toys. The buyers are often adults, the items are scarce, prices are higher and the arguments are louder. A limited release is an item you receive in fewer units than people want. The risk is fairness and theft, not margin.

Write the rules before the first box arrives:

• Set a per-customer limit, such as one per person, and say it on the shelf.
• Keep a written list for requests, in order of when they were made. Do not rely on memory.
• Take a deposit to hold a unit, such as 25% of the price, with a hold deadline of 7 days after arrival.
• Keep held units off the sales floor and out of the sellable count.
• Do not list the item online until the shelf and the request list are covered.
• Decide whether opened or unsealed collectibles can be returned. Most shops say no.

Here is the math. You receive 12 units of a figure that costs $38.00 and sells for $64.99, and you have 40 requests. At one per customer, the first 12 people on the list get one. A 25% deposit is $16.25 each, so you hold $195.00 in deposits, and the margin on each sale is $26.99, or 41.5%. If three people miss the deadline, those three units go to the next three on the list, and you have lost nothing.

For high-value items, stock tracking by unit matters. Retailer OS supports serial-number tracking and available-to-promise, which is the stock you can still promise to a new customer after units are set aside. For a collectible that sells at $200 or more, a serial number on the record means a return or a theft claim points to one specific unit. Retailer OS also has customer profiles with purchase history, gift cards and store credit as a tender, and customer accounts. A deposit on a held unit is a process you set up using those tools, and I would ask for that exact flow in a demo, since a preorder feature is not something the product lists.

When a unit arrives and the customer needs to know, texting needs a Messaging & AI plan. Starter is $39.99 a month and includes 100 texts and 500 emails a month; extra texts are billed per use.

How should you mark down seasonal toys without losing money?

The first week of January is when overbought toy stock turns into cash or into a storage bill. Set a markdown schedule in November, with dates and floors, so nobody makes it up under pressure. A floor is the lowest price you will sell at, set above cost unless you have decided to take the loss.

Take an item that costs $12.00 and sells for $24.99. Its margin at full price is $12.99, or 52.0%. Now walk it down:

• 25% off on December 26: $18.74, margin $6.74, or 36.0%.
• 40% off on January 15: $14.99, margin $2.99, or 19.9%.
• 60% off on February 1: $10.00, which is $2.00 below cost, a loss of 20%.

The third step only makes sense if the storage cost or the cash you free up is worth more than $2.00 a unit. For a case of 24, that is $48.00 of loss to clear the shelf. Sometimes that is right. Decide it on purpose. Sell-through by category tells you where to start: markdown the types with under 40% sell-through first, and leave the ones that are still moving.

At the register, price overrides and discounts should be limited by role, so only a manager can change a markdown. Our post on price overrides at the register covers who should be allowed to do what.

What should a toy store look for in a POS?

This is the buying criteria that matter for a toy shop, in no particular order. Use them on any system, including ours.

• Fast item search that works on partial names, because gift shoppers do not know the exact product.
• Item fields or categories for product type, age band and brand, and reports that split on them.
• Gift cards and store credit that work in a split payment.
• Serial-number tracking and a way to hold stock for a customer without selling it.
• Reorder points per item and purchase orders with receiving, so cost updates when the box is opened.
• Roles that limit price overrides, discounts and returns.
• Offline selling on the main register, since the busiest days are when the network fails.
• A clean CSV import for items and customers if you are moving from an older system.

How does Retailer OS handle the parts of a toy store?

• Catalog: SKUs, barcodes and label printing, variants, units of measure, and CSV import for items, customers and vendors.
• Stock: per-item, per-location stock with a movement ledger, purchase orders, receiving, reorder points, stock counts and transfers, including in-transit tracking.
• Collectibles: serial-number tracking and available-to-promise.
• Tenders: cash, card, gift card, store credit and customer account, with split payments, returns and exchanges.
• Customers: profiles with purchase history, loyalty programs, gift cards and referrals. Texting and email campaigns need a Messaging & AI plan.
• Reports: dashboards, saved views and scheduled email digests.
• Offline selling: the desktop app keeps ringing sales when the internet drops and syncs on reconnect. The iOS app has no offline mode.

If you also sell online, the online store is a paid add-on at $99.99 a month and runs on the same catalog and stock as the register. Amazon and eBay are separate paid add-ons at $99.99 a month each.

What does Retailer OS cost for a toy store?

It is priced per store and per user seat: $99.99 a month for the store and $9.99 a month per user, with the owner counting as a seat. A single shop with an owner and two cashiers has three seats: 3 × $9.99 = $29.97, plus $99.99, so $129.96 a month. Add a Messaging & AI plan at Starter ($39.99 a month) and the total is $169.95. There is no platform fee and no cut of sales, and card payments run on your own Stripe account, with Stripe billing its processing fees directly. Full details are on the pricing page, and the small business POS page explains how a one-counter shop gets set up.