https://www.gpldownloads.com/downloads/woobe-woocommerce-bulk-editor-professional/changelog/
Auto Updates
Latest Updates
Log inGet Started
Back to BEAR – WooCommerce Bulk Editor Professional

BEAR – WooCommerce Bulk Editor Professional changelog

Release notes for every version we have on record, newest first.

Latest 2.2.6 17 versions Since May 2026

Undated 16 versions

2.2.6 Latest 2 new22 fixed
New
  • A variation's own image in the Thumbnail column shows a × on hover that removes the image (History keeps it for rollback); with a variation gallery the cell shows its first image faded again.
  • With WooCommerce 11.1 or newer, variation galleries can be edited in BEAR: the Gallery column and bulk edit work for variations, and the MCP image tools (woobe_product_images, woobe_set_images, woobe_upload_link and the other image tools) accept a variation id; on older WooCommerce variations keep the lock as before.
Fixed
  • MCP server fix: woobe_create_product dropped the attributes of simple, external and grouped products without a word; they are saved now, as woobe_update_product saves them.
  • MCP server fix: term names came back HTML-escaped (Clothing & Shoes) from woobe_list_terms and the other tools; they are plain text now (Clothing & Shoes).
  • MCP server fix: woobe_update_product of an attribute, a category, a tag or another taxonomy answered an empty "returned"; it shows the value stored after the write.
  • MCP server fix: on a new install, edits made through the MCP server before the BEAR page was first opened were not recorded in History and could not be rolled back; the History tables are now created by the first write.
  • MCP server fix: categories, tags and other taxonomies given as a comma list ("16,17") kept only the first term, and a name or an id of another taxonomy quietly emptied the product's terms; comma lists are read in full now, and a value that is not a term id of the field is refused with nothing written (woobe_update_product and bulk edits).
  • MCP server fix: an attribute value that matched no term (a name instead of an id, or a comma list) cleared the attribute without a word; ids (also comma separated) and names given as {"name": "..."} are accepted now, an unknown value is refused with the list of allowed ones, and the answer shows the stored values with their names.
  • MCP server fix: images set through the MCP image tools were not recorded in History, so they could not be rolled back; they are now, for products and variations.
  • MCP server fix: the answer of woobe_set_images after a replace showed the tail of the old gallery; it shows what is stored.
  • MCP server fix: images written to one product at the same time (files sent at once to an upload link, parallel woobe_set_images calls) overwrote each other, and the upload link lost track of what arrived; they are written one after another now.
  • MCP server fix: woobe_top_customers stopped with a critical error on dates it could not read; it answers like the other reports.
  • MCP server fix: woobe_export_csv stopped with a critical error when an id was not a product of the shop; such ids are left out and named in the answer.
  • MCP server fix: any text was accepted as a product status, and the product vanished from the shop, the admin lists and the filters; only the shop's statuses are accepted now.
  • MCP server fix: numbers were cast without a word - "12,50" became 12, a price could be negative, "2.5" pieces of stock became 2; such values are refused with the reason, in woobe_update_product and in bulk edits.
  • MCP server fix: woobe_create_order turned a quantity of 0, -2 or 2.5 into 1; it is refused now.
  • A SKU already used by another product was saved anyway and the table showed no error; it is refused now with a message and the old SKU stays, in the table, in bulk edit and through the MCP server.
  • A SKU changed in the table, in bulk edit or through the MCP server did not reach WooCommerce's product lookup table, so the old SKU stayed reserved and other plugins reported "Invalid or duplicated SKU".
  • CSV exports (the Export tab and the MCP server) wrote values starting with = + - @ as they are, so a spreadsheet ran them as formulas; such values get a leading apostrophe now, as in WooCommerce's own export.
  • With TranslatePress active, variation titles in the table, in the line above it, in the Thumbnail tooltip and in the popup editor titles showed markup as text (Shoe - Red).
  • A variation without its own image showed the placeholder in the Thumbnail column although its WooCommerce variation gallery has images; the first gallery image is shown faded, with a note that it is not set as the variation image yet (display only, nothing is saved).
  • Images uploaded in the "Add Image" window of the Gallery popup did not show up in that window's media library and could not be selected; they show up selected now, ready to add.
  • Opening the Gallery popup from a cell that already has images scrolled the page to the top, so after Apply or Cancel the table was no longer where it was; the page stays in place now.
  • The line above the table showed "&" in titles with an ampersand (Black & White); it shows "&".
2.2.5 3 fixed1 changed
Fixed
  • MCP server fix: a change written to particular variations (include_variations matching) with variations_only reached every variation of the product, not only the chosen ones.
  • MCP server fix: include_variations matching with two attributes took the variations matching either of them; it now takes only those matching all of them.
  • MCP server fix: include_variations matching did not narrow anything on attributes with non-Latin names and took every variation of the product.
Changed
  • MCP server: a selection taken with include_variations matching holds only the chosen variations, without their parent products - reports, export and deletion now work on exactly those variations; deleting such a selection no longer moves the whole product to the trash.
2.2.4 2 new2 improved35 fixed4 changed
New
  • History shows who made each change and whether it was done by hand or through the AI assistant; administrators see and can roll back everyone's history, other users see only their own.
  • MCP server fix: adding variations with the same combination listed twice dropped the second one without a word; it is now refused.
Improved
  • History filter "by Author" replaced by "Who made the change" with an extra "by hand / through AI agent" filter (administrators only).
  • Stock quantity, weight and dimension filters - an empty "from" now means no lower limit, so "to" alone also finds negative stock (it started at 0), as through the MCP server.
Fixed
  • MCP server fix: GET request to the MCP endpoint caused a PHP fatal error.
  • MCP server fix: MCP rollback left an empty bulk entry in History.
  • MCP server fix: woobe_find_products refuses a filter key it cannot use, or a value in another shape, and says why; before, such a condition was ignored and the whole catalogue was selected.
  • MCP server fix: number ranges of the product filter work as the tool description says - from included, to excluded, a missing end open, from equal to to exactly that value; a stock range 0 to 0, a stock "from" alone or a weight of 0 selected the whole catalogue.
  • MCP server fix: whole_catalogue in the answer of woobe_find_products is true whenever the selection holds every product.
  • MCP server fix: arguments of the wrong type are refused with a readable error instead of PHP warnings or an HTTP 500; a text such as "maybe" no longer counts as a confirmation.
  • MCP server fix: several product finds in one request carried each other's conditions.
  • MCP server fix: a product read of an id that is no product caused a PHP fatal error.
  • MCP server fix: gallery, upsells, cross-sells and grouped products given as a list of ids were emptied.
  • MCP server fix: creating a product with a SKU already in use now says the SKU was left empty.
  • MCP server fix: creating a product with a category name or a missing category id now warns instead of saying nothing.
  • MCP server fix: an order for a customer that does not exist is refused.
  • MCP server fix: the margin report logged a WooCommerce notice per product when Cost of Goods Sold was off.
  • MCP server fix: a unix timestamp given for a date field (the sale dates) was stored as 1970 - it is read as the day it falls on in the shop's time zone, and woobe_list_fields names the formats a date field takes.
  • MCP server fix: the bulk preview checked each operation of a run against the stored values, so a sale price set together with a new regular price showed as refused; it follows the run's operations in order now, as the apply does.
  • MCP server fix: creating a variable product refused a list with the same variation twice; both were created and checkout sold only one.
  • MCP server fix: the "product with this name already exists" warning no longer counts products in the trash.
  • MCP server fix: the bulk preview showed a new stock for variations that sell from their parent's shared stock and for variable products without stock management, although nothing is written on them; they are now shown unchanged and named in the stock_not_tracked warning.
  • History rows written in the same second could disappear from the list.
  • PHP warnings for shop managers when the field visibility settings had never been saved.
  • History pagination jumped several pages after the list was reloaded.
  • The rollback of a bulk stock edit put a product that does not track its stock - a variable product whose variations hold the stock - under stock management, at 0 and out of stock.
  • History revert of a gallery, upsells, cross-sells or grouped products change emptied the field.
  • History revert of a sale date deleted the sale schedule.
  • History list pages after the second could not be reached after the page size was changed.
  • Sale price filter with only "from" found nothing; PHP warnings for a price or stock range with one end.
  • A stock quantity range or a product URL filter that matched no product selected every product.
  • Stock quantity filter with only "from" filled in selected every product (with "from" 0, only a stock of 0); an empty "to" now means no upper limit, as for the regular price.
  • Weight, length, width and height filters with only "from" filled in found nothing; an empty "to" now means no upper limit.
  • The "Menu order from" filter found nothing.
  • History revert of a stock management switch left the stock status WooCommerce had derived from it (for example out of stock); the status comes back with it.
  • A bulk price edit on a selection with variable products wrote a hidden price onto the parents, which no rollback removed; the parents are left alone - their prices live on the variations -, the rollback of such an earlier edit removes the leftover, and through the MCP server a price edit on variable products only is refused, as it would write nothing.
  • Weight, length, width and height filters from 0 (or exactly 0) found products whose value was left empty; an empty value is no longer part of any range.
  • A stock of 0 entered on a variable product that does not track stock switched stock management on for it, and every variation without a stock of its own went out of stock; the revert did not bring them back. The value is now left alone, as any other value already was - the stock of a variable product is set on its variations.
  • A stock of 0 entered on a variation that sells from its parent's shared stock detached it from the shared stock with a stock of its own, and the revert did not attach it again. The shared stock is changed on the parent.
Changed
  • MCP server: MCP access for selected users - the administrator grants MCP to named users, each gets a personal key and works under his own WordPress account and rights; two-factor connection is always on for them.
  • MCP server: permission map for MCP (hook woobe_mcp_permissions) - full / read / none per area of the shop, per user.
  • MCP server: every report answer says in one line that its figures come from WooCommerce Analytics and, while Analytics imports orders on a schedule, how many newer orders are not in them yet.
  • MCP server: the product creation preview now warns about a SKU already in use and about attribute values that look like existing ones (S next to Small), before anything is written.
2.2.3 2 new9 fixed1 security18 changed
New
  • MCP server: new optional MCP two-factor connection, off by default. With it on, the MCP key alone is not enough: every AI assistant session also needs a token that the shop administrator confirms in the plugin settings, and the session closes by itself after an hour without use.
  • MCP server: when an AI assistant puts a product into a subcategory, its parent categories are added as well - on every way of writing, from creating a product to a bulk edit - so the product shows up where customers expect it.
Fixed
  • MCP server fix: variations created by an AI assistant on attributes with non-Latin names were saved as "any value".
  • MCP server fix: a taxonomy filter without an operator, or with "OR", matched the whole catalogue instead of the chosen terms.
  • MCP server fix: search by product title and sorting of results.
  • MCP server fix: the upload page respects the server's upload size limit and numbers the files correctly.
  • MCP server fix: with the FOX currency switcher, orders created by an AI assistant could get a doubled subtotal, and reports could convert amounts twice.
  • MCP server fix: refunds with restock now actually return goods to stock, and orders created with stock reduction off no longer reduce it.
  • MCP server fix: sales, stock and refund reports now count variations under their own ids.
  • CSV exports are no longer left accessible in the plugin folder, and old export files are removed after 8 hours.
  • Product titles containing HTML are shown as text in the editor.
Security
  • Hardening of the MCP server and the bulk editor. Updating is strongly recommended. Thanks to the WordPress.org Plugin Review Team and Patchstack for responsible disclosure.
Changed
  • MCP server: now off by default and has to be switched on in the plugin settings. Without the MCP key it answers nothing at all.
  • MCP server: an AI assistant can now create products - simple, variable with attributes and variations, external and grouped - with a preview before anything is written. Products are created as drafts and can be published from the chat with one command.
  • MCP server: an AI assistant can now work with product images - the media library, the featured image, the gallery and import from a link. It can also give the owner a one-time upload page, valid for 15 minutes and needing no login, where photos are dragged from the computer straight into the media library and onto the product.
  • MCP server: an AI assistant can now fill a development shop with generated products - up to 5000, with guided questions, written items for small batches or a vocabulary for large ones, unique names and SKUs, written in portions.
  • MCP server: an AI assistant can now create categories, tags, brands and other terms, and attributes together with their values. Non-Latin names are supported.
  • MCP server: an AI assistant can now manage variations of existing products - add and remove variations, add or remove an attribute axis, set the default choices, and spot missing, duplicate and "any" variations.
  • MCP server: an AI assistant can now work with the orders themselves, not only their figures - a filtered order list, a full order card with address and items, top customers, status changes for several orders at once, notes, refunds with confirmation, and manual orders, including in another currency with the FOX currency switcher.
  • MCP server: an AI assistant can now manage coupons - create, edit, trash and restore them, with a preview of what the customer will get.
  • MCP server: an AI assistant can now move products to the trash and restore them, export a selection to CSV with a download link, and run WooCommerce maintenance tasks such as clearing transients.
  • MCP server: an AI assistant can now build reports across the whole catalogue without selecting products first - best sellers, stock velocity, dead stock and margin.
  • MCP server: the sales summary an AI assistant gets now includes refunds for the period.
  • MCP server: bulk edits can append taxonomy terms instead of replacing them.
  • MCP server: before a bulk edit, the AI assistant is warned when replacing attribute values would leave variations that customers can no longer choose.
  • MCP server: bulk edit previews show term names instead of ids, and for "append" the full resulting list.
  • MCP server: order and refund previews say exactly which items will and will not move stock.
  • MCP server: previews come back as a normal result rather than an error, so AI assistants and MCP clients no longer mistake them for a failure.
  • MCP server: errors carry a code the AI assistant can read.
  • MCP server: reports and order lists use the shop's time zone for dates like "today".
2.2.2 1 new3 fixed1 security
New
  • MCP server - connect Claude, ChatGPT or any MCP capable agent to your shop and work with it in plain language: filter and bulk edit products, get sales, stock and refund reports, export CSV. Every change shows a preview first and is revertible from History: https://bulk-editor.com/document/mcp-server/
Fixed
  • Several issues found while building it - the plugin did not initialise on REST requests, currency switcher filters could distort prices read outside the editor screen, sale end dates depended on which columns a user had visible, single field edits outside the editor skipped value preparation, and unquoted attributes in draw_select_e() broke the History author filter
  • Saving the settings form could wipe shop wide options that were not on screen for the current user
  • Memory storage https://pluginus.net/support/topic/plugin-purges-object-cache/
Security
  • Audited all AJAX handlers and added the missing nonce, capability and ownership checks. Reported by Ali Mousavi via WPScan: a taxonomy term update handler with no nonce or capability check, a meta field config handler with no nonce, and several read-by-id handlers that returned another product's meta and protected download links to any logged in user. The audit covered every handler in the plug...
2.2.1 1 fixed
Fixed
  • Button gallery redraw https://pluginus.net/support/topic/button-for-gallery-images-disappeared
2.2.0 1 fixed
Fixed
  • "Invalid Date" error in calendar picker when sale date field is empty
2.1.8 1 security1 changed
Security
  • Security fix (Patchstack)
Changed
  • Code quality improvements for woo.com marketplace
2.1.7 1 fixed1 security
Fixed
  • Set of small fixes
Security
  • Security fix (Patchstack)
2.1.6 1 security
Security
  • 2 security fixes (Wordfence)
2.1.5 1 fixed
Fixed
  • Set of small fixes
2.1.4.7 1 new1 fixed
New
  • Custom woobe.css support in theme folder
Fixed
  • CSS design fixes
2.1.4.5 1 security
Security
  • Security fix (Patchstack)
2.1.4.4 1 security
Security
  • Security fix (Patchstack)
2.1.4.3 1 security
Security
  • Security fix (Patchstack)
2.1.4.1 1 security1 changed
Security
  • Security fix (Patchstack)
Changed
  • Bulk delete is now free

2026 1 version

2.1.9 22 May 2026 1 improved3 fixed1 security
Improved
  • Codebase aligned with WordPress Coding Standards (WPCS) and PluginCheck recommendations.
Fixed
  • Sale price range filter could return incorrect results in certain edge cases. Type handling improved for reliable numeric comparison.
  • Regular price range filter had the same issue and has been corrected.
  • Improved handling of empty values in price filters.
Security
  • Security fix, thanks to Bonds and patchstack.com