What I like best about OneSignal is how it lets me set up segmented push and SMS alerts for our B2B electronics buyers, and I can tag each client with their part number interests, allocated order status and preferred alert types all in one dashboard. Before we started using it, I was manually sending stock updates and lead time changes through separate emails and group texts, and I learned the hard way with our supplier Pacific Component Supply. They notified us that a batch of wireless controller chips would be delayed six weeks, and I only put that delay note in our shared spreadsheet. I was sending out a mass stock alert and forgot to exclude the buyers who had pre-ordered that exact chip. One of our biggest retail clients got the “in stock” notification, committed to a downstream sale, and then we had to call them to break the bad news. That cost us a small reorder and a lot of trust. After that mess, I knew I needed a tool that can filter audiences automatically before any alert goes out.

I really rely on the custom tags and journey automation features. I can tag every buyer by their SKU interests, pricing tier, and whether they only want critical delay alerts, not routine stock updates. When we get supply updates from vendors like Pacific Component Supply, I just update the tag on the affected product, and OneSignal keeps that segment separated. I also love the A/B testing and delivery scheduling; I can send alerts at times that work for our west coast and east coast buyers separately, instead of blasting everyone at once. A couple months ago, a buyer told us they didn’t want to get pings for anything except shipment release notices for their bulk HDMI cable order. I set their tag and built a simple journey rule, so they only get triggered alerts when their goods are ready. That would’ve been impossible to manage reliably when I was doing everything manually.

CSV bulk uploads also save me hours every time we onboard new reseller clients. I import their account details, tag their preferred product lines, and they are ready to receive relevant alerts right away. Every sent notification, click and reply stays attached to their subscriber profile. If our sales rep is out visiting clients and I have to cover their accounts, I can quickly pull up their alert history and see what messages they’ve received, no long phone calls to chase context. We’re just a small wholesale electronics shop, we don’t have a dedicated dev team to build custom notification tools. OneSignal is straightforward enough for me to manage without constant engineering support. It’s not perfect, I still double-check every segment before sending urgent supply alerts, but it stops those careless mix-ups where the wrong client gets the wrong update. It keeps our communications with resellers precise and helps us avoid the costly missteps we ran into before. Review collected by and hosted on G2.com.

Honestly, OneSignal works great for our stock and shipment alerts for electronics resellers, but there are some frustrating limitations that have burned me before, and the trouble with Pacific Component Supply is still fresh in my mind. I was doing a bulk CSV update to adjust subscriber tags, marking all buyers waiting on those delayed wireless controller chips so they would be suppressed from in-stock alerts. I mapped all the columns correctly, uploaded the file, but OneSignal didn’t properly overwrite the old tags for that group. The alert still went out, and one of our retail resellers got the wrong stock notice again. I thought I had locked that segment down, and I ended up spending the whole afternoon calling customers to apologize and reset expectations. Now I only update small batches of subscribers at a time, and I manually spot check every single suppressed account, which eats up a ton of my week.

I also find the alert rule logic pretty rigid for our supply chain workflows. We often have partial shipments from our vendors. For example, when we received a partial delivery of USB power modules from Zenith Electronics Parts last month, I tried to set up a rule that only alerts buyers whose order quantity matched the newly received stock. OneSignal’s filtering can’t split a single SKU’s subscriber list by the quantity they ordered. I had to manually split the list into two separate CSV files, one for customers getting partial fulfillment and another for those still waiting. It took me hours, and I almost mixed up the two lists before I sent anything out. I wish there was a way to build more nuanced conditional triggers around order quantity and partial shipments.

The notification preview is another weak spot. I can see how the message looks on mobile, but there’s no quick way to test it against a specific subscriber tag. I once drafted a delay alert for buyers waiting on parts from Zenith Electronics Parts, and I accidentally left in a placeholder for the revised ship date. I didn’t catch it until a buyer replied confused, asking what the new timeline was. There’s no sandbox test group that inherits the exact same tag rules as our real customers, so testing feels risky. Review collected by and hosted on G2.com.