Managing Daily Gachapon Machine Counts
with AnyDB

Replacing manual floor counts with a mobile-friendly system for daily stock counts, machine refills, capsule sales, reporting, and purchasing signals.
Gachapon machine count and inventory system in AnyDB
  • Company

    Brick-and-mortar gachapon retailer

  • Team

    Not specified

  • Industry

    Retail and entertainment

  • Scale

    Around 200 machines with daily counts and refills

Keywords: Gachapon inventory management, daily stock count, machine inventory, capsule toy inventory, mobile inventory count, machine refill tracking, retail sales reporting

Location: Not specified

The company is opening a physical store with around 200 gachapon machines dispensing capsule toys from Japan.

Each day, an employee needs to walk the store and record the capsules remaining in every machine using a mobile device.

The counts must be fast while still supporting refills, purchasing decisions, and sales reporting by product, machine, zone, manufacturer, and period.

Result: A connected inventory system for manufacturers, products, machines, daily counts, count lines, and refills.

Operational Objective

Create a fast mobile count process and clean data for sales, refills, and purchasing.

In practice, that meant:

  • Track around 200 active machines
  • Connect each machine to its product, zone, position, and manufacturer
  • Create daily counts with the sale date prefilled
  • Generate one count line for every active machine
  • Let employees enter only the remaining quantity
  • Report sales by product, machine, zone, manufacturer, and period
Operational objective illustration
Manual machine count illustration

What They Tried at First

The owner had already planned Products, Machines, Daily Inventory, and Daily Inventory Lines.

The main challenge was preparing one line per machine so employees only entered the remaining quantity during the daily count.

The structure also needed to support refills, capsule sales, product stock, reporting, and future purchasing without complicating the launch.

Where the Operation Broke Down

The daily count would be too slow if employees had to prepare or manage machine details.

What broke:

  • Around 200 machines needed daily counts
  • Each machine needed a prepared count line
  • Machine and product details had to be prefilled
  • Employees should update only the remaining quantity
  • Refills needed separate tracking
  • Counts needed to support sales and purchasing

Operational impact:

  • Daily counts could take too long
  • Machines could be missed
  • Employees could change the wrong details
  • Inconsistent lines could affect sales reporting
  • Refill and purchasing signals remained unclear
  • Future stock calculations needed cleaner data

The Operating Model Designed in AnyDB

Manufacturers, products, machines, counts, count lines, and refills stay connected.

Manufacturers, products, and machines

Each manufacturer connects to its products, and each product connects to the machines where it is sold.

Daily stock count record

Each count records the sale date, employee, progress, capsules sold, and estimated sales.

Prepare Stock Count button

The button creates one prefilled line for every active machine, leaving only the remaining quantity to enter.

Mobile-friendly count entry

Employees follow a table-style list organized by zone or room while walking through the store.

Machine refills and product refreshes

Separate refill records show which product and quantity were added to each machine.

Reporting and sales visibility

Count lines support sales reporting by product, machine, zone, manufacturer, and period.

Connected gachapon inventory operating model

What Changed in Daily Work?

  • A new stock count is created each day
  • Every active machine receives a prepared line
  • Employees enter only the remaining quantity
  • Count lines follow the store layout
  • Refills stay connected to machine activity
  • Managers can review sales and count progress

Operational Outcomes

Faster daily machine counts

Less setup and fewer field changes

Cleaner machine-by-machine history

Clearer refill and purchasing signals

Sales reporting across machines and products

Result: Every active machine receives a prepared count line, employees enter only the remaining quantity, and reporting uses the same connected data.

Scalable operations illustration

Why This Works and Scales

The floor-counting task stays simple while the relationships behind it remain connected.

Employees only enter remaining quantities, while each count line already carries the machine, product, manufacturer, zone, and sale date needed for reporting.

The same structure can later expand into purchasing, order lines, refill planning, inventory valuation, and deeper product performance reporting.

Manage Daily Gachapon Counts From One Connected System.

Build your operational system with AnyDB.