What should you prepare before switching alerts on?

Start with a short list of products you want someone to review before they run out. Choose items with clear stock records and a known supplier. Leave the full catalogue until you have tested the process.

In this guide, a low stock threshold means the quantity you choose as a warning level. A reorder point is the point at which you review replenishment. Treat these as practical purchasing decisions, rather than numbers copied from another shop.

Build a working stock list

• Product name and SKU, your internal product identification code.
• The specific size, colour or other variant being tracked.
• The shop or warehouse holding the stock.
• Counted stock and the quantity shown in your system.
• Recent sales records and supplier delivery expectations.
• The person who will review the warning.

For a hypothetical accessories shop, start with one phone case in one colour. Count that exact item and compare it with the record. Decide who will record deliveries, returns and sales before configuring the notification.

If customers also browse a WhatsApp Business catalogue, include that sales route in your written process. Decide where staff should check availability before confirming an order. Do not assume that creating an alert connects every selling channel.

What is a good low stock threshold?

Choose a starting threshold around expected demand while you wait for replenishment, plus an extra buffer you are comfortable holding. Use your own records. Review the decision when delivery arrangements or selling plans change.

Lead time means the wait between placing an order and having stock ready to sell. Ask your supplier what that wait includes. For the initial calculation, also allow for the time your team needs to notice the alert and approve a purchase.

Use the questions in this wholesale supplier guide to clarify delivery and minimum order terms. Keep the warning level separate from the quantity you decide to purchase. Before approving a larger order, check it against your cash flow plan.

How do you configure Shopify, WooCommerce or Square?

Use the system already holding your stock records as the starting point. Follow the relevant setup below, then test one product. Avoid purchasing another app until you can name the requirement your current setup cannot meet.

WooCommerce: enable stock emails

The WooCommerce product settings guide documents this setup:

1. Open WooCommerce → Settings → Products → Inventory.
2. Enable stock management.
3. Tick Enable low stock notifications.
4. Enable out of stock notifications if you want that separate warning.
5. Enter Notification recipient(s), separating multiple email addresses with commas.
6. Set the Low Stock Threshold and Out Of Stock Threshold.

The same documentation states that quantity counts are not maintained when stock management is disabled. Low stock email is triggered when stock reaches the configured amount. Check both the tracking setting and the notification setting before testing.

Shopify: choose Flow or an inventory alert app

Shopify's inventory management guide identifies Shopify Flow and inventory alert apps as routes to low stock notifications. Flow is Shopify's tool for automating store tasks and processes. The cited page does not provide a complete button-by-button Flow recipe.

Write a clear requirement before building or choosing a workflow: monitor this product or variant, check this threshold and notify this person. Confirm how your chosen workflow handles locations and repeat warnings. Test those behaviours instead of assuming every app works the same way.

Square: set the alert in Dashboard

For items at one location, open Square Dashboard → Items, select the items, then choose Actions → Update low stock alert. Enter the alert amount and select Update. These steps appear in Square's inventory alert instructions.

Square generates a warning below the threshold. Its emails are sent 90 minutes after each location's configured closing time, with separate emails for multiple locations. Check your business hours before interpreting a missing message as a failure. See Square's delivery timing.

What should happen when someone receives an alert?

Assign one person to review the product and record a purchasing decision. Name a backup for days off. My recommended rule is simple: check the count, check outstanding orders, then decide whether another order is needed.

Where message editing is available, include the details below. Otherwise, keep the missing information in an accessible purchasing sheet. Treat this as a message design requirement, not a promise that every platform provides these fields.

Ask the owner to record one clear outcome: order placed, existing delivery awaited, count corrected or purchase deferred. Include the reason when a purchase is deferred. Keep that note beside the stock record so the next person can understand the decision.

Before anyone promotes an alternative product, agree which substitutes are suitable. Your upselling and cross-selling process should follow that decision. Keep customer recommendations separate from the internal purchasing alert.

How do you test an alert without disrupting orders?

Use a test product and record its starting quantity. Avoid changing stock attached to live customer orders. At the end, restore the correct records and remove any temporary purchasing instructions.

1. Start above the threshold. Record whether an unexpected warning appears.
2. Move to the threshold. Note whether that exact quantity triggers the rule.
3. Move below it. Check the next change separately.
4. Test the out of stock setting. Confirm the separate warning if you enabled it.
5. Restore and reduce stock again. Observe whether a fresh low stock event is recognised.
6. Ask the recipient to act. They should identify the item, location and next decision without guessing.

Pay attention to the boundary: WooCommerce describes notification at the threshold, while Square describes stock falling below it. Check WooCommerce's threshold definition against Square's alert rule when writing your test expectations.

Keep a short test record

Write down the starting count, ending count, change time, expected result and actual result. Record when the email arrives and who receives it. If another stock change produces another message, note that too.

For a missing email, inspect the enabled rule, tracked quantity, recipient address and expected delivery time. Then check the spam folder. For repeated messages, investigate what triggered each one before changing the threshold.

If you require one warning followed by reminders, make that a separate acceptance requirement. Confirm whether the chosen tool supports it. Do not approve the setup solely because the first email arrived.

What should you do during the first week?

Run a small pilot with a clear finish line: the right person receives a useful warning and records what happened next. Use the following sequence rather than enabling every product at once.

• Count the selected products and resolve discrepancies.
• Confirm delivery expectations and choose initial thresholds.
• Configure recipients and stock notification settings.
• Run the test cases and correct unclear messages.
• Review unanswered alerts and purchasing decisions with the owner.

During review, ask whether warnings were relevant, noticed and acted on. Treat an unread alert as an unfinished process. Decide whether to change the recipient, timing or working instructions before expanding coverage.

If you are considering an extra app, include setup time and ongoing checking in your small business cost review. Write down the missing capability it must provide. Buy against that requirement, then repeat the same acceptance test.