Settings
How your tracking page looks, and where your events go.Your tracking page
Create a page in your online store, add the Enroute tracking block to it, then paste that page's address here. Customers who follow a tracking link land there.
A path on your own store, starting with a slash. Leave it empty until the page exists.
How long you expect an order to take before it ships. It sets what the customer is told while the order is being made, and it is the window the production check measures.
One sentence, shown under the progress steps. Keep it a range rather than a date: a date that slips is the message that creates the question you are trying to prevent.
What the customer sees
The progress steps and the four shipment moments, with your own sentence about what to expect. No carrier scan feed at all. This is the default.
The same steps, plus every carrier scan with its place and time.
Whichever you choose, the customer sees your operation: who makes your products is never shown on the tracking page.
Colours
Used on the tracking page so it looks like the rest of your store.
A small "You might also like" row under the order, drawn from your own catalogue.
Events
What gets sent to the places you connect below. Turning one off stops it everywhere at once.
Where your events go
Enroute never contacts your customers itself. It hands each event to the tools you already use, and they decide what to send.
Klaviyo Not connected
Paste a Klaviyo private key and each event arrives as its own metric you can build a flow on.
Once saved, the key is never shown again, here or anywhere else.
Shopify Flow
Nothing to set up: the triggers appear in Flow on their own once the app is installed.
Your own endpoint Not connected
A signed JSON POST per event. Works with Omnisend, Sendlane, Zapier, Make or anything you have built yourself. Failed deliveries are retried with backoff for about a day.
Ticking this finishes that step of your setup checklist.