What this helps you do
Your point-of-sale keeps the takings and the stock count, your online store keeps the orders, your loyalty rules stay wherever you run them, and whatever takes names for a workshop keeps the list. The Hub keeps none of that: it holds the people who chose to hear from you, the interests they picked, and what you sent. Nothing about an order, a price, a stock level or a registration lives here, which is why a restock notice is something a person sends once their own system tells them the delivery landed. Whatever the system, the doors are the same four: a CSV export you upload on Customers, the inbound webhook that adds one person at a time, signed outbound events that tell your systems who connected or replied, and the Zapier app when both ends are apps rather than code.
When to use it
Use CSV when your newsletter list or customer export is the thing you already have. Use the inbound webhook when a signup form or an online-store confirmation should add someone the same day. Use outbound events when your own spreadsheet or CRM should know who connected. None of it is required: plenty of shops run the Hub on the in-store code and email addresses taken at the counter.
How to do it
- Export the opted-in part of your customer or newsletter list and upload it on Customers. Email is the only required column; addresses are checked and previewed before any invitation goes out.
- Point your website signup or your online store's confirmation step at the inbound webhook on Integrations, so a new customer joins within minutes.
- Add your HTTPS endpoint under events out if your own systems should hear when someone connects, opts out or replies.
- Ask for the Zapier app if you would rather wire the store and the Hub together without code.
- Send the restock or the pickup note from Send or Conversations when your own system tells you the item is in. The Hub is not watching your stock.
Example
A garden center exports its opted-in newsletter list, uploads the CSV, and points the website form's confirmation step at the inbound webhook. When a delayed order of spring bulbs finally lands, the manager reads it on the packing slip and sends one Blast to Back in Stock. The Hub never saw the order; it just carried the message to the people who asked for it.
Good to know
- There is no point-of-sale, online-store, inventory, loyalty or event-registration connector. Shopify and WooCommerce appear in the Blasts platform's own integrations, not as a RetailBlasts connector.
- The Hub holds no order, stock, price, spend or registration data, and cannot trigger a message from a sale, a stock change or a sign-up.
- Everyone arriving through a door still picks their own interests and can leave at any time.