Automate the tasks that repeat daily, have an unambiguous rule and whose mistakes are easy to undo: order status changes, reminders for unpaid orders, tracking-number notes and low-stock alerts. Tasks that need judgement — handling a return, making an exception for a good customer, cancelling an order — are not worth automating. The rule of thumb: automate what you could explain to a temp in one sentence.
How to spot a task worth automating
A good candidate meets three conditions at once. It repeats at least several times a day — for a weekly task, setting up the rule takes longer than doing it by hand for a year. It has an unambiguous rule with no "it depends" — if explaining it takes three sentences and one exception, the rule is not finished. And its mistakes can be undone — a wrongly changed status can be changed back, a wrongly sent email cannot.
The third condition matters most and is overlooked most often. An automation that emails two thousand customers has the same chance of being wrong as one that changes an order status — it just cannot be taken back.
Order status changes
The most common and safest place to start. Order packed → status "shipping". Handed to the carrier → "shipped". Delivered → "completed".
The gain is not only saved time. Order status triggers emails to the customer, so a more accurate status means fewer "where is my parcel" questions. And because the system changes it, an order does not sit in "processing" for three days because someone forgot on a Friday evening.
Reminders for unpaid orders
A prepaid order not paid within three days gets a reminder. After another seven, a second one. After fourteen it is proposed for cancellation.
This is the task nobody in a small shop does systematically — and it brings in money directly. What matters is that the rule can be stopped: if the customer pays in the meantime, the second reminder must not go out.
Tracking numbers and alerts
Writing the tracking number into the order and alerting on low stock are tasks that risk nothing and save attention. The alert also solves a problem you would otherwise notice only once the goods are sold out.
What to automate later, or never
- Handling returns — needs judgement, and customers can tell a person from a template.
- Cancelling orders without confirmation — irreversible and expensive when the rule is wrong.
- Repricing against competitors without an upper and lower bound — a rule without guardrails eventually runs away.
- Bulk emails without checking the recipient list — the most common source of damage from automation.
How MitoOps handles it
The Automations module works with rules of the form "when this happens and this holds, do that". The trigger is an event on an order or a shipment; the action can be delayed by hours or days. Ready-made templates switch on with a single click — precisely the four tasks above.
Every run is recorded, so you can find out afterwards what a rule did and when. The module runs in production.