FileDeck Store Master for WooCommerce

Changelog

3.0.1

• Security and reliability improvements. Updating is recommended.

3.0.0

• Added: upgrade to Pro from inside WordPress. The plugin’s Upgrade link buys Pro, installs it, switches it on and switches the free copy off, and your configuration carries over. This uses Freemius, which asks on activation whether you want to opt in; decline and nothing is sent.
• Changed: the shortcodes, the WP-CLI command, the REST routes, the developer hooks, the admin page address and the webhook headers now all use one name, storemaster: for example [storemaster_table], wp storemaster, /wp-json/storemaster/v1/ and X-StoreMaster-Signature. Update any you placed or call by hand.
• Changed: the plugin’s folder and main file are now filedeck-store-master/filedeck-store-master.php, matching its WordPress.org address. Updating from 2.38.0 switches the plugin off once and does not carry that version’s settings over; switch it back on under Plugins.
• Fixed: having the free and Pro copies installed together no longer stops the site with a fatal error. The second copy stands down and says which one is running.

2.38.0

• Changed: the Modules screen now groups capabilities by where they land in a customer’s visit — finding products, choosing one, what it costs, trade accounts, cart and checkout, after the order — instead of listing all thirty-six in one column.
• Added: a find box on the Modules screen. Type part of a capability’s name, what it does, or its id.

2.37.0

• Changed: Get started now sits at the top of the control centre menu, with Overview. It was the fourth item under “Set up” — the thing you need first, where you look last.
• Changed: setting up now shows which of its three stages you are on, instead of each one arriving as a new page with nothing to say it was part of anything.
• Changed: the setup checks list what needs your attention rather than everything that passed. One warning used to print all nine checks, eight of them green ticks, before the question the screen exists to ask.
• Fixed: each kind of shop now has a button naming it — “See what Wholesale & B2B does” — rather than six buttons all reading “See what this does”, which a screen reader announces identically.

2.36.0

• Changed: the control centre’s sections are now a list down the left rather than a row across the top, so each heading sits above its own items instead of a fragment of them. On a narrow screen it goes back to a row.
• Changed: the lapsed-licence notice gives its full explanation on the Overview screen and one line elsewhere, instead of repeating two paragraphs on all twenty-five.
• Fixed: when two shipping methods share a name — WooCommerce ships two called “Local pickup” — a trade tier’s “hide shipping methods” list showed two identical checkboxes. Methods that share a name now show which is which.

2.35.2

• Fixed: every control centre screen showed two headings — the plugin’s name and then the screen’s. Only the screen’s name remains.

2.35.1

• Fixed: a screen could disappear from the control centre menu if it asked for a section the plugin no longer has. Its page still worked, but nothing linked to it. Anything in that position now appears under “More”.

2.35.0

• Changed: a screen with nothing on it yet now says what the capability is for instead of showing a table of column headings. Product options, product tables, trade tiers, trade applications and live preview each explain themselves on first use.

2.34.0

• Changed: the control centre’s sections are now Catalogue, Pricing, Customers and Orders instead of one heading called “Sell” that held twelve screens — half the plugin — in a single list.
• Added: a find box in the control centre navigation. Type part of a section’s name to narrow the list to it; a term that matches nothing says so rather than emptying the menu.

2.33.0

• Fixed: every control centre screen now has a page heading naming the screen you are on. There was none — the only heading in the page was the one shown when JavaScript is off — so each screen’s sections sat under nothing, and anyone using a screen reader had no title to orient by.
• Fixed: the control centre now takes its accent colour from the admin colour scheme you chose in your own profile. It was always the default blue, so on Midnight, Ocean or any other scheme it was the one screen in your admin that did not match.

2.32.0

• Fixed: a filter panel anywhere other than your shop or a category page drew itself, took a click and did nothing. It now sends the shopper into your shop with that filter applied — so a panel on a landing page, in a sidebar or in a footer is a way into your catalogue, and needs no template editing.

2.31.0

• Fixed: on a category page, the number beside each filter option counted the whole catalogue instead of that category — so a category could offer you an option that led to an empty page. The counts now answer for the page you are on, and an option with nothing to show is not offered.
• Changed: the help centre’s advice on where to put a filter panel was wrong for block themes, which is every theme WordPress has shipped since Twenty Twenty-Two. It now tells you to add the panel to your Product Catalog template — with a Shortcode block if you want the styles, or the plugin’s own block if you just want the facets — and says which placements narrow a list and which only draw a panel.

2.30.0

• Fixed: shop managers could not open FileDeck Store Master at all, even though they are granted permissions for catalogue, products, order emails and documents. Those permissions now work: a shop manager sees the screens they are allowed and nothing else. Turning modules on and off stays with administrators.

2.29.0

• Added: with the catalogue index built, search also matches a product’s categories, tags and attribute values — so a shopper who knows the finish or the material but not your product name still finds it. Names still win: a product called “Bracket” ranks above one merely filed under Brackets.

2.28.0

• Fixed: live preview did nothing on the storefront. The canvas showed the product but there were no controls to type your text into or upload artwork with, so nothing a customer entered ever appeared and no design was saved to the order. Each preview area now gets the controls it was set up to allow.

2.27.0

• Removed: the Site Health check added in 2.26.0 about access rules and the catalogue index. It was wrong — searches already apply your access rules before counting out results, whether or not the index is built, so the warning described a problem that does not exist. Sorry for the noise.

2.26.0

• Added: a Site Health check that warns when you have access rules but no catalogue index. Nothing restricted is ever shown either way, but in that state a search can return fewer results than it should, and now you are told rather than left to wonder.

2.25.0

• Added: product tables can put a variation’s choices in the row. Pick size and colour from menus on the line itself, type a quantity and add — no need to open the product page. Works with JavaScript turned off.

2.24.0

• Added: a Variations screen. Pick a product, tick the variations you want, and change the price, sale price, stock, SKU, weight, image or whether they are enabled — up to 100 at a time. It reports what it did not change as well as what it did, so a SKU WooCommerce refused is named rather than skipped.
• Added: the variation matrix settings — whether it replaces WooCommerce’s dropdowns, and whether it is an order form or a price matrix — now have a screen. They could be stored but not set.

2.23.0

• Product tables can now give each variation its own row, with its own price and Add button, so a buyer who already knows the size they want adds it without opening the product page. Choose it per table under “Products with variations”; existing tables keep linking to the product page as before.

2.22.0

• Added: a product option a customer uploads an image to — JPEG, PNG or WebP, up to 12 MB. The image is re-encoded on arrival and kept outside your public uploads folder, so no web address reaches it; the order shows the customer’s own file name and opening one needs a signed link that expires.
• Note: an upload that never reaches an order is deleted after seven days. Once it is on an order it stays as long as the order does.

2.21.0

• Added: filter panels can be drawn as checkboxes, radios, a dropdown or category images, as well as the links they have always used. Set one style for the panel or pick per facet. Checkbox, radio and dropdown apply together with a single button; links still apply on click.
• Note: there is no colour-swatch style. WooCommerce stores no colour against an attribute term, so one could only be invented — and a swatch that shows the same grey square for every value is worse than a style that is not offered.

2.20.0

• Changed: a quantity rule set to “Each product” now counts that product across the whole basket, not one basket line at a time. A maximum of ten used to refuse eleven of one size and then accept ten of one size plus ten of another. This can refuse baskets your shop accepts today — which is the point, but check any rule you rely on before updating.
• Fixed: the same rule’s minimum ran the harmful way round. Three of one size and two of another were refused against a per-product minimum of five the basket plainly met.
• Note: a rule scoped to a variation still counts that variation on its own, which is what it is about. Category, role and whole-store scopes still count one line at a time; each needs its own counting unit decided and is listed in the build ledger rather than guessed at.

2.19.0

• Added: a trade application now emails the applicant. Approving or turning one down used to tell them nothing at all — the first they knew of a decision was noticing their prices had changed, if they came back to look.
• Added: five email templates you can rewrite — application received (to them and to you), approved, turned down, suspended — on a new Trade emails screen, with {name}, {site}, {tier}, {reason} and {login} placeholders. Clear a box and the default comes back; none is ever sent empty.

2.18.3

• Fixed: the errors a customer sees when an image upload is refused, and the ones shown when a quote cannot be submitted or accepted, were written in English and could not be translated. So were the messages shown when a configuration import is refused.
• Fixed: five messages still called the plugin by its old name. The rename reached everything translatable; these were the strings that had never been translatable, which is why they were missed.

2.18.2

• Fixed: five emails were written in English and could not be translated — the back-in-stock confirmation and alert, the abandoned-basket reminder, the quote offer sent to your customer, and the trade-application and quote notices sent to you. A store selling in another language now sends all of them in that language.

2.18.0

• Added: preview the shop as a wholesale tier. Prices and visibility on the storefront become that tier’s, with a bar on every page saying so. Nothing signs you in as anyone — you stay yourself, and only what the pricing and access engines are told about the shopper changes.
• Note: preview stops at the basket. It does not apply to your cart, the checkout, the Store API or wp-admin, so a previewed trade price cannot reach a real order.

2.17.0

• Added: a wholesale tier can now hide coupons, shipping methods and payment gateways from the customers in it, alongside the tax display it already controlled. The methods and gateways offered are the ones your store has installed.
• Added: wholesale tiers can be edited. Previously a tier could only be created, so nothing on it could be changed afterwards.
• Note: hiding never removes the last shipping method or the last payment gateway. A tier that would leave a customer unable to choose delivery, or unable to pay, hides nothing instead.

2.16.1

• Fixed: after setting up, the check that confirms your capabilities switched on was reading an empty list, so it always reported that everything was on and could never tell you when something was not. It now reads the real list, and says separately when a capability simply is not in your build.

2.16.0

• Added: setting up for the first time now checks your store before you choose anything — supported versions, HTTPS, the background job runner, your database, which checkout you use, how orders are stored, and any plugin that overlaps. Nothing it finds stops you setting up.
• Added: after you apply a setup, it checks the capabilities really did switch on, runs their health checks and gives you links to open your shop and look.
• Added: the end of setup now prompts you to export the configuration you just built.

2.15.0

• Added: four of the plugin’s documented PHP hooks now actually fire — storemaster/access_decided, storemaster/cart_configuration_validated, storemaster/order_item_snapshotted and storemaster/search_projected. Code written against those names did nothing at all before this release.

2.14.0

• Changed: the plugin is now called FileDeck Store Master for WooCommerce. The WordPress.org Plugins Team asked for an identifier clearly associated with its author, and this is it. Nothing about what the plugin does has changed, and no setting needs revisiting.

2.13.0

• Changed: the plugin’s translation domain now matches the slug the WordPress.org directory assigned it, so community translations can be applied. This is a packaging change; nothing in the plugin behaves differently.

2.12.1

• A hardening release for protected catalogues. If you use them, update. Nothing to reconfigure, and no policy, rule or price behaves differently afterwards.

2.12.0

• Fixed: a price in a search suggestion or in quick view’s variation list showed its currency symbol as raw code — “£20.00” rather than “£20.00” — because those two places send the price as text rather than as markup and nothing was decoding it.
• Fixed: and a discounted price in those same two places read out the explanation written for screen readers, to everybody, with both figures run together. It now reads “£10.00 (was £20.00)”.

2.11.1

• A hardening fix in a module that is not part of this edition, so nothing in this release changes what the free build does. The version moves so both editions stay on one number.

2.11.0

• Fixed: a manual order placed for a trade customer is now priced for that customer, which is what the help centre has always said it does. It was priced for the member of staff creating it, so a wholesale buyer’s order written up in wp-admin came out at retail. If you have been correcting those lines by hand, you no longer need to — and the totals on new manual orders for customers with a trade role will drop to match what those customers pay themselves.

2.10.1

• Fixed: the number of Pro modules named in this listing was two short, and had been since the two that shipped in September. Nothing in the software changes.
• Fixed: the free capability list named lead times twice, as two bullets.

2.10.0

• Fixed: a correct password did not open a private shop. The shop’s own password was accepted and the visitor was sent back to the form told it did not open this shop, losing the page they had asked for — because the question was asked on the request that issues the cookie, which cannot yet read it. That notice now appears only where it is true: a password that opens some of the catalogue but not the thing you asked for.
• Fixed: a Blocks checkout saved an extra notification address and then sent to nobody. The snapshot was written on the classic checkout only, and the Blocks one — WordPress’s default since WooCommerce 8.3 — places its order by a different route. Both now write it.
• Fixed: a bulk add from a product table, a variation grid or a saved list counted the lines it attempted rather than the lines the basket took, so WooCommerce’s own refusal and “3 products added to your basket.” arrived together. A variable product saved without choosing options is the common case.
• Fixed: a quote request at its line limit said the product could not be added. It now says the request is full, which is a fact about your own list — and the two refusals that ARE about a product stay identical to each other.
• Fixed: a search box answered a rate limit, a server error or a dead network with “No products found.”, which is a claim about the catalogue rather than about the request. It now says suggestions are unavailable and offers the full search.
• Fixed: “Clear all” on the filter panel left the price range in place, so clearing the filters did not clear them.
• Fixed: a product option printed a price beside a choice that was not what the choice costs. With a percentage, per-character, formula or customer-entered price, the figure shown came from the choice while the charge came from the field — so a choice marked “+5%” could cost 10%, and “+£5.00” could cost £50. A figure is now shown only where it really is the charge, and a reduction no longer renders with a plus sign in front of the minus.

2.9.0

• New: wp storemaster config import can now apply a configuration file, not only preview one, with --apply and --strict. It previously refused every import and said this build could only preview — which was not true of a build with the configuration-import module, and left the capability reachable from the control centre and nowhere else. Without --apply it still previews and changes nothing, and --dry-run still forces a preview, so a script written when that flag was required cannot start writing.
• Fixed: wp storemaster index rebuild said it was rebuilding when it had joined a rebuild already running, so a build that had stopped without finishing reported progress indefinitely. It now says which of the two happened, wp storemaster index status says whether a build has stalled, and --force discards an abandoned one. The live index keeps serving throughout either way.
• Fixed: wp storemaster rules validate could not be run. It answered “Too many positional arguments” and stopped, because the command never declared the word validate that its own usage line told you to type. It now runs — and checks every rule rather than the first hundred in each area, refusing to call the result clean if it could not read them all.
• Fixed: wp storemaster module, diagnostics and blueprint accepted an output format they did not produce. They now accept only the two they do.
• Changed: wp storemaster safe-mode enable now says in its own help that it applies to the whole site, which is what it has always done.

2.8.0

• Fixed: a shop closed for more than a week told shoppers it reopens on a weekday without saying which week, so a fortnight’s closure named a date it would not open on. Reopening times a week or more away now carry the date.
• Fixed: a product table refusing some of a bulk add now says how many lines it refused, and says when the list of names is cut short.
• Fixed: a filter facet listed backordered stock under “Out of stock”. It is now “On backorder”.
• Fixed: several notices described what the product does more broadly than it does — what clearing the extra-recipient box changes, how long a back-in-stock alert waits, whether a trade application is reviewed by a person, and what a minimum-order figure is measured before.

2.7.0

• Fixed: a discount campaign now reaches a variable product’s price range. WooCommerce builds that range from each variation’s stored price, which skips the filter every other surface goes through, so a listing showed undiscounted prices while the basket charged the discounted one.
• Fixed: a variable product on a listing showed the price of its cheapest variation, struck through, with a saving worked out from it — as though that were the product’s price. It now shows both ranges: what the product was, and what it is.

2.6.1

• Product options are not part of this edition, so nothing in this release changes what it does. The version moves so both editions stay on one number.

2.6.0

• Changed: wording across the control centre, where a label or a help line described something other than what the code does. The Settings screen no longer tells you a module is switched off at the moment you switched it on; Fast search no longer says it reads an index this edition does not have; Quick view says where its wording is set instead of “nothing to set up”; and the safe-mode notice names the command that turns it off rather than linking to a screen with no such control.

2.5.0

• Fixed: opening a checkout field saved before conditional fields existed showed “Require an answer: Always” whichever way the field was actually set. Saving it then made every customer answer it. It now opens with the field’s own setting.
• Fixed: the extra-recipients screen said a customer could add up to ten addresses. One is what the product stores, and what the paragraph above it already said.

2.4.0

• New: when quick view cannot load a product, the dialog now offers a link to that product’s page instead of a message on its own.
• Fixed: the notice shown when a licence has lapsed said the whole plugin was read-only. Only the paid modules’ settings are; everything the free edition includes stays editable, and a module can always be switched off.
• Changed: FileDeck Store Master now requires WooCommerce 9.8, which is what the plugin header has always declared and the lowest version the test suite runs against. The compatibility check inside the plugin was admitting 9.0, so on WooCommerce 9.0 to 9.7 WordPress showed the plugin as incompatible and FileDeck Store Master loaded anyway, untested. On those versions it now stays inert and says why, which is the safe direction for something that sets prices.

2.3.0

• Fixed: the “Applies to” list on a quantity rule now offers only the scopes this edition applies. Two of its five options named scopes this edition leaves alone by design, so a rule set to either saved without complaint and then did nothing. Naming them here would put them back in this file, which is the point of removing them from the screen.

2.2.0

• Saved lists and access rules are not part of this edition, so nothing in this release changes what it does. The version moves so both editions stay on one number.

2.1.0

• Access rules are not part of this edition, so nothing in this release changes what it does. The version moves so both editions stay on one number.

1.13.0

• New: quick view’s button wording and fast search’s minimum number of characters each have a setting under FileDeck Store Master -> Settings. Both were read on every storefront request and could not be set from any screen.
• New: an order’s document box shows the number the next invoice would get without reserving it, and offers to replace a document that needs correcting. The original is kept and the new one records what it replaces; pressing Issue a second time used to return the document already there and report success.

1.12.0

• New: product tab settings have a screen. FileDeck Store Master -> Settings -> Product tabs renames, reorders or hides WooCommerce’s Description, Reviews and Additional information tabs, and chooses which tab opens first. The storefront has always honoured these; there was nowhere to set them.
• Fixed: a settings form you do not have permission to save is no longer shown to you, rather than refusing the save after you have filled it in.

1.11.0

• New: document numbering is something you can set. FileDeck Store Master -> Order documents now opens a form, and invoices and packing slips each take a pattern — INV-{year}, PS-{year} — with {year} replaced when a document is issued. The patterns were always read; there was nowhere to type one, and the menu item led to a screen this build did not contain.
• Changed: a configuration export no longer carries customer ids. A rule whose conditions name specific customers is exported with that list emptied and marked as redacted, and the file reports how many rules that applied to. The rule still comes across — an empty list matches nobody, so an imported rule of this kind does nothing until you point it at customers on the new site.
• Fixed: the spreadsheet export offers only the modules you have switched on. A module that was off still appeared in the picker and then produced an empty file.

1.5.1

• Fixed: switching a module off left its scheduled background work running. Turning off cart recovery, saved lists, stock alerts, quotes, live preview, webhooks or bulk documents now cancels that module’s jobs, and deactivating FileDeck Store Master cancels all of them. Previously nothing was ever cancelled, so a job kept firing against a module that was no longer listening.

1.5.0

• New: a FileDeck Store Master block. Every surface — product search, tables, filters, the variation matrix, saved lists, opening hours, quote basket and the rest — can now be placed from the block editor instead of by typing a shortcode. Pick what to show from a list, set its options in the sidebar, and see the real thing while you edit.
• The list only offers what your site has: a surface whose module is switched off does not appear.

1.4.0

• New (Pro): bulk and tiered quantity pricing is now something you can actually set up. Give a rule up to three quantity tiers — from 10 take 5%, from 50 take 15%, from 100 a flat unit price — and the highest tier the quantity reaches wins. Below the lowest tier the normal price stands.

1.3.0

• New: FileDeck Store Master’s data is now included in WordPress’s own privacy export and erase tools. A request from a customer for a copy of their data, or for it to be removed, now covers extra email recipients, checkout answers and — in Pro — back-in-stock alerts, saved lists, abandoned baskets, uploaded files, catalogue access and quote requests. Until now none of it was included, so an export looked complete and was not.
• Quote requests are anonymised rather than deleted, because the shop keeps a record of what it offered. Checkout answers stay on the order, which the shop is required to retain, and the tool says so rather than silently keeping them.

1.2.0

• New (Pro): buy X, get Y free. Set how many a shopper has to buy and how many they get, and choose whether the free item is the cheapest qualifying thing in their basket or another of whatever they bought most of. The gift appears as its own basket line at no charge, disappears if the basket stops qualifying, and stays gone if the shopper removes it.
• Fixed: the advanced discounts health check reported every discount family as available without checking. It now asks the rule editor’s own registry, so a family that is documented but not registered is reported as a failure instead of a pass.

1.1.8

• Documentation only: three code comments described a PDF renderer that does not exist in either edition. Documents are, and always have been, accessible printable HTML.

1.1.7

• The free edition now contains no licensing code of any kind. It never ran any — the licence bootstrap sat behind a check for a file this build does not ship — but it was still present in the download, and it should not have been. It is now removed at build time, and the build fails if a trace of it survives.
• Translations load the way WordPress has loaded them since 4.6, rather than being requested early by the plugin. This also removes a notice on WordPress 6.7 and newer.
• No change to any feature, setting or stored data.

1.1.5

• Fixed: the fast cart never opened. The panel’s markup was printed after the script that drives it, so the script found nothing to attach to and stopped — clicking a basket link went to the cart page as though the feature were switched off, and it …