Inventory & recalls
Know what you hold, what you will need, and what has to stop.
Stock control usually tells you what is on the shelf and leaves the rest to you. This reads what you have actually sold to say what to reorder, and — on the day it matters — pulls a product off every channel at once and tells you exactly who bought it.
Inventory, purchase orders and suppliers are on Growth and above · the recall workflow is on Scale
- Of your own sales read
- 90 days
- Reorder horizon suggested
- 30 days
- Recall freeze across channels
- Instant
- Recall export for regulators
- Notice
Velocity and sell-through, per SKU
With an urgency and a suggested quantity
Storefront and register in the same moment
A text file listing every affected case
Two jobs, one catalogue
Keep the right stock. Stop the wrong stock.
One of these runs every week and quietly protects margin. The other runs once in a while and protects everything else.
Reordering
Rather than reporting the shelf back to you, BestWebby reads your last 90 days of sales and proposes what to reorder for the next 30 — grounded in your own history, with seasonality and a safety-stock buffer taken into account.
- Sales velocity per SKU
- 30-day reorder suggestions
- One-click draft purchase orders
- Supplier ETA tracking
- Goods-received updates stock on arrival
Recalls
A recall is time-critical and unforgiving, and it usually arrives while you are busy with something else. The workflow takes it from freezing the SKU everywhere, through emailing the buyers who have one, to exporting the notice you submit.
- Instant inventory freeze
- Customer cross-reference
- Team alerts on recall open
- Buyer emails with an acknowledgement link
- Per-case return tracking
- Notice export with every case listed
A recall, start to finish
Five stages, in the order the day demands them.
From the moment you open the recall to the moment the paperwork is ready, each stage runs against the same catalogue and order history the rest of the platform uses.
- 01
Freeze
Open a recall and every affected SKU is set to recalled — gone from the storefront and the register at the same moment.
- 02
Cross-reference
Order items are queried for the affected SKUs, and a case is opened for each customer who bought one.
- 03
Notify
Your team gets email and in-app alerts; every affected buyer gets their own email carrying the product, the reason and the batch, plus a private link to acknowledge it on your storefront.
- 04
Track
Each case moves through notified, acknowledged, returned and closed. Acknowledgements from the storefront land here; mark returns one at a time or in bulk.
- 05
Export
Download the recall notice as a text file — reference, severity, reason, SKUs and batch, units affected against units returned, and every case with its dates.
Buyers are emailed one case at a time, each with a link that opens only their own case on your storefront — and a self-service lookup there for anyone who mislays it, which asks for the order number and the email the order was placed under. The recall workflow is on the Scale plan.
In detail
What the stock side actually does.
All of it reads and writes the same inventory the storefront and the register are working against, so there is no second count to keep in step.
Reorder suggestions
Your last 90 days of sales per SKU become a suggestion of what to restock over the next 30, each with an urgency and a quantity. Approve one and it drafts a purchase order for supplier review.
Inventory is on the Growth plan and above.
Purchase orders and suppliers
Turn a suggestion into a draft order, assign the supplier, and follow it through to goods-received — which updates stock on arrival. Supplier contacts stay on the order for chasing.
Purchasing and suppliers are on the Growth plan and above.
Revenue anomaly alerts
Your daily revenue, order count and refund rate are each scored against your own last 30 days with a z-score model, so a day well outside the norm is flagged instead of becoming a month-end surprise.
Included from the Growth plan.
Recall freeze
Creating a recall sets every affected SKU to recalled immediately. They stop selling on the storefront and the register at once, with no manual pass across channels.
The recall workflow is on the Scale plan.
Customer cross-reference
On creation, every order item is checked against the recalled SKUs and a case is generated per affected customer, ready for notification.
Team and buyer notifications
Your team gets email and in-app alerts when a recall opens. Notify the affected buyers and each one is emailed their own notice — the product, the reason, the batch and a private link to acknowledge it on your own storefront.
Acknowledgements come back into the case list; recall emails are sent per case, never as a bulk blast.
Per-case tracking
Follow every customer through the lifecycle — notified, acknowledged, returned, closed — and mark returns individually or in bulk as they come back.
Regulatory export
Download the notice as a text file: your company and the reference, severity, reason, affected SKUs and batch, units affected against units returned and the return rate, then every case with its notification and return dates.
A plain-text notice to attach to your own submission — not a regulator-specific form.
Stop reacting to stockouts.
Reorder from what you have really sold, keep purchase orders and goods-received in the same system as the shelf, and have the recall workflow ready before you need it.