What is RetailBlasts?
RetailBlasts is the direct line from an independent store to its customers, organized by what each customer wants to hear about. A customer joins with an email address at the counter or on the store's website, picks interests such as New Arrivals, Back in Stock, Events, Offers and Store Updates on a preferences page, and hears when something in those interests happens: by email until they connect the free Blasts app, then on their phone. The Hub is where the store works: one interest per kind of news, a composer, replies in one shared inbox, and roles so the buyer sends arrivals and the events lead sends events. It is not a point-of-sale, inventory, online-store or loyalty system and it connects to none of them: the store knows something is back or a workshop has places, and tells the customers who asked.
Do customers have to install an app before we can reach them?
No. A customer on your list receives every message by email until they connect the Blasts app; when they do, the Hub notices and moves their messages to the app on its own. Blasts itself is connection-based: nobody can be reached on it by a store they have not approved.
How do customers join, and does entering the code connect them?
They join with an email address: at the counter, on your website form, or through an opted-in import from your newsletter tool or online store. To move to the app, a customer installs the free Blasts app and enters the short enrollment code from the counter card, the receipt or the bag slip. That sends your store a connection request, which you accept on Customers; with auto-accept on in Settings they are connected the moment they join. Your Hub prints the kit with the code and a QR code.
People receive on the Blasts app for iOS or Android, on a browser extension for Chrome, Edge, Brave and other Chromium browsers, or in the web app at blasts.app.
How do customers choose what they hear about?
On their preferences page, which is linked from the counter card and every email. They tick the interests they want, such as New Arrivals, Back in Stock, Events, Offers, Store Updates and anything you added by name, and change them whenever they like. You can also add a customer to an interest by hand when they tell you at the counter. Nothing sorts a customer automatically.
Does the Hub know when something is back in stock?
No, and it does not pretend to. Your inventory system or the packing slip tells your team; your team sends one note to Back in Stock. Back in Stock is an interest a customer chooses, not a per-product alert: nobody subscribes to one item, and nothing is triggered by a stock change.
That is why the note reads like a person wrote it. Somebody did, the morning it landed.
Does RetailBlasts connect to Shopify, WooCommerce, Square or our loyalty platform?
Not with a native connector, and we will not pretend otherwise. There is no built-in integration with Shopify, WooCommerce, Square, Lightspeed, Clover, Klaviyo or any other point-of-sale, inventory, online-store or loyalty platform, and the Hub never sees orders, stock or spend. The Hub's doors are generic and work with all of them: import a customer list as a spreadsheet, point any website form or automation tool at the inbound webhook, receive signed events back when a customer connects, replies or opts out, and ask for the Zapier app if you would rather not write code.
Separately, the Blasts platform has its own integrations: Blasts integrates with Shopify, WooCommerce, Stripe, PayPal and Zapier, and can log sends as contact activities in Salesforce, HubSpot and Dynamics 365. That is the platform, not a RetailBlasts connector to your till.
If a customer replies YES to a limited shipment or a workshop, is it theirs?
A YES is the customer's own answer, which the Hub counts. It does not hold merchandise, reserve a place, charge a card or register anyone. Someone on your team reads the count and follows up with each person, and whatever takes names for the workshop keeps taking them.
Is this an event-registration or ticketing system?
No. An Event Campaign carries the messages around one date, from the announcement two weeks out to the thank-you the day after, and moves them all when the date moves. It holds no places, counts no seats and takes no payment. If a form, a ticketing site or a sign-up sheet at the counter takes names today, it keeps that job.
When should we send to All Customers?
When something genuinely concerns everyone: holiday hours, a closure, a move, a change of ownership. The Hub asks you to confirm an All Customers send with a passkey or your phone, which keeps it deliberate. Most merchandise and event news is more useful to the interest it belongs to, and a store that keeps the everyone-send rare keeps it read.
Does the Hub replace our email?
No. Email is the first channel inside the Hub: a customer who joins by email receives every message that way, through the Hub, until they connect the Blasts app. Your newsletter and lookbook stay wherever you send them now. Email is metered in email credits, and every new Hub includes 50.
Email is still the right tool for the long lookbook with twenty photographs. A Blast is the right tool for the restock the customer asked to hear about.
What does it cost to reach 4,000 customers, and is there a subscription?
A typed Blast is one credit per customer, so a note to all 4,000 is 4,000 credits, and a note to the 480 who chose one interest is 480. Credits are prepaid one-time deposits that never expire, with no subscription or marketing-platform contract. Current packages are on BlastCredits.com.
Will customers feel spammed?
Customers decide, and they are well armed: they approved you, they chose their interests, and at any time they can change them, mute you for a day, set quiet hours or disconnect silently. Blasts also auto-delete after 30 days. The discipline is the one a good shopkeeper already uses: send the restock to the people who asked about it, and keep the everyone-send for things that concern everyone.
What can we put in a message we send from the Hub?
A typed or rich note with photographs of what landed, links and up to three attachments of 5 MB each, to one interest or to everyone. You can ask for a YES or NO reply the Hub counts, schedule a send ahead or repeat it weekly, and read every reply in one conversation thread. Delivered counts come from the Blasts app, not tracking pixels; read counts appear where your account's sending lane reports them. Blasts itself, the platform underneath, also carries badges, voice Blasts and polls when a message is sent from the Blasts app rather than from your Hub.
Is there a verification program or a discount for retailers?
No. Stores buy at standard BlastCredits pricing. The verification program with bonus credits is a nonprofit and church program and does not apply to a retail Hub, and verification has never been a condition of Hub access. The only threshold is Hub Pro at $500 in cumulative credit purchases, the same for every organization.
Where do we learn how the Hub actually works?
The shared Hub documentation is public at blastshub.com/en/docs/, and the retail version, written in customer and store terms, is at blastshub.com/en/docs/for/retail/. Blasts itself, the consent-based network underneath, is documented at blasts.app.