=== VendMizer ===
Contributors: vendmizer
Tags: ecommerce, online-store, shop, payments, store
Requires at least: 6.0
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.121.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

VendMizer is the complete commerce platform for WordPress. Launch a professional online store with a ready-to-use, customizable storefront.

== Description ==

VendMizer is the complete commerce platform for WordPress. Launch a professional online store with a ready-to-use, customizable storefront and the business tools behind it. Manage products, orders, payments, shipping, inventory, customers and sales analytics from one platform — no extra theme, no design experience and no plugin juggling.

This plugin is fully functional on its own. It includes:

* Product catalog with categories, attributes, brands and product tags
* Cart, a complete checkout flow, order management and a customer directory
* Coupons and discounts, inventory tracking, shipping rates and tax rates
* Reviews, wishlist and digital downloads
* A built-in storefront with editable Home, About and Contact pages, a blog, and scheduled announcement banners you can show as a top bar, a popup, a slide-in or inline
* Analytics dashboard with revenue and order reporting
* A privacy-first cookie consent banner that holds Google Analytics and the Meta Pixel back until the visitor agrees (granular categories, bilingual, first-party only, no IP lookup)
* Contact inbox, media library, staff roles and outgoing webhooks
* Maintenance and coming-soon modes, with an optional countdown, a bypass link for you, and an optional visitor email signup
* Multilingual interface — English and Arabic out of the box, with full right-to-left support, and you can add and translate further languages

VendMizer integrates with third-party payment, shipping and anti-spam services. They are optional and contact nothing until you configure and enable them; "External services" below lists every one and what it sends.

VendMizer is a whole storefront and admin rather than a widget, so it takes over things a smaller plugin leaves alone: your login page, where staff land, and some URLs. The FAQ describes each, and how to switch it off.

A separate commercial extension adds modules of its own. It is not required, nothing here is locked or degraded by its absence, and this plugin never advertises it to you in the admin.

== External services ==

VendMizer can connect to the third-party services below. With one exception, none is contacted unless you enable and configure the matching feature, and no data reaches any of them while that feature is off. The exception is Gravatar, at the end.

Two admin actions also reach a service, and only when you click them. "Test connection" on a payment gateway, shipping carrier or SMTP settings screen sends the credentials you entered to that provider to confirm they work (the Payoneer test additionally sends your site address and a one-dollar sample order that is never charged), and "Send test email" relays a test message through the SMTP host you configured. Neither runs on its own.

**Payment gateways.** When you enable a gateway and a customer pays with it, order and payment details (amount, currency, order reference and the billing information needed to process the charge) go to that provider to create and confirm the transaction. Supported providers and their terms/privacy policies:

* Stripe (API host: api.stripe.com) — https://stripe.com/legal/ssa — https://stripe.com/privacy
* PayPal (API hosts: api-m.paypal.com, and api-m.sandbox.paypal.com in sandbox mode) — https://www.paypal.com/us/legalhub/useragreement-full — https://www.paypal.com/us/legalhub/paypal/privacy-full
* Square (API hosts: connect.squareup.com, and connect.squareupsandbox.com in sandbox mode) — https://squareup.com/us/en/legal/general/ua — https://squareup.com/us/en/legal/general/privacy
* Authorize.Net (API hosts: api.authorize.net, and apitest.authorize.net in test mode) — https://www.authorize.net/about-us/terms.html — https://www.visa.com/en-us/legal/global-privacy-notice
* 2Checkout (Verifone) (API hosts: api.2checkout.com, and api.avangate.com in sandbox mode) — https://www.2checkout.com/legal/terms/ — https://www.2checkout.com/legal/privacy/
* Klarna (API host depends on the region of your Klarna account: api.klarna.com, api-na.klarna.com or api-oc.klarna.com, and api.playground.klarna.com, api-na.playground.klarna.com or api-oc.playground.klarna.com in sandbox mode) — https://www.klarna.com/international/terms-and-conditions/ — https://www.klarna.com/international/privacy-policy/
* Moyasar (API host: api.moyasar.com) — https://moyasar.com/en/resources/terms/ — https://moyasar.com/en/resources/privacy-policy/
* Tamara (API hosts: api.tamara.co, and api-sandbox.tamara.co in sandbox mode) — https://tamara.co/en-sa/terms-and-conditions — https://tamara.co/en-sa/privacy-policy
* Tabby (API host: api.tabby.ai) — https://tabby.ai/en-AE/legal — https://tabby.ai/en-AE/legal/privacy-policy/latest
* Payoneer Checkout, the Oscato platform (hosted payment page; API hosts: api.live.oscato.com, and api.sandbox.oscato.com in sandbox mode) — https://www.payoneer.com/legal/ — https://www.payoneer.com/legal/privacy-policy/

Some gateways complete the payment on a page the provider hosts rather than on your site: PayPal, Klarna, Tamara, Tabby and Payoneer send the customer's browser to that provider's checkout page to approve the payment, and 2Checkout may send it to the card issuer's 3-D Secure page; the customer is returned to your store afterwards. Those pages are the provider's own, at addresses the provider supplies in its API response.

Several of these gateways collect card details in a field the provider hosts, keeping card numbers off your server. That field is drawn by the provider's own JavaScript, so enabling one loads a script from js.stripe.com (Stripe), web.squareup.com or sandbox.web.squareup.com (Square), js.authorize.net or jstest.authorize.net (Authorize.Net), 2pay-js.2checkout.com (2Checkout), or cdn.moyasar.com (Moyasar, which also supplies a stylesheet). Loading these tells the provider the visitor's IP address and user agent on any page carrying the checkout, before the visitor types anything; Stripe's and Moyasar's also load in the customer account area when a shopper retries payment on an unpaid order. They must come from the provider's own origin.

**Shipping carriers.** When you enable a carrier and request a rate or create a shipment, the recipient address, parcel weight and dimensions and your sender details go to that carrier to generate rates, labels and tracking:

* Aramex (API hosts: ws.aramex.net, and ws.dev.aramex.net in test mode) — https://www.aramex.com/us/en/terms-of-use — https://www.aramex.com/us/en/legal-details/privacy-policy
* SMSA Express (API hosts: track.smsaexpress.com, and stg-track.smsaexpress.com in test mode) — https://www.smsaexpress.com/terms-and-conditions — https://www.smsaexpress.com/privacy-policy
* Naqel Express (API host: infotrack.naqelexpress.com in test mode; in live mode the endpoint URL is the merchant-specific one you enter in the carrier settings) — https://www.naqelexpress.com/en/About/TermsCondition — https://www.naqelexpress.com/en/privacypolicy/cookies-policy/
* USPS (API hosts: api.usps.com, and api-cat.usps.com in test mode) — https://about.usps.com/who/legal/terms-of-use.htm — https://about.usps.com/who/legal/privacy-policy/full-privacy-policy.htm
* EasyPost (multi-carrier rating and label generation; API host: api.easypost.com) — https://legal.easypost.com/ — https://legal.easypost.com/#privacy-policy
* Shippo (multi-carrier rating and label generation; API host: api.goshippo.com) — https://privacy.goshippo.com/policies?name=terms-of-use — https://privacy.goshippo.com/policies?name=privacy-notice

When a carrier returns a label as a URL rather than file data, the plugin can download that PDF once so it can be reprinted. The fetch is off unless you enable it, and the address is the carrier's own domain or file-delivery CDN, so it cannot be listed in advance. Nothing is sent beyond the URL the carrier supplied; cleartext http:// addresses and any address that does not resolve to a public host are refused.

**Spam protection.** If you enable a CAPTCHA provider, the visitor's challenge token and IP address — plus the secret key you entered — go to that provider when a protected form is submitted. Verification hosts: www.google.com (reCAPTCHA), api.hcaptcha.com (hCaptcha), challenges.cloudflare.com (Turnstile). The widget script loads separately in the visitor's browser from www.google.com, js.hcaptcha.com or challenges.cloudflare.com on any page carrying a protected form:

* Google reCAPTCHA — https://policies.google.com/terms — https://policies.google.com/privacy
* Cloudflare Turnstile — https://www.cloudflare.com/website-terms/ — https://www.cloudflare.com/privacypolicy/
* hCaptcha — https://www.hcaptcha.com/terms — https://www.hcaptcha.com/privacy

**Currency exchange rates.** When you change your store's base currency or enable an additional one, the plugin fetches reference rates from Frankfurter, which sources European Central Bank data. Only currency codes are sent. The API host is api.frankfurter.dev, and the plugin does not follow redirects on that request, so it cannot be carried to a host not named here. Frankfurter publishes no separate privacy policy; its terms are its licence and its data-handling statement is on its home page. Service and privacy statement: https://frankfurter.dev/ — Licence/terms: https://github.com/lineofflight/frankfurter/blob/main/LICENSE

**Analytics and advertising.** If you enter a Google Analytics 4 / Google Tag Manager measurement ID or a Facebook (Meta) Pixel ID in the settings, the storefront can load that provider's script — Google's from www.googletagmanager.com, Meta's from connect.facebook.net — and send visitor and e-commerce events (page views, product views, add-to-cart, checkout, purchases). Both are off until you enter an ID, and an ID alone does not start them: the storefront holds both scripts behind a consent banner until the visitor grants the matching category, with Google Consent Mode v2 default-deny signals set first. No request reaches either host before the grant. The gate covers these two scripts only; every other embed listed here loads under its own entry.

* Google Analytics / Google Tag Manager — https://policies.google.com/terms — https://policies.google.com/privacy
* Facebook (Meta) Pixel — https://www.facebook.com/terms/ — https://www.facebook.com/privacy/policy/

**Maps and address lookup.** If you enable the map address picker, the storefront loads map tiles from OpenStreetMap (tile.openstreetmap.org) and uses OpenStreetMap's Nominatim service (nominatim.openstreetmap.org) to geocode the address a customer types and, when the customer drops the pin instead, to turn the map coordinates they chose back into an address; the customer's language preference is sent with the lookup so the result comes back in it. The picker appears at checkout, in the customer account address book, and in the admin for shipping zones and your store location. Neither host is contacted until it is opened.

* OpenStreetMap (map tiles) — https://operations.osmfoundation.org/policies/tiles/ — https://osmfoundation.org/wiki/Privacy_Policy
* Nominatim (geocoding) — https://operations.osmfoundation.org/policies/nominatim/ — https://osmfoundation.org/wiki/Privacy_Policy

**Map embeds (Google Maps / OpenStreetMap / Bing Maps / Mapbox / Yandex Maps).** If you paste a map embed URL into your contact page, your About page or a homepage section, the storefront frames that provider's map on that public page. Only https addresses on these hosts are accepted: google.com, www.google.com, maps.google.com, openstreetmap.org, www.openstreetmap.org, bing.com, www.bing.com, api.mapbox.com, yandex.com and yandex.ru. Any other host is discarded on save, so the storefront cannot be made to frame an arbitrary site; the `vendm_map_embed_hosts` filter adds a regional provider. The plugin sends no customer data, but a visitor loading the page tells that provider their IP address and user agent, as any embedded frame does. https://policies.google.com/terms — https://policies.google.com/privacy — https://osmfoundation.org/wiki/Privacy_Policy — https://www.microsoft.com/en-us/servicesagreement — https://www.microsoft.com/en-us/privacy/privacystatement — https://www.mapbox.com/legal/tos — https://www.mapbox.com/legal/privacy — https://yandex.com/legal/rules/index.html — https://yandex.com/legal/confidential/en/

**Video embeds (YouTube / Vimeo).** If you add a YouTube or Vimeo video URL to a product, blog post or storefront section, the storefront embeds that provider's player on that public page. YouTube players are framed from www.youtube-nocookie.com — YouTube's privacy-enhanced host, so the view is not used to personalise the visitor's YouTube experience or the advertising they see elsewhere. Vimeo players are framed from player.vimeo.com. No thumbnail or other file is loaded from either provider: where a section shows a still image with a play button, that image is one you uploaded. This happens only for videos you add, and the plugin sends no customer data. https://www.youtube.com/t/terms — https://policies.google.com/privacy — https://vimeo.com/legal — https://vimeo.com/legal/privacy/policy

**Outgoing webhooks.** If you create a webhook, the plugin sends the event data you configure to the destination URL you specify. That destination is entirely under your control.

**Search engine indexing (IndexNow).** If you turn on IndexNow in the SEO settings, the plugin notifies that service when your store URLs change so participating search engines (such as Microsoft Bing) can re-crawl them. Only public URLs from your own site are sent. It is off by default and needs a key you generate in the settings. The API host is api.indexnow.org. IndexNow publishes no separate privacy policy; its terms document contains its privacy statement. Service: https://www.indexnow.org/ — Terms and privacy statement: https://www.indexnow.org/terms

**Outgoing email (SMTP).** If you configure an external SMTP server for store email, the plugin connects to the host you name and relays order confirmations, shipping notices and password resets through it, including the recipient's address and the message body. The host, the credentials and therefore the recipient of that data are your choice. Leave SMTP off and WordPress's own mail handling is used instead, with no external connection.

**Incoming email (IMAP).** If you connect a mailbox to the Contact inbox (Settings → Contact), the plugin signs in to the IMAP server you name, with the username and password you enter, on a scheduled task every few minutes, and copies new replies into the inbox so you can answer them from the store admin. The server, the credentials and the mailbox are your own; nothing is sent to us. Leave the mailbox unconfigured and no connection is made.

**Email open and click tracking.** Off by default. If you switch it on under Settings → Email, store emails carry a one-pixel image and links that redirect through your own site, so the email log can show opens and clicks. The requests go only to your own site; no third party is involved.

**Push notifications (Web Push).** Only when a person turns notifications on in an installed app — a staff member in Settings › Apps, or a shopper with "Turn on" under their order confirmation — their browser gives VendMizer a subscription address at its own push service, and VendMizer later sends each notification there. The message (an order number and status, or a staff alert's title and text) is end-to-end encrypted for that one device (RFC 8291), so the push service sees only ciphertext, the subscription address, a timestamp and the site's public key; the request is signed with a key generated for your site (VAPID, RFC 8292), whose contact field is your site address, or the site admin email when the site is not on HTTPS. Which service is used depends on the device's browser, not on VendMizer: Apple (web.push.apple.com — https://www.apple.com/legal/internet-services/terms/site.html — https://www.apple.com/legal/privacy/), Google Firebase Cloud Messaging (fcm.googleapis.com — https://firebase.google.com/terms — https://policies.google.com/privacy), Mozilla (updates.push.services.mozilla.com — https://www.mozilla.org/about/legal/terms/services/ — https://www.mozilla.org/privacy/websites/) or Microsoft (*.notify.windows.com — https://www.microsoft.com/servicesagreement — https://privacy.microsoft.com/privacystatement). Turning notifications off on the device, or switching them off in Settings › Apps, stops all sending.

**Avatars (Gravatar).** The staff list, staff detail and your own profile screen in the VendMizer admin show each staff member's photo from Gravatar, operated by Automattic, because that is what WordPress itself uses. The request sends a one-way hash of the staff member's email address plus the viewing browser's IP address and user agent. The address is built by WordPress's own `get_avatar_url()`, so the host is whichever your WordPress version uses — secure.gravatar.com on current releases. No customer, order or store data is involved, and it happens only on those admin screens, never on your storefront. Turning off Settings → Discussion → "Show Avatars" stops it entirely; the plugin then draws coloured initials locally.

* Gravatar (Automattic) — https://wordpress.com/tos/ — https://automattic.com/privacy/

== Installation ==

1. Upload the `vendmizer` folder to the `/wp-content/plugins/` directory, or install the plugin through the WordPress Plugins screen.
2. Activate the plugin through the Plugins screen in WordPress.
3. Open VendMizer from the admin menu and follow the setup wizard, which walks you through your store name and timezone, your country, currency and units, then payments, shipping and which features to switch on.
4. Optionally configure payment gateways, shipping carriers, and other integrations under Settings. Each integration is off until you enable it.

Requirements: WordPress 6.0 or later, PHP 7.4 or later, MySQL 5.7+ or MariaDB 10.3+, and pretty permalinks (any setting except "Plain" under Settings → Permalinks). The storefront, customer account and store admin live at their own addresses such as /shop and /shop-admin, which WordPress can only route with pretty permalinks; if Plain is selected, the plugin shows a notice with a link to change it and nothing else is affected. Single sites only: network activation on multisite is refused.

== Frequently Asked Questions ==

= Is any feature here locked, limited, or switched off until I pay? =

No. There is no licence key, no activation, no registration and no trial clock. Nothing checks a date or an entitlement before letting you use a feature, and no part of the plugin stops working after any period. The plugin contacts no VendMizer server: the only vendmizer.com address in the code is the Plugin URI line in the plugin header, and nothing fetches it. All the modules ship switched on, and Settings → Modules lets you turn any of them off and back on whenever you like.

A separate commercial extension exists and adds modules of its own. Nothing in this plugin is disabled, degraded or hidden by its absence, and this plugin never advertises it to you in the admin.

= Does VendMizer require another e-commerce plugin? =

No. VendMizer is fully standalone and runs on its own database tables and REST API.

= Does it change my WordPress login page? =

Yes. VendMizer replaces wp-login.php with its own login screen so that staff and customers sign in through the storefront rather than through WordPress. Anyone who visits wp-login.php is sent to the VendMizer login page instead, and password reset, registration and logout follow the same route.

If you would rather keep the standard WordPress login, open the store admin, go to Settings → Access & Policies and switch off "Use the branded storefront login". That steps VendMizer out of the way completely: wp-login.php works as it always did, and every login, logout, password-reset and registration link WordPress generates points back at it rather than at the storefront. If you are ever locked out — a broken theme, a caching problem, anything — visiting wp-login.php?vendm_native_login=1 always renders the stock WordPress form. Developers who manage settings in code can do the same with the `VENDM_DISABLE_LOGIN_TAKEOVER` constant or the `vendm_login_takeover_enabled` filter.

= Can staff use two-step sign-in? =

Yes, built in, with no extra plugin. Anyone with a store account opens Profile → Security, chooses "Set up two-step sign-in", scans the QR code with an authenticator app (Google Authenticator, 1Password, Authy, Microsoft Authenticator or any other that supports standard time-based codes) and types the six-digit code it shows. From then on, signing in asks for the password and then a fresh code. The secret is stored encrypted, each code works once, and the QR code is drawn in the browser — nothing is sent to any outside service.

Turning it on also shows ten single-use recovery codes. Keep them somewhere safe: each one signs you in once if your phone is lost, and you can make a new set from the same screen. While two-step sign-in is on, emailed sign-in links and Google or Facebook sign-in are refused for that account, because they would skip the second step. If someone loses both their phone and their recovery codes, a store administrator opens Staff, edits that person and chooses Reset beside "Two-step sign-in"; they can then sign in with their password alone and set it up again.

= Where do store staff land after signing in? =

Anyone you make store staff is sent from wp-admin to the VendMizer dashboard instead, because wp-admin has nothing in it for them. That covers the Shop Admin and Shop Manager roles VendMizer creates, and any existing WordPress user you give one of them to. Your WordPress administrators are never redirected, and neither are your store customers. The profile screen always stays reachable, so everyone can still change their own password, and editors, authors and subscribers who are not store staff carry on using wp-admin exactly as before. To turn the redirect off, use `add_filter( 'vendm_redirect_staff_from_wp_admin', '__return_false' );` — it receives the user's ID, so you can decide person by person.

= Which URLs does the storefront take over? =

The storefront is served from /shop/, the admin from /shop-admin/ and the customer account area from /shop-account/. All three are prefix rules that claim everything beneath them, so a page of your own at, say, /shop-account/anything is no longer reachable. The admin and account paths are fixed; the storefront path is held in the `vendm_store_slug` option, which has no settings screen of its own in this release, so changing it means changing the option directly. If you switch on "Use the site home page for the store" under Settings → Storefront, the storefront is served from your site root instead and your existing WordPress front page is no longer shown — that option is off unless you choose it.

Four more routes are claimed under /vendm-auth/ — /vendm-auth/google/start, /vendm-auth/google/callback, and the same pair for facebook. They are the redirect endpoints a sign-in provider is registered against. This plugin implements no provider, so all four are inert here: the handler checks whether anything is listening and returns immediately when nothing is, which is the case unless you install an extension that adds one. Product images are also served through short /m/ URLs, described under "What does the plugin write to my uploads folder?" below.

Your product sitemap is always available at /vendm-sitemap.xml, and the plugin additionally answers the shorter /sitemap.xml when no other plugin has claimed that route. If you run Yoast, Rank Math, All in One SEO or similar, they keep it and VendMizer quietly uses its own prefixed URL, which is the one it advertises in robots.txt. There is also a product feed for Google Merchant Center and Meta Commerce at a REST endpoint.

VendMizer creates its own database tables rather than storing products as posts. Uninstalling gives you the choice of keeping your data or removing it completely, and the default is to keep it: deleting the plugin leaves your store intact unless you have turned that setting off first. If you do choose removal, every table, option, user meta key, role and scheduled task the plugin created is deleted.

= Are storefront pages rendered on the server? =

Yes, always. The home page, product, category, shop, brand, tag, blog and custom pages are all delivered as complete HTML from the server, so search engines and social previewers read real content and shoppers see the page before any JavaScript has run; the storefront app then takes over the page in place for the interactive experience. There is no setting for this — it is how the storefront works — and the cart, checkout, account and search screens, which are personal to each visitor, are rendered by the app on purpose.

If you ever need to switch server rendering off while diagnosing a problem on a live site, add `define( 'VENDM_DISABLE_SSR', true );` to wp-config.php, or `add_filter( 'vendm_storefront_ssr_enabled', '__return_false' );` from a small plugin of your own; every page then loads through the app instead. It is an emergency switch, not a preference: leaving it on costs you the search and first-paint benefits. To leave a single home-page section type to the app while keeping everything else server-rendered, return its type key from the `vendm_ssr_skip_section_types` filter.

= What does the plugin write to my uploads folder? =

Three directories inside wp-content/uploads, and nothing written there is copied to us or to any third party.

Files you sell go into `uploads/vendmizer-private/`, inside a subdirectory whose name is twenty random characters generated once for your site and stored in your database, and each file is saved under a random UUID name rather than the name it was uploaded with. At activation the plugin puts three guard files in that directory: an `.htaccess` that denies every request to it and switches off PHP execution and CGI handlers, a `web.config` that denies every request on IIS, and an empty `index.php` so the directory cannot be listed. Customers never touch any of that — a purchased file is delivered by PHP through a short-lived signed link that is checked against the order before a byte is sent. Read the next sentence carefully, because it is the part that depends on your host: `.htaccess` is an Apache mechanism and `web.config` an IIS one, so on nginx, Caddy or LiteSpeed in its non-Apache mode neither file is read at all, and the random directory name is then the only thing between the internet and a paid file. That name is unguessable rather than secret, and it is not an access check. If you run nginx and sell downloads, add a rule denying `/wp-content/uploads/vendmizer-private/` to your server config; it takes one block and it is the only way to get on nginx what `.htaccess` gives you on Apache.

Product images, category images and anything else you add through the media library go into `uploads/vendmizer/`, and those are public on purpose — that is how a shop shows a photo. The storefront serves them through a short /m/ URL rather than by their path on disk, but that route is not an access check of any kind: it hands the image to whoever asks for it, and the file underneath stays readable by your web server as well. So this directory gets a smaller guard than the private one — directory listing is switched off and PHP and other executable file types are refused — and that is all it needs, because the contents are meant to be seen. The installable-app icons and launch screens are generated from your logo into `uploads/vendmizer/pwa/` under the same guard, with an empty `index.php`; they are rebuilt when you change the logo or colours, and old sets are removed once a day.

Shipping labels are the third and the one to think about. When a carrier hands back a label as file data rather than as a link — which is what most of them do — the PDF is written to `uploads/vendmizer-labels/` so it can be reprinted and shared without asking the carrier again. That happens automatically, with no setting to enable, because a label that only exists inside an API response is a label you lose. A label carries the customer's name and delivery address, so treat that directory as sensitive. Three things bound it. The directory carries its own guard files — an `.htaccess`, a `web.config`, and both an `index.php` and an `index.html` — which switch directory listing off and refuse to execute anything stored there, while still allowing a plain request for a known filename, because opening a label is exactly such a request; any of them that has gone missing is written again the next time a label is cached, so a migration or a security plugin that strips them does not leave the directory bare for long. Each filename carries a sixteen-character random suffix, which is what stops one label URL leading to another. And cached labels are deleted ninety days after they are written, by the plugin's daily maintenance job, so the copy on disk has a bounded life instead of accumulating forever; that window is changeable through the `vendm_shipping_label_cache_settings` filter, including setting it to zero to keep labels indefinitely. Two honest caveats. `.htaccess` is Apache and `web.config` is IIS, so on nginx, Caddy or LiteSpeed in its non-Apache mode neither is read, the random filename is then the whole of the protection, and a link you have already sent a customer stays valid until the file is purged. And the ninety-day cleanup is registered together with the rest of the shipping features, so if you switch the Shipping module off under Settings → Modules, labels already on disk stop being purged and stay there until you delete them yourself.

One more thing goes to disk, and only if you ask for it: if you run a database backup from the plugin's own tools, the archive is written to `uploads/vendmizer-private/backups/`. That is inside the deny-all private directory described above, with the same guard files and the same nginx caveat, and the archive contains your store's database — orders, customers, addresses — so it is the most sensitive file the plugin ever writes. If you also tick "Product images and downloadable files", copies of `uploads/vendmizer` and `uploads/vendmizer-private` (never the backups folder itself) are written next to the backup as numbered companion archives, built in the background and kept and deleted with it. Backups are created only when you run one, never on a schedule, and you delete them from the same screen. Otherwise nothing goes to disk. CSV exports are built in memory and streamed straight to your browser, PDF invoices are generated when they are asked for and never stored, and the plugin writes no log files of its own. It does not keep an activity-log table either: notable events are announced on a WordPress action, `vendm_activity`, which you can attach your own listener to, and the records the plugin does keep — email sends, stock movements, webhook deliveries, shipment events, download deliveries — are ordinary rows in its own tables. Since 1.73.0 one small diagnostic table joins them: an event log of failures nobody was watching — a payment notification that was rejected, an outgoing webhook that gave up, a background task that crashed — shown under Tools → Event log, holding no card data or secrets, and pruned daily to 30 days and 10,000 entries. Debug output goes to WordPress's own error log, and only when you have WP_DEBUG on. Uninstalling keeps your data by default, files included. If you switch "Keep data on uninstall" off, deleting the plugin removes its tables, options, roles and scheduled tasks and also these three directories — `uploads/vendmizer`, `uploads/vendmizer-private` and `uploads/vendmizer-labels` — so product images, download files, backups and cached labels go with it. The Settings screen says so next to the switch. Nothing else under uploads is touched.

= Does the checkout keep an email address before the order is placed? =

Yes, and it is worth knowing. When a guest starts filling in the checkout form, the storefront saves the email address onto that shopper's own cart row a few seconds after they stop typing, and once more if they leave the page — before they have submitted anything. It is kept so that a returning shopper is recognised and so that an add-on which sends basket reminders has an address to send to. This plugin does not email it and does not list it on any admin screen; it is returned in a WordPress personal-data export, but only to whoever asks for their own data using that address. The request that carries it is nonce-protected and rate-limited, it can only write to the cart the caller already holds, and the address is deleted along with the cart, which expires thirty days after the last activity on it. No third party ever receives it.

= Can a customer get a copy of their data, or have it deleted? =

Yes. VendMizer registers with WordPress's own privacy tools, so Tools → Export Personal Data and Tools → Erase Personal Data cover the store's tables as well: orders and their shipments, the customer record, reviews, the wishlist, the live and abandoned cart, contact messages, download entitlements and their delivery log, and the notification and email history. The export explains, field by field, what was held back and why — download tokens are credentials rather than information about a person, and the download log stores a one-way hash of each IP address rather than the address itself. The plugin also contributes a section to your site's privacy policy draft, and a customer can start an erasure from a confirmation link sent to their own address.

= Does the plugin send my data anywhere? =

Not during normal use. External services are only contacted when you enable and configure the matching feature. The one exception is Gravatar, which supplies staff avatars in the admin and follows your existing WordPress avatar setting. See "External services" for the complete list and what each one sends.

= Does it have a cookie consent banner? =

Yes, and there is nothing to switch on. The moment you enter a Google Analytics or Meta (Facebook) Pixel ID, the storefront starts showing a granular consent banner and holds both scripts back until the visitor agrees. Every visitor is asked, wherever they are, and neither script loads for anyone who has not agreed — there is no geographic exemption and no way to grant a category on someone's behalf. Under Settings → Cookie Consent you can change the banner's wording, its position, its colour theme, how many months a choice is remembered, the privacy-policy link it points at, and whether a "Cookie preferences" link appears in your footer so visitors can reopen it; bumping the policy version there asks everyone again. If you set no tracking IDs, no banner appears, because the only cookies left are the strictly necessary ones that keep your basket and language working; the rest of what the store remembers on a visitor's device — a local copy of the basket, display preferences such as theme and currency, recently viewed products, search history, dismissed announcements, a returning-visitor flag, a compare list and half-filled checkout fields — is browser storage rather than cookies, is never read by anything outside your own site, and reaches your server only when the store has to act on it, as when a lost session is rebuilt from the local copy of the basket. Consent itself is stored in a single first-party cookie on the visitor's device; the plugin performs no IP lookup and keeps no server-side consent log.

= Can I put the store behind a maintenance or coming-soon page? =

Yes, under Settings → Maintenance. Pick maintenance mode or coming-soon mode, write your own title, subtitle and body in each of your languages, and optionally show a launch countdown. The two differ in what they tell a search engine, deliberately: maintenance mode answers with HTTP 503 and a Retry-After header whose length you set, so the outage reads as temporary rather than as a dead site, while coming-soon mode answers with an ordinary 200, because a launch page is real content rather than an outage. Either way you get a bypass token, and visiting your store once with `?vendm_preview=<token>` sets a twelve-hour cookie that lets you — or anyone you send the link to — browse the real store while everyone else sees the notice.

One part of it collects personal data, so it is worth stating plainly. If you switch on the optional email signup, the screen shows visitors a single email field, and an address entered there is saved to your customer list — the same list and the same table a shopper who signs up in the storefront lands in. It posts to the ordinary storefront newsletter endpoint, so it is rate-limited and validated like any other signup, it is covered by the export and erase tools described above, and nothing is sent to any third party. The field is off unless you turn it on, and there is no signup at all in maintenance mode with it off.

= Why is there a PHP file in the assets folder, and why don't the plugin's pages call wp_head()? =

Because the storefront, the admin and the customer account area are standalone documents rather than pages inside your theme. They build their own `<head>`, so `wp_head()` and `wp_footer()` are not called on them — if they were, every plugin and theme on your site would inject markup into a document it knows nothing about.

That does not mean the assets bypass WordPress. Every stylesheet and script is registered with `wp_register_style()` and `wp_register_script()` and printed by core's own `wp_print_styles()` and `wp_print_scripts()`, each called with an explicit handle, so core writes the tags and core's dependency, versioning and defer handling all apply. Nothing another plugin has enqueued is printed into these documents, because naming a handle prints only that handle.

`assets/load.php` is the concatenator. It is not reachable on its own: it carries the standard `ABSPATH` guard, it is loaded by the plugin after WordPress has booted rather than requested directly, it will only assemble bundles named in a fixed list inside the file, every path is checked with `realpath()` to stay inside the plugin directory, and the admin and account bundles additionally require a valid signature. What it returns is a concatenation of this plugin's own files and nothing else, served with a long `Cache-Control` because the URL carries a content fingerprint that changes whenever the files do.

WordPress itself works this way where it has the same problem. `wp-login.php` and `wp-admin/install.php` are core's own standalone documents: neither calls `wp_head()`, both assemble their own head, and `install.php` prints its scripts with `wp_print_scripts()` given an explicit list of handles — the same call this plugin makes for the same reason.

= Does it support languages other than English? =

Yes. English is the default language and Arabic is included out of the box (with full right-to-left layout). You can also add and edit additional languages and their translations from the admin.

The messages the plugin itself sends back — form errors, confirmations, payment and shipping notices — are standard WordPress translations in the `vendmizer` text domain. Arabic ships in `languages/`, `languages/vendmizer.pot` lists every string for anyone translating into another language, and a language pack from translate.wordpress.org takes precedence over the bundled file once one exists. Each request follows the language the shopper or staff member picked in the store, not only the site language.

= Why do some web addresses appear in VendMizer's source code that it never contacts? =

Some of what VendMizer draws is an address on someone else's domain rather than a request to it. A package-tracking number becomes a link to the carrier's own tracking page (UPS, USPS, FedEx, DHL, Aramex, SMSA, OnTrac, or AfterShip as a fallback). A product page can offer share links for WhatsApp (wa.me) and X (x.com), and every blog post carries share links for X (twitter.com), Facebook (www.facebook.com) and LinkedIn (www.linkedin.com). Fill in a WhatsApp number and a floating contact button links to wa.me too, and your footer carries whatever social profile addresses you enter. In the admin, the email settings link to Google's app-password page and the shipping settings to EasyPost's, Shippo's and USPS's developer sites (developer.usps.com); a Naqel shipment links to Naqel's own tracking page; and the map picker carries the attribution links OpenStreetMap's licence requires (www.openstreetmap.org/copyright, leafletjs.com). Every one is an ordinary link: nothing is fetched, no script is loaded, and no request reaches those hosts unless someone clicks through.

A few of the web addresses that appear in VendMizer's source are identifiers rather than places, and the plugin never fetches anything from them. The SOAP requests it builds for Aramex and Naqel Express carry the XML namespace declarations those carriers' own services require (`schemas.xmlsoap.org`, `www.w3.org`, `schemas.microsoft.com`, `tempuri.org`); the XML sitemap and the Google product feed declare their formats the same way (`www.sitemaps.org`, `base.google.com`, and `www.google.com/schemas/sitemap-image` for the image entries); the structured data on product and store pages names its vocabulary (`schema.org`); every inline SVG icon names the SVG namespace (`www.w3.org`); and the plugin header points at the licence text (`www.gnu.org`). An XML namespace is a globally unique name that is merely spelled like a URL — the format requires the exact string, and no connection is ever opened to it. The requests those envelopes are actually sent to are the Aramex and Naqel hosts listed under "Shipping carriers" above, and nowhere else.

= My site is behind Cloudflare, a load balancer or a reverse proxy. Which visitor address does the store use? =

The address the connection came from, unless that address is a proxy you trust. Private and local addresses (a proxy on the same server or network) are trusted automatically, and Cloudflare's own `CF-Connecting-IP` header is used when the request came through such a proxy. For any other proxy, list its addresses or ranges in `wp-config.php`, for example `define( 'VENDM_TRUSTED_PROXIES', '203.0.113.10, 198.51.100.0/24' );`, or with the `vendm_trusted_proxies` filter. Forwarded headers from anyone else are ignored, so a visitor cannot pick an address to get around the checkout's per-address order limit or the sign-in throttling. That order limit is under Settings → Access & Policies ("Orders per hour from one address", 30 by default); signed-in customers who have paid for an order before are not counted against it.

= Does it work on WordPress Multisite? =

Not network-wide. A VendMizer store keeps its own tables, pages and roles per site, so network activation is refused. Activate it on each site that runs a store instead.

= Which third-party libraries, icons and fonts are bundled, and under what licences? =

VendMizer bundles the open-source libraries and fonts below, and reproduces icon path data from two icon projects. Each is redistributed under its own licence, which ships beside the files it covers. `assets/vendor/README.md` records the version, origin and a SHA-256 for every bundled file — the four libraries and all thirteen fonts alike — so you can fetch the same release and confirm nothing was edited on the way in. Path data is not a file and has no checksum; its licence names the source files instead.

**Chart.js 4.5.1** — MIT. Draws the charts on the admin dashboard and report screens. The plugin ships the project's official published UMD build, `assets/vendor/chartjs/chart.umd.min.js`; its complete, unobfuscated source is public at https://github.com/chartjs/Chart.js/tree/v4.5.1 . Licence: `assets/vendor/chartjs/LICENSE.md`

**Leaflet 1.9.4** — BSD 2-Clause. Powers the optional map address picker. The full unminified source ships as `assets/vendor/leaflet/leaflet-src.js`. Licence: `assets/vendor/leaflet/LICENSE.txt`

**SheetJS (js-xlsx) 0.20.3** — Apache License 2.0. Used only in the admin, to read spreadsheet files during product import; nothing is written or exported through it. The file the plugin loads is upstream's own prebuilt bundle, and both of its readable sources ship alongside it as `assets/vendor/sheetjs/xlsx.js` and `assets/vendor/sheetjs/cpexcel.js`. SheetJS left npm after 0.18.5 and publishes at https://cdn.sheetjs.com now. Licence: `assets/vendor/sheetjs/LICENSE`

**qrcode-generator 1.4.4** — MIT, by Kazuhiko Arase. Draws the QR code shown when someone sets up two-step sign-in, in the browser, so the secret never leaves the page. Shipped unminified as `assets/vendor/qrcode-generator/qrcode.js`; the licence is the notice in that file's header, as upstream ships it.

Apache 2.0 is compatible with GPL version 3 but not version 2. VendMizer is "GPLv2 or later", so any distribution including SheetJS is taken under the GPLv3-or-later branch of that grant.

**Lucide icons** — ISC, and **Feather** — MIT. The interface icons are inline SVG path data from Lucide, which is a fork of Feather, and a few are Feather's original drawing; no script or stylesheet from either is bundled. Both licences, and the four files the data sits in: `assets/js/lib/LICENSE-lucide.txt`

**Brand marks.** VendMizer draws a small identifying mark beside each payment gateway in the settings, beside the Google Analytics and Meta Pixel fields, and on the WhatsApp contact button. Each is its owner's trademark, used descriptively; no owner is affiliated with VendMizer. Most are VendMizer's own artwork, and the WhatsApp handset glyph is Simple Icons' (CC0-1.0). Detail per mark: `assets/js/lib/LICENSE-brand-marks.txt`

**Fonts** — SIL Open Font License 1.1. DM Sans 4.004, Outfit 1.100 and Noto Kufi Arabic 2.109 ship as eleven .woff2 files in `assets/fonts/`, and the Saudi Riyal symbol font by Emran Alhaddad (version 2) as two more, so the new SAR currency sign displays everywhere, each family with its own `OFL-*.txt` licence there. No font is loaded from a third-party CDN, and every stylesheet and script VendMizer ships is served from your own site; the only externally hosted assets are the ones described under "External services".

**VendMizer's own minified JavaScript.** Every `.min.js` file under `assets/js/` is generated from the readable `.js` source that ships in the same directory — the human-readable source of every minified file is therefore included in the plugin itself. They are produced with terser by the included build script, `bin/build-min.mjs`: run `npm install` and then `node bin/build-min.mjs` from the plugin root to regenerate them, or `node bin/build-min.mjs --check` to confirm every shipped file matches its source. `package.json` pins the terser version, and the asset loader falls back to the readable sources automatically when a `.min.js` file is absent, or when `&min=0` is appended to an asset URL.

= Console pages fail to load behind Cloudflare (or another CDN/firewall)? =

The admin and account consoles are single-page apps whose page modules load in the background from your own site. If a CDN or firewall in front of your site — for example Cloudflare with Bot Fight Mode, a Managed Challenge, "Under Attack" mode, or a rate rule — answers one of those background requests with a "checking your browser" challenge, the browser cannot complete that check for a background request, so the page shows "Failed to load page module." (This is most likely right after a plugin update, when every asset address is new and none is cached yet.) VendMizer now recovers automatically by reloading the console once, which lets you pass the check and the page then loads. To stop it happening at all, add a rule in your CDN that skips the bot/security challenge for requests whose query string contains `vendm_asset=1` — those are the console's own script and style bundles. On Cloudflare this is a WAF custom rule (or Configuration Rule) with the expression `http.request.uri.query contains "vendm_asset=1"` and the action Skip; it does not weaken security for the rest of your site.

== Changelog ==

= 1.121.0 =
Last round of the 2.0 performance audit.
* Changed: the first Dashboard load after an order is about twice as fast on a large store (120,000 orders: 30 days 2.5 s to 1.3 s, 90 days 2.7 s to 1.7 s). The best seller and the category figures are now worked out from one pass over the period's order lines instead of two, and the product-type figures read each product's type from a small lookup instead of the full product rows. All figures are unchanged. Servers that do not allow temporary tables use the previous queries.
* New: a Site Health check, "VendMizer scheduled jobs". It recommends running scheduled jobs (order emails, reminders, stock alerts, clean-up) from a server cron instead of on visitor page loads, and shows the exact lines to add. Once WP-Cron is turned off, it warns if VendMizer's jobs stop running.
* Fixed: on databases that do not validate the orders table's JSON data themselves (MariaDB before 10.4.3, or a column changed by hand), an order whose stored data was not valid JSON could not be saved when the database ran in strict mode. Two indexed order columns now read that data only when it is valid. The update rewrites them only on such databases, which copies the orders table once.

= 1.120.0 =
Database changes from the 2.0 performance audit.
* Changed: order lines get an indexed "part of a bundle" flag, and orders an indexed "placed in the app" flag, both kept up to date by the database itself. The Dashboard's best sellers and product-type figures, the app (PWA) order statistics and the orders list's channel filter read these instead of searching each row's stored data. On a store with 120,000 orders the first Dashboard load went from about 3.8 s to about 2.5 s and the app statistics from about 1.6 s to 0.06 s; all figures are unchanged.
* Changed: when VendMizer Pro 1.59.0 has added its unique branch stock key, setting a branch's stock is a single statement instead of a read followed by an insert or update.
* The update adds a generated column to order lines and rebuilds one of their indexes, and adds a generated column and an index to orders. On a very large store the first admin page load after the update can take a few seconds while this runs, once.

= 1.119.0 =
Checkout and cache-refresh fixes from the 2.0 performance audit.
* Changed: checkouts no longer wait for each other. Every order used to update a shared settings row while the order was being saved, so a second shopper's checkout waited for the first to finish. Those updates now happen once the order is saved.
* Changed: a sale no longer clears the whole store's page cache. Only the product's own pages are refreshed; store-wide pages are refreshed when a product sells out, comes back in stock or crosses its low-stock line, and that product's page is then also purged from page caches and CDNs. Listings sorted by best sellers follow new sales within five minutes.
* Changed: order confirmation emails are sent after the shopper's checkout page has its answer (on PHP-FPM and LiteSpeed servers), and the invoice PDF is built once per order instead of once per email. Low-stock alerts also go out after the answer.
* Changed: an unavailable payment method is refused before any stock is reserved, and a cart line reads the product's settings once instead of on every stock step.
* Changed: after an order, the Dashboard shows its last figures at once, labelled with their age ("Figures as of 2 minutes ago — refreshing in the background"), while one background job rebuilds them; figures older than ten minutes are rebuilt before they are shown.
* Changed: guest catalogue requests (product lists, search suggestions, filters) may be reused by the visitor's browser for a minute.
* Fixed: the checkout page sent the same abandoned-cart email address twice when two of its handlers fired together.

= 1.118.0 =
Admin report speed-ups from the 2.0 performance audit.
* Changed: the Dashboard is rebuilt once, not twice, when it and the Pro insight card load together: a real lock lets the second request wait for the first and read its result. On a store with 120,000 orders the first Dashboard load needed about 7 s of database work per request, twice.
* Changed: a new index on orders serves the dashboard, AI and report totals from the index alone (the payment-method split went from about 1 s to under 0.1 s on a large store), and windowed reports name the order statuses that count as sales instead of the ones that do not, so the database reads only the dates asked for.
* Changed: the transactions page total and summary, the email log statistics and the app (PWA) order statistics are cached for one to five minutes and refreshed by any order, payment or refund. The email log list no longer sends the stored email contents with every row, and its statistics use a dedicated index (an older, redundant one is removed).
* Changed: the Shipping page loads a tab's data the first time the tab is opened, not all four tabs at once.
* Changed: the notifications bell does not poll while the browser tab is hidden, and a page refresh keeps the field you were typing in focused, with the cursor where it was.
* Fixed: two settings that do not exist by default were looked up in the database on every request; they are now created once.

= 1.117.0 =
Large-store fixes from the 2.0 performance audit.
* Fixed: Tools → Export now exports every row. Products, customers, orders and coupons used to stop at 10,000 rows without saying so (on a store with 120,000 orders that was the newest 8%). Large files are built in batches and streamed, so a 19,456-product export uses about 11 MB of memory instead of 123 MB. Columns added by add-ons are still included.
* Fixed: the product feed (Google Merchant Center) lists the whole catalogue instead of stopping at 5,000 products. It is built in batches once an hour and served from a file in the uploads folder (about 30 ms), and removed whenever prices are hidden from guests.
* Changed: the orders export (Orders → Export) reads each batch of orders straight from the orders table before adding customer and branch details: 120,000 orders now export in about 4 seconds instead of 71.
* Fixed: the transactions export pages by date and transaction number. Rows that share the same second could be skipped or written twice between batches.
* Fixed: the storefront page cache no longer grows without limit. Ad-click and analytics tags (fbclid, gclid, utm_…) no longer create a separate cached copy of a page; addresses with other unknown parameters are shown fresh and not cached; "not found" pages and redirects are not cached; a page keeps one cached copy instead of one per stock change; and the store's product API keeps one cached copy per product.
* Fixed: two visitors filling the same page's cache at once no longer overwrite each other's entries.
* Changed: stock history older than two years is removed by the daily maintenance (change it with the vendm_stock_log_retention_days filter; 0 keeps it forever). Unread notifications older than a year are removed too.
* Fixed: expired carts and old email logs are cleared until none are left, instead of a fixed number per run that a busy store outgrew.
* Fixed: the 90-day clearing of order IP addresses checks every older order again. 1.116.0 started where its last run stopped, which missed orders created with an older date (imports, backdated orders).

= 1.116.0 =
Safety fixes from the 2.0 performance audit.
* Fixed: the dashboard, the sales report and the order counts now follow every change to an order: an admin status change (with or without an email to the customer), a payment marked paid by a payment provider or by hand, an order edited or created by staff, a bulk action, an order completing on its own, and unpaid stock being released. Before, only new orders and refunds refreshed them, so a cancellation or a payment could take up to five minutes to show. The refresh happens once per request, after the order is saved.
* Fixed: a low-stock alert email is sent after the order is saved, not while it is being saved. A slow mail server no longer holds up other shoppers' checkouts, and no alert is sent for an order that then fails.
* Fixed: an order email could be sent twice when the scheduled email queue ran during a slow send. The queue now leaves an email alone for ten minutes while the request that wrote it is still sending it, and still recovers it after that if the send never finished.
* Fixed: clearing order IP addresses and browser details after 90 days, clearing old download-log details, and removing old read notifications now keep going until they are done (in the background if needed), instead of one batch of 2,000 a day. Busy stores taking more than about 2,000 orders a day now meet the 90-day promise.
* Fixed: the daily clean-up of the page cache reads its rows in small batches. On a large store it could run out of memory, and it now runs after the privacy clean-up, so nothing it does can stop that.
* Fixed: a restore no longer writes the database's calculated columns (MySQL rejects that), and afterwards every cached count, dashboard figure and storefront page is rebuilt from the restored data.
* Fixed: cache-plugin and CDN purges use the exact page address the store serves (with the trailing slash), and also clear the /shop/ listing, so exact-address purges such as Cloudflare's now take effect.

= 1.115.0 =
Inventory redesign, in the same layout as Orders.
* Changed: the four cards (Tracked products, In stock, Low stock, Out of stock) filter the list when clicked, and say what they count. Tracked products shows what the stock on hand cost ("Worth $2,496,643 at cost") to people who may see product costs.
* Fixed: "In stock" counted untracked products too (downloads, gift cards), so it could be higher than the total. All four cards now count tracked products only.
* Changed: Stock levels and Stock history sit in the shared tab bar. The stock table shows each product's picture, SKU and bin, the quantity in colour with its alert level under it ("Alert at 6"), status and units sold. A click on a product opens Adjust; a product with variants unfolds them as indented rows, each with its own Adjust.
* Changed: Adjust stock shows what is on hand now, lets you Set to, Add or Remove, shows the result before you save ("Stock will be 20 (+8)"), and offers quick reasons (Recount, Received, Damaged, Returned, Lost or stolen).
* Changed: Stock history reads in plain words: when, the product (opens it), the change with before → after, why ("Online sale", "Unpaid order released", "Adjusted by hand"…) with the note, and who made it. The Source filter lists every kind of change your store's history holds, not just five.
* Changed: Export, Import and the location picker sit in the page header; the import preview counts rows ready and rows with a problem before you apply.

= 1.114.0 =
Categories, Attributes, Brands and Product tags redesign, in the same layout as Orders.
* Changed: Categories is one table. Each row shows the category's image, its name with how many subcategories it has and its description, how many products it holds, and its status. Subcategories sit indented under their parent and fold away with the arrow beside it, or all at once with Collapse all. Drag a row, or use its up and down arrows, to change the order, as before. Click anywhere on a row to edit it.
* Added: a "No products" card and filter on Categories finds categories that hold nothing yet. Search also matches the slug.
* Changed: Attributes shows each attribute's type, how many values it has, its values as chips (colour swatches and pictures included, with "+N more" past eight), and a new "Used by" column with the number of products that use it. Click a row to edit it.
* Changed: Brands and Product tags each get a search box and All / Active / Inactive chips with counts. Rows show the logo or tag, the slug and website, how many products it holds and how many of those shoppers can't see, and the status.
* Changed: the category, attribute, brand and tag editors use two columns: details on the left; visibility, image or logo and a short summary on the right. Fields that need it explain themselves in a line of help. Attribute values sit in compact rows, and the hint under "Shown as" changes with the choice.

= 1.113.0 =
Transactions and Credit notes redesign, in the same layout as Orders.
* Changed: Transactions shows every payment and refund as one table on every screen size: date and time, order with the customer, a type tag (Payment, Refund), how it was paid with the card's last four digits, the amount (refunds in red, failed payments crossed out), status with the reason a payment failed, and the transaction ID. Fee and net columns appear when your gateway reports fees.
* Changed: the charts sit in matching cards. "By payment method" lists each method with its share and number of transactions, and a click shows only those. A new line under it counts failed and pending payments, and opens them.
* Changed: a transaction opens on a cleaner sheet: the amount, its tags, why it failed (when it did), the order and customer, the method, a copy button for the ID, fees, and an Open order button.
* Fixed: payments recorded as "bank_transfer" showed that raw key and could not be filtered. They read "Bank transfer" and have their own filter.
* Changed: Credit notes shows totals for the period (credit notes, total credited, tax refunded, next number) and one table with the invoice number, customer, reason, where the money went, and tax. A credit note opens in place with its lines, the customer's email and when it was emailed, with Download PDF.
* Changed: both screens page within the table and keep the shared filter bar.

= 1.112.0 =
Wishlist redesign, in the same layout as Loyalty and Marketing.
* Changed: the tabs are the shared tab bar with icons. "All saves" always shows its count, not only after you open it.
* Changed: Most wanted ranks products with a bar for how many shoppers saved each one, the sale price with the regular price crossed out, units sold and when it was last saved. A row opens the product.
* New: a "Wanted but out of stock" card, and "Wanted, but can't be bought" on those products.
* Changed: All saves shows each product's photo, and the shopper and the product open their own pages. The search also finds shoppers by their account name and email.
* Fixed: a shopper who has an account but no customer record yet (has never ordered) was listed as "—". They are named from their account.
* Changed: removing a saved item names the product and the shopper, and says they are not told.

= 1.111.0 =
Coupons and Reviews redesign, in the same layout as Orders and Customers.
* Changed: each coupon says what it gives in words ("$5 off the order", "20% off", "Buy 2, get 1 free") and what limits it (minimum order, selected products, per customer, free shipping). The Buy X / Get Y description was English-only.
* Changed: coupons show uses against their limit with a bar, when they are valid ("Until Jan 11, 2027"), and a warning in their last week. A copy button copies the code.
* New: the coupon form shows a live "What customers get" summary, plainer field names, and uses left of the limit.
* Changed: reviews lead with the stars, title and the start of the text; product and customer follow, and "Verified buyer" replaces a bare tick.
* Fixed: a pending review can now be rejected, and a rejected one approved again, from both the list and the review page.
* Fixed: replies to reviews from guest buyers (no account) never emailed the customer; their own email address is now used.
* New: the review page opens the product or the customer, says whether the review is shown on the product page, and keeps the reply in one box ("Update reply") instead of showing it twice.
* Fixed: "73 reviews" under the Reviews title was English-only.
* Fixed: product and category pickers in the coupon form showed a box inside a box; each is now one field with the chosen items inside it.
* Fixed: the Generate button now sits flush against the coupon code field, and on phones shrinks to its icon.
* Fixed: in Buy X Get Y coupons, the "Maximum discount" field was not saved.
* New: the coupon form checks the code, amount (above 0, at most 100%), and dates before saving, and points at the field to fix. Save can't be pressed twice.
* Changed: the amount field shows % or the currency, restriction fields are named "Only these products", "Only these categories" and "Never these products", and short help lines explain each limit.
* Fixed: date pickers' calendar icons were hard to see in dark mode.
* Fixed: field spacing in the coupon form on phones, and fields with a unit (such as px) in right-to-left languages.

= 1.110.0 =
Orders redesign, in the same layout as Customers and Marketing.
* New: the customer's checkout note is shown on the order. It was saved but never displayed.
* New: the order shows where it came from (online store or in store) and the branch, the loyalty points it earned, and the customer's phone number. "View customer" opens their page.
* Changed: order lines show the amount before tax, so they add up to Subtotal; tax appears once, in the totals, which now sit under the items. SKU moves under the product name.
* Changed: one Addresses card with shipping and billing ("Same as shipping address" when they match) and full country names.
* Changed: the order timeline names payments in your language ("Payment received · Stripe" instead of "Charge · STRIPE").
* Changed: the header shows the status next to the order number; Refund is an outlined button instead of a solid red one.
* Changed: the Orders list uses the shared table: "1 item" instead of "1 items", totals right-aligned, date with the time underneath, and named row actions.
* Fixed: form spacing in dialogs on phones.

= 1.109.1 =
* Fixed: on a customer's page, clicking an order in the Orders list did not open it.

= 1.109.0 =
Customers redesign. The list, a customer's page and Customer groups share one clean layout with clearer labels, readable phone and email fields in right-to-left languages.
* New: "Email customer" sends a real message (subject and text) using your store's email design. It used to send a sample welcome email instead.
* New: "Add customer" on the Customers list.
* Changed: adding someone to a group is a search by name or email instead of typing a customer ID. Groups get colour swatches, a discount field with its unit, and clearer help text.
* Changed: a customer's page shows the full order history with paging (date, status, payment, items, total; each row opens the order). "View all" used to open every order in the store.
* New: on a customer's page, an Activity card (customer since, first and last order, average order, marketing consent, last email), billing and shipping addresses side by side, Edit for name, phone and both addresses, a Groups card to add or remove the customer, and a reason field for tax exemption.
* Changed: tables stay tables on phones and scroll sideways inside their card, like every other list in the admin.
* Accessibility: every switch, field and icon button has a name; the language toggle on translatable fields says how many languages are filled in.

= 1.108.0 =
Page builder: page templates, saved sections, version history and scheduled publishing; product page templates per category. Nothing to do after updating.

= 1.107.0 =
Page builder: section library with picture previews and ready-made design variations; new Counters, Filterable Gallery and Contact + Map sections. Nothing to do after updating.

= 1.106.0 =
Page builder: Image + Content section, undo/redo, copy and paste, drafts. Nothing to do after updating.

* New: Image + Content section for the homepage and every page. Put the image left, right, above, below or behind the text, and choose a different position for tablets and phones (phones stack side-by-side layouts with the image on top by default). Add separate tablet and phone images — each device downloads only its own. Tap the subject to set the focal point, and choose the image shape, fit, corners, darkening for text over the image, a small label, a checklist, two buttons and a soft background.
* New: undo and redo in the page builders (buttons in the top bar, or Ctrl/Cmd+Z and Ctrl/Cmd+Shift+Z).
* New: copy a section from its menu and paste it into any page from "Add section".
* New: drafts. Unsaved builder changes are saved as a draft every few seconds ("Draft saved 14:02"); if you close the tab or switch devices, the builder offers to restore them next time. Your store only changes when you press Save.
* Changed: on phones the builder's top bar keeps the page name readable and shows undo/redo; the admin bottom bar and the assistant button stay out of the builders.

= 1.105.0 =
Product page layout editor. Nothing changes on your store until you edit it.

* New: Design › Product page. Choose how the photos show (thumbnails below, thumbnails beside, or an image grid with every photo large), the column widths (balanced, larger photos or larger details), and what stays in view while scrolling (photos, details and Add to Cart, or nothing).
* New: show the description, specifications and reviews as tabs, an accordion or all open, in the details column or full width below the product.
* New: reorder the blocks of the details column (name, rating, price, short description, stock, options, add-ons, Add to Cart, delivery and trust notes, extras below the button, wishlist/share/compare, SKU/brand/tags, details) and hide the optional ones. Name, price, options, add-ons and Add to Cart are always shown. Choose whether related or recently viewed products come first.
* New: preview your changes on a product you pick, live, before saving; "Back to the default layout" restores today's page.

= 1.104.0 =
Product page refresh. Nothing to do after updating; the delivery estimate and trust notes stay hidden until you set them up.

* Changed: while a choice is still missing, the Add to Cart buttons no longer show a faded, disabled pill. They say what is missing ("Choose Storage", "Choose an amount", "Add the recipient's email") and, when tapped, scroll to that control, highlight it and put the focus there. Out of stock is the only state that disables the button.
* Changed: on phones the buy bar (photo, price, product name and button) takes the place of the bottom menu on product pages, so the screen has one bar instead of two.
* Changed: on phones the gallery is full width with position dots and swipe, and Description, Specifications and Reviews are an accordion (Description open first) instead of tabs.
* New: Settings › Catalog › Product page. A delivery estimate under Add to Cart ("Arrives Mon, Nov 16 – Wed, Nov 18", with "Order within 3 h 12 min to ship today" before your cut-off hour), counted in business days with your choice of weekend. Up to three trust notes with icons (for example free delivery, returns, secure checkout). Both are off and empty until you fill them in.
* Changed: description lists, tables and the specifications table are easier to scan: aligned labels, row lines, bullets in your accent colour.
* Changed: Wishlist, Share and Compare are one quiet row of text buttons. Product cards line up their Add buttons and prices; the category line is grey.
* Changed: an add-on block can ask to sit below the Add to Cart row (placement 'after'), where recommendations belong. VendMizer Pro 1.45.0 moves "Frequently bought together" there.
* Fixed: on iPhone the gift card's delivery-date field ran off the right edge of the screen.
* Fixed: swiping the product photos on a phone no longer scrolls the page to the thumbnail strip.

= 1.103.0 =
Eight product sections join the free page builder. Nothing to do after updating.

* New: the page builder (Homepage, About, Contact and custom pages) now includes Product Carousel, Best Sellers, Product Tabs, Recently Viewed, Product Spotlight, Collection Showcase, Shoppable Lookbook and Comparison Table, in a "Products" group. They were add-on sections before. Pages that already use them keep their settings and look the same.
* Changed: when an older add-on still lists a section that VendMizer now provides, the builder shows the VendMizer version once, without an add-on badge.

= 1.102.0 =
Design screen, images and phone dialogs. Nothing to do after updating.

* Fixed: choosing an image for the store logo, dark-mode logo or favicon on the Design screen did nothing. The image library returned images without the address the screen looked for. Every image picker now gets a full address.
* Fixed: image buttons in About, Contact and custom-page sections did nothing, because they relied on the WordPress media window, which the store admin does not load. The repeater image buttons (team photos, logos, gallery) were not connected at all. They now open the store's image library.
* New: upload images right from the image library: an Upload button, drag-and-drop and paste. A single new image is chosen as soon as it finishes uploading. Selected images show a check mark, a double-click chooses, and the Select button names the image and stays off until one is picked.
* New: on the Design screen, a logo or favicon box takes a file dropped onto it, shows the image on a checkerboard so white and transparent logos stay visible, and has Replace and Remove buttons. Section images in About, Contact and custom pages now show a thumbnail.
* Changed: on phones, dialogs and bottom sheets open at full height instead of sizing to their content. Confirmation prompts stay compact.
* Fixed: unsaved Brand changes (colours, card, header and type options) were lost when switching to another Design tab. Saving from another tab also cleared the "unsaved" warning without saving them. Save now writes every changed part (Brand plus header, menu, footer and mobile bar) in one go, from any tab.
* Fixed: saving Brand or applying a starter theme erased the stored media ids of the logo, dark logo and favicon.
* Fixed: several header, footer and Brand fields did not count as unsaved changes, so leaving the page gave no warning.
* New: an "Unsaved changes" bar with Discard and Save, and a row of section shortcuts that stays in view on the long Brand tab. The Design tabs stay pinned while scrolling and scroll sideways on phones.
* New: colour fields show the real colour, show "Default" when empty instead of a black swatch and "#18181B", and have a clear button. Accent, header and footer colour pairs show a contrast rating ("Easy to read (AA)", "Hard to read").
* New: menu and mobile-bar icons are picked from a grid of icons instead of a list of file names. Payment icons and social networks show their real names ("Apple Pay", "X (Twitter)"). Menu row actions are always visible on touch screens.
* New: Design backup. Export your whole design (colours, fonts, card and header options, header layout, menu, footer, mobile bar) to a file, and import it here or into another VendMizer store. An import is applied as unsaved changes so you can preview it first. Store name, logos and favicon are not included.
* Fixed: 25 icons used across the admin (including the Design tab and page title, header-layout cards, media, orders and contact inbox) were missing and showed a warning symbol.

= 1.101.0 =
Phone and tablet fixes. Nothing to do after updating.

* Fixed: tapping into a field on an iPhone or iPad no longer zooms the page in, in the store admin, the customer account and the storefront. Every typing field on a touch screen is now at least 16px, the size below which iOS zooms. Pinch-to-zoom still works.
* Fixed: on phones the store admin's bottom bar was covering the POS cart. It is now hidden on the POS screen. The menu button in the POS header still opens every admin page.
* Fixed: the assistant button no longer covers modal and sheet content (for example the stock count list or the quote settings fields). It steps aside while a modal is open.

= 1.100.0 =
Groundwork for add-ons that sell from quotes and in sets. Nothing to do after updating.

* New for add-ons: `vendm_checkout_claim`, a last check inside the checkout's database transaction, just before the order is written. An add-on can reserve something the order uses up (such as a quote) and can stop the checkout. What it reserves is kept or undone together with the order.
* New for add-ons: `vendm_checkout_shipping_override` lets an add-on set the shipping price for a cart. The checkout preview and the placed order use the same value. It is never used for local pickup or split shipping.
* New for add-ons: the cart context now includes the number of units of each product (`qty_by_id`).

= 1.99.0 =
Fewer requests on product pages and in the store admin. Nothing to do after updating.

* Faster: a product page no longer asks the server for anything after it loads. The first page of reviews, the related products and an add-on's product data (options, bought-together items, suggestions) come with the page for visitors who are not signed in. It used to make 5 requests.
* Fixed: since 1.98.0, a shop or category page served from the storefront cache was missing its built-in product list, so the browser fetched it again. It is included again.
* Faster: add-on scripts and stylesheets in the store admin, account and storefront load as one combined, minified file each, cached by the browser for a year. With VendMizer Pro the admin went from 49 files to 8.
* Faster: the storefront settings record (homepage sections, header, footer, theme) is no longer loaded on every request. Only the short list of custom page addresses WordPress needs at startup is.
* Changed: store cookies (cart session, language, preview, cookie consent) now belong to the store's own address. Two stores in different folders of one domain no longer share them. Existing carts are kept. Stores at the root of a domain see no change.

= 1.98.0 =
Storefront pages now need about 10 database queries instead of 30–60. Nothing to do after updating.

* Faster: home 62 → 11 queries, product 47 → 10, category 38 → 10, cart and checkout 29 → 10 (demo store, warm page). Of the ones left, most are WordPress's own.
* Faster: all store settings load in one query per request instead of one per settings group.
* Faster: data every storefront page needs (store configuration, categories, shipping hints, critical CSS, translations, active announcements, counts) is kept together in one cached record and read in one query. Each page keeps its own sections, product details and SEO tags together the same way.
* Faster: with a persistent object cache (Redis or Memcached, recommended for busy stores) the same data is served from it and these records are not used.
* Freshness: a saved setting, any change in the store admin, a product edit and every stock change (sales included) retire the cached data at once. Nothing waits for a timer.
* Housekeeping: expired cache records are removed by the daily maintenance task and on uninstall.

= 1.97.0 =
Faster storefront pages. Nothing to do after updating.

* Faster: about 20% fewer database queries on storefront pages (home 78 → 62, product 59 → 47, category 49 → 38, cart and checkout 40 → 29 on the demo store). WordPress's own post query is skipped on pages the store renders itself, settings are read from the per-request cache instead of the database, and the storefront configuration is built once per page instead of up to five times.
* Faster: the home page's hero image is requested first (preload with high priority), so it appears sooner.
* Faster: a first-time visitor's pages no longer ask the server for an empty cart; a small "has cart" cookie (no identifier in it) tells the store when there is one to load.
* Changed: an announcement's views are counted once per visit instead of on every page view, which also removes a database write from every page.
* Changed: background tasks no longer read the contact-inbox settings on every storefront page, and the gift-card delivery task is removed when no gift-card add-on is active.
* Fixed: the per-site uninstall file added in 1.96.0 now carries the standard direct-access guard (reported by Plugin Check).

= 1.96.0 =
Security and privacy hardening from the pre-submission audit. Nothing to do after updating.

* Security: password-protected blog posts no longer show their excerpt in blog lists, and private posts are no longer included in the server-rendered blog pages that search engines read.
* Security: rate limits can no longer be dodged by sending a made-up Cloudflare visitor address. The address Cloudflare passes on is now trusted only when the request really came through Cloudflare (or a proxy you list in VENDM_TRUSTED_PROXIES), and stores behind Cloudflare now see each visitor's own address.
* Security: a replayed Mailgun inbound message is refused (timestamp and one-time token checked).
* Privacy: the IP address and browser user agent stored with an order are cleared 90 days after the order (filter: vendm_order_ip_retention_days). The download log's user agent is cleared after 90 days, download log rows after two years, and notifications you have read after 180 days.
* Privacy: on a multisite network, deleting the plugin now cleans every site it was used on, each by its own "Keep data" setting, and removes all of the plugin's user settings (including POS PINs).
* Fixed: "Order again" showed a price change on items with add-ons that had not changed.
* Fixed: the credit-notes total adds up amounts in the store currency only.
* Fixed: IndexNow works on sites installed in a subdirectory.
* Fixed: no PHP 8.5 deprecation notices from image handling (app icons, image resizing) or the currency-change preview.
* Changed: receipt output is escaped line by line instead of under one blanket exemption.
* Readme: the FAQ now points to Settings → Access & Policies to keep the standard WordPress login.

= 1.95.1 =
Plugin Check 2.2.0 clean-up. No change in behaviour.

* Changed: every database query Plugin Check 2.2.0 reported as an error is now either rewritten or carries a stated reason why it is safe (two statements rewritten, the rest documented). Plugin Check now reports no errors.

= 1.95.0 =
Fixes from the pre-submission audit: refunds, late payments, two-step sign-in and personal-data requests. Nothing to do after updating.

* Fixed: with "Prices include tax" on, refunding a line paid back its tax a second time (115 refunded as 130). Credit notes now split net and tax correctly in that mode too.
* Fixed: on orders split across several shipping addresses, each line's tax and discount are now stored correctly, so refunding a line pays back what it cost.
* Fixed: a gift card or store credit returned when an order was cancelled is no longer refunded again. On online orders part-paid with a gift card or store credit, a refund now returns the card payment first and the rest to the gift card or credit, instead of asking the payment provider for more than it took.
* Fixed: stores in KWD, BHD, OMR, JOD and other three-decimal currencies kept their full precision in refunds, payment records and credit notes (amounts such as 10.125 were rounded to 10.13 and refused by the payment provider).
* Fixed: a PayPal, Square, Moyasar, Tabby, Tamara, Klarna or Payoneer payment that arrives after the order was automatically cancelled now takes its stock, gift card, credit and coupon back first, or holds the order for review — it could sell the same stock twice.
* Fixed: a Moyasar payment for the wrong amount is recorded and the order held for review, instead of being marked failed with its stock and gift card left held.
* Security: two-step sign-in can no longer be replaced without the current code, and wrong codes are limited to 10 per 15 minutes on every sign-in path. Only a WordPress administrator can reset another administrator's two-step sign-in.
* Fixed: store search no longer stops with an error on hosts without the mbstring PHP extension.
* Privacy: saved addresses are now included in personal-data exports and removed by erasure requests.
* Privacy: email open and click tracking is now off by default (switch it on under Settings › Email). Existing settings you saved are kept. The suggested privacy-policy text now covers tracking and app notifications.
* Changed: the app-icon folder in uploads now holds an empty index.php, as the plugin directory guidelines require.
* Readme: requirements (pretty permalinks), the Contact inbox's IMAP connection and the Saudi Riyal symbol font are now documented.
* Translations: gateway "Test connection" messages and the PHP-version notice are translatable.

= 1.94.0 =
Every optional feature is now a module you can switch on or off in Settings › Modules. Nothing changes after updating: each new module starts in the state the feature was already in.

* Added: seven new modules — Credit Notes, Order Again, Direct Carriers & COD, Back-in-Stock Alerts, Announcements & Pop-ups, Contact Form & Inbox, and Outgoing Webhooks. Turning one off removes its menu item, screens, storefront parts, routes and background jobs; records already made (issued credit notes, contact messages, COD entries, shipments) are kept.
* Added: back-in-stock emails. Shoppers who asked to be told when a sold-out product returns are now emailed once when it is back in stock (hourly check; new "Back in Stock" email template, editable like the others). Before this the requests were stored but never sent.
* Changed: the "Issue a credit note for every refund", "Let customers order again" and "Notify me when back in stock" switches moved from Settings › Invoice, Checkout and Catalog to Settings › Modules.
* Changed: a module that needs another (Credit Notes → Invoice & Receipts, Direct Carriers → Shipping Zones, Back-in-Stock Alerts → Inventory) stays off while that one is off.
* Fix: the USPS tracking poll was tied to the Tracking & Analytics (Google Analytics) module; it now follows Direct Carriers & COD.
* Fix: with Direct Carriers & COD off, the carrier webhook still accepts updates for parcels already on their way.

= 1.93.0 =
The rest of the app features: notifications, icon badges and a separate POS app. Manage them under Settings › Apps.

* Added: push notifications for staff — new orders, low stock, reviews and messages reach the admin app on every device a staff member turns them on for (the same alerts as the bell, following each person's Profile › Notifications choices). Tapping one opens the order or screen it is about. "Send a test" checks a device.
* Added: order updates for shoppers — after checkout, "Get updates on this order" sends a notification when the order is confirmed, shipped (including when a carrier label is bought), delivered, completed, cancelled or refunded. Order updates only, never marketing; works for guests and signed-in customers, in the shopper's language (translatable; Arabic is bundled).
* Added: app icon badges — the admin app shows the unread notification count, the store app shows the cart count (each can be switched off).
* Added: a separate POS app (with VendMizer Pro's register) — installed on the counter device it opens straight on the register, full screen, with its own icon and launch screens.
* Added: Analytics › Installed apps shows POS app use, how many devices have notifications on, and opens from a notification.
* Added: Installable Apps (PWA) is now a module in Settings › Modules (on by default). Turning it off removes the apps' manifests and head tags, hides Settings › Apps and the Analytics card, stops notifications, and retires the service workers already installed on devices.
* Added: actions vendm_notification_added and vendm_order_status_changed (also fired when a carrier confirms delivery) for extensions.
* Improved (installed apps): no extra page request for pages the app does not own (wp-admin, sign-in, the admin under the store app); an app or module switched off now removes its worker from devices; icons and launch screens are written atomically, made from a reduced copy of large favicons, and old sets are cleaned up; the worker caches only VendMizer's own versioned files, with a size cap.
* Improved (notifications): long alerts are shortened to fit one push message; outages, timeouts and rate limits no longer count against a device; the site's push keys can never be replaced by a concurrent first request; a device signing out of a staff app stops its alerts; signed-in customers get updates for every later order; Analytics › Installed apps follows branch access; guest and dead subscriptions and usage counters older than three years are cleaned up daily.
* Improved: the apps add no database queries to storefront pages — the icon signature and push key are kept in one autoloaded option.
* Improved: app names, descriptions, shortcuts and the offline page follow the language of the page the app was installed from (an Arabic storefront installs an Arabic, right-to-left app), using the bundled Arabic translation even where no WordPress language pack is installed.
* Improved: app usage counters only move for a device that loaded one of the store's pages that day, and installs and daily-active counts are capped per network address per day.
* Updated: the bundled Arabic translation covers every string added since 1.80.0.
* Notifications are encrypted end to end with your site's own keys (generated on first use); no third-party library or account is needed. See "External services" for the push services browsers use.

= 1.92.0 =
Your admin and your store can now be installed as apps. Both are on by default; manage them under Settings › Apps.

* Added: installable admin app and storefront app (web app manifest, service worker, icons, launch screens). An installed app opens full screen and stays full screen on every screen — sign-in, sign-out and every admin page included. The browser bar no longer appears when moving between screens.
* Added: Home Screen icons made from your favicon (the admin app on a dark tile), maskable icons for Android, and iOS launch screens for current iPhones and iPads in light and dark.
* Added: an offline page for both apps that reloads by itself when the connection returns. Pages, carts, checkout and accounts are never cached; only versioned scripts, styles, icons and storefront images are.
* Added: Settings › Apps — switch each app on or off, install the admin app on this device, set the store app's name, Home Screen label and launch-screen colour, and the install banner for returning shoppers.
* Added: Analytics › Installed apps — installs, opens, daily active devices, install-banner results, opens by platform, and orders and revenue placed in the store app. Counted as daily totals with no identifiers; forwarded to Google Analytics as app_* events when GA4 is set up.
* Added: orders placed from the store app are marked; filter the order list by channel (store app / website) and see a channel column in the CSV export.
* Added: in an installed app — a Refresh item in the account menu, pull to refresh on iPhone and iPad, an offline notice, and links that leave the app open in the browser sheet.
* Changed: the storefront's browser theme colour now follows the header colour instead of the accent.

= 1.91.1 =
* Changed: on a phone, the main button on an order now moves it forward — Ship order while it is waiting to ship, Edit order while it can still change, Invoice once it is complete. Refund stays in the ⋯ menu.
* Changed: on a phone, the main button for an active customer is Send email; Suspend moved into the ⋯ menu, above Delete.
* Changed: the Contact inbox header no longer repeats the unread / all / replied counts — the status tabs below show them.

= 1.91.0 =
The 1.90.0 product-screen design now applies across the whole admin. Nothing to do after updating.

* Improved: every admin screen uses the same four colour levels as Edit Product (page, card, tinted inner panel, recessed field with a clear edge), in dark and light themes.
* Improved: one look for fields, selects, checkboxes, radios, switches, pill tabs, badges, tables, alerts and save bars; a visible keyboard focus ring everywhere; card headers show their icon in a tinted chip.
* Improved: the Settings and Marketing section rail marks the current item with an accent bar on the start side; in-page section menus stay a scrolling strip on phones.
* Improved: charts use compact axis labels (18k, 1.2M), keep date labels level on phones, and draw horizontal bars from the right in Arabic.
* Improved: Arabic names show a single initial in avatars; back arrows point the right way in Arabic; long Latin text (phones, slugs, details) reads correctly inside Arabic.
* Improved: Transactions and Wishlist stat cards fill their rows; Loyalty and Analytics cards keep their own height; Recent orders on the dashboard shows 7 orders.
* Improved: Attributes show the type as a word, and term chips keep their reading order in Arabic; Product tags title and button are translated.
* Fix: Media folder rows were split apart (a button inside a button); Shipping's title now sits above its tabs; Inventory row borders reach the action column and out-of-stock rows no longer dim their buttons.
* Fix: the admin CSS bundle removed the space before a colon, which broke descendant selectors such as ".card :is(…)"; the space is now kept.

= 1.90.0 =
A clearer, better-fitting product form. Nothing to do after updating.

* Improved: Edit Product colours. Cards, the boxes inside them and fields each have their own colour level in dark and light themes, so a box inside a card and a field inside a box are always easy to tell apart. Unticked checkboxes and field edges are clearly visible.
* Improved: read-only stock (managed by variations) shows as a solid value box instead of an empty-looking dashed field.
* Improved: fields size to the space they get. Short fields sit side by side when there is room and stack when there isn't; pairs such as sale dates, minimum/maximum quantity and weight + unit stay together. SKU and Barcode now share a row, and Inventory and Pricing are much shorter on desktop.
* Improved: on desktop the Sections list stays on screen while you scroll, and the save bar stays at the bottom of the screen.
* Improved: on phones the section chips stay in view under the top bar and follow the open section, every field uses the same text size, the rich-text toolbar is one scrolling row, and switching sections starts at the top.
* Improved: variation and attribute checkboxes use the VendMizer checkbox style.
* Improved: products list columns now read Product, Price, Stock, Status, Type; badges share one size and row actions stay quiet until you hover.
* Changed: on phones, data tables across the admin scroll sideways as one piece — the checkbox and first column are no longer pinned — and the edge with more columns fades. Product names wrap to two lines so price shows beside them.
* Improved: rarely used settings fold away (Schedule the sale price, Purchase limits) and open by themselves when set; profit margin shows as a compact stat strip; sold count is a plain line.
* Improved: tablets and small laptops get a sticky section strip under the top bar; the desktop Sections list marks the current section; every control has a visible keyboard focus ring; field edges meet the 3:1 contrast minimum in both themes; status colours are readable in light mode.
* Improved: on phones the variations list stays a table that scrolls sideways (the select column is kept); headers line up with their columns.
* Fix: the check icon on Publish was invisible; product descriptions show real bullets and a tidy spec table in the editor.
* Fix: in the products list, a product that takes backorders showed "Out of stock"; it now shows "On backorder", matching the Out of stock tile. Bundle and gift card types show proper names and colours.
* Fix: the section title no longer shows a white focus box after switching sections on a phone.

= 1.89.1 =
* Fix: a product on backorder showed "Low stock" on its page and in quick view; it now reads "Available on backorder".

= 1.89.0 =
Credit notes and order again. Nothing to do after updating; use Orders → Credit notes → "Issue for older refunds" once if you want notes for refunds made before this version.

* New: credit notes. Every refund now issues a credit note automatically — admin refunds, store-credit refunds and refunds your payment provider reports. Numbers never skip (CN-2026-00012 by default, restarting each year; change the format in Settings → Invoices). A credit note lists the refunded lines and tax, names the invoice it reduces and cannot be edited.
* New: Orders → Credit notes lists every note with a period filter, search, totals and a CSV export for your accountant.
* New: the refund email attaches the credit note PDF and states the refunded amount (it used to show the order total). Customers can download their credit notes from the order page in their account. New webhook topic: credit_note.created.
* New: order again. "Buy again" on the customer's orders checks today's prices and stock first. When nothing changed the items go straight to the cart; otherwise the customer sees what changed — a new price, fewer left, or no longer sold, with "Notify me" for out-of-stock items — and chooses Add to cart or Checkout now. Bundles and add-on choices are kept from this version on.
* New: a "Buy it again" row on the customer account dashboard. Both can be turned off in Settings → Checkout.
* For add-ons: a related-products source for the product page and cart, a cart drawer slot, a button-label hook for product blocks, a line-hold badge on order lines, an "ext" namespace for add-on storefront settings, a filter that lets an add-on create an admin order without moving stock, "price on request" products (no price or Add to cart on cards and the product page), a generic business-document PDF and file attachments on add-on emails.

= 1.88.0 =
Admin and store fixes for phones. Nothing to do after updating.

* Fixed: the shop filter's colour, size and other attribute options returned no products on MariaDB servers.
* Fixed: "Clear all" in the shop filter now clears every filter and resets the filter panel, so the next "Show results" starts clean. A "Clear all" link also appears beside the active filters.
* Fixed: media thumbnails were broken on sites installed in a subfolder, and SVG thumbnails were broken everywhere.
* Lists on phones are now compact data tables that scroll sideways inside their own box, with the checkbox and first column pinned. Card view is still one tap away on lists that have the switch.
* Settings → Dashboard theme → KPI cards: choose Classic, Compact, Accent or Minimal number cards, and whether phones show them as a swipe row or a two-column grid.
* Contact inbox: a mail-style message list (avatar, sender, time, subject, preview) that fits phones; the page no longer scrolls sideways.
* Tools → Import: the six import types are tiles on desktop and tappable rows on phones (they were squeezed into one row).
* Products page: one primary button, with Export, Import and add-on buttons grouped as pills; on phones the filter bar puts search, refresh and the view switch on one line and the filters in a compact row.
* Customer account: address fields show their icons and stack on small phones; the store name no longer wraps in the account header.
* Categories: tree rows fit phones (name, then status and count) and the product count is translated. Staff search no longer collapses on phones.

= 1.87.0 =
Storefront polish and per-country payment methods. Nothing to do after updating.

* Payments: every payment method has an "Available in" setting — all countries, only some, or all except some. Checkout shows only the methods available for the order's country and updates the list when the country changes; the order is checked again when it is placed. Instalment badges (Tabby, Tamara) on product and cart pages follow the same rule.
* The Saudi Riyal shows its official sign (⃁) again, drawn by a bundled font that now contains only that one character. Emails and PDF invoices, which cannot load fonts, show "SAR".
* Shop filter: a real dialog with a close button, Esc and backdrop to cancel without changes, a sticky "Clear all · Show results" footer, active-filter count on the Filter button, "Show all" for long lists, and colour swatches with names and counts. A side panel on larger screens.
* Colour options show as swatches on product pages (with the chosen colour's name), and in the filter — also for colour attributes created without colour values.
* Shop page: hide the product count, Filter button, grid/list switch or sorting (Settings → Catalog → Shop page toolbar). Sorting is now a compact icon button.
* Checkout and address forms: field titles can be hidden (Settings → Checkout); they remain for screen readers.
* Profile: the phone number has a country picker like checkout. Changing the phone now asks for the current password in the form instead of failing.
* Fixed: an email-only sign-up got its email address as its first name. Existing accounts are repaired when you update.
* Fixed: blog posts whose content was plain text broke the article page.
* Fixed: homepage button links to store pages ("products") were saved as dead external links; existing links are repaired. Hero overlay opacity is saved on the scale the slider uses. Logo-cloud items are saved. Server-rendered sections draw every icon. The scrolling marquee works in Arabic.
* Hero: new "mirror background in right-to-left languages" option.
* Mobile menu currency choice is a compact grid and can be hidden (VendMizer Pro → Currencies).
* Manager empty-state hints share one width; the announcement bar's close button no longer covers its link.

= 1.86.0 =
Fixes found while building the new demo store. Nothing to do after updating.

* Media library: uploads stopped getting a working address from about the 37th file on, because two short ids that differ only in letter case were treated as the same. Short ids are now case-sensitive, and files left without an address are repaired when you update.
* Checkout lists card and wallet payments first, then instalment plans, then cash on delivery and other offline methods. Previously the list was alphabetical, so cash on delivery was often the method selected by default.
* The homepage category row could hide its first categories off-screen when there were more than fit; it now starts at the first one and scrolls.
* The store name in the header stays on one line on narrow phones instead of wrapping.

= 1.85.0 =
Add-on interfaces, from the November 2026 audit. Nothing to do after updating. If you use VendMizer Pro, update it to 1.30.0 after this.

* Bundles, product add-ons, marketing (abandoned-cart recovery and mailing-list sync), text messages and an add-on's table list now connect through typed interfaces. Point of sale, returns, tickets, subscriptions and the activity log are recognised by a declared module name instead of a class name. VendMizer no longer names any add-on class outside its compatibility layer, which keeps older add-ons working unchanged.

Older releases are listed in changelog.txt.

== Upgrade Notice ==

= 1.121.0 =
Faster first Dashboard load on large stores, and a Site Health check that recommends a server cron.

= 1.120.0 =
Faster dashboard best sellers, app statistics and channel filter on large stores. The update adds indexed columns to the orders and order lines tables.

= 1.119.0 =
Faster, non-blocking checkout; a sale refreshes only that product's cached pages; order emails no longer delay the checkout answer.

= 1.118.0 =
Faster dashboard and reports on large stores (one rebuild, new orders index, cached report totals). The update adds an index to the orders table.

= 1.117.0 =
Exports and the product feed are complete (no more 10,000 / 5,000 row limits); the orders export is much faster; the page cache stays small.

= 1.116.0 =
Safety fixes: the dashboard follows every order change, low-stock alerts are sent after checkout, no duplicate order emails, privacy clean-up keeps up on busy stores.

= 1.115.0 =
Inventory redesign; In stock no longer counts untracked products.

= 1.114.0 =
Categories, Attributes, Brands and Product tags redesign; attributes show how many products use them.

= 1.113.0 =
Transactions and Credit notes redesign; bank transfers can be filtered.

= 1.112.0 =
Wishlist redesign; shoppers without a customer record are named.

= 1.111.0 =
Coupons and Reviews redesign; review replies now reach guest buyers.

= 1.110.0 =
Orders redesign; the customer's checkout note now shows on the order.

= 1.109.1 =
Fixes opening an order from a customer's page.

= 1.109.0 =
Customers redesign, a working "Email customer", and adding group members by name instead of ID.

= 1.108.0 =
Page templates, saved sections, version history and scheduled publishing in the page builders; product page templates per category.

= 1.107.0 =
Section library with previews and one-click design variations, plus Counters, Filterable Gallery and Contact + Map sections.

= 1.106.0 =
New Image + Content section with per-device images and layouts; undo/redo, copy/paste and autosaved drafts in the page builders.

= 1.105.0 =
New Design › Product page: gallery layout, column widths, sticky column, details as tabs/accordion/all open, and block order.

= 1.104.0 =
Product page refresh: guided Add to Cart, one buy bar on phones, accordion details, optional delivery estimate and trust notes.

= 1.103.0 =
Product carousel, best sellers, product tabs, recently viewed, spotlight, collections, lookbook and comparison sections are now free. Update VendMizer Pro to 1.44.0 too.

= 1.102.0 =
Image picking and uploading fixed across Design and page sections, full-height dialogs on phones, and a reworked Design screen.

= 1.101.0 =
No more zooming when typing on iPhone and iPad, and the POS cart is visible on phones. Pair with VendMizer Pro 1.43.0.

= 1.100.0 =
New checkout seams for add-ons. Pair with VendMizer Pro 1.42.0.

= 1.99.0 =
Product pages make no extra requests after loading, and the store admin loads 8 files instead of about 50 with VendMizer Pro.

= 1.98.0 =
About 80% fewer database queries per storefront page (about 10 per page on the demo store).

= 1.97.0 =
About 20% fewer database queries per storefront page and a faster first paint on the home page.

= 1.96.0 =
Hides protected blog posts from lists and search-engine pages, hardens rate limits behind Cloudflare, and clears old order IP addresses after 90 days.

= 1.95.1 =
Code-quality update for Plugin Check 2.2.0; no change in behaviour.

= 1.95.0 =
Fixes refunds with tax-inclusive prices, gift cards and three-decimal currencies, late payments on cancelled orders, and hardens two-step sign-in.

= 1.94.0 =
Every optional feature is now a module in Settings › Modules, and back-in-stock requests are finally emailed. Nothing to do after updating.

= 1.93.0 =
Push notifications for staff and shoppers, app icon badges and a separate POS app. Nothing to do after updating; turn notifications on per device in Settings › Apps.

= 1.92.0 =
Installable admin and storefront apps with offline pages, launch screens and app analytics. Nothing to do after updating; see Settings › Apps.

= 1.91.1 =
Clearer main actions on phones and a tidier Contact inbox header. Nothing to do after updating.

= 1.91.0 =
One unified design across every admin screen. Nothing to do after updating; update VendMizer Pro to 1.35.0 as well.

= 1.90.0 =
Clearer product form colours and layout on every screen size. Nothing to do after updating; update VendMizer Pro to 1.34.0 as well.

= 1.89.1 =
Backorder label fix. Nothing to do after updating.

= 1.89.0 =
Credit notes for every refund and one-tap order again. Update VendMizer Pro to 1.33.0 for pre-orders, upsells, purchase orders and quotes.

= 1.88.0 =
Fixes attribute filters on MariaDB and media thumbnails in subfolder sites; phone-friendly tables and KPI card styles.

= 1.87.0 =
Per-country payment methods, shop filter redesign and colour swatches. Update VendMizer Pro to 1.31.0 for the mobile-menu currency toggle.

= 1.86.0 =
Fixes media addresses after the 36th upload and orders checkout payment methods. No action needed.

= 1.85.0 =
Typed interfaces for the remaining add-on modules. Update VendMizer Pro to 1.30.0 afterwards.
