merchmix

horizon · Cycle counting

Counting never closes the shop.

Count a slice while trading continues, post the variances, keep the figure honest. No Sunday.

Stocktakes report how wrong you were.

The doors shut, everyone counts, and the figure is stale the week after. A cycle count stops the gap opening.

A count covers one slice.

The cycle in horizon, in order.

  1. CreateOpen the count with its expected quantities from the record.
  2. CountMove it to counting and record what is on the shelf.
  3. ReviewCheck progress and each variance before anything posts.
  4. PostEvery difference becomes a correction in one transaction. The stocktake history stays.

Counters see no expected quantity.

Blind by default: the shelf is counted, not confirmed.

Blind count
In orbit the expected quantity stays hidden until the count is submitted.
Variance
Observed against expected, per line, once the count is in.
Approval
Someone approves the count. Only then does each variance post to the ledger.
Ledger
Refuses a negative balance, so a wrong count cannot go below zero.
Audit log
Keeps the count, the corrections and the history.

Trading continues while you count.

Do we close the aisle?

No. One slice at a time, tills running.

Does every count wait for a manager?

Posting waits for approval. Counting does not.

And the year-end stocktake?

horizon keeps stocktake history beside the cycle counts. Year-end gets a trail, not a weekend.

yukti does not do the counting.

Its 4 actions are rebalance, allocation and replenishment, purchase orders and new styles. None is a count, and it posts no variance. It reads the figure a correction leaves behind, live in seconds.

A posted correction reaches core.

What feeds the count, and what it feeds.

orbit

Books stock in, holds the bins, runs the blind count.

horizon

Holds the record: cycle counts, adjustments and the stocktake audit log. This page is part of horizon.

core

Reads operational actuals into the plan. A posted correction moves the WSSI (MFP).

Questions, answered.

How often should we count?

As often as the slice needs. You create each count with its expected quantities.

Can the counter see the expected quantity?

Not by default in orbit. It stays hidden until the count is submitted and the variance is approved.

Who approves a variance?

Whoever approves the count. Each variance then posts as a ledger adjustment in one transaction, audit log kept.

Do we need orbit to cycle count?

No. horizon runs cycle counts on its own record. The blind count and the negative-balance refusal are orbit.

Six weeks proves it on your shelves.

A 1-hour demo with sales and product, then a free 6-week POC on your own data, no contract. Live in 12 to 15 weeks, end to end.