StoreHub Missing Features: 3 Jobs Still Need People

StoreHub missing features start after the sale

StoreHub’s pricing page already lists a point-of-sale app, inventory, a customer database, reporting and integrated payments in its entry plan. The higher plans add multi-location management, advanced inventory, stock transfers and workflow automation. Its retail page also documents exchanges, refunds, marketplace connections, a Webstore, loyalty and SMS promotions.

Use those features before buying another tool. A retailer whose customers buy at the counter or through StoreHub’s documented online channels may already have the clean path it needs. StoreHub’s own Webstore and marketplace connections are the sensible answer when the job is catalogued products, shared stock and a standard checkout.

The gap appears when the customer takes another route or the evidence is outside the system. StoreHub can hold the final record. It cannot decide what happened in an unstructured conversation or what is physically on a shelf without somebody supplying that evidence.

Verdict: keep StoreHub as the operating record. Inspect the work that happens before data reaches it and after an exception leaves it.

WhatsApp enquiries do not become orders by themselves

A customer asks whether a size is available, sends a photo of the colour, changes the pickup outlet and confirms the order in WhatsApp. StoreHub’s public retail pages document its own Webstore, marketplaces and SMS marketing. They do not document a WhatsApp conversation becoming a StoreHub retail order.

StoreHub’s Takeaway & Pickup page makes the boundary unusually clear. Its answer to WhatsApp and phone orders is to send customers through a Beep-powered link or app, where the order flows into StoreHub. That is a good native route when customers will use it. The page does not say StoreHub reads an existing WhatsApp thread and turns the choices inside it into an order.

For a retailer that can change customer behaviour, the link is enough. Put it in the WhatsApp greeting, product replies and staff scripts. The customer completes a structured checkout, and the team avoids retyping the order. A simple reminder or notification around that link may be enough for Zapier or Make if the connected services support the trigger you need; do not rebuild StoreHub’s order path.

A separate customer workflow becomes useful when WhatsApp itself is the sales desk. It can collect the product, variant, pickup or delivery choice and payment evidence, then ask a person to approve an unclear request before the order is recorded. The approval matters because “the blue one from last time” is a conversation, not a SKU.

The closest Biks proof is Rosalie: WhatsApp Order Automation, Replies Under 30 Seconds. Rosalie was handling about 1,000 WhatsApp chats a week by hand. After months in daily use, admin time is down 2 hours a day and the closing rate has doubled, while the team approves exceptions. Those are Rosalie’s results, not a forecast for every retailer.

Verdict: use StoreHub’s order link when customers accept a structured checkout. Add a bounded WhatsApp workflow only when the conversation must remain the storefront.

The customer record depends on the checkout moment

StoreHub already gives staff several good ways to identify a customer. Its help centre says a cashier can search by name or phone number, scan a membership barcode, enter a new record or let the customer scan a loyalty QR code. Once attached, the record can carry contact details, order history and store credit.

The timing is the catch. The customer must be added before checkout finishes and cannot be attached to that transaction afterward. A busy cashier who skips the step leaves an anonymous sale, even if the same shopper had just given a phone number in WhatsApp.

Start with StoreHub’s own QR flow. That solves the common case without another product. Train staff to ask before payment. Automation should help only when a repeated upstream source, such as a WhatsApp order, already has a customer identifier that staff copy into checkout.

Verdict: StoreHub stores the customer record well. The retailer still owns the moment of identification.

Can StoreHub replace a physical stock count?

No. StoreHub makes stocktaking easier, but somebody still has to see and count the goods. Its current help page tells staff to search or scan each item, enter the counted quantity and confirm it. The screen then shows expected quantity, counted quantity and the difference.

That is useful work already built into the product. Staff can count in more than one unit on eligible plans, pause and return later, or use a CSV for a large catalogue. When the count is complete, a person chooses whether uncounted items stay unchanged or fall to zero, then marks the stocktake complete so inventory updates.

The system exposes the variance. It does not know whether the cause was damage, a missed transfer, a wrong unit, theft, a late return or a counting mistake. StoreHub lets the team export items with variances for review. The investigation and final adjustment remain management decisions.

Use the native stocktake first. A scanner and a clear cycle-count schedule will beat a separate spreadsheet for most retailers. Add an alert or task tool only if the problem is chasing assigned counts across outlets. Add a larger workflow only when recurring evidence from deliveries, transfers and approved write-offs must be gathered before a manager decides.

Verdict: the software shortens the count and records the difference. People still establish physical truth.

Draw the line around one repeated handoff

StoreHub itself offers built-in integrations and custom workflow options, while warning that some connections carry an add-on or third-party subscription. Ask StoreHub first when the missing step sits inside its documented channels. The native feature will usually be simpler to support than a parallel system.

Use Zapier or Make for a low-risk side task when a supported trigger and action cover the whole job, such as notifying an owner that a review is due. Do not use them to guess a product from free-form chat or approve an inventory adjustment. Those jobs need evidence and an explicit stop for a person.

Before buying anything, follow one week of work and ask three questions. Which customer request starts outside StoreHub? Which StoreHub record should exist when the job is finished? Which exception needs a named person to approve it? Count completed orders and minutes of retyping, not messages sent.

A new admin can copy WhatsApp orders and chase stocktake sheets. That helps the queue today, but the same handoffs return tomorrow. The better first move is to keep StoreHub, pick one repeated edge and make the handoff clean.

A useful result leaves StoreHub doing its core job and stops your team acting as the copy-paste layer around it.