OrderPing — A Merchant's Guide to Making Sure the Right Person Sees Every Order

Meet Maya — she runs a women’s apparel brand on Shopify with three fulfillment locations, a warehouse manager in Nevada, a CX lead in Portugal, and a part-time wholesale rep in New York. This is her story.

---

First, Let Me Tell You About My Problem Today

I run an apparel brand on Shopify — premium loungewear, a small fragile-collection line of ceramic-button cardigans, and a growing wholesale business selling to boutique retailers. We do roughly $1.6M a year, ship from three locations (our main warehouse in Reno, a 3PL in New Jersey for East Coast, and a small dropship hub in Portugal for EU orders), and run with a distributed team of four: me, Jamie (my warehouse manager in Reno), Sara (our CX lead in Lisbon), and Tom (our part-time wholesale rep in New York).

Here’s what keeps me up at night: every single order email from Shopify comes to my inbox. Every. Single. One.

Last month, a wholesale buyer placed a $1,400 order for 48 cardigans. She needed them custom-packed with individual tissue paper and a handwritten note — her boutique was doing a launch event the following week. I know this because the order notes said exactly that. The problem? I was at a buyers’ show in Chicago for three days with patchy Wi-Fi and a phone full of distracting messages. The order came in at 9pm on a Tuesday, sat in my inbox, and by the time I saw it on Thursday evening, we had 36 hours to pack and ship a custom order that normally takes two full days. We rushed it. One of the cardigans went out with the wrong size. The buyer wrote back a week later: “I appreciate the speed, but this isn’t the experience I expected. I’ll think about whether to reorder.” She hasn’t. That’s roughly $12K a year in future wholesale revenue, gone, because an order email landed in the wrong inbox.

Here’s my current “system” for making sure the right person sees each order:

1. Shopify sends the order email to [email protected] — my inbox.
2. I set up Gmail filters to forward wholesale orders to Jamie. They break every time a customer types “Wholesale” with a capital W or forgets a tag, because Gmail filters are essentially a brittle regex running on HTML emails.
3. I made a “shared” inbox at [email protected] that auto-forwards the Shopify notifications. Nobody checks it. We’ve all quietly admitted that.
4. When something urgent comes through, I manually Slack-message Jamie or Sara with “hey did you see order #4127?” — usually while they’re asleep in a different timezone.

The thing is: Shopify is great at capturing the order. It is terrible at telling the right person about it. The notification email is the same whether it’s a $12 sticker or a $1,400 wholesale order. The same whether it’s ordinary loungewear or the fragile-collection ceramic-button line that needs extra packing attention. The same whether it ships from Reno or Lisbon.

My team doesn’t need to see every order. They need to see their orders — the ones where they actually have a decision to make or a job to do. Jamie doesn’t care about a $22 retail order. He cares about a $700 wholesale order going out of his warehouse. Sara doesn’t need to see wholesale; she needs to see anything flagged VIP because the customer will email her next. Tom only cares about his own wholesale accounts.

What I need is dead simple: look at every new order, figure out who should know about it based on what it is, and tell them on the channel where they actually live. That’s the whole job.

---

What OrderPing Actually Gives Me (And Why Each Piece Matters)

---

1. Rules That Match The Way You Work — “Not every order needs the same person”

The Problem I Had

Gmail filters are built for spam, not business logic. You can filter on “from” and “subject” and a handful of header fields, but the actual content of a Shopify order — the line items, the customer tags, the shipping location, the total — all lives in the HTML body. Trying to route orders based on that with email filters is like trying to sort mail by reading the envelopes through frosted glass.

The other inventory and order apps I looked at before OrderPing all had “notifications” as a feature. But when I actually tried them, the notification settings were one global switch: “email me on every order.” That’s not a rule. That’s a firehose.

What I actually needed was something that could answer questions like:

• Is this a wholesale order? (tag match)
• Is it above a certain value? (order total)
• Does it include anything from the fragile collection? (product match)
• Is it shipping from the New Jersey location? (location match)

And then route based on the answers.

What OrderPing Does Instead

OrderPing lets me build rules — each rule is a set of conditions on the order, combined with AND/OR logic. Every new order gets evaluated against every active rule. The most specific rule wins (I set the priority), so I don’t end up triple-pinging people.

Here are the four rules I run today:

1. Wholesale orders — condition: customer has tag "wholesale". Routes to: Jamie’s Slack in #reno-warehouse, plus Tom’s email. Priority: highest.

2. High-value retail — condition: order total > $500 AND customer does NOT have tag "wholesale". Routes to: my phone (push), plus Sara’s email. Priority: second.

3. Fragile collection orders — condition: line item product is in "Fragile Collection" collection. Routes to: packing team Slack in #packing. Priority: third. This one fires in addition to the wholesale or high-value rule when it applies — I set it up as an “always also ping packing” rule specifically for fragile items.

4. Default fallback — condition: none (catches everything else). Routes to: Sara’s daily digest email. Priority: lowest.

That’s it. Four rules. Took me about ten minutes to set up. Every one of them is editable in a form — no scripts, no webhook URLs to hand-craft, no code.

Why This Matters for My Business

The wholesale buyer incident I described above? Under these four rules, her order hits rule #1 and rule #3 (she bought two ceramic-button cardigans in the fragile collection). Jamie’s Slack lights up in Reno. Tom gets an email. Packing gets pinged to set aside tissue paper. I don’t need to be in the loop at all — and that’s the point. The order gets to the right people without going through me as a middleman. If I’m in Chicago with bad Wi-Fi, the business keeps running.

The priority system matters too. Before OrderPing, I once tried running two overlapping notification setups on a different app and got three duplicate messages for every order that matched both. OrderPing’s “most specific rule wins” approach means I can layer rules without creating noise for myself.

---

2. Three Channels, One Source of Truth — “Where the person actually lives”

The Problem I Had

Every person on my team lives in a different digital room. Jamie, the warehouse manager, has Slack open eight hours a day and barely touches email. Sara, the CX lead, lives in Gmail — she’s got her inbox sorted into fifteen labels, and that’s where her work happens. I bounce between my phone (always) and email (sometimes), but if something’s truly urgent, the only thing I’ll see within five minutes is a lock-screen notification on my phone.

The previous order-routing setup I tried was email-only. Jamie never saw wholesale orders because, in his words, “I don’t check email, sorry.” Adding Slack meant forwarding every email to a Zapier hook that parsed it and posted to a channel, which cost me another $29/month and broke every time Shopify changed the email template. Adding push notifications wasn’t even on the table — nobody sold it.

What OrderPing Does Instead

OrderPing has three channels, all native, all running simultaneously:

• Email — up to 5 recipients per shop. I configure Jamie, Sara, Tom, me, and our returns-handling contractor once in the settings, then reuse those addresses across any rule. Notifications across all three channels draw from a single monthly quota — 100 on Free, 2,000 on Starter, 50,000 on Pro, unlimited on Unlimited.

• Slack — up to 5 incoming webhook URLs. I have one for #reno-warehouse, one for #packing, one for #ops, and one for #vip-alerts. Slack pings count against the same shared monthly quota as email and push — there’s no separate per-channel cap. No third-party Zapier glue required.

• Push notifications — delivered via ntfy, a free open-source app that lives on my phone’s lock screen. Setup was 90 seconds: scan a QR code in OrderPing, install ntfy from the app store, done. A $3,000 order now buzzes my phone within a few seconds of the customer hitting checkout.

I configure each channel once, at the shop level. Then when I build a rule, I pick which channels it uses — no re-entering Jamie’s Slack URL or Sara’s email address for every rule I make.

Why This Matters for My Business

Meeting each person where they already live is the whole reason this works. I’m not asking Jamie to install a new app or check email more often. I’m not asking Sara to join Slack. I’m sending each person a ping on the tool they already have open. The setup cost to my team was zero minutes of retraining. They just started getting the orders that mattered to them, on the channel they were already staring at.

And the “configure once, reuse everywhere” part saved me from a mistake I’ve made in every other tool: forgetting to update the recipient in one rule when I hire someone new or a team member leaves. When our old CX lead left in February, I updated Sara’s email in the shop settings once. Every rule picked up the change.

---

3. Per-Rule Channel Overrides — “VIP orders to the owner. Wholesale to the warehouse. Fragile to packing.”

The Problem I Had

Here’s the thing about “every channel gets every order”: it’s just a different flavor of the original problem. If I turn on email + Slack + push for every rule, now instead of one inbox drowning, my entire team’s tools light up for every $12 sticker order. Jamie’s Slack becomes noise. Sara stops opening the email alerts. My phone buzzes at 2am for a retail order I didn’t need to see.

The routing isn’t just “tell someone” — it’s “tell the right someone, on the right channel, and nobody else.” That last part is where every previous tool fell down. They treated channels as “all on” or “all off” per shop, with no way to say “this specific kind of order goes to this specific channel.”

What OrderPing Does Instead

Every rule can override the default channel set for that specific rule. Same engine, different routing per rule:

• Wholesale rule → overrides to: Jamie’s Slack + Tom’s email only. Not my phone. Not Sara. Not packing.
• High-value retail rule → overrides to: my phone (push) + Sara’s email. Not Jamie. Not Tom.
• Fragile collection rule → overrides to: #packing Slack only. Nothing else. Packing knows to add the tissue paper; nobody else needs this signal.
• Default fallback → routes to Sara’s digest email only. She sees the daily roll-up; nobody else is pinged.

Each rule is its own little routing decision. I can tune the channel mix per rule without affecting any other rule.

Why This Matters for My Business

This is the single most important feature, honestly. It’s the reason OrderPing works and the reason my team actually uses it. Signal-to-noise ratio is the entire game in notifications. The moment Jamie’s Slack starts getting retail orders, he’ll mute the channel, and now wholesale orders don’t reach him either. The moment my phone buzzes for a $22 order at midnight, I’ll turn off push, and now the $3,000 order at midnight doesn’t wake me up either.

Per-rule overrides let me keep each channel surgical. #packing Slack has exactly one kind of message: fragile orders that need extra care. Jamie’s Slack has wholesale. My phone has high-value. Everyone trusts their channel because nothing irrelevant shows up on it. That trust is what makes notifications actually work instead of getting ignored.

---

4. Real-Time, Webhook-Driven — “Seconds, not ‘next time someone checks the admin‘“

The Problem I Had

Some of the “notification” tools I tried before OrderPing were polling-based — they’d check Shopify every 15 minutes for new orders, then batch-send the alerts. That’s fine if you’re reporting on inventory trends. It’s useless when a $3,000 VIP order comes in at 11:47pm and your warehouse has a 6am pickup truck leaving in the morning.

I also had a homegrown Zap running for a while that fired on new orders. It worked, mostly, except when Zapier’s queue backed up, or when the email template changed, or when the webhook retried twice and sent two Slack messages. I stopped trusting it.

What I needed was real-time, in seconds, with a trail that tells me it actually went out.

What OrderPing Does Instead

OrderPing is webhook-driven, not polling. The instant Shopify creates an order, Shopify fires the orders/create webhook to OrderPing. OrderPing evaluates the rules and dispatches to the matched channels. In my experience, the time from “customer hits checkout” to “Slack ping in Jamie’s channel” is under five seconds. Pro and Unlimited plans run on a priority queue that protects that delivery time during traffic spikes — Free and Starter share the standard queue, which is fast on a normal day but can lag during a flash sale.

This works because OrderPing lives as close to the Shopify event loop as any app can without running inside Shopify itself. It doesn’t have to ask Shopify anything; Shopify just hands it the order the moment it’s created.

Why This Matters for My Business

Black Friday last year, a single $2,200 order for a custom-embroidered robe set landed at 11:47pm Eastern. Under my old setup, it would have sat in my inbox until 8am the next day. Jamie’s shift at the Reno warehouse starts at 6am, and he does the morning pickup run for outbound shipments at 7:30. Under OrderPing, the order hit #reno-warehouse Slack at 11:47pm. Jamie saw it at 6:02am when he opened Slack with his coffee. It was picked, packed, and on the truck by 7:28. The customer got a shipping confirmation the same day she ordered.

Five-second alerts is the difference between “we’re on it” and “we missed it.” For a premium brand where customers expect a concierge experience, that gap is brand-defining.

---

5. Notification History With Delivery Status — “Proof it went out, not just hope”

The Problem I Had

Every time I’d set up any kind of automation in the past, there was this nagging doubt: did it actually fire? Did the Slack message go through? Did Sara’s email land? Did Zapier silently rate-limit me? There was no way to check without asking each person on my team “hey did you get the alert for order #4127?” — which defeats the whole point of automation.

I also had a real incident: a Slack webhook URL got rotated because someone had archived and restored the channel. For a week, wholesale alerts were firing into the void. Jamie was checking the Shopify admin manually because he’d noticed the Slack pings had stopped, but I had no idea — from my side, the automation was “running.” No errors, no bounces, just silent failure.

What OrderPing Does Instead

Every alert OrderPing dispatches is logged, per channel, with a delivery status. I open the Notification History tab in the OrderPing admin and I see:

• Which order triggered the alert
• Which rule matched
• Which channel(s) the alert went to
• Whether each channel delivered successfully or failed (with the error reason if it failed)
• Timestamp down to the second

I can filter by date, by rule, by channel, by status. When Jamie told me a few weeks back that #reno-warehouse had been quiet, I pulled up the history, filtered to “Slack” + “failed,” and saw a string of webhook errors from three days earlier. Rotated webhook URL. I fixed it in two minutes.

Why This Matters for My Business

The “did anyone get that?” Slack thread is gone forever. When a customer emails asking “did you receive my order?” Sara pulls up the history, confirms the order was alerted to the right people at the right time, and can honestly say “yes, it’s been with our warehouse team since Tuesday at 2:14pm.” That’s not just internal peace of mind — it’s how you answer customer questions with confidence.

And debugging broken channels used to take a morning. Now it takes a minute. The difference between “silent failure” and “visible failure” is the difference between a month-long problem and a five-minute fix.

---

6. Daily And Weekly Digests — “Quiet inbox during the day, complete picture at the end of it”

The Problem I Had

Not every order needs an instant ping. Instant alerts for high-value wholesale? Yes. Instant alerts for fragile-collection orders? Yes. Instant alerts for a $24 set of lounge socks? Absolutely not — at our volume, that’s 40-60 pings a day of orders nobody on my team needs to act on individually.

But I still want someone to have an overview. Sara does a morning review of all new orders for customer service prep: watching for repeat VIPs, flagging anyone who’s emailed before, tagging orders that need a personalized thank-you note. She doesn’t need a ping for each one — she needs a single email with the full list, at a time that matches her work routine.

What OrderPing Does Instead

OrderPing lets any rule on the Unlimited plan use digest mode instead of (or in addition to) instant alerts. Pick daily or weekly, pick the time of day, pick the channels. OrderPing rolls up everything that matched the rule during that period and sends one clean summary.

Sara’s setup: the default fallback rule (all retail orders that didn’t match a more specific rule) digests to her email every morning at 7am Lisbon time. It’s one email. Ten or forty orders, doesn’t matter — one email. She reads it with her coffee, flags what needs attention, moves on with her day.

Rules that need instant routing (wholesale, high-value, fragile) still fire instantly. Digests don’t replace instant alerts — they’re a separate mode for different types of signal.

Why This Matters for My Business

The whole philosophy of my notification setup is this: every channel has a clear contract with the person receiving it. Jamie’s Slack contract: “you only see wholesale — act on it immediately.” My phone’s contract: “you only buzz for something over $500 — it’s important.” Sara’s digest contract: “you get one email a day — it’s everything else, handle at your own pace.”

Without digest mode, I’d have to either flood Sara’s inbox with 40+ individual order emails (which she’d ignore after two days) or skip her in the routing entirely (which means those orders get no CX prep). Digest mode hits the middle ground: comprehensive coverage, zero noise.

---

A Day in My Life With OrderPing

Here’s what a normal Thursday looks like now. Every order below is real; I pulled these from my last real Thursday.

7:03am Lisbon time — Sara opens her laptop and her morning digest from OrderPing is waiting. 27 retail orders from overnight, listed cleanest first: order number, customer name, total, whether they’re a returning customer. She flags three VIPs for personalized shipping notes. Takes her eleven minutes.

9:41am Reno time — a wholesale boutique in Denver places a $780 order for 24 pieces of our spring collection. Within five seconds, Jamie’s Slack in #reno-warehouse lights up with the order details, shipping address, and customer notes. He acknowledges with a 👀 emoji. It’ll go out in tomorrow’s morning run.

10:12am Lisbon time — Sara’s looking through her customer service queue and doesn’t need to ask anyone about a wholesale order. She knows it’s being handled because Jamie’s Slack picked it up; she can see that in the OrderPing history if she ever needs to confirm.

11:28am Pacific time — a $340 retail order comes in that includes a ceramic-button cardigan from the fragile collection. The high-value rule doesn’t fire (under $500). But the fragile-collection rule matches, so #packing Slack gets a single-line ping: “Order #4389 — 1x Ceramic Button Cardigan (Ochre) — fragile collection, tissue + bubble wrap.” The packing team moves it to the “needs care” tray. Takes them ten seconds.

2:17pm Pacific time — my phone buzzes. I’m mid-meeting with our accountant. Lock-screen push: “ORDER $1,240 — wholesale — Gallery Boutique NYC.” I don’t need to do anything — Tom and Jamie both already have it — but I see the signal. I know a big wholesale order just closed. I note it for the Friday investor update and go back to my meeting.

5:48pm Pacific time — a $3,110 custom-embroidered robe set order comes through. High-value rule fires. My phone buzzes. Sara’s email gets a line. I’m driving home, but I can pull over and call the customer to thank them personally within five minutes of checkout. She was stunned: “I literally just placed the order.” That’s the kind of moment that turns a one-time customer into a brand loyalist.

11:00pm Lisbon time — Sara’s winding down. Tomorrow morning’s digest is already being built for her. She doesn’t need to check anything tonight.

Contrast this with my pre-OrderPing Thursday:

• 7am: I wake up to 47 order emails in my inbox. I scroll through them on my phone in bed, trying to catch anything big.
• 9:41am: the $780 wholesale order comes in. It goes to my inbox. I’m deep in a call with a supplier. I don’t see it.
• 12:15pm: I see the order. Slack Jamie: “hey, wholesale order #4387, saw it?” He didn’t. Scrambles to process it.
• 11:28am: the fragile-collection order comes in to my inbox. Nobody sees it. It gets pulled, packed normally, shipped. Customer writes in two weeks later annoyed about the packaging.
• 5:48pm: the $3,110 order comes in. I miss it entirely because I’m driving. Customer gets a standard automated confirmation. No personal touch.

Same day. Same orders. Completely different experience for everyone involved.

---

The Pricing Feels Like a No-Brainer

Here’s the full plan breakdown, straight from my admin:

Feature	Free	Starter ($9/mo)	Pro ($49/mo)	Unlimited ($99/mo)
Notifications per month (shared across all channels)	100	2,000	50,000	Unlimited
Active rules	Unlimited	Unlimited	Unlimited	Unlimited
Email recipients	Up to 5	Up to 5	Up to 5	Up to 5
Slack webhooks	Up to 5	Up to 5	Up to 5	Up to 5
Push notifications	Yes	Yes	Yes	Yes
Per-rule channel overrides	Yes	Yes	Yes	Yes
Notification history	Yes	Yes	Yes	Yes
Priority notification queue	No	No	Yes	Yes
Daily / weekly digests	No	No	No	Yes
Priority support	No	No	No	Yes

I ran on Free for the first couple of weeks while I built out my four rules and watched the alerts land. Free gives you unlimited rules, which surprised me — the limit on Free isn’t how many rules you build, it’s the 100-notifications-per-month cap pooled across email, Slack, and push.

For my volume — about 40 retail orders a day plus wholesale, and most orders match two or three rules — that 100-per-month cap burns through in less than a day. Starter ($9) gets you to 2,000, which would last me roughly two weeks. Pro ($49) at 50,000 is the obvious tier for a real shop with steady order flow. The tipping point for me was actually the digest mode for Sara’s morning roll-up — that’s gated to Unlimited ($99) — so I jumped straight there.

Honest framing: $99 a month to make sure every order lands with the right person, on the right channel, within seconds of checkout — and to give Sara her morning digest on top of it — is trivial compared to one missed $1,400 wholesale order. I’ve already paid for OrderPing for the next decade by not repeating the Chicago buyers’-show mistake.

Billing goes through Shopify directly. One invoice. No separate credit card. Cancel anytime from the admin. I appreciate that because I’ve been burned before by apps where cancellation was a five-click process across three different dashboards.

---

Why This Works Better Than What I Was Doing

	Before OrderPing	After OrderPing
Where orders go	One inbox (mine)	Routed by rules to the right person on the right channel
How the team finds out	Forwarded emails, manual Slack pings, shared inboxes nobody checks	Auto-routed to each person’s native tool
Speed from checkout to alert	Minutes to hours (email delay + me seeing it + me forwarding it)	Under five seconds, webhook-driven
Audit trail	”Did anyone see that?” threads	Per-channel delivery log with status
Noise level	Every order pings the owner	Instant only for what matters, digest for the rest
Setup effort	Gmail filters, shared inboxes, Zapier hooks, custom workarounds	Four rules, ten minutes, done
Cost	$29/month for Zapier plus my time	Free up to 100 notifications/month; $9 for 2,000, $49 for 50,000, $99 for unlimited + digests
Failure mode	Silent — I’d find out days later	Visible — history tab shows every failed delivery

The whole philosophy shift is this: my inbox stopped being a routing layer. It used to be the central dispatch point where every order landed and I had to figure out what to do with it. Now it’s just… my inbox. OrderPing is the dispatch layer. Each person on my team has a clear contract with the channel they’re watching, and they trust that channel because nothing irrelevant shows up on it.

That trust is the whole thing. Notifications only work if the people receiving them believe each ping is worth acting on. The moment you break that, the tool becomes background noise. OrderPing’s rules + per-rule overrides + digest mode are what keep the signal-to-noise ratio high enough that every channel stays credible.

---

If any of this sounds like your Thursday, install OrderPing from the Shopify App Store. Setup is four or five rules and about ten minutes of thinking about who on your team should see what.