StockPing Alerts Explained — Resolve, Snooze, and Managing Your Inventory Incidents

You’ve set up StockPing, configured your thresholds, and alerts are coming in. Now you’re looking at the Alerts page and wondering: what does “Resolve” actually do? What happens when I snooze something? Will I lose track of it?

This guide explains how StockPing’s alert system works — from the moment an alert fires to the moment it’s resolved — so you can manage your inventory confidently without second-guessing the buttons.

How Alerts Work: The Lifecycle

When inventory drops below your threshold at any location, here’s what happens behind the scenes:

Shopify sends a webhook — the moment inventory changes, Shopify notifies StockPing in real time.
StockPing creates an incident — an incident is a single, trackable record for one product at one location. Think of it as an open issue: “Classic Cotton T-Shirt — Medium / Black is low at Main Warehouse.”
You get notified — via email, Slack, push, or all three, depending on your setup.
The incident stays open until you take action or stock recovers on its own.

One Product, One Location = One Incident

If the same product drops below threshold multiple times at the same location, StockPing doesn’t flood you with duplicate incidents. It groups them into a single incident and updates the count. You’ll see “3 breaches” on one incident rather than three separate entries. This keeps your Alerts page clean and actionable.

Cooldowns Prevent Notification Spam

Every time an alert fires, a cooldown timer starts. During this window, StockPing won’t send another notification for the same product at the same location — even if stock fluctuates. This prevents the “50 emails in an hour” problem when inventory keeps changing slightly.

The cooldown is 60 minutes on the Free plan and as low as 5 minutes on PRO.

What Does “Resolve” Mean?

Resolving an incident means “this is handled — I don’t need to see it anymore.”

When you resolve an incident, it moves from the Open tab to the Resolved tab. It’s not deleted — it becomes part of your historical record. You can always go back and see what was resolved, when, and whether it was resolved by you or automatically.

Manual Resolve

You resolve an incident manually when you’ve taken action — you’ve reordered stock, transferred inventory between locations, or decided the low stock is intentional (maybe you’re running down a discontinued item).

Hit the Resolve button on any open incident, and it’s done. It’s your way of telling StockPing: “I’ve seen this and handled it.”

Auto-Resolve

Here’s where it gets helpful: StockPing resolves incidents automatically when stock recovers above the threshold.

Say your threshold for a product is 10 units, and it dropped to 3 — triggering an alert. Your supplier shipment arrives, stock goes back up to 50. StockPing detects the inventory change, resolves the incident for you, and sends a recovery notification so you know the restock went through without having to check manually.

Auto-resolved incidents show up in the Resolved tab marked as “auto” — so you can distinguish between incidents you handled and ones the system closed.

What Happens If Stock Drops Again After Resolving?

A brand new incident is created. Resolving is a clean close — if the same product drops below threshold again later, StockPing treats it as a fresh issue with its own timeline. This is the right behavior: a restock that held for two weeks and then dropped again is a different situation than the original alert.

What Does “Snooze” Mean?

Snoozing an incident means “I know about this, but I can’t deal with it right now.”

It’s the inventory management equivalent of snoozing your morning alarm. The incident doesn’t go away — it just stops demanding your attention for a while.

How Snooze Works

When you snooze an incident, you pick a duration:

1 hour — quick pause, maybe you’re in a meeting
4 hours — you’ll handle it this afternoon
24 hours — waiting for tomorrow’s delivery
7 days — supplier lead time, weekend stock, or you’re on vacation

During the snooze period, the incident is still tracked. If stock drops further, the incident updates silently — the breach count goes up, but you won’t get new notifications for it. When the snooze timer expires, the incident automatically returns to the Open tab as an active alert.

When to Snooze

Snooze is perfect for situations where you’re aware of the problem but the fix is already in motion:

Supplier delivery scheduled — you’ve already placed the reorder. Stock will arrive Thursday. Snooze until then.
Weekend stock — your retail store is low on a product, but your next shipment from the warehouse goes out Monday. Snooze for the weekend.
Intentional low stock — you’re running a clearance sale and expect stock to drain. Snooze it so it doesn’t clutter your active alerts.
Delegated to someone else — you’ve told your warehouse team to handle it. Snooze until you’d expect it to be done, then check.

Can I Unsnooze Early?

Yes. If plans change and you need the incident back in your active view, you can unsnooze it at any time. It immediately returns to the Open tab.

Resolve vs. Snooze — The Simple Rule

Still not sure which to use? Here’s the quick version:

	Resolve	Snooze
Meaning	”I’ve handled this"	"I’ll handle this later”
Where it goes	Resolved tab (historical)	Stays in Open tab (hidden temporarily)
If stock drops again	New incident created	Same incident updated silently
Notifications	Stop permanently for this incident	Paused until snooze expires
Best for	Restocked, transferred, or intentionally low	Reorder in transit, scheduled restock, weekend

Rule of thumb: If the action is done, resolve. If the action is pending, snooze.

The Three Tabs on Your Alerts Page

Open

Your main working view. This shows every incident that needs attention — including snoozed ones (which are visually marked so you can tell them apart). This is where you’ll spend most of your time.

Incidents are sorted by most recent activity, so the alerts that just fired are at the top.

Resolved

A read-only archive of closed incidents. Use this to:

Verify restocks — check that auto-resolved incidents actually recovered as expected
Spot patterns — if the same product keeps showing up in Resolved, your reorder point might be too tight
Audit trail — see when each incident was opened, how many times it breached, and when it was closed

Resolved incidents show whether they were closed manually (by you) or automatically (stock recovered).

History

This is the raw notification log — every individual alert StockPing has ever sent for your store. While Open and Resolved track incidents (grouped by product + location), History tracks individual notifications.

Use History when you need to:

Check delivery status — “Did that alert actually send to Slack?”
Debug channels — see which channels received each notification
Review timing — see exactly when each alert fired, down to the minute

Bulk Actions: Manage Multiple Incidents at Once

When you’ve been away for a few days and come back to a pile of alerts, you don’t have to resolve them one by one.

Select multiple incidents using the checkboxes, then use the bulk action bar to:

Bulk resolve — mark everything selected as handled
Bulk snooze — snooze everything for the same duration

You can also use “Select all” to act on every incident matching your current filters — not just the ones on the current page. This is useful when you want to resolve all alerts for a specific location or clear out everything older than a certain date.

Tips for Managing Alerts Effectively

Don’t Let Open Incidents Pile Up

An Alerts page with 50 open incidents is just as useless as no alerts at all. Make it a habit to triage regularly — resolve what’s handled, snooze what’s pending, and investigate anything that’s been open too long.

Use Snooze for Known Restocks

If you’ve already placed a reorder, snooze the incident until the expected delivery date. This keeps your Open tab focused on things that actually need action, not things you’re already waiting on.

Check Resolved After Restocking

After a delivery arrives, glance at your Resolved tab. If StockPing auto-resolved the incidents, your restock went through correctly. If some incidents are still open, something didn’t arrive as expected — and you caught it early instead of finding out from a customer complaint.

Set Thresholds at the Reorder Point

The most common mistake is setting thresholds too high. If you get an alert when you still have three weeks of stock, you’ll snooze it every time — and eventually stop paying attention. Set thresholds at the point where you’d actually take action, and every alert will feel relevant.

Get Started

StockPing is free to install from the Shopify App Store. Set up your thresholds, connect your notification channels, and let the alert system handle the rest. When alerts come in, you’ll know exactly what Resolve and Snooze do — and when to use each one.