BrikPanel: WooCommerce Dashboard, Abandoned Cart Recovery, Google Sheets Sync, Inventory Management & Bulk Editor

Değişiklik Kaydı

3.2.69 (2026-08-15)

• Fix: A payment that fails no longer leaves the cart marked “Recovered”. A cart was counted as won back the moment WooCommerce created the order, which is before the payment gateway has even run. A card that was then declined left the cart reading “Recovered” for good, so the Recovered count and its value included money the store never took, and your follow-up emails stopped going to exactly the shopper who still needed them. A cart is now recovered only once its order reaches a status that means a real sale, which covers bank transfer, cash on delivery and any custom order status your store uses, and the row re-opens by itself if that order is later declined, cancelled or deleted. Reported by a store owner.
• Fix: Retrying a failed payment no longer splits one cart into two rows. Because the first attempt had already closed the cart, the shopper’s next try opened a fresh row for the same cart, which became another abandoned cart an hour later. One shopper could end up with an active cart and several recovered ones side by side. One cart now stays one row however many times payment is attempted.
• Fix: Figures already recorded are corrected once on update. Carts credited to an order that failed, was cancelled or has since been deleted go back to Abandoned or Active, and duplicate rows left behind for the same cart are merged into one. Carts that really were bought are left untouched.
• Fix: A cart abandoned at the payment page no longer disappears from the list. With gateways that send the shopper to the bank’s own site, the cart is emptied on the way out, and a shopper who gave up there had their saved cart contents overwritten with an empty one, which took the row out of the abandoned list altogether. The saved cart is now kept while payment is in flight, so the shoppers most worth chasing stay visible.
• Fix: Saving a product can no longer clear its images. When the image gallery had not finished loading, a save said nothing about images at all and the server read that as “the merchant removed them”, so the product’s featured image and gallery were quietly emptied. Because the editor also saves by itself every minute, this could happen without anyone pressing Save. The editor now stays silent about images until it knows what they are, and removing every image by hand still works exactly as before, on simple and variable products alike.
• Developer: A new brikpanel_cart_recovery_reverted action fires when a recovery is undone, so an email tool that cancelled its follow-up series can queue it again. Documented, with the rest, under WooCommerce → Settings → BrikPanel → Developers.

3.2.68 (2026-08-15)

• Fix: “Active carts” now counts carts, not empty email signups. An email captured with nothing in the cart was counted as an active cart, which is why the card could read “Active carts 6” next to “Value in cart $0.00”. Those rows also never aged out, because only carts holding items are moved to abandoned, so the number could only grow. Emails captured without a cart still count under “Emails collected” and are listed as “Email only”. Reported by a store owner.
• Fix: “Recovered” now means a cart that really was abandoned and then bought. Any order matching the shopper marked their cart as recovered, including one placed moments after the email was captured, without the cart ever having been left behind. Those are ordinary sales, and counting them made the card and its “Recovered value” read far higher than the carts you actually won back. They are now listed separately as “Converted”, and Recovered counts only carts that were abandoned first.
• Fix: One order no longer counts as several recoveries. A shopper captured more than once (a popup signup and a checkout entry, say) had every one of those rows credited with the same single order, so both the Recovered count and the recovered value were inflated by carts that never separately sold. One order now credits one cart. Figures already recorded are corrected once on update, so existing stores will see Recovered fall to its true value.
• New: You can set how long a cart stays eligible to be counted as recovered. WooCommerce → Settings → BrikPanel → Cart abandonment has a new “Count as recovered within” setting, seven days by default. A customer returning long after they left a cart behind is a new sale rather than a recovery, and previously a cart from a month earlier was still credited to that order.
• Fix: Changing an order’s status in the admin no longer credits the wrong cart. Recovery matched the browser making the request as well as the billing email. On the order screen that browser is yours, not the shopper’s, so a store admin with their own captured cart could have it credited to whichever order they were editing. Browser matching now applies only where it belongs, at the checkout itself.

3.2.67 (2026-08-15)

• New: You can now decide, per attribute, whether it shows on the product page. Every attribute row in the product editor has a “Show on product page” switch, matching the checkbox WooCommerce offers on its own product screen. Switch it off and the attribute disappears from the Additional information table on the storefront while everything else about it stays the same. On a variable product you can hide an attribute from that table and still keep it as an option buyers choose, exactly as WooCommerce allows. Reported by a store owner.
• Fix: Attributes you had hidden no longer come back on the next save. The editor did not read WooCommerce’s “Visible on the product page” setting and switched it back on every time a product was saved, so an attribute hidden from the WooCommerce product screen reappeared on the storefront as soon as the product was saved in BrikPanel. Your setting is now read, shown and kept, on both simple and variable products.

3.2.66 (2026-08-15)

• New: Abandoned Carts lets you choose which columns you see, and in what order. A “Columns” button above the table switches any column off, and you can drag the entries to put the columns in the order you prefer, or move them with Alt and the arrow keys. Your choice is remembered for you alone, so it does not change what anyone else on the store sees. Two columns you could not see before are now available: “Cart total” on its own, and “Created”, the date the cart was first started.
• New: You can sort abandoned carts by cart value or by age. A “Sort by” picker above the table offers highest and lowest cart value, and oldest and newest cart, alongside the usual last activity. Sorting by highest value makes the big carts worth chasing easy to find, and oldest first surfaces the ones that have been sitting the longest. Exports follow whatever sort you have chosen, so the file matches the screen. Requested by a store owner.
• New: Pick a date range in one click instead of typing two dates. The two empty date boxes above the abandoned carts list are gone, replaced by a single picker with Today, Last 7 days, Last 30 days and Last 90 days. Two specific dates are still available under “Custom range”, which reveals the date boxes only when you ask for them. The list opens on “All time” as before, so nothing changes until you choose a range.
• Fix: Date filtering now follows your store’s timezone. Filtering the abandoned carts list by date compared your dates against UTC rather than your store’s own clock, so on a store several hours ahead of UTC a day’s filter was shifted by that many hours: carts from the early hours were missing and some from the previous evening appeared instead. Dates are now read in your store’s timezone.
• Tweak: The filters above the abandoned carts list are now a single tidy row that applies itself. Search, status, source, date range and sorting sit on one line with their labels inside them, searching happens as you type, and every other control applies the moment you change it, so the “Apply” button is gone. A “Clear” link appears whenever a filter is active.

3.2.65 (2026-08-15)

• Fix: Store Health no longer stops part-way through scanning your products. On stores with more than 200 products the scan ran its first batch and then stopped, so the page sat on “Scanning 200 / 667 products…” forever and the image check never produced a result. Each batch queues the next one, and that hand-off was being refused because the batch already running counted as a duplicate of itself. Scans now run to the end whatever the size of your catalogue. Reported by a store owner.
• Fix: A scan that stops halfway no longer leaves “Scan now” greyed out with no way back. While a scan was believed to be running the button was disabled, so a store left on a frozen progress bar could not start a new scan at all and had to wait an hour for the state to expire. Store Health now checks whether anything is actually still queued, and picks the scan up from where it stopped instead of leaving it hanging. This also repairs stores that were left frozen by the previous version: opening the page is enough.

3.2.64 (2026-08-15)

• New: You can put variations in the order you want. Grab a row by the handle on its left and drag it where it belongs, or use the arrow keys once the handle has focus. There is also a “Sort variations” picker above the table for A to Z, Z to A, and the order your attribute values are already in. The order is saved with the product and is the order you see everywhere else, including WooCommerce’s own product screen. Until now there was no way to sort variations at all: the list always came back in the order the variations happened to be created. Reported by a store owner.
• Fix: “Generate variations” no longer rearranges the variations you already have. It used to rebuild the whole list from scratch, so an order you had arranged by hand was lost every time you pressed it, and a newly created variation could jump to the top. Existing variations now stay exactly where they are and only genuinely new combinations are added, at the end of the list. Reported by a store owner.
• Fix: Regenerating no longer silently deletes variations. A variation whose combination is no longer in your attribute values, and a row you added by hand with “Any”, both used to vanish when you pressed “Generate variations”, and the next save removed them for good. They are now kept and marked “Not in your attributes” so you can decide whether to delete them. A variation you had just deleted can also no longer come back from a later “Generate”.
• Fix: Fields added by other plugins now stay with the right variation. If another plugin adds its own field to each variation, deleting a variation used to shift every one of those values onto the variation below it, and the last one was lost. The same applied when reordering. Each value now stays with the variation it belongs to, and anything you type into such a field is no longer wiped when the table redraws.
• Fix: Saving a variable product with the variations section switched off no longer destroys it. If “Variations” was turned off in WooCommerce → Settings → BrikPanel → Products, saving a variable product from the editor turned it into a simple product and permanently deleted every one of its variations, because the hidden switch reported “not a variable product”. The editor now leaves the product type alone when it has no variations section to ask about.

3.2.63 (2026-08-14)

• Fix: A phone number that already carries its country code no longer gets a second one in front of it. A shopper who typed “90 545 728 83 42” at a store based in the United States was linked to “+1 90 545 728 83 42”, a number belonging to nobody. When BrikPanel has no country on file for a shopper it used to fall back to your store’s own country and put that code in front regardless; now, if the number already begins with a country code, the number is trusted and left alone. When the shopper’s real country is known nothing changes. Reported by a store owner.
• New: Abandoned carts remember which country the phone was typed in. Checkout now records the billing country alongside the phone, so the WhatsApp link no longer has to guess one afterwards. Where a guess is still the only option, the button’s tooltip says so, and shows the exact number it will dial before you click it. Carts saved before this update keep working and simply fall back to the smarter detection above.
• Fix: The Orders and Abandoned Carts screens now build WhatsApp links the same way. The two screens each had their own copy of the number logic and could disagree: a Caribbean number gained a duplicated area code on one screen but not the other, a number already written with its country code was doubled on one screen, and one screen would happily build a link from a number too long to be real. Both now share one routine, so the same customer always gets the same link. Numbers written with “+”, with “00” or with the North American “011” dial-out prefix are all understood, and a single national leading zero is dropped without eating the rest of the number.

3.2.62 (2026-08-14)

• New: Attributes you type in the product editor can become real WooCommerce attributes, in any language. Colour and size swatches, layered navigation and attribute filters all read what WooCommerce calls global attributes, the ones listed under Products → Attributes. The editor used to convert one for you only if you happened to name it Color, Colour, Renk, Size or Beden, so a Dutch shop typing “Kleur” ended up with a product-only attribute its theme could not use, while an English shop typing “Color” got a site-wide one it never asked for. There is now one switch, “Create global attributes automatically” in WooCommerce → Settings → BrikPanel → Products, on by default and no longer tied to a list of words. An attribute that already exists is reused instead of duplicated, whatever capitalisation you type. Nothing is created while the product is still a draft, and a name WooCommerce will not accept, too long, reserved or just a number, quietly stays product-only rather than failing the save. Switching it off later leaves attributes that already exist alone; remove those in Products → Attributes. Reported by a store owner.
• Fix: A variation’s default choice no longer disappears when you save twice without reloading. When an attribute became a global one during a save, the editor kept referring to it by its old name, so the “Default Form Values” dropdown came back empty and the next save cleared the default you had picked. The editor now picks up the new attribute, its proper label and its values straight from the save, so a second save keeps everything and a variation row you add by hand offers the right options.
• Fix: The item list in an abandoned-cart WhatsApp message now puts each product on its own line. Products were strung together on one line separated by semicolons, so a cart of four or five items arrived as a crowded paragraph that was hard to read on a phone. {items} now writes one product per line, variations included. Downloading the list as CSV or Excel is unchanged, where the whole cart still belongs in a single cell. Reported by a store owner.
• New: The WhatsApp button on your orders now opens with the message already written. Clicking the WhatsApp icon on the Orders list, or the button on an order’s page, used to open an empty conversation and leave you to type everything yourself. It now opens with a draft ready to send, which you can still edit or delete before sending; nothing is ever sent on its own. Write your own in WooCommerce → Settings → BrikPanel → Orders, with {customer_first_name}, {order_number}, {order_status}, {order_total}, {order_items} and more. Clear the box to go back to opening an empty conversation.
• New: A different WhatsApp message for each order status. Say one thing while an order is being prepared and another while it is still awaiting payment. Every order status your store has is listed, including your own custom ones and any a shipping plugin adds; switch one on and write its message, and every status you leave off keeps using the general message. Simple and variable products both list correctly, with each variation’s options shown once.

3.2.61 (2026-08-14)

• New: A button another plugin adds to the top bar now follows you everywhere. BrikPanel’s own top bar steps aside on a few screens, the post and page editor, the site editor, and for staff accounts without WooCommerce permissions, and WordPress shows its own toolbar there instead. Until now a button registered for the BrikPanel bar simply disappeared on those screens. It is now placed in the WordPress toolbar automatically, so the plugin author writes one registration and the button is there on every screen. The store owner keeps the same on/off switch and per-role visibility rules over it either way. Requested by arcanetech.

3.2.60 (2026-08-13)

• Fix: The Rank Math SEO score is correct again in the product editor. A product scoring 100/100 in the product list showed 0/100 on the BrikPanel editing screen. Rank Math loads its Advanced Custom Fields bridge on any product screen, and with the ACF section switched off that bridge threw an error which cancelled the entire analysis before a single test had run, so the score fell back to zero. The bridge is now left out when no ACF field is on screen, an add-on that fails while Rank Math gathers the content can no longer take the whole score down with it, and the product’s first image is handed over as the featured image so the image tests pass exactly as they do in the WordPress editor. Both screens now report the same number, on simple and on variable products.
• New: Write your own WhatsApp message for abandoned carts, in your own language. The message opened from the Abandoned Carts list was fixed text. WooCommerce → Settings → BrikPanel → Cart abandonment now has a “WhatsApp message” box with {customer_name}, {store_name}, {items}, {cart_url} and {recovery_url} placeholders. {recovery_url} rebuilds that exact cart in a single tap, with the right variations selected. Leave the box untouched and the message stays as it was, in your store’s language.
• Fix: Text in Arabic, Turkish or any other non-Latin alphabet is no longer cut in the middle of a character when a message or popup field reaches its length limit.
• New: Live Visitors shows what each visitor is browsing on. Mobile, tablet or desktop now appears as a small icon at the start of every row, worked out with the same detector as the Devices breakdown, so the two can never disagree. No raw browser information is stored and nothing extra is sent from the visitor’s browser.
• Security: A customer can no longer inject code into your dashboard through their own billing details. Details a customer types in themselves, such as a phone number, were placed in the Live Visitors row tooltip without escaping the double quote character, so a crafted phone number could run its own script the moment the store owner hovered over that row. Every row tooltip, label and link now uses attribute-safe escaping.
• Fix: Saving a variable product no longer stops after the first variation. BrikPanel asks other plugins to save their own variation fields after each variation. A plugin that ends the request outright instead of returning an error, which Woo Product Variation Gallery does when it does not recognise the form it is given, left every variation after the first one unsaved and showed no error at all. Such a plugin now loses only its own field write, your variation data is saved, and every other plugin carries on as normal. The same protection covers the plugins that run when the product itself is saved.
• Fix: Admin-only wording no longer turns up in translation plugins. Text that only ever appears on BrikPanel’s own admin screens was being prepared on every storefront page view and every background request, so front-end translation plugins such as TranslatePress collected it as store text: 112 such rows on a test store, now none. It is prepared only where it is actually shown, which also takes a slice of needless work out of every page load.

3.2.52 (2026-08-13)

• Fix: Saving a bundle, composite or booking product no longer wipes its own data. After a save, BrikPanel told other plugins to process the product, which is how their fields get saved. For a product type whose own WooCommerce panel the simplified editor cannot show, those plugins received a form that never contained their fields and read that as “the merchant cleared everything”: a WooCommerce Product Bundles product lost every bundled item and had its layout and cart settings reset. When BrikPanel saves a product type it cannot fully represent, it now holds back only the plugin that owns the missing panel, so that plugin’s data is left exactly as it was while every other plugin still saves normally, and the editor says where those settings can be changed. Reported on the support forum.
• Fix: A product whose type is added by another plugin (bundle, composite, booking, subscription) keeps that type when saved from the editor with the product type selector switched off, instead of being turned into a simple product.
• Fix: One plugin failing while WooCommerce draws its product data panels no longer hides every other plugin’s panel from the “Additional product data sections” list, or from the editor itself.

3.2.51 (2026-08-13)

• New: Find a product by your own supplier or manufacturer code. The product list search already matched the title, the description and the WooCommerce SKU, including a variation SKU, but a warehouse that scans a supplier code kept in its own custom field got nothing back. Stores can now tell BrikPanel which extra fields to search with the new brikpanel_product_search_meta_keys filter, and a code found on a variation returns its parent product, so simple and variable products both work. Nothing changes unless you use the filter: out of the box BrikPanel still searches exactly the WooCommerce SKU field. Requested on the support forum.
• Fix: A SKU containing an apostrophe is now findable. Searching the product list for a code such as OB’RIEN-9933 returned nothing, because the apostrophe was still escaped when the SKU was matched. Searching by product name was unaffected.
• Fix: A product search no longer leaves its extra search rule switched on for the rest of the page load when another plugin throws an error while the product list is being built, which could quietly widen unrelated searches on the same request.
• Fix: While a product search is running, BrikPanel’s extra search rule is no longer applied to searches another plugin happens to run at the same moment, which could quietly widen someone else’s results.

3.2.50 (2026-08-13)

• Fix: Cookie consent now works with the banners people actually use. The consent gate added in 3.2.48 was tested against the eleven most-installed consent banners, and two problems turned up. Banners that report a decision without declaring which privacy law applies, which includes CookieYes and GDPR Cookie Compliance by Moove, left BrikPanel waiting forever after the visitor had already clicked Accept. And banners that announce “everything denied” on the very first page load, CookieYes among them, made BrikPanel send a pointless clean-up request on every page view before the visitor had touched anything. Both are fixed: a decision from your banner is honoured whichever way it is reported, and a refusal with nothing to clean up is now the no-op it should be.
• Tweak: The consent documentation now lists which banners work with no setup at all (Complianz, CookieYes, GDPR Cookie Compliance, WPConsent, Cookiebot, iubenda, Beautiful Cookie Consent Banner), which one needs its own Compliance mode connected (Cookie Notice), and gives a tested copy-paste bridge for the ones that do not use the WordPress Consent API at all (CookieAdmin, Real Cookie Banner, Termly).

3.2.49 (2026-08-13)

• New: Remove an expense straight from the dashboard. The Profit section’s Expenses breakdown was read-only: you could add a cost with the “+” button but there was no way to take one back out without leaving the page. Every line that comes from your own expenses now has a small remove control. Because a line is a grouped total rather than a single entry, the confirmation tells you exactly what it covers: one entry is named with its date and amount, several are summed and counted.
• New: Repeating expenses ask what you meant. Removing a line that belongs to a repeating expense offers a choice between clearing only the period you are looking at and removing the repeating expense altogether. The first entry of a series is the date the whole series is generated from, so it is kept out of the “only this period” option and the dialog says so rather than quietly deleting future occurrences.
• Fix: Deleting one occurrence of a repeating expense now sticks. Removing a single generated occurrence, from either the Operational Expenses page or the dashboard, looked like it worked but the entry came straight back the next time the figures were read: the engine that fills in a repeating expense saw a period with no entry and created it again. Removed occurrences are now remembered, so they stay removed, while the rest of the series keeps running. Editing the expense’s amount no longer brings them back either, and changing its start date or frequency correctly forgets removals that no longer apply.
• Fix: A repeating expense set to a percentage of revenue can no longer be expanded into dated money entries, which would have multiplied the rate as if it were an amount.

3.2.48 (2026-08-13)

• New: Visitor tracking can now wait for cookie consent. Until now the only way to stop BrikPanel writing a visitor cookie before a consent banner had been answered was to switch tracking off entirely, which also emptied the Visitors, Live Visitors and conversion funnel cards. A new Wait for cookie consent switch under WooCommerce → Settings → BrikPanel → Analytics keeps the statistics and holds everything back until the visitor allows analytics: no cookie, no browser storage, no request. Consent takes effect immediately without a page reload, and withdrawing it stops tracking and deletes BrikPanel’s own cookies and browser storage for that visitor. Off by default, so nothing changes unless you turn it on. Reported by silaghichris.
• New: Works with the WordPress Consent API out of the box. With the consent switch on, BrikPanel reads the statistics category, follows live consent changes from your banner, and declares every cookie and browser storage key it uses so a consent platform can list them in your cookie policy automatically.
• Developer: Consent can also be driven from any cookie banner through the brikpanel_frontend_tracking_allowed PHP filter or the brikpanel_start_tracking() / brikpanel_stop_tracking() JavaScript methods. Both are documented under WooCommerce → Settings → BrikPanel → Developers.

Older releases are listed in changelog.txt, bundled with the plugin.