Just in (New Arrivals)
[Item or category] arrived this morning. [One line about it.] It's on the floor from [time].
Free guide
A practical guide to bringing your customers onto the Hub and reaching them by interest: where the invitation goes, how to name your interests, who sends what, the messages worth having ready, and a 30-day plan for the first month.
Written for the owner, manager or buyer who will run RetailBlasts at the store, and for the events lead and the counter staff who will send from it.
A store has many things worth saying, and most of them are not for every customer. The napkins people kept asking about are back; the season's first herbs landed; the workshop has four places left; new work from three makers is on the front table; holiday preorders open tomorrow. Each of those is useful to some customers and noise to the rest.
RetailBlasts organizes the relationship around that fact. A customer joins with an email address, picks the interests they want on a preferences page, and hears about those: by email until they connect the free Blasts app, on their phone after. The test for every send is the one a good shopkeeper uses: would the customer who ticked this interest be glad it reached them? The restock, the arrival, the workshop and the holiday hours pass. A weekly coupon to everyone does not. The occasional honest offer goes to the customers who ticked Offers, and only to them.
Put the invitation at the moments you already own, with the same code everywhere. Open Customers in your Hub and click Sync connections once to publish your enrollment code; the QR code and the printable enrollment kit come from the same screen.
Stand the kit as a card at the register and print the code or the QR on the receipt. A customer who enters the code in the Blasts app sends your store a connection request: you accept it on Customers, or auto-accept in Settings connects them on the spot. Give whoever is on the register one sentence to say: join, choose what you want to hear about, and hear about it.
A slip in the bag reaches the customer at home. A shelf talker on the department people keep asking about reaches the ones who care most about that department, and tells them the interest exists.
Add the enrollment code, or the standing enrollment link where it is enabled for your Hub, to the order and pickup emails your online store already sends and to your newsletter welcome. There is no Shopify, WooCommerce, Square or loyalty connector: you paste the line into your own template yourself, once.
If your signup form can post to a URL, point it at the inbound webhook on Integrations, or use the Zapier app on request, so each new customer joins as an email subscriber the day they sign up.
Every door leads to the same consent-based relationship. A customer can change their interests, mute you or disconnect silently at any time.
Most stores start with a list: the newsletter subscribers, the opted-in customers your online store lets you export, the special-order book in a spreadsheet. Export it as a CSV and use Add many at once on Customers. The file needs an email column; the Hub also recognizes name, phone, birthday and an interests column, and previews everything first. Tick the opt-in box for people who already agreed to hear from you and they join as email subscribers right away; everyone else is invited.
Onboarding seeds six for a new store: All Customers, which reaches everyone and cannot be deleted, plus New Arrivals, Back in Stock, Events, Offers and Store Updates. Rename them in your store's words, and add the ones your customers would recognize by name. Open interests appear on each customer's preferences page; you can also assign a customer to any interest by hand from Customers.
There is deliberately no pickups or holds interest. A hold, a special order or a ready order is one person, and that note belongs in their conversation thread.
Roles keep the All Customers sends and the billing with the owner while the people who know send to their own interests.
This is the part worth being clear about, because it is where a retail tool usually overpromises. The Hub holds no stock, order, purchase or registration data at all. It does not know what anyone bought, what is on hold behind the counter, what landed in the stockroom, or who put their name down for the workshop. No point-of-sale, inventory, online-store, loyalty or event-registration connector exists to tell it.
What works, and works well, is simpler. Your own system or the packing slip tells your team the delivery is in. Your team sends one note to Back in Stock or New Arrivals. When a customer replies YES to a limited shipment, the Hub counts it and a person follows up; nothing is held or charged. When an order or a hold is ready, your team opens that customer's thread and sends one line: it is here, it is under your name, reply if you want a different day. It takes fifteen seconds and it reads like a person, because it is one.
If you want any of that automated one day, the honest answer today is that you would build it yourself against the inbound webhook and the Zapier app. Nothing in this guide depends on it.
A send from the Hub is a typed or rich note with a photograph of what landed, links and up to three attached files of 5 MB each, such as the workshop calendar. Pick the interest, ask for a YES or NO reply when you want to gauge interest, click Send a test to me, then Send now, Schedule for later, or Repeat weekly. Delivered counts come from the Blasts app rather than open pixels, and read counts appear where your account's sending lane reports them; neither is a confirmation, so ask for a YES or NO reply when you need an answer.
Replies land in Conversations, one inbox for both rails. A regular asking whether the cookbook could wait for her until Saturday, a question about a workshop, a customer checking on a special order: assign each thread to the counter or the buyer, and keep the hold wherever you keep holds today. The Hub is not the stock book.
A customer who joined by email receives every message by email, through the Hub, until they connect the Blasts app; then the Hub moves their delivery on its own. Email is metered in email credits; every new Hub includes 50.
A Content Series is a set of different prewritten messages on a schedule: the buyer writes four notes on Sunday, and each Thursday at 10 a.m. the next one goes to New Arrivals once the delivery is unpacked. A customer who joins in week three gets week three's note, never the backlog. Content Series is included from the start.
Hub Pro adds Journeys and Event Campaigns. The Welcome to the Store starter runs five messages over three weeks from the day each customer joins: what they can hear about, an invitation to choose their interests, what's new, the events, and a reminder that the choice is theirs. The In-Store Event starter lays out six messages around one date: the announcement two weeks out, the reminder a week out, a places-left update three days out (a number a person types), the day before, the morning of, and the thank-you the day after. Change the date once and the pending messages move. Campaign steps carry no YES or NO; to gauge interest, send a regular Blast. Hub Pro unlocks at $500 in cumulative credit purchases for any organization, and nothing in the 30-day plan depends on it.
One month from sign-in to a list you can reach by interest. Adapt the order to your trading week.
Sign in at /hub/signin/ with an email code, a passkey or your Blasts sign-in; a new store sets up its Hub through onboarding. Set the store name, website and timezone. Open Customers, click Sync connections, and print the enrollment kit.
Stand a card at the register, put a slip in the bag, add a shelf talker to the department people ask about most, and paste the code into your order and newsletter emails. Export the opted-in list and use Add many at once. Decide on auto-accept. Give whoever is on the register one sentence to say.
Rename the seeded interests in your words and add your departments by name. Invite the manager as an Admin and the buyer with New Arrivals and Back in Stock. Send your first note to the interest it fits about something true this week, after Send a test to me. Write the holiday hours now and schedule them to Store Updates.
Send something that came back to Back in Stock with a YES or NO reply and watch the count come back before you open; a person follows up with each YES. Give the counter a daily habit: open Conversations at the start of the day, answer the questions, send the ready-for-pickup notes your own system flagged.
Read the Reach funnel: how many on email, how many connected, through which door. Start a weekly what-is-new Content Series to New Arrivals if the delivery lands on a predictable day. Decide the monthly rhythm (just in, back again, this weekend, seasonal, store news, an offer now and then) and check your credit runway on Home.
Blasts, the platform underneath, does carry those sender features when a message is sent from the Blasts app rather than from your Hub. This guide describes only what the Hub sends.
There is nothing to apply for and nothing to read first. Sign in to your Hub, set it up through onboarding if you are new, and buy credits on BlastCredits at standard retail pricing when you are ready to send. The retail documentation covers every screen this guide mentions, in customer and store terms.
See it in action at Morrowpine Market (a fictional example organization created to show the product, not a customer)
Product facts on this page reflect published Blasts.app information as of September 24, 2026.