Kyte AI
ManageControl

You trade an unexplained loss for a record of each one, writing the reason down only when you actually know it, and "unknown" when you don't.

A guided tutor that teaches you to log every loss, whether it's breakage, an expired product, or stock that's simply gone, noting what was lost and separating the reason you actually know from a cause you're only guessing at. You leave with the record of one real loss, without filling "unknown" with a guess.

Chat screen showing the loss tutor asking what was lost and the reason for a store loss

What this skill does

This tutor doesn't build your store's loss spreadsheet for you. It teaches you to log each loss with what was lost and the reason, when that reason is actually known. You show up with a recent loss, a broken product, an expired one, or something that's simply gone, and the tutor asks where that loss was written down and what reason went into the record.

If you're not writing anything down yet, the focus stays on logging just what was lost. If you already note the product but not the reason, the focus shifts to writing the known reason or "unknown." And if the cause on record is something you never saw happen, like "it must have been theft" or "it must have spoiled in the heat," the tutor shows the difference between a known reason and a guessed cause.

At the end, it tells you plainly that there's no ready-made feature yet to generate the loss spreadsheet automatically, and it points you to one cycle: log one real loss, starting now, with what was lost and the reason, when it's known.

How it works

You show up and the tutor asks one thing at a time: what was lost, where that loss was recorded, what reason went into that record, and whether that reason was seen happening or is a guess. From your answer, it spots the gap: if you're speaking from memory, it asks for the record; if the reason is a cause you didn't see, it goes back to "unknown."

It compares logging a loss to counting what's left on the shelf when you close up: when something's missing and you saw what happened, the reason is known. When something's missing and nobody saw anything, the reason stays unknown until proof shows up. After rebuilding that logic with you, the tutor asks you to repeat it in your own words: "every loss, I log what was lost and the reason, when I actually know it; when I don't, I write unknown."

You leave the session with one request: log one real loss that happened in your store, with what was lost and the reason. Next time you come back, it asks what was lost and what reason got recorded, checks the record, and fixes only the point that got stuck, without repeating the whole explanation.

Use cases

Real examples of how this skill fits into a store’s routine to speed up decision-making and sales.

01

A product breaks right in front of the clerk

A glass jar falls off the shelf, a bottle cracks on the way to the counter, a package gets crushed too badly to sell. The tutor teaches that this is a known reason, breakage, because someone saw the exact moment it happened. That way the record comes out complete on the spot, instead of relying on remembering later which product it was.

02

An item expires before it sells

Products with a shelf life, cosmetics, packaged food, hygiene items, expire on the shelf when turnover is slower than expected. The tutor teaches you to log that item as a loss with a known reason, expired, instead of just tossing it and moving to the next customer. That way every expired product gets a date and a reason on record, not just a spot off the shelf.

03

A product disappears and nobody saw it happen

The count comes up short and there's no explanation: nobody saw it break, nobody saw it expire, the product is just gone. The tutor teaches you to log that loss as missing stock with an unknown reason, without pointing to theft or a counting error until that's confirmed. The record stays accurate even without a cause to point to.

04

The cause is a guess, not something anyone saw

After stock goes missing, it's common to jump to "it was stolen" or "it spoiled in the heat" without being sure of anything. The tutor asks whether that reason was actually seen or is a bet, and asks you to turn the guess into "unknown" on the record. That way the store stops treating a hunch as a confirmed fact.

05

A month of losses gets lumped into one line

At the end of the month, it's easier to sum it up as "we lost a bit of stock this month" than to list every item. The tutor asks for one specific loss at a time, what was lost and its reason, instead of accepting a general summary. Each loss logged this way can be checked later, one by one.

Benefits

You stop guessing the reason for each loss

Before, a product that went missing or broke turned into the same guess repeated, "it must be that again," with nothing behind it. With the record separating known reasons from "unknown," the store knows exactly how many losses have a confirmed cause and how many still don't.

You build a record of what actually happened

Without notes, each loss lived only in the memory of whoever was in the store that day, and that memory faded over time. With the habit of logging what was lost right after it happens, the store gets a picture of what was breakage, what was expiration, and what's still unexplained.

You stop basing stock decisions on an invented cause

When every loss turns into "theft" or "bad supplier" without proof, decisions like switching suppliers or changing a process start from a guess, not a fact. With the reason split between known and unknown, any decision based on losses now rests on what's actually on record.

Frequently asked questions

Free · No installation · No setup

Pick your store type, walk away with the finished result.

Learn to Log It Right

More skills

A guided tutor that teaches a fixed rhythm for opening and closing your store: sort what needs action at opening, review what's left open at closing. You bring in your last real workday and leave knowing which of the two moments still needs work.

A guided tutor that teaches you to revise the listed price when cost changes, update availability when stock moves, and mark an item unavailable when it runs out. You come in with a real product from your catalog and leave with the check done and logged in a note.

A guided tutor that teaches four questions to review any shop decision before you apply it: whether it makes the next step easier, whether it happens at the right time, whether it considers the right customer, and whether the information you need to decide is visible. You bring a real decision from your shop and leave knowing whether to keep, change, or drop that idea based on proof, not a guess.