Order Status Automation ยท NZ Wholesale
Automated dispatch confirmations and backorder alerts for wholesale orders that Shopify's email flows never reach. Triggered by Cin7 โ not by someone remembering to send a message.
If your trade customers order by email, phone, or through a B2B portal, those orders land in Cin7 directly. Shopify's dispatch notifications and order update emails are triggered by Shopify checkouts โ which means wholesale orders get nothing.
So customers chase status by emailing whoever picks it up. Someone opens Cin7, checks the order, and writes back. 30 orders, 30 status queries, 30 manual replies. Once a day, sometimes twice.
The order is in Cin7. The dispatch status is in Cin7. Every piece of information the customer needs exists in the system โ someone's just manually transcribing it into an email when asked.
Shopify's notification flows are purpose-built for consumer checkout. The scenarios wholesale introduces that fall through the gap:
Orders placed off-platform.
Phone, email, trade portal โ any order created directly in Cin7 is invisible to Shopify's notification system. No trigger, no email.
Backorders.
When a line can't ship on time, someone has to notice and tell the customer. Without automation, they usually find out by following up โ which means you're always playing catch-up.
Partial shipments.
Part of an order went out; the rest is coming. Shopify won't notify on a partial dispatch. Without something watching Cin7 for it, the customer doesn't know.
Honest version: if all your wholesale volume is small โ say 5 accounts who all call Sarah โ the manual handling is probably fine. This earns its keep when the volume of status queries is meaningful and the time spent on them adds up.
Dispatch confirmation โ when Cin7 marks it dispatched.
The moment an order status changes to dispatched in Cin7, the customer gets a confirmation. Your branding, your format, the right tracking link. No one has to notice and act.
Backorder alerts โ before the customer asks.
When a line goes to backorder status, the customer finds out from you, not by chasing. Turns a reactive problem into a proactive heads-up.
Partial shipment handling.
When part of an order dispatches and part doesn't, the customer gets a message that covers both โ what's on its way and what's still to come.
Customisable by customer tier.
Key accounts can get more detail. Smaller accounts get the standard template. The logic is yours to define, not hardcoded into the platform.
Manual status responses are surprisingly expensive at scale. Count the queries, the lookup time, the writing time, multiply by the hourly cost of whoever's handling it โ then see the annual number.
Three sliders, 30 seconds โ work it out before the call.
Open the calculator โA wholesale distributor with around 150 active accounts was fielding 30โ40 order status enquiries a week by email, each taking 5โ10 minutes to look up and respond to. We set up a dispatch confirmation triggered directly from Cin7 dispatch events, plus a backorder alert when lines moved to backorder. The status queries dropped sharply within a few weeks โ customers were being told before they thought to ask. The team reclaimed around 90 minutes a day that had been going on email management.
Step 1
From $750 โ credited toward the build
I map your order flow, where notifications are missing, and what automating them is worth in actual time. Fixed fee, credited toward the build.
Step 2
$4,000โ$12,000 fixed price
I build the Cin7-triggered notification flow โ dispatch confirmations, backorder alerts, partial shipment handling. Scoped from the audit, fixed price.
Step 3
From $400/month ยท cancel any time
I keep it running as your Cin7 config and order process evolves. On call when a Cin7 API change breaks a trigger. Month-to-month, no lock-in.
The TimeBack Guarantee
If the build hasn't cut the time on these tasks to under 20% of what you spend today โ within 3 months โ I refund the audit fee in full. On top of it already being credited toward the build.
The audit pins the baseline first, so the guarantee is tied to exactly what we scoped.
You manage wholesale orders in Cin7 that don't go through Shopify's checkout.
Order status queries from customers take meaningful time to answer each week.
Customers sometimes find out about backorders or delays by chasing, rather than you telling them first.
You have enough wholesale accounts that manual status comms doesn't scale without dedicated time.
Not sure if your volume justifies it? The free call answers that in 15 minutes.
It does, but only for orders placed through Shopify. Wholesale orders placed by phone, email, or a trade portal don't go through Shopify's checkout, so they don't trigger Shopify's notification flows. Cin7 is where those orders live โ and it doesn't have the same notification capability by default.
Cin7 status changes: when an order is marked dispatched, when a line item goes to a backorder status, when a partial shipment is created. The trigger is the system event, not a person remembering to send an email.
Yes. The template is yours โ your branding, your language, your tracking link format. You can also vary messages by customer tier if some accounts need a different level of detail.
The from-address can be a real inbox, so replies land where they'd normally go. Customers don't have to know it was automated.
Work out what that time costs โ then decide whether to automate it.
Timeback Systems Ltd ยท gettimeback.co.nz ยท The audit fee is credited toward your build โ and refunded if these tasks aren't cut to under 20% of today's time within 3 months.