Skip to main content
GullySystem
Retail

Loyalty and Offers for Toy stores

Apply customer reward and promotional rules to eligible purchases.

Retail and POS

Does this function belong in your operation?

Use when repeat purchases support a defined loyalty or promotional programme.

A customer earns or redeems a configured reward.

Parents earn points on toy purchases and receive offers around a child’s birthday or festival sales. Buy-two schemes on a brand are set per period. Staff apply them without a calculator.

Bring the records the workflow depends on.

  • Customer identifiers and permissions
  • Earning and redemption rules
  • Offer dates and exclusions

Outputs to check

  • Customer reward ledger
  • Offer application and redemption record
  • Expiry and reversal statement

Follow the loyalty and offers workflow.

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

  1. 1. Define the programme

    Approve earning, eligibility, redemption and expiry rules.

  2. 2. Identify the customer

    Use the permitted account or contact reference.

  3. 3. Record eligible purchase

    Calculate the reward from the accepted transaction.

  4. 4. Redeem under the rules

    Check the available balance and apply the authorised offer.

  5. 5. Reconcile changes

    Adjust returns, expiry and approved corrections with their source references.

Who uses the module, and who approves?

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

Counter staff

Types the number, and the offer is already on the bill.

Whoever sends the messages

Picks a list, such as customers who have not come since the last festival, and sends one message that suits them.

Owner

Reads two things: the regulars who have drifted away, and what the last scheme actually cost.

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.

Return after redemption

Apply the agreed reversal policy and show any resulting adjustment.

Duplicate customer identity

Review balances and permissions before merging accounts.

Offer withdrawn early

Record the effective decision and treatment of already accepted transactions.

Can this work independently?

Loyalty depends on eligible customer transactions and a permitted customer identifier. It can accept reviewed imports, but POS or invoicing links provide current earnings and redemptions. Messaging and refunds are separate processes; a reward balance is not automatically cash payable to the customer.

Systems and records it connects with

  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Product management: Item identifiers, units and controlled variant definitions.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.
  • Multi-outlet stock: Outlet quantities and acknowledged transfer movements.

Configure, test and introduce the workflow.

  • Rules matter here. Tell us how customers earn and spend points and which offers you run, and a written note comes back for approval.
  • Send phone numbers and names from wherever you keep them. A trial import arrives with duplicates marked. Counter staff bill a few sample sales. Points and offers apply, and corrections go into the setup.
  • You write or approve the wording. Templates for WhatsApp or SMS come back for the person who sends them.

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.

  • Rewards follow eligibility rules.
  • Redemption cannot exceed the permitted balance.
  • Returns apply the agreed reward reversal.
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 loyalty and offers?

Use when repeat purchases support a defined loyalty or promotional programme. A customer earns or redeems a configured reward.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer identifiers and permissions; Earning and redemption rules; Offer dates and exclusions. 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. Apply customer reward and promotional rules to eligible purchases. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Customer consent, promotion terms and financial treatment require approved business rules.

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. Rewards follow eligibility rules. Use this check when reviewing the first working version.

Talk to us

Discuss loyalty and offers 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