Automating customer journeys and retail reporting in HubSpot comes down to one dependency: the data from your store has to reach the CRM reliably before any workflow or dashboard is worth building. For Small Batch Cigar, a US online retailer of boutique cigars, our HubSpot onboarding covered that connection to the e-commerce site and inventory database, alongside tailored properties, views, dashboards and automated journeys.
Short answer
A specialty retailer needs four things in HubSpot to automate journeys and reporting: a reliable sync with the store and inventory data, properties and views that match how the team actually sells, automations tied to real retail events such as product drops and restocks, and dashboards built around the decisions the business makes. Small Batch Cigar's onboarding covered all four.
Established in 2012, Small Batch Cigar is an online retailer and curated distributor of boutique, high-end and limited-edition cigars in the United States. It focuses on quality, fast shipping and careful product handling, and it specializes in sought-after releases from boutique manufacturers, including brands such as Black Label Trading Company, alongside curated samplers and subscription clubs.
That business model shapes the CRM. The reporting in this project covered wholesale performance, retail accounts and consumer engagement, so the setup had to serve more than one type of customer, and much of the calendar is driven by new releases, restocks and limited editions. A generic CRM setup would not reflect that.
The project was an enhanced onboarding of HubSpot's Professional-tier bundle of Hubs, which HubSpot now sells as the Professional Customer Platform. The goal was a scalable environment with four parts: clear dashboards and reports, properties and views tailored to the team, automated customer journeys, and all of it synchronized with the e-commerce website and the inventory database.
Each of those four parts was a challenge in its own right. Here is what each involved, and what it takes to get right if you are a specialty retailer considering the same setup.
The sync had to be reliable between HubSpot, the website and the existing database, so that customer orders and account information stay current in the CRM. Everything else depends on it. A workflow that emails customers about a restock is only as good as the inventory data that triggers it, and a dashboard showing retail account performance is only as accurate as the orders that feed it.
What it takes: decide which records and fields need to cross over and how often, before anyone builds an automation. Then plan to monitor the connection, especially on high-traffic release days, when a quiet failure can go unnoticed at the moment it matters. If you are connecting other systems too, see our HubSpot integrations services.
We customized properties and views so the team could work with relevant, structured data, and tailored pipeline views to the internal sales process for boutique product distribution. For a business that serves both wholesale accounts and consumers, this is where the two worlds either stay organized or blur together.
What it takes: an agreed definition of each customer type and each stage before the properties are created. Properties are cheap to add and expensive to clean up, so fewer, well-defined fields beat many optional ones.
We built workflows to support and standardize customer communication during new product drops, restocks and standard lifecycle stages. In specialty retail, those are moments when customers are paying attention, so inconsistent follow-up is easy to notice.
What it takes: journeys triggered by real events in your data rather than by calendar dates, plus an owner who reviews them as the product calendar changes. Release-driven automation also needs regular review, because the releases themselves keep changing.
We configured dashboards and reports that surface insights on wholesale performance, retail accounts and consumer engagement, designed around the specific tracking and decision-making needs of the business.
What it takes: start from the decisions, not the data. Ask which questions the owner and the sales team need answered each week, and build reports for those. Expect to revise them once real sales data from new releases starts coming in.
The result was a HubSpot setup with data-driven dashboards, tailored pipeline views, automated product journeys and a synchronized ecosystem connecting HubSpot, the website and the database. In practical terms, the team now has one structured environment for managing retail accounts, e-commerce data and customer journeys.
A setup like this is worth it for the right retailer, but it is not free of costs, and it helps to know them going in:
It fits a specialty or e-commerce retailer that sells online, runs a steady calendar of releases or restocks, has a team making weekly decisions from sales data, and already holds its orders and inventory in systems that can be connected. It suits businesses serving both wholesale accounts and consumers particularly well, because that is where structured properties and views pay off most.
It is probably too early if your product and inventory data still live in spreadsheets that change by hand, or if nobody on the team will own the workflows after launch. In that case, start by cleaning up the data and deciding who owns the CRM.
With the foundation in place, we identified four opportunities to build on:
For other examples of how we build on HubSpot, see how we built two customer-facing freight calculators for Freightzy, how we rolled out HubSpot's Prospecting Agent at Eternity Group Mexico, and our campaign and conversion path work for VivaWell.
Yes. Workflows can trigger communication from events such as a new product release, a restock or a change in lifecycle stage, as long as the data those triggers depend on reaches HubSpot reliably. For Small Batch Cigar, we built workflows to standardize customer communication around new product drops, restocks and standard lifecycle stages.
A defined data model first: which records, properties and events need to reach HubSpot, and how often. Then the sync itself, and then monitoring, because a sync that silently fails leaves automations running on stale data. The Small Batch Cigar project connected HubSpot to the store and the inventory database so orders and account information stay current.
Yes, but it takes deliberate structure. Wholesale accounts and individual consumers behave differently, so they need their own properties, views and, often, separate pipelines and reporting. In Small Batch Cigar's case, separating the wholesale B2B pipeline from direct consumer marketing more fully is one of the next opportunities we identified.
Small Batch Cigar's onboarding was built on HubSpot's Professional-tier bundle of Hubs, which HubSpot now sells as the Professional Customer Platform. Whether you need that tier depends on how much automation, custom reporting and segmentation you plan to run, so it is worth scoping before you buy.
Design them early, but expect to refine them. A dashboard is only as useful as the data behind it, and for a retailer with seasonal and limited-edition releases, the questions worth asking change as new sales data comes in. Plan a review of your reports after the first few release cycles.
Want your store and your CRM working as one system?
We're a HubSpot Elite Partner. We'll scope what your retail business needs from HubSpot before you buy a single seat. See our HubSpot implementation and onboarding services.
Book a call