Recover a WooCommerce variation's stock after a partial refund

Separate the refund from the stock movement

Open WooCommerce > Orders, then the affected order. Record its status, existing refunds, refunded amount and refunded quantity beside the product line. A €5 allowance may be a goodwill gesture with no returned item. A one-unit refund describes a line and quantity. The presence of an amount therefore does not establish that WooCommerce should have increased stock. Also record whether the item actually returned and can be resold.

In the order notes, find the initial stock reduction and any increase at refund time. Record the variation's SKU, name and attribute combination. The note contains an identifier and quantities. To interpret those numbers, you must know which product owns the counter. A blue variation can be sold under its own SKU while consuming the variable product's shared stock.

A partial refund can leave the order processing or completed. That status is not evidence about stock. Compare refunded amount, returned quantity and inventory counter. These three elements evolve separately. Keep before-and-after values in the same record. If a plugin handles returns or stock software synchronizes the store, also record the last movement's time and the tool that wrote it.

Identify the variation's stock counter

Under Products > All Products, open the variable product named on the order. Under Product data > Variations, expand the exact combination and find that variation's stock management. If it has its own stock, record its quantity and that of a neighboring variation. Also check the parent product's Inventory tab. When the parent manages shared stock and the variation has no individual management, the counter to check belongs to the parent.

If quantity management is enabled neither at the relevant level nor globally under WooCommerce > Settings > Products > Inventory, an ‘In stock’ display may be a selected status without a counter. Instead, find out how the team actually deducts sales. Do not change those settings to obtain a movement on an old order. If the management mode changed since the sale, reconcile the original movement with the current product before deciding where to return a unit.

Prepare a comparison order

On a local installation, create two fictional variable products, one with variation-level stock and the other with parent-managed stock. Prepare a control with ten units. Add two units to a staging order with a simple price and no active gateway. Change the order to processing, then reread the counter before opening the refund. The control must first show a two-unit reduction. If stock stays at ten, check the line and staging configuration before testing the return.

Create a new control order for each comparison. Keep the same line, initial quantity and starting status. Change only one parameter at a time. Compare an amount alone, then a one-unit quantity with the checkbox checked, then the same quantity with it unchecked. A manual refund is a record in the store. In staging without payment, it involves no money transfer.

Compare effects on the same staging line

Under WooCommerce > Orders, open the fictional order and click Refund below the items table. In the first test, enter only €5 in the amount field without changing the line quantity. In the other two tests, enter one unit on the blue line. Let WooCommerce fill in the corresponding line amount. Record the restock checkbox's position before choosing Refund manually. On the copy, record the new counter immediately and review refund details. The checkbox's exact label depends on the translation.

Example expected results with a blue variation at ten units and a red one at fifteen: ordering two blue units should reduce the blue counter to eight. Refunding one unit with restocking should raise it to nine without changing red. Without restocking, blue should remain at eight; with an amount alone and no refunded quantity, it should also remain at eight. Verify these states on separate staging orders and record any difference. These numbers illustrate the protocol; no executed result is provided here.

With shared stock, record the parent's counter before the order, after the two-unit reduction and after the one-unit return. Starting from ten, the expected values are eight, then nine. The order line identifies the variation while the counter belongs to the parent. Also compare a neighboring variation using that same stock: its availability may reflect the same quantity without having been refunded.

First reproduce these comparisons with the native engine, without payment or gateway calls. If a returns plugin replaces the button or an external warehouse controls quantities, then prepare a separate comparison with that component. Record the versions and settings actually used; the native procedure is a diagnostic reference, not proof of every integration's behavior.

Fictional example of expected values for one refunded and restocked unit.

Variation bleue   avant commande : 10 | après commande : 8 | après retour : 9
Variation rouge   avant commande : 15 | après commande : 15 | après retour : 15

Read order statuses without using them to repair stock

Order transitions and refunds are two distinct mechanisms. On fictional orders, compare a stock reduction in Processing or On hold status with an order left Pending payment. First record the original movement, then observe a partial refund with quantity and restocking. If no unit was deducted from the line, do not automatically expect an increase. A temporary cart reservation is yet another mechanism.

After a partial refund, an order can retain Processing or Completed status. Read amounts and quantities in all existing refunds before interpreting its status. An unchanged status does not justify another attempt. Manually changing status is not the same operation as recording a refund on a line.

Cancellation deserves a separate check on a fictional order. After deducting two units and refunding with the return of one unit, record cancellation's effect on the unit still deducted and on the refund list. On a real order where one unit remains sold, cancellation may make stock available that is no longer in the warehouse. Keep the status describing the actual transaction and correct inventory separately if necessary.

Check what another attempt would do

If the screen closes or takes time to respond, reopen the order in a new tab before submitting the refund again. Look for a negative line or a new refund record, then reread notes and the remaining balance. If a gateway was used, reconcile its refund ID with the order before any new operation. A manual refund and a gateway refund can show the same amount while representing different actions. Choose the mode only after establishing what was already recorded and what genuinely remains to do.

To understand the duplicate risk, use only a fictional €24 order for two units. A first €12 refund with one unit returned still leaves a refundable balance. A second identical request can therefore create a second refund and stock movement. Do not treat a first success as protection against resubmission. Record existing refunds before any further action; no additional request should be used to check a real order.

If the real order already has the correct amount and quantity, move to inventory reconciliation. Another financial line would not correct the first movement's destination. If no refund is recorded and a financial operation is genuinely expected, handle that decision with the person authorized to manage the order, then check the new record and stock movement once.

Correct an established discrepancy on the right counter

This approach suits an existing refund when the team can confirm an item returned, is resellable and is absent from current stock. It requires an account authorized to edit products, access to order notes and a verified inventory value. If external stock software is authoritative, make the movement there and observe its effect in WooCommerce. Otherwise, record the current value in WooCommerce for the variation or parent managing stock. A quantity correct at refund time may since have been replaced by an import or synchronization. That write's time indicates which tool needs correction.

Calculate the discrepancy from stock observed now. New sales, receipts and corrections may have occurred since the sale. Apply the discrepancy to the current record. For example, if the active counter is eight and only one returned unit is missing, the expected result is nine. If another person edits inventory concurrently, coordinate the operation and reread the counter immediately before saving. If physical counts are disputed, retain the record and reconcile it with the warehouse before making the item available.

For a variation with its own stock, open Products > All Products > the relevant product > Product data > Variations. Expand the exact combination and apply the discrepancy to its quantity. Save variations, then update the product if the interface asks. For a shared counter, edit the quantity under the parent's Product data > Inventory and update the product. Retain the existing stock-management rule, then reload the product records. Check that quantity changed on the selected counter and that no independent variation received the same correction.

In a private order note, record the SKU, modified counter, quantity added or removed, date and reason. Do not create a customer-visible note for this internal record. In staging without another simultaneous movement, a plus-one adjustment should take eight to nine without changing the refund list. Then check that the inverse operation restores the initial record. If the real adjustment proves wrong, apply only its inverse to the same counter after recording subsequent movements. Stock can thus be corrected without erasing refund evidence or canceling a still-valid sale.

Confirm the result in three places

Return to the order and check that refunded amounts and quantities still match the intended return. Open the counter's product record and reread the saved quantity, then check that combination's storefront availability from a fresh page without placing an order. If the parent counter is shared, check another combination using it. If stock belongs to the variation, instead check that the neighboring combination retained its quantity. Public availability may also depend on backorders, visibility and caching, which justifies this separate final check.

If notes and the counter still contradict each other, reproduce one order on the copy using the actual returns or stock plugin. Record quantity immediately after the refund, then after the next synchronization cycle. If the counter changes at the second reading, compare integration logs at the recorded time. If no movement appears at the first reading, recheck refunded quantity, the checkbox and original deduction before looking for a conflict. Keep both readings and the order number to reproduce the discrepancy without touching the real order a second time.

Read the stock counter managed by WooCommerce without repeating the refund

Checking the interface remains free in WooCommerce. To resolve ambiguity between parent and variation, a maintainer can also save this PHP probe outside the web root and run it with wp eval-file on the copy, passing the variation ID as its only argument. Keep WooCommerce loaded; the code changes neither stock nor orders.

Compare the counter ID with the parent and variation IDs. A null quantity with management inactive does not necessarily mean zero items: it may be availability without a counter. The probe reads current state without reconstructing movements since the order. Therefore reconcile the result with notes and physical stock before any correction. Remove the diagnostic file after testing; this read requires neither a financial return nor refund cancellation.

<?php
if (!function_exists('wc_get_product')) {
    WP_CLI::error('WooCommerce doit etre charge.');
}
$id = filter_var($args[0] ?? null, FILTER_VALIDATE_INT, ['options' => ['min_range' => 1]]);
if (count($args) !== 1 || $id === false) {
    WP_CLI::error('Indiquez un ID positif de variation.');
}
$variation = wc_get_product($id);
if (!$variation || !$variation->is_type('variation')) {
    WP_CLI::error('Variation introuvable.');
}
$compteur = wc_get_product($variation->get_stock_managed_by_id());
if (!$compteur) {
    WP_CLI::error('Produit portant le compteur introuvable.');
}
WP_CLI::log(wp_json_encode([
    'variation' => $id,
    'compteur' => $compteur->get_id(),
    'gestion_active' => $compteur->managing_stock(),
    'quantite' => $compteur->get_stock_quantity(),
]));