Skip to main content
GullySystem
Retail

Product Management for Toy stores

Maintain the item definitions used by sales, purchasing and stock.

Inventory Management

Does this function belong in your operation?

Use when several business processes need the same product or service definitions.

An item, service code or variant is added or changed.

Each toy is held by brand, character, age band, piece count and price, with photos for the shelf and for online lists. A Lego-style set and a soft toy follow different fields. Staff find a gift by age.

Bring the records the workflow depends on.

  • Item codes
  • Units and variants
  • Pricing and tax references

Outputs to check

  • Controlled item and variant catalogue
  • Unit and classification reference
  • Item-change approval history

Follow the product management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Request the item

    Identify its business use and check for an existing equivalent.

  2. 2. Define attributes

    Set units, variants and required classifications.

  3. 3. Review settings

    Check price, tax and stock-related references with the responsible owners.

  4. 4. Approve use

    Release the item to permitted transactions.

  5. 5. Maintain history

    Control changes and retirement without rewriting earlier documents.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Counter or sales staff

Finds the item by whatever they call it, and sees the rate and what is in stock.

Store and purchase

Adds new items with their units, rates and reorder levels before the first delivery arrives.

Owner

Controls who may change a rate. In most shops that is a very short list.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Duplicate item discovered

Review linked transactions before merging or retiring a code.

Unit changes after use

Preserve historical quantities and define any conversion for future entries.

Item discontinued

Restrict new use under the agreed rule while retaining old orders and stock history.

Can this work independently?

The catalogue can exist independently, but sales, purchasing and stock must use its identifiers to share records. Prices and taxes may be maintained in separate controlled settings. Adding an item does not create opening stock or confirm that it is available to sell.

Systems and records it connects with

  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Purchase order management: Authorised supplier commitments and open line balances.
  • Barcodes and labels: Item-code mappings and verified printed-label values.

Configure, test and introduce the workflow.

  • We look at your sheet and counter software. You provide an export, and we report on duplicates and gaps.
  • A coding scheme and categories are proposed. You approve them before anything is loaded. Duplicates are merged with your staff. Each decision is logged for later reference.
  • A sample of items is loaded into a test copy. You check units, rates and tax codes. Billing and stores read from the new list. A short session for each team closes the step.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Item codes are unique.
  • Units remain consistent across transactions.
  • Inactive items follow the agreed transaction rule.
Toy stores

How the business operates.

A toy store lives on peaks. A quiet shelf in spring becomes a queue in the weeks before a gifting season. Brands, licensed characters and fashions change fast, and last year’s best seller can become this year’s clearance rack.

Toy catalogue by brand, age band and character

Hold each toy with brand, licensed character, age band, battery need, pack size and barcode, so a parent can be shown the right shelf.

Seasonal buying plan

Plan orders by line against last season’s sell-through, and mark which lines need a pre-season order from the distributor.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Toy catalogue and age bands. Each toy holds brand, licensed character, age band, battery need, small-parts warning, pack size and barcode, and a photograph prints on the shelf label for the bay.
  • Seasonal buying plan. Compare last season’s sell-through by line against current stock and open orders, set pre-season quantities, and mark jigsaw, plush and ride-on lines for early distributor booking.
  • Brand and distributor orders. Raise orders with delivery windows, carton minimums and brand discounts, then follow each distributor’s outstanding lines until the last carton is received and the invoice is matched.
  • Receiving with piece checks. Open each carton against the order. Count the pieces in every set. Photograph crushed packs and loose battery covers, then raise a supplier claim that carries the carton number, the photographs and the count of pieces found.

Operational bottlenecks to check

Seasonal stock is bought blind

Orders for the gifting peak are placed months ahead from memory of last year. Nobody can see which lines sold through. Others stayed in the backroom all winter.

Pre-orders and deposits go astray

A parent pays a deposit on a launch toy. The brand ships late or short, and the shop cannot say which customer is first in line.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Season plan

    The buyer reads last season’s sell-through by line and brand, then sets quantities for the gifting peak before distributors close their booking windows. Data leads the plan.

  2. 2. Ordering

    Purchase orders reach each brand distributor with delivery windows, carton minimums and trade discounts, and launch toys such as a new plush line are flagged for pre-order.

  3. 3. Receiving

    Cartons are opened against the order. Set contents are counted piece by piece. A crushed pack, a loose battery cover or a short piece bag is photographed and held for a supplier claim before the set reaches a shelf.

  4. 4. Shelving and display

    Toys go to a bay by age band and brand, from baby rattles to teen model kits, and each display sample is logged with its shelf.

  5. 5. Selling

    The counter bills the toy, adds gift wrap and a card as chargeable lines, applies a voucher, and takes a layaway or pre-order deposit on the same receipt.

  6. 6. After the sale

    Returns are judged by condition. A recall lot or a clearance line is flagged on the record, and the owner sees what was pulled and what still stands on the floor.

Industry reports to connect with

  • Sell-through by brand and age band
  • Pre-orders open and allocated
  • Layaway balances and collection dates
  • Open-box returns by decision

Questions before implementation.

When should toy stores consider product management?

Use when several business processes need the same product or service definitions. An item, service code or variant is added or changed.

What should we bring to the requirements discussion?

Bring anonymised examples of Item codes; Units and variants; Pricing and tax references. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Maintain the item definitions used by sales, purchasing and stock. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An item catalogue does not itself manage stock movements or fulfilment.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Item codes are unique. Use this check when reviewing the first working version.

Talk to us

Discuss product management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements