Connect the business once. Snoop keeps working from there.
Sales come in. Inventory moves. Refunds happen. Supplier invoices arrive.
Problems show up at inconvenient times. Snoop's job is to keep the running
picture together and bring you the part that actually needs your attention.
You should not have to rebuild the story of your business every morning.
Snoop keeps the story moving while you're busy running it.
The short version
✓Give Snoop sales, starting inventory, and the business sources you want connected.
✓Snoop keeps the running math and watches for things that do not fit.
✓You get the useful part back in alerts, conversation, and your morning brief.
Step 1
1
Give Snoop a reliable starting point.
Snoop does not need you to replace the systems you already use.
It starts with the business data you already have.
Connect a supported POS where available, or upload sales reports when that is the better fit.
Add your starting inventory. Forward invoices or documents you want Snoop to understand.
If your location uses Snoop Vision, that can add another layer of operational context.
✓Supported POS connection for sales activity
✓Uploaded sales reports when direct POS sync is not the right path
✓Starting inventory so Snoop knows where the running count begins
✓Supplier invoices, bills, and notices forwarded into Snoop
✓Optional Snoop Vision for compatible locations
Step 2
2
Snoop keeps the running math.
Once the starting point is there, Snoop begins doing the repetitive bookkeeping work
that owners normally have to reconstruct by hand.
When an item sells, Snoop can deduct the mapped inventory item.
When a menu item uses a recipe, Snoop can deduct the ingredients tied to that recipe.
When a refund or void comes through, Snoop can hold the inventory decision for the owner
instead of blindly assuming the item went back on the shelf.
✓Direct item sales can reduce mapped inventory
✓Recipe sales can reduce the ingredients behind the item
✓Refunds and voids can be separated from the restock decision
✓Damaged, consumed, or non-restockable items can stay out of inventory
✓Duplicate processing is guarded so the same event is not supposed to move stock twice
"The goal is not to make you count faster. The goal is to stop making you rebuild the same math from zero."
That is the difference between software you operate and a watchdog that keeps working.
Step 3
3
Snoop looks for the part that does not fit.
Snoop is useful when the systems agree.
It becomes valuable when they do not.
A sale says something left the building, but inventory did not move.
A refund happened, but nobody decided whether the item should be restocked.
A supplier invoice changed.
A physical check does not match the running count.
A service event happened without a matching sale.
Those are the moments Snoop is built to surface.
→A tire sold but the expected inventory effect is missing
→A refunded item needs an owner decision: restock, damaged, consumed, or something else
→A supplier price or document deserves attention
→The running inventory says five, but the physical check says three
→Vision activity has no matching sale and may be worth reviewing
Step 4
4
Snoop comes to you.
Most business software waits for you to remember it exists.
Snoop is built around the opposite idea.
When something matters, the result should reach you in plain language.
Your morning brief can summarize the prior day's sales and surface the things worth looking at.
Alerts can point you toward a problem.
And when you want more detail, you can ask Snoop about the business directly.
"Yesterday: $452 in sales. One inventory issue is worth checking. Nothing else urgent."
The point is not more reporting. The point is knowing where to look.
Step 5
5
You verify what still needs a human.
Snoop is not pretending software can physically see every shelf, every tire rack,
every bottle, or every box.
Physical verification still matters.
The difference is that Snoop is designed to give you a running expected count first,
so your check becomes:
"Is this exception real?"
instead of:
"Let me count everything from zero again."
That is a much better use of an owner's time.
What Snoop can watch
One business. A lot of moving pieces. One place tying them together.
💵
Sales
Supported POS data or uploaded sales reports feed the operating picture.
📦
Inventory
Mapped items and recipes can update expected quantities as sales happen.
↩️
Refunds & voids
Inventory movement can wait for the right restock decision instead of being guessed.
📨
Invoices & documents
Forward business documents so Snoop can pull useful information into the same operating context.
⚠️
Alerts
Things that deserve a second look can be surfaced instead of buried in another report.
🌅
Morning brief
Each location can have its own briefing time and its own operating context.
👁️
Snoop Vision
Compatible camera setups can add traffic and service-area activity as another signal.
📍
Multiple locations
Sales, inventory, documents, alerts, settings, and briefs stay tied to the location they belong to.
The honest explanation
Does Snoop remove every manual task?
No — and it should not pretend to.
Some things still need a person: a physical inventory check, deciding whether a damaged item can go back into stock,
reviewing a flagged clip, or deciding whether an alert actually matters.
Snoop's job is to make those human decisions smaller, faster, and better informed.
Instead of asking you to inspect everything, Snoop tries to narrow the question down to what deserves your attention.
The questions owners ask
Straight answers. No fluff.
Not always. A supported POS gives Snoop the cleanest automatic sales feed,
but businesses can also use uploaded sales reports where that makes more sense.
Snoop is designed around read-only supported POS access.
It can use sales and adjustment data to update Snoop's own operating picture,
but it is not there to take over your payment system.
Uploaded sales can still be part of the daily sales picture.
The goal is to keep Snoop useful even when every sale does not arrive through the same integration.
A refund does not automatically mean the item is usable again.
Snoop can separate the refund from the inventory decision so the owner can choose
whether the item is restocked, damaged, consumed, or otherwise not returned to usable inventory.
Yes, physical verification still matters.
The difference is that Snoop is designed to give you an expected count first,
so you are verifying exceptions instead of rebuilding the whole picture from scratch.
Snoop's running picture comes from the business data and inventory workflow tied to the account.
Physical counts and owner decisions can correct reality when needed,
but the point is to preserve a traceable operating history instead of relying on one unexplained number.
No. Snoop Vision is built around operational activity, not identifying people by face.
Its job is to add context such as traffic, dwell, and service-area events — not build a biometric identity database.
Each location can have its own inventory, sales connections, documents, alerts, Vision setup,
and morning brief timing. The point is to keep one owner's businesses organized without mixing them together.
Why this feels different
Snoop is not trying to give you another place to go check.
Most business software is useful after you open it.
Snoop is built around what happens before you open anything.
It keeps the running picture moving.
It looks for the mismatch.
It prepares the context.
Then it comes back to you with what deserves attention.
You do not go looking for Snoop. Snoop comes looking for you.
Give Snoop a starting point. See what it takes off your plate.
Start with a supported POS or uploaded sales, add the business data you want Snoop watching,
and see how much easier the morning feels when the story is already waiting for you.