Category: Uncategorized

  • How to Track Profit in WooCommerce: Which Approach Fits Your Store

    <!– target keyword: woocommerce profit tracking –>

    <!– meta description: Compare ways to track profit in WooCommerce — built-in reports, a spreadsheet, accounting software or a cost ledger — and pick what fits. –>

    —

    slug: how-to-track-profit-in-woocommerce

    type: post

    title: “How to Track Profit in WooCommerce: Which Approach Fits Your Store”

    seo_title: “How to Track Profit in WooCommerce: Choosing an Approach”

    meta_description: Compare ways to track profit in WooCommerce — built-in reports, a spreadsheet, accounting software or a cost ledger — and pick what fits.

    focus_keyword: woocommerce profit tracking

    —

    How to Track Profit in WooCommerce: Which Approach Fits Your Store

    There is no single best way to track profit in WooCommerce. There are four common approaches, and each is the right answer for a different kind of store. Choosing badly is usually not a matter of picking a bad tool — it is picking a tool built to answer a different question.

    This page compares the approaches by category, says honestly who each one suits, and gives you a checklist for deciding.

    First, decide which question you are answering

    Most confusion starts here. Two questions sound similar and need different tools:

    • “Did this order or product actually make money?” This is a margin question. It needs product cost, payment fees, the shipping you paid and a share of overhead, joined to individual orders.
    • “What do I owe, and where is my cash?” This is an accounting question. It needs double-entry bookkeeping, VAT or sales-tax handling, reconciliation and a tax return.

    If you only need the second, an accounting system is the correct choice and the rest of this page is background. If you need the first, read on.

    Approach 1: The built-in WooCommerce reports

    What it is good at: revenue, order counts, tax collected and best-seller lists. It is already there, it is free, and for many stores it is the fastest way to see what is selling.

    Where it stops: WooCommerce can store a product cost. There is an opt-in Cost of Goods Sold feature under WooCommerce > Settings > Advanced > Features; it records the cost in order item meta, and the order editor can show a Cost column and a cost total for the order. What it does not give you is a profit report: its Analytics reports remain revenue reports, with no COGS line and no profit total. It also does not hold your supplier invoices or your operating expenses, so the product with the highest sales can still be the one losing you money.

    Honest verdict: this may be all you need if you sell one or two products with a flat, known cost and you only track turnover. It can now hold a per-product cost, but with no profit report in Analytics it is still not a margin tool: once you want profit rather than sales across a catalogue, it runs out.

    Approach 2: A spreadsheet you maintain yourself

    What it is good at: total control and no lock-in. You export orders, join them to a cost list, apply your own formulas, and the numbers are exactly as good as your inputs. It is free beyond your time.

    Where it stops: the joining is manual, so it happens only as often as someone does it. A single missing cost silently becomes full profit, because the empty cell is treated as zero, so revenue minus nothing looks like full profit. A supplier invoice in another currency needs a rate you have to record on the right date. As the catalogue and the team grow, the spreadsheet gets fragile — one wrong cell reference and a whole month is quietly wrong.

    Honest verdict: it works for a small catalogue reconciled monthly by someone who enjoys it. It is a poor fit for a store where costs change often or more than one person touches the numbers.

    Approach 3: Full accounting or bookkeeping software

    What it is good at: the accounting question. Tax, VAT or sales-tax returns, bank reconciliation, cash-flow statements and something your accountant can work with. If compliance is the goal, this is not optional and no plugin replaces it.

    Where it stops for margin: accounting software is organised around money in and out of accounts, not around per-order product profit. Seeing “this product, over this period, after its real costs” often means building a report your system was not designed to produce. It also carries a setup cost in both money and time.

    Honest verdict: the right foundation for the books, and usually the wrong place to look for a quick per-product margin.

    Approach 4: A cost-and-profit ledger inside WooCommerce

    What it is: a plugin that stores your product costs, supplier invoices and operating expenses inside your store, joins them to your existing WooCommerce orders, and reports profit per order, per product and per period. It is not accounting — it is the margin layer between your orders and your books.

    What to look for in one, whichever you choose:

    • Does it distinguish an estimate from a fact? Some gateways store the fee on the order; many do not. When one has, use the captured figure; when it has not, label the number an estimate. A trustworthy tool makes that distinction rather than presenting a configured percentage as audited reality.
    • What does it do with a missing cost? The only safe behaviour is to flag the row incomplete and exclude it from the totals. A tool that counts a missing cost as zero turns a gap in your records into imaginary profit.
    • Does it freeze history? If editing an old supplier invoice silently rewrites last quarter’s profit, your comparisons are worthless. Costs should be locked to the order when it is placed.
    • Where does the data live? On your own site, and it should stay there if you deactivate the plugin.
    • Can you get the numbers out? A report you cannot export is a report you cannot hand to anyone.

    Honest verdict: the best fit when your question is margin, your costs are real records you are willing to enter, and you want the answer next to the orders that produced it. It is not a replacement for accounting software.

    A five-question decision checklist

    Work through these before you choose:

    1. Margin or compliance? Compliance needs accounting software. Margin needs a cost-and-profit tool.
    2. How many products, and how often do costs change? A handful of stable costs is spreadsheet territory. Dozens of changing costs need something automatic.
    3. Do you buy in a foreign currency? If so, the tool must record the exchange rate on the invoice date, not guess one later.
    4. Who will maintain the cost data, and how often? The best tool is the one the person responsible will actually keep up to date.
    5. Do you need per-order and per-product detail, or just a monthly total? Detail is what lets you reprice a product or stop promoting a loss-maker.

    Where Store Profit Ledger fits — and where it does not

    Store Profit Ledger is a free WooCommerce plugin built for the margin question. You keep a supplier directory and record supplier invoices with line items, shipping, deposits and the exchange rate captured at entry; you attach manual costs to products and variations and can use a target-margin calculator; you record operating expenses by date, category and currency. It then reports profit per order, per product and per period, labels every fee as estimated unless the gateway recorded a verified one, and flags any order or product whose cost is missing as incomplete and excludes it rather than counting it as profit. It is free and complete, with no key and no paid tier.

    It is deliberately scoped. It does not issue invoices to customers, extract data from PDFs, file tax returns or track inventory, and it is not a replacement for your accounting software. If your only question is what you owe, choose accounting software and come back to margin later.

    The short version

    • Need to know what you kept, per order and per product? Use a cost-and-profit ledger.
    • Only track turnover with one or two known costs? The built-in reports may be enough.
    • Love your spreadsheet and reconcile it monthly? It can work, if you watch the blank cells.
    • Need tax, compliance and cash flow? That is accounting software’s job, and it is a different purchase.

    Pick the tool for the question you are actually asking, and the rest gets simpler.

  • WooCommerce Wishlist Bot Traffic: Why Bots Add to Wishlists

    <!– target keyword: woocommerce wishlist bot traffic –>

    <!– meta description: Crawlers follow ?add_to_wishlist= links and can create wishlist rows for visitors who don’t exist. Here’s how to confirm it and stop it. –>

    WooCommerce Wishlist Bot Traffic: Why Bots Add to Wishlists

    You check your wishlist plugin’s table and the numbers do not match your customers. There are rows for people who never bought anything, never created an account and, as far as you can tell, never visited the site. Your server log tells a similar story: the same ?add_to_wishlist=123 URL, over and over, from user agents that are not browsers.

    This is not a bug in your wishlist plugin. It is what happens when a feature built for a click is exposed as a URL that anything can request.

    Why a wishlist button is a link a crawler can follow

    Some wishlist plugins render the button as an ordinary link rather than a form submission:

    ?add_to_wishlist=123&_wpnonce=...

    A browser sends that request when a shopper clicks. So does a search engine, a social preview fetcher, an AI training crawler, a price-monitoring bot or a script someone wrote in an afternoon. None of them needs to understand the page. They only need to follow links, and your shop and category pages contain one on every product, on every page of pagination.

    That is the multiplier. A catalogue with 2,000 products and 100 paginated category pages is not one wishlist URL a crawler can find. It is thousands of them, and the same crawler may come back next week.

    On some wishlist plugins, following that URL is not a read-only event. The plugin treats the request as a shopper adding an item and writes a row. A crawler that never renders the page still creates the row, because the row is written by PHP on the server before any JavaScript runs.

    How to confirm it is bots, not shoppers

    Before changing anything, get evidence from your own site. Three checks are enough for most stores.

    1. Look at the user agents hitting the wishlist URL. In your access log, filter for add_to_wishlist and count the user agents. Browsers send long, varied strings. Crawlers often announce themselves (AhrefsBot, GPTBot, Bytespider, curl, python-requests), and spoofers send a browser string that is identical across thousands of requests from rotating addresses.

    2. Compare wishlist rows with customers and orders. If rows are being created for sessions with no account, no order and no other page views, they are not shoppers browsing. Look at the timestamps too: a burst of rows a few seconds apart, at 3 a.m., with no product page views in between, is a pattern no human produces.

    3. Run in monitor mode first. A request-level shield can record the block and challenge verdicts it would have applied without blocking anything. Give it 48 hours of real traffic, then read the log. If the same crawler names keep appearing on wishlist URLs, you have your answer from your own data rather than from an article.

    One caution: not every unexplained row is a bot. A logged-out shopper can legitimately add an item, and some plugins create a row for a real visitor whose cookie later expires. The question is not “are there rows without accounts” but “are these requests coming from software that is not a browser”.

    Why robots.txt and a firewall rule are only half a fix

    The obvious first move is a Disallow rule in robots.txt. It is free and it is worth doing, but it is a request, not an enforcement. A crawler that ignores it — and a user-agent spoofer always ignores it — still gets through. It also does nothing about requests that are already queued or already indexed.

    The second obvious move is a firewall or CDN rule that blocks the wishlist query string. That can work well at the edge, and if you already run a WAF it may be the cheapest option. Two costs come with it. Address-based rules are blunt: shared addresses, mobile networks and privacy VPNs mean you can block real shoppers along with the bot. And a rule written against one query argument misses the moment a plugin changes its parameter name or a crawler starts using a slightly different URL.

    Neither approach looks at the request the way your wishlist plugin does. That is the gap a request-level shield fills.

    What actually stops it

    The reliable approach is to decide, before your wishlist plugin runs, whether a request looks like a shopper. Four layers, cheapest first:

    • Nonce check. A request with a missing or malformed nonce is rejected before the wishlist plugin sees it. That removes naive requests which omit the token, but not anything that copies a full URL, nonce included.
    • Known-crawler block. Match the user agent against a list of crawler, scraper and automation signatures. This is a blocklist, so it is a first filter, not a guarantee.
    • A JavaScript and signed-cookie challenge. A real browser can run a tiny script and return with a signed cookie. A spoofed user agent that cannot execute JavaScript cannot pass, and neither can a crawler that does not run scripts. This is the layer that catches bots that lie about who they are but cannot run a browser.
    • Rate limiting. Cap requests per visitor fingerprint and site-wide. When the cap is hit, return HTTP 429 with Retry-After rather than doing the work.

    Order matters. If the challenge runs after the wishlist plugin has already written a row, you have paid the database cost and only cleaned up afterwards. The check has to sit in front of the wishlist handler.

    Do not forget the search leak

    Bot traffic and search indexing are the same URL problem. If ?add_to_wishlist= URLs are crawlable, they can be indexed, and every indexed variant is another invitation. Three rules help, but they do different jobs:

    • Disallow: /*add_to_wishlist=* (and the hyphenated variant) in robots.txt reduces crawling. It does not remove a URL that is already indexed, and it can stop a crawler from seeing the noindex response, so it is not a de-indexing tool on its own.
    • X-Robots-Tag: noindex, nofollow on responses carrying the argument is the signal that keeps the URL out of the index and removes an entry that is already there, provided the crawler is still allowed to fetch it.
    • A noindex robots meta tag and a canonical link with every wishlist argument stripped consolidate variants that are still crawled: the meta removes the action URL from the index, and the canonical points at the clean product URL.

    If you need to de-index an already-indexed URL, apply the noindex first and add the Disallow afterwards, once the URL has dropped out. A request that carries no wishlist argument should be untouched: no header, no meta change, no canonical rewrite. That is the line between cleaning up an action URL and accidentally noindexing your shop.

    What this does not fix

    Be honest with yourself about the edges before you buy or install anything.

    A crawler that runs a full headless browser can execute the challenge script and pass. A signed-cookie test raises the bar; it does not make the site invisible. A full-page cache or CDN that serves the wishlist URL without invoking PHP is safe from a database-write point of view — no PHP, no wishlist row — but the request will not appear in any log the plugin keeps. And a wishlist plugin that processes its action extremely early, before other plugins load, can still win the race on some configurations.

    These are reasons to test in monitor mode, not reasons to do nothing.

    A sane rollout order

    1. Install the shield and leave it in monitor mode. Nothing is blocked; every block and challenge verdict is recorded, while allowed requests are not.
    2. After 48 hours, read the log. Filter by reason. Confirm the blocked requests are bots, and check your server logs or analytics to confirm your real shoppers were allowed.
    3. Switch to enforce. Watch the log for the first day, particularly for any real customer who hits the challenge twice.
    4. Add the SEO rules if they are not already on, then fetch a wishlist URL and a normal product URL and compare the headers and canonical tag.
    5. Set log retention to the shortest period you actually review. Seven days is a reasonable default; there is no reason to keep hashed visitor data longer.

    If the log shows nothing after a week of real traffic, you may not have this problem. That is a useful result: leave the shield in monitor mode or remove it, and spend the effort elsewhere.

    The bottom line

    Wishlist bot traffic is not mysterious once you look at the request. A public URL that writes a database row will be requested by software that is not a shopper, and a wishlist button rendered as a plain link is exactly that URL. You can confirm it from your own logs, decide in monitor mode, and enforce before the wishlist plugin runs.

    If you want the four layers above in one plugin, without changing your wishlist plugin or its templates, Wishlist Bot Shield is free to download and use. It includes the missing/malformed nonce guard, the crawler block, the signed-cookie challenge, rate limiting, the blocked-request log, monitor mode and the robots/noindex/canonical cleanup. It works with wishlist plugins that use a query-argument action URL; check yours before installing. No account, no key, no time limit.

    Download it, run monitor mode for two days, and read your own log before you enforce.

  • How to Let Guest Customers Start Returns in WooCommerce

    <!– target keyword: woocommerce guest returns –>

    <!– meta description: Guest checkout leaves no My Account returns area. Here is how to let guest customers start a WooCommerce return without creating accounts. –>

    —

    slug: woocommerce-guest-returns

    type: post

    title: How to Let Guest Customers Start Returns in WooCommerce

    seo_title: WooCommerce Guest Returns Without an Account – TillFoundry

    meta_description: Guest checkout leaves no My Account returns area. Here is how to let guest customers start a WooCommerce return without creating accounts.

    focus_keyword: woocommerce guest returns

    —

    How to let guest customers start returns in WooCommerce

    Most guides to WooCommerce returns assume the customer has an account. They log in, open My Account, find the order, and ask to send part of it back. That works right up to the point where the order came from a guest.

    If you allow guest checkout — and plenty of stores do, because forcing account creation costs conversions — then a whole group of customers has no My Account and no order history. When one of them wants to return something, they do the only thing left: they reply to the order confirmation email. You answer, ask which item, wait, answer again. The return works, but it lives in your inbox instead of your records.

    This guide is about that awkward case specifically: how to let a guest start a return in WooCommerce without making them create an account, and without opening a hole that lets strangers browse your orders.

    Why guest returns are harder than they look

    A logged-in return is easy to trust. WordPress knows who the user is, WooCommerce knows which orders belong to them, and the plugin only has to check that the order and the current user match.

    A guest return has none of that. Nothing on the page proves the visitor is the person who bought the item. So anything you build has to answer one question first: how do you know this visitor is allowed to see this order?

    That question is why many stores simply don’t offer guest returns, and why guest orders keep arriving as email.

    What not to do: an order number in a link

    The obvious shortcut is a URL like /returns/?order=8123. It is also the one to avoid.

    WooCommerce order numbers are usually sequential. If a return page accepts an order number on its own, anyone can change the number in the address bar and step through your order history one order at a time. They may not be able to refund anything, but they can learn order statuses, names, addresses and what your customers bought. That is a data leak dressed up as a convenience.

    A second shortcut is worse: sending a link with the order ID baked in and nothing else. That link is not signed and does not expire, so it can be forwarded, guessed or found in an old email months later.

    If a guest is going to identify themselves, they need to prove something they know, and the result of that proof has to be short-lived.

    The two things a guest already has

    A guest who checked out has exactly two useful facts in front of them: the order number from the confirmation email, and the billing email address they used on the order.

    Neither is a secret, but together they are a reasonable signal when the check is done carefully. The important word is carefully. Three rules make an order-plus-email lookup safe enough to ship:

    1. Both must match the same order. The order number alone, or the email alone, must never reveal anything.
    2. Failures must be indistinguishable. “No order with that number” and “that email doesn’t match” tell an attacker which half they got right. One generic message for every failure gives them nothing.
    3. Attempts must be rate-limited. Without a limit, a script can try thousands of order-number and email combinations.

    Do those three things and the lookup becomes a fair trade: a real guest gets in, and an attacker gets a wall of identical failures.

    Adding guest returns without an account requirement

    One way to do this is a shortcode rather than an account requirement. With Returns Desk, create a page — “Returns”, “Start a return”, whatever fits your store — and add the [returns_desk_guest] shortcode to it.

    The page then shows a short form: order number and billing email. When the two match a WooCommerce order, the plugin returns a signed link bound to that order and email, valid for seven days. The guest follows it and lands in the same per-item return form an account holder would use.

    The lookup is rate-limited, and both failure cases return the same message, so the form can’t be used to discover orders. There is no account to create and no login to remember.

    If you would rather build it yourself, everything described here is implementable in a small plugin: collect the two fields, compare them against the order, sign a token that encodes the order and email, expire it, and rate-limit the lookup. What you should not do is skip the signature and the expiry.

    Either way, the alternative is leaving guest returns in the inbox: fine at two a month, painful at twenty. Guest return initiation is part of the free Returns Desk plugin, so that is the download that carries the shortcode — the free self-service returns portal for WooCommerce. That is the one link in this article; the rest of it works the same whether you use Returns Desk or build the flow yourself.

    What the guest sees after the lookup

    Once the signed link is open, a guest return should feel exactly like a normal one. In Returns Desk it does:

    • The order’s items are listed with a quantity selector capped at what hasn’t been returned yet.
    • The guest ticks the items, picks a reason for each, and submits.
    • The plugin issues an RMA number and records the request.
    • The request moves through Requested, Approved, Rejected, Received and Cancelled, and the guest can check the status instead of emailing you.
    • Both the guest and the store get an email on the request and on every status change.

    That last point is the real return on the work. The reason a returns inbox is exhausting is not the first email; it is the second and third asking for an update. A status the customer can check replaces those.

    Where the money still happens

    It is worth being precise, because the phrase “returns plugin” hides a boundary. A guest return request collects the intake: which items, how many, why, and an RMA to track it by. It does not have to move money, and there is a good argument that it shouldn’t.

    In Returns Desk the free plugin records the request; the refund is issued from WooCommerce’s own order screen, where it belongs and where your gateway already handles it. Resolving a return — recording the decision and closing it out — plus partial refunds, exchanges and store credit are capabilities of the separate Returns Desk Pro add-on. If all you need is the intake and the trail, the free plugin is enough.

    Test it with a guest order before you publish the page

    A guest lookup form is security-sensitive, so do not ship it on faith. A ten-minute check:

    1. Place a test order as a guest, or use an existing guest order in a test store.
    2. Add the shortcode to a page and view it while logged out.
    3. Enter the correct order number and the correct billing email — confirm you get a return form.
    4. Enter the correct order number with a wrong email — confirm the message is identical to a wrong order number.
    5. Submit the form a handful of times quickly and confirm you get rate-limited rather than unlimited attempts.
    6. Open the link a day later and confirm it still works inside its seven-day window.

    If any of those steps behaves differently, fix it before the page goes live.

    When you don’t need this

    Be honest about your store. If every order comes from a registered customer, a guest lookup adds a page you don’t need. If guest checkout is switched on, though, you already have guest returns — the only question is whether they arrive as a form or as an email.

    The short version: match the order number against the billing email, sign the result, expire it, limit the attempts, and never let an order number alone open anything. Do that and guest returns stop being the awkward case.

  • WooCommerce disabled your webhook: how to find the failed deliveries and re-send them

    <!– target keyword: woocommerce webhook disabled –>

    <!– meta description: WooCommerce disables a webhook after repeated failures and hides the payload in its own log. How to find what failed and re-send it. –>

    WooCommerce disabled your webhook: how to find the failed deliveries and re-send them

    It usually surfaces as a question from someone else. A customer asks why their order has not appeared in the warehouse system. The bookkeeper asks why yesterday’s invoices never landed. Your ERP is missing orders, but nothing in WordPress told you anything was wrong.

    The cause is often a webhook that WooCommerce turned off days ago and never announced.

    What “disabled” actually means in WooCommerce

    WooCommerce’s native webhooks are fire-and-forget. For each event a webhook is subscribed to — an order created, a product updated, a customer changed — WooCommerce queues a single delivery and sends it to your endpoint. If the endpoint answers with a success, the delivery is done. If it answers with anything else, WooCommerce records the failure and counts it against the webhook.

    After a handful of consecutive failures, WooCommerce sets the webhook’s status to Disabled. It stays that way. Nothing is queued, nothing is retried, and no order data reaches your endpoint until a human notices and switches it back on. In current WooCommerce the threshold is five consecutive failures, and it can be filtered — but the default behaviour is silent, and that silence is the real problem.

    Why you find out days later

    Two things work against you.

    The first is that the failure count lives on the webhook, in WooCommerce → Settings → Advanced → Webhooks, and nobody watches that screen. The second is worse: WooCommerce’s own delivery log records that an attempt failed and what HTTP status came back, but it replaces the request and response bodies with a placeholder. To see the payload that was actually sent you have to turn on WP_DEBUG — which is not something you want to do on a live store, and which writes to a debug log rather than a screen you can filter.

    So the sequence is always the same: the endpoint has a bad hour, the webhook crosses the failure threshold, WooCommerce disables it quietly, and the feed stops. You find out when a human downstream asks a question.

    Step 1: Confirm the webhook was disabled

    Open WooCommerce → Settings → Advanced → Webhooks. Each row shows a status. A webhook that has been switched off reads Disabled. Find the one your integration uses and check the Delivery URL while you are there, so you are looking at the right row.

    Do not simply flip it back to Active yet. If the endpoint is still broken it will fail five more times and be disabled again, and you will have learned nothing.

    Step 2: Find out what actually failed

    You need the status code and the response the endpoint gave you. WooCommerce shows a status per attempt in its delivery log, but not the bodies. A delivery-log tool can record the status, the response body and the exact request that was sent, which is what you need to tell an endpoint outage apart from a payload problem.

    Check whether the endpoint was unreachable — connection refused, DNS failure, timeout — or whether it received the request and rejected it with a 4xx or 5xx and a body. The distinction decides what you fix: the network path, the receiving application, or the payload itself.

    Step 3: Re-send the deliveries that were missed

    Reactivate the webhook, then re-send what failed. Three things are easy to get wrong.

    • Re-activate first. New events need the webhook live. Re-sends are a separate operation.
    • Re-send the captured bytes, not a fresh event. If you re-trigger the original action by editing the order, you re-serialise the payload from the order’s current state, which has probably changed. The point is to send the body that was captured at the time.
    • Mind duplicates. Re-sending an order the receiving system already has can create a duplicate record. WooCommerce stamps each delivery with an X-WC-Webhook-Delivery-ID header; if you reuse the original ID on the re-send, an endpoint that de-duplicates on that header will discard it. If your endpoint does not, expect a duplicate and reconcile it.

    If a webhook’s secret was rotated between the failed attempt and now, the signature on the re-sent payload has to be recomputed with the current secret or the endpoint will reject it. A re-send tool should do that for you.

    Step 4: Stop it happening again

    Re-sending fixes the hole. It does not stop the next one, and the next one comes from the same design: one attempt, a hard failure count, and silent disabling.

    Three changes alter the outcome:

    • Automatic retry with backoff. A failed delivery is rescheduled and re-sent a short time later, then with a longer gap, up to a ceiling you set. A blip of a few seconds is absorbed without you doing anything.
    • Keeping the webhook active while retries are owed. This is the one that addresses the silent disable directly. While a retry is pending, the failure ceiling is raised, so an endpoint that is down for an hour no longer costs you the webhook; it keeps retrying and resumes normal delivery when the endpoint recovers.
    • An alert when it does fail. Retries you cannot see are not much better than no retries. An email to a real address, throttled so a flapping endpoint does not flood the inbox, turns a silent failure into a known one.

    Be honest about the trade-off

    Keeping a webhook active while it is failing is a deliberate choice with a cost: a permanently dead endpoint keeps accumulating failed deliveries instead of being switched off. If you take that route, alerts and a failure history are not optional extras — they are what stops the protection from hiding a bigger problem. If you would rather WooCommerce disable a dead webhook and make someone notice, leave the default behaviour alone.

    What kind of tool fits

    If your integration is a one-off and the endpoint rarely fails, the built-in WooCommerce webhooks screen and its status column may genuinely be enough. Fix the endpoint, flip the webhook back on, move on.

    If you already run a webhook platform or a general integration service, check the receiving side before adding anything — retries and a delivery log may already exist there.

    The remaining gap is a store that pushes order data to an ERP, a 3PL or an accounting tool and needs to see and re-send what failed without standing up another service. That is the category WebhookGuard fills: it observes the native webhooks you already run, stores the request and response bytes core discards, and adds retry and replay on top. It is free and needs no external service.

    FAQ

    Does reactivating a webhook re-send what was missed?

    No. Reactivation only allows new events to be delivered. Failed deliveries have to be re-sent separately.

    Will re-sending create duplicate orders in my ERP?

    It can, unless the endpoint de-duplicates on the X-WC-Webhook-Delivery-ID header. That header exists for exactly this, but whether your endpoint uses it is up to the endpoint.

    Can I see the payload without turning on WP_DEBUG?

    Not with WooCommerce’s own delivery log — it redacts the bodies unless WP_DEBUG is on. A delivery-log plugin stores the payload in its own table instead.

    How long should I keep failed deliveries?

    Long enough to cover your worst outage plus the time it takes someone to notice. Thirty days is a common default; use a shorter window if you watch alerts, a longer one if you do not.

    Why not just increase WooCommerce’s failure threshold?

    Raising it only delays the disable; it adds no retry. Without a retry behind the higher ceiling you simply get more failures before the same silent stop, which is why the ceiling and the retry belong together.