tiqline is a process SLA monitoring tool: it turns events from Shopify and your own systems into one case per piece of work, gives every step a time limit and alerts you in Slack or by email when a step runs over.
Overdue order alerts that reach the right people, once per problem
An overdue order is only useful information if someone hears about it in time and can act on it. tiqline sends one alert when orders pass the time limit of a step, to Slack, by email or to a webhook, with the step, the limit, how many orders wait and a link to each of them. When the orders move again, the alert is resolved.
The problem with alerts about late orders
Most teams have tried some kind of late-order alert. The common failures look alike. Alerts arrive one per order, so a single outage produces fifty messages and the channel gets muted. Alerts arrive as a daily summary, so a problem that started at 9:00 is seen the next morning. Alerts say that something is late but not which step, which limit or which orders, so someone still has to search. And alerts never say that the problem is over, so nobody knows whether the last message still matters.
How late-order alerts are built today
Shopify Flow has templates that email a daily summary of unfulfilled orders older than two days, tag late fulfilments and send a daily count of orders that miss a two-day shipping promise, and one that waits two days after an order and sends a Slack message if it is still not shipped. Zapier combines a Shopify trigger such as New Paid Order with a Delay step of up to 30 days, a filter and a Slack or email action; changing the Zap while runs are delayed stops those runs. n8n lets you build the same with a Shopify Trigger, a Wait node and a Slack node, or with a Schedule Trigger that queries open orders. Each of these sends what you build into it, one workflow per rule.
How tiqline alerts on overdue orders
1. Deadlines per step
Each step of a process after the first has its own limit, for example Packed within 4h after payment and Shipped within 24h after packing. tiqline calculates the deadline of every order on every step and notices when it passes, without a scheduled job on your side.
2. One incident per step
Orders that are overdue on the same step are grouped into one incident. You get one message when it opens, not one per order. A required step that is skipped opens a separate incident of the kind skipped, 15 minutes after the later event arrived.
3. Slack and email
Slack messages go to an incoming webhook of a Slack app, so they land in the channel you chose. Emails go to up to 20 recipients. Each message names the process, the step and its limit and links to the process and the cases. The Slack message says how many cases are waiting, and the email lists them.
4. Webhook for your own tools
A webhook sends incident.opened and incident.resolved to any https address, signed with the Standard Webhooks headers webhook-id, webhook-timestamp and webhook-signature, optionally with a Bearer key. The payload carries the organisation, the incident and its kind, the process, the step and its limit, case counts and up to 20 example cases with links. A helpdesk, an internal tool or an automation such as a Cursor Automation can react to it. You can send a test message when you set it up.
5. Resolved when the orders move
When the missing events arrive and no case is stuck on the step any more, the incident is resolved. A webhook receives incident.resolved. If you raise a limit, cases whose new deadline lies in the future run again, and an incident without stuck cases is resolved too.
Example: a carrier pickup that did not happen
The orders, the carrier and the times are made up to show the flow. The process: Order Paid opens the case, Order Packed from the warehouse has 4 hours, Fulfillment Created from Shopify has 6 hours after packing.
Friday 15:00: packed orders wait for the label
Thirty orders were packed between 09:00 and 12:00. The label service is down, so no fulfilment is created in Shopify.
Friday 15:00 to 18:00: the deadlines pass
Stuck
From 15:00 the first packed orders pass their six-hour limit. tiqline opens one incident for Fulfillment Created, posts one Slack message to the shipping channel and sends incident.opened to the helpdesk webhook, which puts a banner on orders the support team opens.
Friday 18:30: labels are printed
The label service is back, fulfilments are created, and the cases move on.
Friday 18:40: one resolved message
With no case left on the step, the incident is resolved. The webhook receives incident.resolved and the helpdesk removes the banner.
What tiqline does not do
There is one Slack channel, one email list and one webhook per organisation, so alerts for all processes go to the same places; routing different processes to different channels has to happen in the receiver of the webhook. tiqline does not escalate, page or repeat a message on a schedule: one message when an incident opens. It does not message customers and does not change orders in Shopify. Limits run on the clock, including nights and weekends. Deadlines that passed more than seven days before their events arrived do not alert. On the Free plan with 5,000 events a month, alerts pause when the quota is used up, while events are still stored.
Choosing the channel
Slack suits a team that watches a shared channel during the day. Email suits people who do not live in Slack, such as a 3PL account manager. A webhook suits everything that should happen automatically: a ticket in a helpdesk, a flag in an internal tool or an agent that looks into the cases. All three can be on at once, and each can be switched off.
tiqline monitors process SLAs and is not one of the classic product-analytics tools.
Questions about overdue order alerts
Will I get a message for every overdue order?
No. Overdue orders on the same step share one incident and one message. The message says how many cases wait and links to them.
What is in a webhook alert?
The event incident.opened or incident.resolved, the kind stuck or skipped, the organisation, the process, the step and its limit, case counts and up to 20 example cases with links. It is signed with Standard Webhooks headers.
Can I send alerts to more than one Slack channel?
No. An organisation has one Slack channel for alerts. Email and a webhook can be on at the same time, and a webhook receiver can route alerts further.
Do I learn when the problem is over?
Yes. The incident is resolved when no case is stuck on the step any more, and a webhook receives incident.resolved.
Can I test a channel before going live?
Yes. When you set up a channel you can send a test message.
Which steps can make an order overdue?
Every step after the first that has a limit. That can be a Shopify step such as Fulfillment Created or Order Fulfilled, or a step from your own systems such as Order Packed, sent through the track API. Steps without a limit and conversion steps never alert.
Can an agent poll for incidents instead?
Yes. The MCP server has a list_incidents tool, so an AI agent can read open incidents on request.
Start for free
The Free plan includes 5,000 events a month.