Alerts
Intro
Alerts collect operational problems that need a human — orders that failed to import, shipments stuck syncing to a fulfillment provider, webhook backlogs, delivery dates a calendar would not have offered. The bell in the top bar shows the unread count; the Alerts pages let you triage and close them.
Purpose
- Surface problems before customers notice them
- Track that each issue was seen, and how it was resolved
- Stop the same false positive from coming back every hour
The pages
| Page | Contents |
|---|---|
| Overview | Counts by level and category, top alert codes, trend |
| Active | Open alerts that need attention |
| Resolved | Closed alerts with their resolution |
| All alerts | Everything, for search |
Open them from the bell or from the account navigation. Alerts require the Edit orders permission.
Levels
| Level | Meaning | Where it is sent |
|---|---|---|
| Critical | Data is being lost or a store is not syncing | In-app, plus Slack and email when configured |
| Error | A job or sync failed and needs a fix | In-app, plus Slack when configured |
| Warning | Something is late or looks wrong | In-app |
| Info | Worth knowing, no action required | In-app |
Alert catalog
Order sync
| Alert | Meaning |
|---|---|
| Order import failed | A Shopify order could not be imported |
| Orders missing locally | Shopify has orders StoresBoost does not — an import gap |
| Duplicate order | The same order exists twice locally |
| Order reconciliation stalled | The periodic Shopify ↔ local check stopped progressing |
| Shipment not created | Orders that should have shipments do not |
| Shipment creation pending | Shipments for an order are still queued |
| Shipment creation failed | Building shipments for an order failed |
Shipment sync
| Alert | Meaning |
|---|---|
| Fulfillment provider sync pending | Shipment is still waiting to reach the provider |
| Fulfillment provider sync failed | The provider (e.g. ShipStation) rejected the shipment |
| Provider cancellation failed | A cancel could not be pushed to the provider |
| Store sync pending / Store sync failed | Fulfillment or tracking has not reached Shopify |
| Multiple shipping methods | A shipment carries ambiguous shipping methods — decide which applies |
| Conflicting delivery dates / Missing delivery date | Delivery date data does not add up |
| Held too long | A shipment has sat On Hold past the threshold |
| Merge evaluation stuck | Merge suggestion processing stopped |
| Merge evaluation failed | The merge scanner hit an error on these shipments; they were skipped this run — merge manually or re-trigger once the cause in the message is fixed |
| Duplicate shipment items | The same line appears twice on one shipment |
Fulfillment provider & webhooks
| Alert | Meaning |
|---|---|
| Provider error spike | Unusually high provider sync failure rate |
| Provider authentication failed | Provider credentials are wrong or expired — see Fulfillment Providers |
| Webhook backlog | Shopify webhooks are queuing faster than they process |
| Webhook processing failed | A store webhook could not be handled |
| Job … failed | An internal sync job failed — usually resolves on re-check; persistent ones need support |
Delivery Calendar
| Alert | Meaning |
|---|---|
| Delivery date not offered by calendar | An order carries a delivery date the calendar would not have offered (often a customer-side change) — see Delivery Calendar |
Routines
| Alert | Meaning |
|---|---|
| Routine ready for you | A scheduled Routine finished its automatic steps and is parked at a step that needs a person (printing a document, a manual task). Open the run from the alert (or Continue run on the routine) to finish it |
| Scheduled routine needs attention | A scheduled run could not start, or one of its automatic steps failed — open the run to see which step and the error |
Hooks
A hook whose action is Raise an alert adds one alert for the run, with the matched shipments attached. The title and message are whatever the hook was given ({count} and {hook} are filled in). While that alert stays open, later runs of the same hook increase its count instead of opening a new one. Resolve it the same way as any other alert.
Alerts you do not recognise (raw codes) come from internal probes; open the details and contact support if they repeat.
Work an alert
- Open Active and read the alert's title, details, and linked order / shipment.
- Acknowledge it so teammates know it is being handled.
- Fix the cause — an address, a carrier or provider connection (Integration), a sync problem (Webhook Status).
- Click Re-check to let StoresBoost confirm the condition is gone, or Resolve it yourself with a resolution and optional note.
Actions
| Action | Use it when |
|---|---|
| View details | You need the payload, linked records, and history |
| Acknowledge | Someone owns it |
| Snooze (1h · 4h · 1 day · 3 days · 1 week) | It will fix itself or you will get to it later |
| Re-check | You fixed the cause and want the alert to verify |
| Resolve | Close it with Fixed, False positive, Expected behaviour, or Won't fix |
| Resolve all with this code | The same alert fired for many records and you fixed the root cause |
Alerts closed as False positive, Expected behaviour, or Won't fix are suppressed from re-raising for 30 days. Alerts the system clears on its own show Auto-resolved.
Related
- Integration → Webhook Status
- Orders → Print & Order sync
- Apps → Inventory Management — sync run errors live there, not in Alerts
- Advanced → Hooks — custom alerts raised when a trigger matches
Profile & billing
Manage your personal profile, the store subscription, and understand what each plan unlocks.
AI assistants (MCP)
Connect Cursor, Claude, ChatGPT, or another MCP client to your store so it can explain rules, simulate orders, diagnose shipments and price-test carts — with a personal token that can never do more than you can.