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.
Time limits per warehouse and channel: one process, different deadlines
Not every order has the same deadline. A warehouse close to the customer packs faster than one abroad, a marketplace order may promise a different dispatch time than your own shop, and an express order should leave the same day. tiqline lets one process carry all of these: a branch sends each order down its own path, and every path has its own time limits.
One deadline for everything does not fit
A single limit for all orders is either too tight for the slow path, so it raises alerts nobody acts on, or too loose for the fast path, so real delays go unnoticed. Shops with two warehouses, a store that ships online orders, wholesale and retail orders, or domestic and international shipping all have different promises for different orders. The monitoring has to know which promise applies to which order.
How teams handle different deadlines today
In Shopify Flow, a Wait action holds one run for one fixed time of up to 90 days, so different deadlines mean condition branches, each with its own Wait action. Two warehouses and two channels already make four variants to keep in sync. In n8n, If and Switch nodes split a workflow into several paths, and each path needs its own wait or schedule logic and its own state. In Zapier, each deadline needs its own Delay step of up to 30 days. In a spreadsheet, a column for the warehouse and a formula per deadline work until someone sorts the sheet wrong. All of these tie the deadline to the automation that checks it, so changing a limit means editing every variant.
How tiqline handles deadlines per warehouse and channel
1. A branch reads a property
A branch is a step without a limit of its own. It reads a property of the event that reached the step before it, or of a step you name, and sends the case down the first path whose conditions match. Conditions compare a property with a value: equal, not equal, present, or one of a list. One path is the else path and takes every case that matches none of the others, so every case always takes exactly one path.
2. What you can branch on from Shopify
From Shopify orders, tiqline keeps the order source (Shopify's source_name, such as web or pos), the country code of the shipping address, the payment gateways, the total, the currency and the number of line items, and from fulfilments the carrier name. That is enough for splits such as online store versus point of sale, domestic versus international or one carrier versus another.
3. Warehouse from your own event
The Shopify data tiqline keeps does not include the fulfilment location. To split by warehouse, the warehouse has to arrive in an event from your warehouse system or middleware through the track API, for example Order Assigned with warehouse set to north or west.
4. Each path has its own steps and limits
After the branch, each path has its own steps, for example Packed within 4h for Lager Nord and Packed within 8h for Lager West. Paths can meet again in a shared step, such as Order Fulfilled, and from there one limit applies to all.
5. Change a limit once
A limit belongs to the step, not to an automation. When you change it, the new deadline applies at once, also to cases already waiting on that step. A case that was stuck and whose new deadline is in the future runs again. The process map shows the branch and marks every step with stuck cases.
Example: Lager Nord and Lager West
The warehouses, the order and the times are made up to show the flow. The process: Order Paid opens the case, a branch reads the warehouse from Order Assigned, Lager Nord packs within 4 hours, Lager West within 8 hours, and both meet at Order Fulfilled with 24 hours.
10:00: order 1042 is paid and assigned
The middleware assigns the order to Lager Nord and sends Order Assigned with warehouse north. The branch sends the case down the Nord path, and packing is due at 14:00.
10:05: a second order goes to Lager West
Order 1043 is assigned to Lager West. Its packing is due at 18:05.
14:00: Nord is late
Stuck
Order 1042 has no Order Packed. The case turns stuck on Packed (Nord), and the Slack message names that step and its four-hour limit.
16:30: both orders are packed
1042 is packed and moves on. 1043 is packed within its eight hours and never alerts. Both now wait at Order Fulfilled with the same 24-hour limit.
What tiqline does not do
A branch reads one event: the one that reached the step before it, or the step you name. It does not combine properties from different events. Conditions check for equal, not equal, present or one of a list; there is no greater-than or less-than, so a split by order value needs a property such as a value tier that your system sends. The warehouse is not part of the Shopify data tiqline keeps, so it has to come from your own event. There are no calendars per warehouse: limits run on the clock, and a warehouse that does not ship on Sundays needs a longer limit or a separate path. A branch can have at most 20 paths, each with at most 20 conditions. Alerts for all paths go to the organisation's one Slack channel, one email list and one webhook.
When a separate process is the better choice
If two warehouses follow completely different steps, two processes can be clearer than one with a branch. If they share most steps and differ in limits, one process with a branch keeps the overview in one place and lets you compare the paths on one map.
tiqline monitors process SLAs and is not one of the classic product-analytics tools.
Questions about time limits per warehouse and channel
Can I set a separate limit for each warehouse?
Yes. A branch reads the warehouse from an event and sends each case down the matching path. Each path has its own steps and limits, for example four hours in Lager Nord and eight in Lager West.
Where does the warehouse come from?
From an event your warehouse system or middleware sends through the track API. The Shopify data tiqline keeps does not include the fulfilment location.
Can I branch by sales channel?
Yes. tiqline keeps the sales channel of a Shopify order, so a branch can treat online store, point of sale or other channels differently.
What happens to an order that matches no path?
It takes the else path. Every branch has exactly one, so every case takes exactly one path.
Can paths meet again?
Yes. After separate steps, paths can lead into a shared step, such as Order Fulfilled, and one limit applies from there.
Can I branch on the order value?
Not with a threshold. Conditions compare for equal, not equal, present or one of a list, with no greater-than. Send a property such as a value tier from your system and branch on that.
Does a change apply to orders already waiting?
Yes. A changed limit applies at once to every case on that step.
Start for free
The Free plan includes 5,000 events a month.