Contact
Email shin@sognoragroup.com. Include your store URL, the order number, and roughly when the event should have been sent. Screenshots help — remove buyer names, street addresses, email addresses and payment details first. Never send a password, an API token or a staff login; support does not need them.Building your first automation
Open the app from your dashboard. All four triggers are already on, so there is nothing to connect and nothing to configure.Press Open the builder in a new tab at the top of the card, before you read the steps. The builder opens on a blank automation in a tab of its own, so the steps stay on screen behind it: pick the trigger from the Order Triggers group and Apply, press + below it and choose the action, then fill in the subject and body. Every value comes from Customize beside the field rather than from the keyboard. Then Apply, then Activate. The card that leads carries a subject and body, and a Copy the draft button that puts both on your clipboard; what you paste has a [name] everywhere a value belongs, and each one is replaced with Customize beside that field.Button names follow your dashboard language.Then press Send a test event on that trigger. The app reports a real event for your most recent order, so your automation runs within about a minute and you can read the result before a customer ever does. The activity log marks the row as a test, and it is free — a test never uses one of the free plan's monthly events.Putting the tracking number in an email
In the email action, press Customize beside a field rather than typing the value. Seven values are there to drop into the message: order number, tracking number, carrier, tracking link, items, order total, and when it happened.The trigger carries an eighth field that is not in that list: the customer's contact. It connects the buyer to the automation, which is what lets Send an email reach the right person. It also puts the contact's own fields within reach in the same message, so you can open with their first name.Fields that do not apply are left out of the event rather than sent empty. An order canceled before it shipped carries no tracking number, so build cancellation emails without those fields.Which trigger you build on decides whether the number is there yet, and the app decides it from your own orders rather than asking you. Step 1 on the card names one trigger and counts, in the same sentence, what it was read off: how many of your last 30 shipped orders already carried a tracking number at the moment they were marked shipped. Marking an order shipped in your dashboard records the number in the same action, so a store that works that way is pointed at Order shipped and the email is complete. A shipping or label app is different: it can mark the order shipped first and add the number afterwards, and an email built on Order shipped would already have gone out with the tracking line empty, so a store that works that way is pointed at Tracking number added. Under 5 shipped orders there is nothing to read yet, and step 1 names the safer of the two with no count in it rather than guessing.The test event names the other trigger, as the way back. It reports your most recent shipment exactly as it stands, so if that shipment had no tracking number the app says so on the spot and names Tracking number added — the same thing you would have found out from a customer's email. Both events are reported whichever you build on — the shipped one with no number, then the tracking one carrying it — and the activity log shows both.The first email action on a site asks for sender details before the template opens. That step belongs to the automation builder rather than to this app, and the default reply-to address cannot be restored once you change it, so pick the address you want customers to answer to.You cannot see the triggers in the builder
Three things to check, in this order. The app has to be installed on the same site you are building the automation on. The triggers appear under this app's name in the trigger list, not under the store's own triggers. And if you installed an earlier version, open the app market listing and accept the update, because a new permission is only granted when you approve it.If all three are true and the triggers are still missing, email support with your store URL and we will check the installation from our side.Will a customer get two emails for one shipment?
Not from one shipment. Adding a tracking number in your dashboard marks the order fulfilled and changes its shipments, which sends this app two notifications about a second apart. Both are recorded, and only one event is reported: Order shipped, with the tracking number already in it. So the activity log shows one row for that shipment rather than two: the second notification is folded away, and Show folded duplicates above the table shows the folded rows and says how many there are.Tracking number added reports only when a tracking number appears on, or changes for, an order that had already shipped — which is exactly the case where the customer needs to hear from you again.From another app, yes. A shipping, label or fulfillment app that already emails your customers keeps doing it — this app cannot see that email and cannot stop it — so an automation you build here sends a second one for the same parcel. Turn the other app's shipping email off before you activate yours, or leave yours deactivated until you have.Order shipped comes from the order being marked fulfilled, not from who marked it. This app reads the order's fulfillment status back from your store and never looks at the sender, so a fulfillment your label app records counts the same as one you record by hand.What the activity log means
Reported means the event reached your automations. It does not mean a customer was contacted: this app only supplies the event, and whatever a customer receives is sent by the automation you built on it. With no automation built, a reported event simply has nothing waiting for it.A shipment reported with nothing in its tracking field is marked No tracking number beside the badge. The event reached your automations, so the row is not a failure; what it tells you is that anything built on it had no number to put in the message, which is the case for building on Tracking number added instead.Skipped means nothing was reported, and the row says why: the trigger is switched off, the order has no order number, the free monthly limit is reached, or “The shipped event already covered this order”. The log shows all of them except that last one, which is the app deduplicating one shipment — those rows are folded away until you press Show folded duplicates. Every one of them is stored and counted the same either way.Failed means the report was attempted and did not go through. The app retries three times over about ten seconds first; a row only becomes failed after all of them. Press Try again on the row in the activity log. It re-reads the order, so a tracking number you have corrected in the meantime goes out corrected, and an event that did land after all is not reported twice. A row skipped at the free monthly limit carries the same button.The free plan and its limit
The free plan reports 30 events per calendar month, counted in UTC. Nothing is charged automatically. Past 30, new events are recorded as skipped and do not reach your automations. After you upgrade, use Try again on each row you want to send. Only events a customer caused count: a skipped event costs nothing, a failed one gives its slot back, and a test event is free, so checking your own setup costs you nothing.At the limit, new events are recorded as skipped with the reason “Free plan limit reached for this month” and the app says so on its first screen. Test events still work at the limit. Upgrading reports the next event straight away, with nothing to switch back on.The events blocked while you were at the limit are not reported for you afterwards, and that is deliberate: a shipping notification arriving four days late is worse than none, and thirty of them going out the moment you upgrade would reach thirty customers at once. They keep a Try again button in the activity log instead, so you decide which ones are still worth reporting, order by order.What this app does not do
It supplies triggers and their values. It does not send the email, the SMS or the HTTP request — your automation does that with the platform's own actions, so the message, the design and the timing are yours. It does not fulfill orders, buy labels, track parcels or edit orders.Cancelling, uninstalling, and your data
Cancelling the plan returns the store to the free 30 events a month; the triggers keep working and your automations stay exactly as they are. Uninstalling removes the triggers from the builder, and any automation built on them stops firing.When the removal is delivered, everything this app stored for your store — its settings, the activity log and the monthly count — is deleted. Event rows are deleted after 90 days in any case. See the privacy policy for the detail.