Skip to main content

​
Connecting Slack

Slack is connected once for your whole store, not per alert. The same connection delivers scheduled reports, so connecting it once covers both. Discord works the same way and is connected in the same place. Authorising it adds the Stockful bot to one server, and each alert then picks a channel inside it.
  1. Go to Settings, then under App click Alert settings
  2. On the Slack row click Connect, and authorize Stockful in the popup
  3. Once connected, you can select a Slack channel when creating alerts
The same row appears on the Integrations page alongside your other connections. Connecting or disconnecting in either place does the same thing.

​
Default channel

Once Slack is connected you can pick a channel that new alerts start on, so creating one doesn’t begin by choosing the same channel every time. It’s only a starting point - you can change the channel on any alert, and changing the default never touches alerts you’ve already made.

​
Cooldown

How long a SKU stays quiet after it alerts, so a product hovering around its threshold doesn’t fill your channel. The default is 24 hours. Anything from an hour to a week is available, and it applies per location and per trigger - the same product can still alert about a different problem at a different location. Shorter means faster warnings and more messages. Longer means quieter, but you may hear about a problem later than you would like. If one particular SKU is the problem rather than the setting, snooze it instead.

​
Quiet periods

Set quiet hours - a time range during which Slack alerts are held back. You can also mark whole quiet days. No alerts are sent on those days at all, midnight to midnight, so a shop that doesn’t want Saturday alerts doesn’t have to fake it with a 00:00 to 23:59 window. Once a window or a quiet day is set you can choose what happens when it ends:
  • Send what was held back (the default). Alerts that fired overnight are re-checked against current stock and sent when the window closes. Anything that resolved itself in the meantime isn’t sent.
  • Don’t send anything from the quiet period. Alerts that fire during quiet hours are let go, and you won’t be told about them later.
Pick the second one if a morning catch-up is more noise than help. Bear in mind a problem that started at 3am and hasn’t moved since will never reach you.

​
During a promotion

If you have declared a promotion in the promotion calendar, low stock and reorder point alerts are held back for the days it runs, including the first and last. Stock falling fast during a promotion you planned is the promotion working, so alerting on it is noise at the busiest moment of your year. Out of stock and oversold alerts still fire: selling out mid-promotion is lost sales and possibly a storefront problem, so it matters more then, not less. Back in stock alerts keep firing too, since a recovery is worth hearing about straight away. Sales drops also still fire - a drop during a promotion you planned is worse news than usual - while sales spikes and traffic surges are held, because both are the promotion working. Promotion stock check and supplier slower than configured are never paused: the first is about the promotion itself, and the second is about a supplier rather than how fast stock is moving. Nothing to switch on: it follows the dates you already declared, and applies only to the products the promotion covers.