Found a bug? Have a great feature idea? Get on GitHub and tell us about it and we'll get right on it: https://eshop-optimizer.com


= 10.3 - 2026-07-30 =
* **Customers can see where a withdrawal stands.** Entering an order number and email now shows the stage — received, approved, items on their way back, refunded — and what happens next at each one.
* **How the refund was made is recorded and told to the customer**: back to the original payment method, bank transfer, store credit or cash.
* The guest withdrawal link now lasts **21 days** instead of an hour, and a lapsed one can always be re-requested from the form.
* **Greek admin fixes**: menu entries that rendered in English now translate, and five withdrawal strings that read "cancellation" say "withdrawal".
* Minimum WordPress is now 6.7.

= 10.2 - 2026-07-29 =
**Withdrawal declarations now notify the shop, plus mobile-navigation refinements and minor fixes.**

* A declaration that needs processing no longer ends at a private order note: an optional interim order status **"Withdrawal requested"** (off by default — mind anything that reads order statuses), and a **store email** built as a real WooCommerce email with its own recipients and overridable template. Both controlled from Operations → Withdrawal Right → Settings.
* Mobile navigator: **Categories | Filters** tabs at the top of the panel on archive pages, so categories are never buried below the filters.
* Subcategory chips: the mobile slider now shows the same progress affordance as the product carousels — an accent-coloured thumb over a thin black line running to the screen edge — and one theme override recolors both.
* Minor fixes: admin checkboxes that could be ticked but never unticked, Wide/Full block alignment on the chip strip, and dual-bundled class loading hardened against cold-opcache redeclare fatals.

= 10.1 — The withdrawal right, end to end, and ten international couriers (29/07/2026) =

* **The withdrawal button, as Directive (EU) 2023/2673 requires it.** In Greece that is Law 5317/2026, published 10 July 2026, which inserts article 3ζα into Law 2251/1994 — in force on publication, with no transition period. A permanent, prominent button; 14 calendar days counted from *receipt* rather than from the order; a separate confirmation step; partial withdrawal on multi-item orders; and an acknowledgement email on a durable medium recording the content, date and time of the declaration. It works for guests throughout: creating an account is offered afterwards and never required, because requiring one is precisely the obstacle the law prohibits. Ships disabled.

* **Cancellation and withdrawal are two flows, not one.** Cancelling an unshipped order is a commercial courtesy the shop grants on its own terms and may refuse once the parcel has left; withdrawal is a statutory right, for a window the shop does not set and cannot decline. Merging them is the commonest way a compliant-looking implementation fails. The instant-cancel courtesy is now settable in hours *and* minutes — 0 hours 15 minutes is a valid answer — or switched off entirely, for shops that would rather not advertise it.

* **An operator stands between the carrier and the customer.** Return vouchers pass through a new awaiting-approval stage: the operator picks the courier, issues the voucher, downloads the label, checks it, and only then approves — at which point it reaches the customer by email and in their account. Nothing carrier-generated reaches a customer unseen. The pickup address is editable (a customer can have the parcel collected from work); the destination is not, since carriers already know where the shop is. A label booked at a courier's own portal can be uploaded and shared exactly like an API-issued one.

* **Ten international courier drivers** — DHL Express, FedEx, UPS, USPS, Royal Mail, DHL Paket, Sendcloud, Colissimo, BRT (Bartolini) and Correos Express — each a real API integration on a shared transport layer handling OAuth, label decoding across PDF, PNG, JPEG, GIF and ZPL, and carrier-specific error extraction. Carriers that cannot bill a third party do not show a "who pays" control, because a choice that cannot change the outcome is worse than no choice. Three of them issue per-customer endpoints, so their base URL is a setting with a sensible default rather than something only a release can change.

* **Greek terminology corrected.** "Withdrawal" had been translated as «ανάληψη» — a *cash* withdrawal — on eighteen strings including the statutory button's own label, and elsewhere as «ακύρωση», which merged the two flows the law requires be kept apart. The term is «υπαναχώρηση».

* **The web-push opt-in banner no longer defaults to on**, and this update switches it off once. Turn it on in Operations → Web Push → Display if you want it; existing subscribers keep receiving campaigns either way.

* Fixed: admin submenus vanishing while the pointer crossed the gap towards them; withdrawal-queue stage counters losing their styling on empty tabs; courier settings being blanked rather than merged on save; and a DHL Paket billing number assembled from an incomplete customer number, which could be accepted against another account.

= 10.0 — Everything findable, everything described, everything correctly named (27/07/2026) =

* **Every screen in the plugin is now reachable from one keystroke.** All 617 addressable destinations — 157 pages, 25 in-page tabs and 435 anchored panels — answer to **Ctrl+K** from anywhere in the admin. Before this, a capability you had not personally been shown was a capability you did not know existed: the panels inside a page were reachable only by knowing which page held them and scrolling to find out.

* **Every page and tab says what you can DO there.** All 195 of them carry a written one-line description, shown on hover and in the navigator. This was not cosmetic work. "Attribution", "Operations" and "Set Up" are honest names that tell a new shop manager nothing, and the Home page lists 169 of them at once. Each line is written once and consumed four ways — the hover modal, the Home search index, the Ctrl+K keywords, and the Insights assistant — so a vague one costs four times and a wrong one teaches something false in four places.

* **Findable by the nouns you actually use.** Descriptions feed the search index, so a destination is reachable by what it deals in — «ΑΦΜ», "Omnibus", "packing slip", "disavow", "Skroutz" — and not only by its label. Measured before this existed: "redirects", "schema", "backlinks", "sitemap" and "swatches" all returned nothing on a Greek install, because the label was Greek and the index held nothing else. Worse, "swatches" surfaced Problematic Variations and "side cart" surfaced Checkout Layout — decoys outranking the namesake tab, which is worse than an empty result.

* **The plugin tells you what kind of site it thinks you are.** The admin header now shows your site profile — shop, catalogue or content — whether it was auto-detected or set by you, and warns when a manual setting no longer matches the evidence. One click to change it. Opportunity scoring, cornerstone selection, the demand score and which signals even apply all follow from that one choice, so having it invisible meant an operator could not tell why a number looked wrong.

* **The whole codebase now speaks English at source, and Greek to the reader.** 151 Greek literals across both plugins were converted to English source strings with the Greek preserved exactly as translations, so nothing a shopper reads changed. Duplicate translations of the same concept were merged onto single strings, and four checkout invoice fields in the runtime plugin had never been translatable at all — they are now. This is what makes any other language possible.

* **Fixes.** OpenAI was dropped as a provider in May, but the AI settings form could still store it: the dropdowns stopped offering it while the save handler kept accepting it, so a stale submission could switch a live site onto an unsupported provider. The AI credits check told operators the Content Connector was not configured even when it was — a message only reachable *after* the token authenticates; it now distinguishes "no Anthropic key on the account" from "AI service disabled", names the account and links to the portal. Admin hero copy no longer quotes one particular shop's catalogue size as if it were yours.

= 9.5 — Audience correctness, identity resolution, admin information architecture (26/07/2026) =

* **Segment and cohort exports no longer download empty files.** "Given an audience NAME, which customers are those" was answered in four places that disagreed. Both CSV exporters accepted segment names while filtering on the dormancy column alone, so exporting a segment produced a well-formed, successful, EMPTY file — 9 of 14 targetable audiences were silent no-ops, including every one named in the lookalike workflow's own instructions (VIP, Loyalist, Brand-Devoted). One resolver now answers for all callers, and it is the union of the four implementations rather than their intersection: exact JSON matching, bidirectional handling of the lapsed→overdue rename, a segment list derived from your data instead of a hardcoded one, and the `pure_intent` audience that previously existed in only one of them. Dormancy cohorts are unchanged.

* **Retroactive identity resolution.** Browsing sessions were only ever tied to a person as orders and logins happened, so a store installing the plugin started with a large backlog of past orders whose visitor was already known but never linked. A new backfill resolves those in one pass — from the admin (Data Pipeline → Identity resolution), from WP-CLI (`wp aieo identity backfill`), or on a daily schedule. It is safe to re-run at any frequency: it only looks at sessions that are not yet resolved, so it converges and then costs nothing. Three further resolution points were added (registration, WooCommerce customer creation, and checkout — a shopper who registers during checkout is auto-logged-in, so the login hook never fired for them).

* **Action Scheduler protection no longer corrupts unrelated queries.** The query guard matched the actions table by name ANYWHERE in the SQL, including as one value in a list. The plugin's own health probe lists every catalogued table in one lookup, so the guard truncated it to ten rows and the Signals screen reported 62 measurements as missing storage that demonstrably existed. It now matches the query's actual target table, and a bounded roll-up over a low-cardinality key is recognised as safe.

* **Admin navigation.** Data prep schedule and Product/Orders analytics were two screens answering one question and are now one page, Data Pipeline. Signals — the catalogue of what this install measures — moved out of an unrelated tab onto its own page, with a Re-measure control.

= 9.4 — Correctness hardening for the 9.3 price fast path (23/07/2026) =

* **Multi-currency detection.** `variation_price_filters_are_safe()` inspected only `woocommerce_variation_prices_price/_regular_price/_sale_price`. WooCommerce Multilingual's multi-currency hooks none of them — it uses `woocommerce_variation_prices` (the aggregated array, applied after the walk) plus `woocommerce_get_variation_prices_hash`, converting at its own layer. The gate therefore found nothing registered on a multi-currency store, concluded "safe" and served unconverted prices. The array filter is now part of the inspected set; verified that a WCML-shaped callback declines the fast path with coverage otherwise unchanged (947/1124, 0 wrong prices).
* **Cross-check against the variations.** The fast path trusted `wc_product_meta_lookup.min_price/max_price`. A full-catalogue comparison against the live aggregation found two products where that aggregate is wrong and, in both cases, LOWER than the real price: a parent row left stale by an import that bypassed `WC_Product_Variable::sync()`, and a variation whose `_price` is the string "24,99" (SQL `CAST` truncates to 24.00 while PHP parses 24.99 — WooCommerce's own lookup row is wrong there too). `lookup_variable_price_range()` now compares the aggregate against the `_price` of the product's visible children and declines on any disagreement.
* **European decimal handling.** That comparison normalises through `wc_format_decimal()` rather than `str_replace(',', '.')`, which would corrupt `1.234,56` into `1.234.56` on a store using a comma decimal separator and a dot thousands separator.
* **Third-party pricing extensions.** The fast path reads raw stored prices, bypassing anything hooked into the price pipeline. It now identifies every registered callback by name (as `CallbackUtil::get_callback_signature()` does) and proceeds only when all are allowlisted; closures and invokables have no stable name to match, so their presence declines. Filter: `aieo_dto_price_filter_allowlist`.

* **Fixed a latent no-op on `delete_term`.** `AIEO_DMM_Swatches::invalidate_on_term_edit()` resolved the term with `get_term()`, but `delete_term` fires *after* the row is removed, so it returned null and the handler exited early — deleting an attribute term invalidated nothing, leaving every product that used it with a stale swatch cache until its next save. The hook now takes WordPress's 4th argument (the already-deleted `WP_Term`) and uses its slug; the variations' `attribute_pa_*` meta survives the delete, so the affected parents are still found. Verified on the live catalogue: a deleted term's slug correctly resolves the 69 products that used it, where the previous code resolved none.
* **Removed the per-variation N+1 in term invalidation.** The handler called `wp_get_post_parent_id()` once per matching variation. Parents are now resolved in one indexed JOIN — 10.47 ms to 0.51 ms (20x) on the busiest term, with an identical result set.
* **Removed silent truncation.** The variation lookup carried `LIMIT 2000`, unordered and unpaged, so a term used by more products than that would silently drop the remainder. The lookup is now keyset-paged and always drains, so nothing is missed; page size is memory hygiene, not a cap.
* **Bounded the rebuild fan-out.** Term edits are recorded at hook time (no queries) and flushed once on `shutdown`, deduplicated across every term edited in the request, then enqueued as one `$unique` Action Scheduler job per affected product. An import editing thousands of terms therefore costs one lookup per distinct term and at most one pending job per product, instead of work per edit. The global settings-hash bust that caused the June cache-rebuild outage remains removed, and this path never reintroduces it.

Upstream: this hardening came out of review feedback on our WooCommerce core contributions — woocommerce/woocommerce#66890 in particular.

= 9.3 — Variable-product pricing performance & role-price cache correctness (22/07/2026) =

* **Fixed: professionals could see stale prices for up to 30 days after a role-price import.** WooCommerce's variable-price cache key recorded the viewer's roles but not the version of the role-price dataset, so a CSV import did not supersede cached ranges until each product was next saved. The dataset version is now part of the key (`aieo_role_prices_v`, bumped from every role-price write path). Public/guest cache entries do not carry the factor and are left intact.
* **Cut needless variable-price cache entries for logged-in customers.** `modify_variation_hash()` keyed on every role a user held, while the price filter only acts for the configured professional roles — so ordinary `customer`, loyalty and newsletter accounts each minted a private cache entry byte-identical to the guest one, each costing a full aggregation of every variation. The key now intersects the viewer's roles with the enabled set and leaves the hash untouched when the intersection is empty, so those visitors share the guest entry.
* **Recommendation/side-cart card DTOs no longer aggregate every variation.** `build_clean_price_html()` now reads `min_price`/`max_price` from `wc_product_meta_lookup` (which WooCommerce already maintains and indexes) instead of walking the variations. Deliberately conservative: it falls back to the full aggregation for logged-in visitors (role pricing rewrites per-variation prices) and on tax-enabled stores (the stored values are raw). Filterable via `aieo_dto_use_meta_lookup_price_range`. Applied in both the admin and runtime plugins.
* **Product labels and Product structured data now use display-context prices.** Discount percentage/amount labels and the `AggregateOffer` `lowPrice`/`highPrice` were computed from raw variation prices; on a tax-inclusive store both understated the figures, and both requested the cache variant WooCommerce had not warmed, forcing a second full aggregation. They now pass `$for_display = true`.
* **`AIEO_DMM_Settings::get_all()` is memoised per request.** The defaults/stored merge ran on every `get()`; `current_user_is_pro()` calls it once per price-filter invocation, so a cold aggregation of a 187-variation product rebuilt the whole settings tree several hundred times. The memo is invalidated by `update()`, `replace()` and by the `update_option_`/`add_option_`/`delete_option_aieo_dmm_settings` hooks, so writes from outside the class are also covered.

Background: this work came out of our contributions to WooCommerce core on variable-product price performance — woocommerce/woocommerce#37629, PRs #66882 and #66889, issues #66883, #66890 and #66892.

= 9.2 - 2026-07-21 =
**Analytics and nightly jobs now repair their own database routines.**

* **Fixed: nightly jobs could fail forever after a site restore or migration.** Database backups exclude stored routines unless explicitly asked for, so restoring a site could silently drop the procedures that power surveys, web-push customer intelligence, product needs and session analytics — while the plugin still believed they were installed. The affected jobs then failed every night with "PROCEDURE … does not exist", and reinstalling or reactivating the plugin did not help, because the check was based on a stored version number rather than on whether the routines actually existed.
* **Now self-healing.** Each job detects a missing routine at the moment it needs it, reinstalls it and retries once. This costs nothing on normal page loads — there is no extra check on storefront requests — and it repairs itself inside the nightly job or an admin action instead of needing manual intervention.
* Covers the survey ingest/intelligence procedures, the web-push customer-intelligence recompute and segment assignment, product-needs population, and the session-analytics aggregation, ranking, summary and cleanup routines.

= 9.1 - 2026-07-20 =
**Stability release — three fixes worth updating for, one of them urgent.**

* **Fixed: a fatal error that could break logging in.** On sites using the identity/attribution layer, the `wp_login` handler called an internal helper it wasn't allowed to reach, which raised a PHP fatal during sign-in — affecting the standard login form, "My account", and passwordless/magic-link sign-in. If you were seeing 500s on login, this is the fix.
* **Fixed: AI credit balance over-reported when you held a top-up.** The remaining balance added your top-up on top of the monthly cap, but the cap already includes it — so the figure could read as much as double. This under-fired the low-balance alert and let the assistant hit its limit while the meter still showed credit. The credit meter now reads "incl. $X top-up" rather than "+ $X" to match how the cap is actually composed.
* **Removed a latent fatal on the paid-order path.** The Meta CAPI purchase-event builder contained an unreachable branch that would have raised the same class of fatal as the login bug if ever taken. Removed rather than left as a landmine.

= 9.0 - 2026-07-20 =
**The plugin is now Rooster One.**

* **New name.** "AI eShop Optimizer" is now **Rooster One** (the front-end companion is "Rooster One — Runtime"). Only the display name changes: your settings, data, shortcodes and block names are all untouched, and updating is a normal plugin update with nothing to reconfigure.
* **One checkout newsletter opt-in instead of two.** A single box now registers new subscribers, with per-list control for shop managers, and customers manage newsletter and offers independently from their account.
* **Tidier checkout birthday field** — day, month and year sit on one row with a full-width explanatory note and a configurable highlight colour.
* **Accessibility fixes** — corrected ARIA usage on rating stars and gave promo and product-card links proper accessible names.
* **Faster perceived loading on category, page and blog pages** — the above-the-fold hero image is now prioritised, improving Largest Contentful Paint. Below-the-fold heroes stay lazy.

= 8.7 - 2026-07-13 =
**Block-library discoverability, plus a clearer block name.**

* **More native blocks now surface in the block editor and on the plugin page.** Recommendations, Product Slider and Product Variations Gallery gained a block-editor registration (they were front-end-render-only before), so they now appear in the inserter with a labelled placeholder and are listed among the blocks this plugin provides. Their front-end output is unchanged.
* **The full block library is documented** in the plugin description — brand, product, local-business (Google Reviews, Store Locator / Map, Opening Hours, Business Info…), content and archive blocks, grouped by purpose.
* **"Post Related Categories" is now "Post Related Product Categories"** to make clear it lists related WooCommerce product categories, not blog categories.

= 8.6 - 2026-07-13 =
**Your admin chat now fixes SEO for you — plus Google Search Console, backlink & disavow tools, a sharper and more relevant storefront assistant, lower AI/embedding costs, and a faster engine that shrugs off aggressive crawlers.**

* **Sales predictor rebuilt to run in seconds, not minutes.** The backtest accuracy step and the per-batch variation build joined the full order-line history on a computed key (`COALESCE(variation_id, product_id)`) that no index could serve, forcing MariaDB into full×full block-nested-loop scans of ~2–5 billion row-pairs per run (300–500s each). Order-line analytics now carry an indexed `effective_pid` column, the backtest is pre-aggregated once instead of a correlated per-row subquery, and every freshly-rebuilt staging table is `ANALYZE`d before it is joined — so the optimiser always picks an indexed nested-loop. Output is byte-for-byte identical (verified across every history row on live data); the nightly job just stops churning the database into swap.
* **Same fix applied across the physical-recovery and monolithic predictor paths.** The five stock-recovery-outcome joins and the legacy monolithic predictor now use the indexed `effective_pid` too.
* **Customer cumulative order-stats no longer stall.** The per-customer lifetime spend/items rollup was a `customeremail` self-join that flipped to a quadratic multi-minute scan whenever the underlying order table had just been rebuilt (stale statistics). It is now a single pre-aggregate pass — structurally impossible to flip — with fresh statistics forced before it runs.
* **Product Data Prep (vitals) rebuilt for speed and stability.** The nightly Data Prep run that computes every product's vitals — the metrics behind recommendations, badges, swatches, archives and analytics — could flip into multi-hundred-second full-table scans right after a staging table was rebuilt, because stale table statistics made MariaDB mis-plan the joins (the classic "n_rows reads as ~1" trap). Every vitals stage now refreshes its statistics and pins the correct index with typed join keys before it joins, so it stays on a fast indexed path; a built-in circuit breaker caps any single query's temp-table size and run time, and a plan-flip detector flags a regressing stage instead of letting it churn the database into swap. Identical output, a fraction of the time — and no more midnight swap spikes on large catalogues.

* **Sitemap & robots.txt scheme fix.** The XML sitemap and managed robots.txt are built offline (cron / WP-CLI), where WordPress cannot detect that the live request is HTTPS. On a site served over https but whose stored WordPress Address is http:// (the classic Cloudflare "Flexible" SSL / http-origin proxy setup), every sitemap `<loc>`, image URL and the robots.txt `Sitemap:` line could be written as http:// — so search engines were handed http canonicals for an https site. Every same-site URL emitted by the sitemap and robots.txt is now normalised to https (overridable via the new `Rooster One_seo_sitemap_scheme` filter for a genuinely http-only origin).

* **SEO Auto-Fix Assistant, in your admin chat.** Ask the Rooster One Insights chat to "fix my top pages" and it now works in two tiers, free before paid. **Free (no AI credits):** it sets the canonical URL and fills the focus keyphrase from the page's own top-ranking Google keyword — structural fixes that need no copywriting, applied instantly and re-scored, with one-click undo; it can also clear an accidental noindex on request. **AI credits:** the content-writing fixes — a SERP-aware SEO title + meta description, descriptive alt text for images missing it, and richer body content (drafted for review; approving saves a WordPress revision so you can roll back) — are written by the AI, drafted for your review by default. The assistant always tries the free fixes first and tells you the credit cost before writing across more than a few pages. A nightly free Autopilot can keep the structural fixes flowing (off by default, opt-in).

* **Google Search Console — your true traffic (new).** Connect Search Console (SEO → Search Queries) and see the real queries and pages that bring you Google organic clicks, impressions, CTR and average position — straight from Google — beside the DataForSEO ranked-keyword view. High impressions with low CTR flag a title/description the AI can rewrite.

* **Backlinks & toxic-link disavow (new).** SEO → Backlinks pulls your referring domains and their spam score from DataForSEO, flags the toxic ones, and generates a ready-to-upload Google disavow file — kept in sync as new bad links appear. (Google provides no API to submit a disavow, so you upload the file once at the Search Console Disavow Tool; we link you straight there.)

* **Content ideas from your customers (new).** The questions shoppers ask your storefront AI that it answers poorly — no matching products, or a low rating — are distilled into a demand-ranked list of content gaps, so you know exactly what to write next. Your customer assistant only surfaces the signal; it never changes your site.

* **Storefront AI assistant — more relevant answers, fewer wrong turns.** The product cards shown alongside a chat answer are now always tied to what the shopper actually asked, with a relevant-product fallback so the assistant never pads a reply with off-topic links. It understands your own Table Rate Shipping rules when answering delivery questions, and a configurable recency boost lets newer arrivals win when a shopper asks "what's new" or browses a fast-moving category (set your "new product" window under Merchandising → Badges). Answers also run to full length by default for more complete replies.

* **Lower AI costs — the semantic index only embeds what changed.** Building your recommendation & search index now embeds only the products, posts and pages that are new or have changed since the last run, instead of re-embedding the whole catalogue every time — a large saving on embedding spend for big or frequently-updated stores. (Switching the embedding model still rebuilds everything, as it must.) Product text is read from the pre-computed product vitals first and only reaches into the full content for the description, so each run is faster too — and the automatic nightly re-embed schedule now runs reliably.

* **Faster and more resilient under heavy crawling.** A few storefront helpers used to make a small uncached background request on every page view — the swatch add-to-cart nonce refresh, recommendation-impression logging, and the free-shipping progress bar's cart check. Under an aggressive SEO crawler those could multiply into a needless server-load spike. They now fire only on genuine shopper interaction (or only when there is actually a cart to sync), and automated JS-rendering crawlers are skipped outright — no change to what shoppers see or do, just no wasted load from bots.

* **Cookie scanner: off by default, on demand instead.** The consent banner's live per-visitor cookie-discovery sweep is now off by default. Your cookie & third-party-service inventory is built from the built-in database plus the on-demand "Re-scan storefront now" button (Consent → Cookie inventory), which loads your key pages in the background whenever you add a new service — so nothing scans on every visitor. Continuous live discovery can be switched back on any time.

= 8.5 - 2026-07-05 =
**SEO grows beyond the shop: site profiles for content & catalogue sites, Google-data-driven AI titles, conversion goals, campaign & exit-page analytics, and complete attribution in your order and form emails.**

* **Site profiles (new).** Tell Rooster One what your site IS — shop, catalogue (products presented as content, without checkout), or content/publisher — or let it auto-detect. Every SEO metric adapts: opportunity scoring, pillar pages and demand now work properly on content and catalogue sites instead of assuming a shop.
* **Content vitals (new).** The per-product health metrics gain a content twin: every post, page and custom type gets daily reach, engagement, freshness and demand scores — including reader time-of-day and day-of-month consumption patterns, the same lens the shop side has for buyers.
* **DataForSEO integration (new).** Connect a DataForSEO account per site (SEO → General) and Rooster One pulls a weekly snapshot of every Google keyword you rank for, computes striking-distance opportunities (positions 8–20 by search volume) and shows them on the Opportunities card — under a monthly spend cap you control.
* **AI titles & descriptions with live SERP context (new).** A nightly queue drafts new SEO titles and descriptions for your highest-ROI pages using the actual Google results for the target keyword — written to win the click against the competitors really shown there. Drafts wait for approval on SEO → Health, or switch on Autopilot.
* **Conversion goals (new).** Choose which Gravity Forms (plus the Newsletter plugin) count as conversions per site. Rooster One's AI reads each form and derives its goal context, which feeds the SEO descriptions of the pages hosting that form — and goal conversions flow into content demand and the new campaign analytics.
* **Campaign attribution in form notification emails (new).** Gravity Forms staff notifications can include the full campaign story — channel, all five utm parameters, landing page and original referrer — with no hidden form fields or per-site code snippets. Visitor autoresponders are never touched, utm form fields auto-prefill, and the page URL sent to HubSpot is cleaned of tracking parameters.
* **Order attribution emails, completed.** The "Order origin & attribution" block in staff new-order emails now always lists all five utm parameters — and it now also appears on orders paid by cheque, bank transfer or COD, which previously missed it on speed-optimised checkouts.
* **Landing pages & campaigns, canonicalised (new).** Session analytics now parse every visitor's landing page into a clean path plus utm parameters (per-click junk such as fbclid is dropped), with a durable per-day campaign × landing-page rollup: sessions, cart adds and goal conversions per campaign.
* **Exit pages (new).** See where sessions end, split by whether the visitor converted first — separating natural end-of-journey pages from the pages that bleed visitors.
* **Ask the insights chat.** New chat skills: ranked keywords, the striking-distance list, the content-vitals leaderboard, landing-page campaigns and exit pages.
* **Redirect import safeguards.** Imports now verify that every redirect target exists on THIS site and refuse any rule that would create a redirect loop at any depth.
* **Cookie consent: position the floating button per device.** The floating "Cookie settings" button can now be placed Left, Centre or Right with exact pixel offsets from the edge and the bottom — separately for desktop and mobile — so it aligns cleanly with other floating widgets (chat bubbles, scroll-to-top). When the Side Cart bottom navigator is active, its coordinated styling automatically takes precedence on mobile.
* **Search Console fixes.** Paginated pages emit correct self-canonicals and sensible robots defaults, addressing "Alternative page with proper canonical tag" and "Duplicate without user-selected canonical" warnings on content sites.

= 8.4 - 2026-07-04 =
**A media-library cleanup tool, a per-user landing page that can resume where you left off, an admin usage dashboard, a managed robots.txt, and more resilient background jobs.**

* **Media Cleanup (new).** A Tools & Settings tool that reclaims disk space by finding and removing image files your site no longer needs — thumbnail sizes your current theme doesn't register, true orphans with no media-library record, and images left behind by products you deleted. It scans in resumable batches (built for libraries with hundreds of thousands of files), moves everything it flags to a recoverable quarantine first, and only deletes for good when you choose to empty the quarantine — with removing the matching media-library records kept as a separate, off-by-default opt-in. A file is only ever touched when nothing on the site references it anywhere — product galleries, variation swatches, brand logos, page/post content, widgets, menus and theme options are all checked, WebP and AVIF included — so an image still in use is never removed.
* **Choose where you land — or pick up where you left off.** A new My Settings card lets each user set which e-shop Manager card the page opens on, instead of always landing on the same default. Pick any card, or choose "continue where I left off" and Rooster One returns you to the last card you were working in.
* **Admin usage dashboard (new, administrators only).** A Tools & Settings panel, visible only to site administrators, that reports how the Rooster One admin is actually used — page views, active users, sessions and most-opened cards — in total and per user, over a time window you select. Lightweight, self-pruning (kept for 180 days), and never shown to non-admins.
* **Managed robots.txt (new).** The built-in SEO engine can now manage your robots.txt alongside the XML sitemap: it serves a correct, sitemap-referencing robots.txt (honouring "Discourage search engines"), lets you add your own custom rules from SEO → Redirects, and writes a static file at the web root so your server can serve it directly. It only ever acts when Rooster One SEO is switched on and no other SEO plugin (Yoast, Rank Math, AIOSEO) is handling robots — and it never overwrites a robots.txt it didn't create.
* **More reliable background jobs.** The protection that stops a mis-behaving recurring task from piling up thousands of duplicate scheduled actions now covers the full set of AutomateWoo jobs and WPForms' spam-purge and form-locator tasks — not just log cleanup — so low-traffic sites keep a clean, fast Action Scheduler queue.
* **Fixes & polish.** The image picker on the SEO → Schema and Social cards now opens reliably (it previously failed to attach on pages where the media library loaded late). Greek translations refreshed, including the Amazon Selling-Partner catalogue and order-import strings.

= 8.3 - 2026-06-26 =
**One-click product import from your marketplaces, an AI-chat analytics dashboard, and a single unified admin navigation.**

* **Catalogue Importer (new) — import your products from eFood, Etsy, Wolt and Amazon.** The mirror image of the marketplace catalogue exports: enter your marketplace API keys, choose a source, and Rooster One recreates the products in your store with one click — auto-building the category tree, product attributes and food option-groups each product references, sideloading its images, and matching on SKU so a re-run updates products in place instead of duplicating them. Imports as Draft + new-only by default (each a per-run toggle, alongside Create + Update and Update-only). A new **Enrich** mode fills gaps on existing products without overwriting anything you already have — so you can, for example, create products from Wolt (for their ingredient / topping option-groups) and then enrich from eFood or Amazon to fill in barcodes. Amazon reads your own Seller listings through the Selling Partner API (no extra AWS keys needed); eFood, Etsy and Wolt use their catalogue APIs.
* **AI Chat Analytics (new, Pro).** A Customer-Profiling dashboard that turns your AI chat history into insight: a searchable conversation log plus aggregate metrics — which page each conversation was opened from (read from the existing Session Tracker, not a second tracker), question volume and topics, the satisfaction ratings customers leave, and chat-assisted conversions (orders that followed a chat, precomputed and cached the same way Competition conversions are — never calculated live on page load). Conversation-history retention is configurable, 90 days by default.
* **Unified admin navigation.** The three Rooster One admin pages — Analytics & Shop Recommendations, e-shop Manager and AI Chat — now share a single menu bar that highlights the section you're in, replacing the old top tab-strip and the separate per-page tables of contents. New "Set Up" and "AI Chat" menu groups deep-link straight to each page's individual cards, so everything is one click away from anywhere.
* **Quick Navigator finds features by what they do.** The Ctrl/Cmd-K Quick Navigator now matches synonyms and capability terms as well as names — so "amazon", "barcodes" or "import" jump to the Catalogue Importer and "happiness" or "sentiment" to AI Chat Analytics — and cross-page results now show the correct section badge.
* **Fixes & polish.** The SEO → Redirects "Rebuild SEO index" card now remembers the object types you last rebuilt (Posts / Pages / Products / Attributes as well as the taxonomies) and pre-ticks them on your next visit, instead of always resetting to the terms-only default.

= 8.2 - 2026-06-25 =
**A built-in FAQ manager, a new "Custom Post Types" admin section with a unified Store Pages panel, scheduled Google-review refresh, Courier Center end-of-day reconciliation, more reliable controllable background jobs — plus an opt-in Food & Beverages product-options toolset and new marketplace connectors (catalogue export + order-taking) for eFood, Wolt, Etsy and Amazon.**

* **Built-in FAQ manager (new).** A self-contained FAQ system — an FAQ content type (title = question, answer in the block editor) with category-style FAQ groups, managed from a dedicated admin panel where you create / rename / delete groups, add and edit questions, and drag-and-drop to reorder or move a question into another group (everything saves instantly). Drop the `[faq]` / `[Rooster One_faq]` accordion shortcode on any page — optionally scoped to one or more groups (`group="shipping,returns"`), rendered as titled per-group sections (`sections="yes"`), or limited to specific entries; a bare `[faq]` lists every published Q&A. Self-contained, theme-agnostic markup with its own styling.
* **New "Custom Post Types" admin section.** The horizontal admin navigation gains a group that gathers the editorial content types in one place — FAQ, Events, Competitions, Locations & Reviews, and Store Pages. Events and Competitions moved here from Customer Profiling and Locations & Reviews from Catalog Sync (same panels, clearer home), and the store-location, store and FAQ post types no longer add their own clutter to the WordPress sidebar.
* **Store Pages panel.** A single screen listing every store / location page on the site — both the theme's store pages and the plugin's store pages — with type, bound Google location, status and Edit / View links. The store-page settings (enable, URL base, labels) moved here from SEO → Schema, so configuration and the page list now live together.
* **Scheduled Google-review refresh.** Reviews used to update only when you clicked "Fetch all", so they silently went stale; they now refresh automatically on the cadence and run-time you set (daily by default), keeping each location's rating and review snippets current. The refresh arms itself only when at least one location has a valid Google API key and place ID — a site that never configured reviews never makes a single Google API call — and it respects per-hour / per-day quota caps (defaults 20/hour, 500/day). The manual "Fetch all" button ignores the caps so an operator-initiated run always completes.
* **Courier Center end-of-day reconciliation.** Courier Center (Qualco "Deliverd") has no separate close API, so Rooster One now reconciles each day through its official `/Manifest` pickup list — the carrier's end-of-day close — and stores the returned manifest PDF as the closing document. "Close & print", the batch "close pending now", the daily auto-close, and "reprint last closing" now self-route by carrier: Geniki uses its close API, Courier Center uses the manifest, and carriers with no end-of-day API get a local manifest close — so every carrier is reconciled, not just Geniki (a per-carrier close on a non-Geniki courier previously failed with a "does not support close_pending" error).
* **Smarter background jobs.** Scheduled jobs no longer do pointless work on installs that haven't set the feature up yet: order-cancellation metrics recompute only on Pro, courier tracking and auto-close run only once you've created a shipment, the monthly AI-model refresh wakes only when your Rooster Content Connector token is set, and session-analytics rollups run only when session tracking is switched on. Fresh sites stay quiet until the relevant feature is actually in use.
* **More control over the always-on jobs.** A new "Automatically capture abandoned carts every hour" toggle lets you pause the hourly capture from the Saved & Abandoned Carts screen (it saves the moment you flip it), and session analytics honours the existing tracking switch — while the manual "Capture now" and "Rebuild now" buttons still run on demand even when the automatic job is off.
* **Self-healing schedules.** If a plugin update or a wiped cron table ever drops a scheduled job, Rooster One now quietly re-creates it — your automated marketplace product feeds and AI analytics / embeddings updates keep running instead of silently stopping, with no need to re-save settings. Only jobs you have already enabled are re-armed.
* **Much faster Competitions tab.** The Competitions admin page used to rebuild its entrant-revenue and Insights figures on every load — a heavy cross-table calculation that made the page take several seconds to open. Those figures are now precomputed in the background, so the page renders them instantly, with an **Auto-refresh** control (Off / Hourly / Daily / Weekly / Monthly, default Daily), a manual **Refresh** button, and an automatic background update shortly after each new entry.
* **Food & Beverages: product options & modifiers (new, opt-in).** A toolset for food and made-to-order products, off by default behind a single "Food & Beverages" switch (Custom Post Types → Food & Beverages) so shops that don't sell food never see any of it. Build reusable option groups — sizes, toppings, with / without extras — and attach several to one product at once from its new "Options" tab. Each group is single- or multi-select with min / max counts (so a shopper can pick more than one in a single go, the way the colour-variation multi-add works); each option carries its own price, with support for a free allowance ("first 3 toppings free"), "always charged" premium options, and prices that vary by size or per product. Shoppers choose on the product page with a live running total and sold-out options flagged immediately; the selection carries through to the cart, checkout and the saved order.
* **Catalogue & menu exports for eFood, Wolt and Etsy.** Three new templates on the Marketplace Feeds page export your catalogue in each platform's own JSON shape — eFood products, Wolt menu items, and Etsy listings (with per-shop who-made / when-made / taxonomy / shipping-profile defaults you set once) — alongside the existing Skroutz, Shopflix and generic CSV / XML feeds.
* **Order-taking from eFood, Wolt, Etsy and Amazon.** Four new connectors in the Marketplace Order Importer pull orders straight into WooCommerce — Etsy (Shop Receipts) and Amazon (Selling Partner API) by polling, eFood and Wolt by signed webhook. Every marketplace has its own on / off switch, and the 5-minute background poll only runs while at least one polling marketplace is actually connected, so it never burdens a store that isn't using it.
* **Fixes & polish.** The account "Communication" page no longer rewrites every main-menu label to "Communication"; the My Account login / register page no longer shows the social sign-in buttons twice (they render once, inside each form); the Brand Story block's opening heading reads "About the Brand"; the redundant "Products" sub-heading was removed from the brand and category archive layouts; and the Navigator's category highlights (the middle column shown when you select a category) now order the Brands and Needs blocks to match your Navigator → Group order, instead of always listing Needs first.

= 8.1 — Events (Beta) & Competitions, a richer storefront block library, storefront polish (20/06/2026) =

* **Events (Beta).** A complete event-management module modelled on Competitions: an Events CPT with a participants table, XLSX/CSV participant import (update-vs-overwrite), tokenised one-click RSVP confirm/decline, parametric newsletter invitations through The Newsletter Plugin ({salutation}/{title} merge, BUILD + dry-run only — never auto-sent), front-end self-registration via a new `aieo/event-registration` block and `[aieo_event_register]` shortcode, a Google Maps location URL, quick-create JS, and an attendance stats panel with XLSX export. Admin-plugin only.
* **Competitions.** A competitions / giveaway module sitting alongside Events.
* **AIEO Product Slider block.** A horizontal product slider with the exact look of the product-page recommendation rails (thin uppercase title + underline, then cards) — manual title, filtered by category, tag and/or a specific set of product IDs. Replaces the legacy OM `[responsive_product_slider]` shortcodes.
* **AIEO Category Footer Hero block.** Lays a product category's SEO footer text beside the category image (image left, small rich text right) with the hero divider line cutting across the image — the horizontal counterpart to the category hero, for the bottom of the archive.
* **AIEO Trust Badges block.** A configurable trust strip of icon + title + subtitle columns (shipping / payment / returns / quality), with four bundled icons.
* **"Feature heading" opt-in for blocks.** The Brand Slider, Google Reviews and Latest Posts Overlay blocks gained a toggle to render their heading in the big thin-uppercase + full-width-underline style the product sliders use — inherited from one source so it never drifts, with the underline contained to the body width on the constrained blocks.
* **AIEO Latest Posts Overlay.** Now supports an optional section heading (with the feature-heading style) and a "glass" card style — tall portrait cards with a frosted-glass info bar — reproducing the legacy live blog layout.
* **Blog category archives.** A redesigned blog (sub)category header: a featured latest-post hero with the category-hero look, a subcategories dropdown, and a category lead, applied across every blog category and subcategory.
* **Product archive cards.** Evened the QUICK VIEW ↔ ΑΓΟΡΑ spacing between variable and simple products (the WC variation-form chrome no longer adds height above the buy button on image/colour-swatch products), tightened the variation swatches, and centred the buy-button label.
* **Side-cart.** The "You might like" recommendations sidebar now hides itself entirely when there are no recommendations (or no seed product) instead of showing an empty pane — the cart takes the full panel width.
* **Greek translations.** Customer-facing recommendation rail titles reworded from back-office jargon ("cross-sells / up-sells") into natural shopper language, plus footer trust-badge copy.

= 8.0.1 — Promo Surface full-width + single consent control (16/06/2026) =

* **Promo Surface "Full width" now bleeds edge-to-edge when nested.** The `aieo/promo-surface` block already forced a full-bleed when it was a direct child of the theme's constrained root, but on a *programmable* front page (where the page is rendered through `wp:post-content`) the surface sat one level deeper and kept its parent's root-padding-inset width, leaving a side gap. The full-bleed rule now sets an explicit `width:100vw` (not just `max-width`), so the surface fills the viewport regardless of nesting depth.
* **One cookie button, not two (consent control de-duplicated).** The first-party CMP rendered its own floating "reopen" button AND the side-cart bottom bar rendered a separate bespoke cookie item — two controls opening the same modal (a duplicate on mobile, and the bar one leaked onto desktop). They are now a single control: the side-cart bar's consent item reuses the CMP's `.aieo-cmp-reopen` styling (the themed floating circle on desktop, via `AIEO_Consent::reopen_button_vars()`) and flattens into the bar on mobile, while `AIEO_Consent::render_reopen()` suppresses its standalone button whenever the bar carries it (`AIEO_Side_Cart_Display::consent_button_active()`). No duplicated markup; styled per breakpoint. (Shared `class-aieo-side-cart-display.php` updated in both the admin plugin and `ai-eshop-optimizer-runtime`.)

= 8.0 "Fable / Mythos 5" - marketplace-feed URLs + an attribute-driven product-colour pipeline for SEO and feeds (14/06/2026) =

* **Absolute marketplace-feed links.** Products with an SEO canonical were being exported with a relative `<g:link>` (no domain), so Google / Skroutz silently dropped them. The catalogue build now absolutises the canonical into the core-vitals product URL, with a defensive absolutise at feed output; the sitemap and the on-page canonical tag were already correct.
* **Product colour from your attributes.** A new "AIEO colour context" flag (Products -> Attributes, with a one-click bulk action) marks which swatch attributes represent a colour; the catalogue build reads the term NAME (e.g. "French Caramel") into the product colour used by the JSON-LD schema and the marketplace feeds, as real per-variant values rather than slugs. Completes the 7.4 colour follow-up (parents stay clean: Google carries colour on each variant plus variesBy:color).
* **Platform.** Asset-minification system (minified CSS/JS served automatically), an SEO opportunities scorer + module, session analytics, the Courier Center fulfilment driver, and SQL runtime helpers. Requires-PHP floor set to 7.4.

= 7.4 Merchant-listing & Local SEO schema completeness — clear Google Search Console's "missing field" warnings across Product and LocalBusiness, plus a clean Channel view for attribution. Now requires WordPress 7.0+ (11–12/06/2026) =

* **Product `color` on every product.** The Product / ProductGroup schema now ALWAYS emits a `color` property, read straight from the core vitals colour (the single source of truth). Variable products carry real per-variant colours (and `variesBy`); simple products emit the field present-but-empty until you designate a colour-denoting attribute to populate vitals — a guided follow-up documented in `documentation/SEO_SCHEMA_NEXT_OPTIMIZATIONS.md`. No data keys were faked: the empty value is honest, and fills in automatically once vitals colour is populated, with no further code change.
* **Shipping & returns on every product Offer.** A new "Returns & shipping" card in the SEO → Schema tab emits `OfferShippingDetails` + `MerchantReturnPolicy` on each Offer — return window (days) + free-returns flag + country, and shipping rate + handling/transit-time range + country. Both are OFF until you enter values, because wrong terms trigger Merchant Center issues; once on, they apply site-wide to every product and variation.
* **`productGroupID` "invalid string length" fixed.** A long slug-style parent SKU exceeded Google's ~50-char item-group-id limit and was rejected; the group id now falls back to the stable numeric product ID when the SKU is too long.
* **LocalBusiness `priceRange` + `image` per store.** The Locations & Reviews location editor (Schema extras) now offers a Google-recognised price-tier selector (€ / €€ / €€€ / €€€€) and a WordPress media-gallery image picker with preview. Both persist per location and feed each store's `HealthAndBeautyBusiness` node, clearing the "missing image / priceRange" Local-SEO warnings across every page that carries the store graph.
* **UTM Explorer — new "Channel" dimension.** A top-level breakdown by the RESOLVED marketing channel, with consolidated friendly labels — paid Google cleanly separated from Organic Search (organic + organic_search merged), plus Facebook – Paid, Direct, Skroutz, Instagram, Phone, etc. The Source view additionally relabels paid traffic so Google Ads no longer hides inside the organic `google` bucket; raw `utm_source` is preserved underneath. Labels are display-only — the stored channel keys other modules match on (ROI Wizard, ad connectors, Enhanced Conversions) are untouched.
* **Attribution accuracy.** Order analytics (`wp_aieo_order_stats`) now bucket by the site's configured WordPress timezone instead of UTC, so AIEO's daily order counts/revenue match WooCommerce Analytics day-for-day; and the self-referral "internal" channel folds into the standard "(direct)" bucket.

= 7.3 In-house SEO engine — replace AIOSEO/Yoast with a faster, Greek-aware engine: rich commerce + local-business + image schema, redirects, a static sitemap, demand-aware scoring + Greek AI Assist, and an AIOSEO migration with a pre-cutover verify — all served from materialized data at ~0 ms (09–10/06/2026) =

* **A complete on-page SEO engine, folded into AIEO.** Title, meta description, canonical, robots, Open Graph and Twitter cards plus the JSON-LD `@graph` are now AIEO's to emit — built ONCE into a head cache and served by the thin runtime in a single cached read. No per-request assembly, no Vue admin SPA, no telemetry, no licence calls: ~0 ms added TTFB versus the 100–300 ms AIOSEO/Yoast/RankMath add per render. It runs **augment-only behind your current SEO plugin** (changes nothing on the page) until you turn it on, so 7.3 is safe to deploy ahead of any cut-over.
* **Canonical category, one resolver.** Pin one canonical category per product (the AIOSEO "primary category" mechanism) and a single resolver drives the **permalink, the `<link rel=canonical>` and the sitemap entry** in lock-step — they can never drift apart. A "SEO" editor metabox offers the canonical-category picker (plus title / meta / canonical override / robots), and a chunked bulk tool sets it across a whole catalogue.
* **Rich, correct commerce schema — entirely from the core vitals table (no live WooCommerce queries on the build path).** Variable products now emit a `ProductGroup` with `hasVariant` / `variesBy` so Google surfaces the variants instead of collapsing them into a phantom single item; on-sale products carry a `UnitPriceSpecification` strikethrough (the "was" price); plus `gtin`, `Brand`, and operator-configured `MerchantReturnPolicy` + `OfferShippingDetails` (off unless they reflect your real terms). Category, brand, attribute and tag archives are first-class landing pages too — `CollectionPage` + a product `ItemList` + `BreadcrumbList` + `inLanguage` — and their canonicals are the pretty `/product-category/…` URLs (a query-string-canonical bug from early builds is fixed).
* **Local SEO for physical stores.** A `LocalBusiness` node per shop, built from your Locations & Reviews Google locations — address, opening hours, geo, "Open in Maps" / "Rate us" links — linked under the site Organization, with one location pinned as HQ. Three new storefront blocks (**Store Locator**, **Opening Hours**, **Business Info**) render the same data anywhere, and an optional **store-page post type** lets each shop have its own page; you choose its URL base and label (nothing is hardcoded), and store pages get their own sitemap entries. Stars are never self-emitted (they stay on your Google Business Profile, per Google's policy).
* **Image SEO (no AI, no credits).** Empty product featured-image alt text is auto-filled from the product title (or your imported format) — only empties, so any alt you or AIOSEO already set is preserved — and one `<image:image>` per product is added to the sitemap for Google Images.
* **Redirects with an automatic slug-change monitor.** Rename a product or post and the old URL keeps working (an automatic 301), so the canonical/permalink changes at cut-over never 404. A clean unique-404 list (deduplicated, with hit counts) offers a one-click "Create redirect". Served at the nginx edge before PHP where available, with a PHP `template_redirect` fallback for portability.
* **A static, outage-proof sitemap.** Cron-built to static `.xml` files — chunked into shards of ≤2,000 URLs plus a sitemap index — and served as files. It keeps serving even if the plugin is deactivated or broken (no repeat of the "two weeks with no sitemap" failure mode).
* **Demand-aware SEO score, health dashboard & Greek AI Assist (day one).** A live 0–100 score with a checklist in the editor, a "SEO Health" dashboard that lists the **highest-demand** low-scoring pages first (not alphabetical), and one-click Claude **AI Assist** — generate/improve title, meta description, summary and keyphrases — fluent in Greek from the start.
* **AIOSEO → AIEO migration engine + a pre-cutover verify.** A read-only importer copies your **entire** AIOSEO configuration — per-object meta, global settings (separator, Organization, social, robots, per-type/taxonomy formats), the image-alt format, and redirects — into AIEO storage, with a mapping report that lists every field as mapped / transformed / dropped (deprecated **FAQPage/HowTo schema is stripped**, not migrated as zombie markup). Then a one-click **"Pre-cutover verify"** compares the head AIEO would emit against your LIVE head over a sample of products, categories and pages, flagging any title / canonical / robots drift and confirming every canonical equals its permalink — so you flip the switch with confidence and keep AIOSEO installed-but-inactive as a rollback.
* **EU Omnibus reference price.** A 30-day-lowest-price history feeds the legally-required "lowest price of the last 30 days" reference on reductions.
* **Multilingual.** Per-language head + `hreflang` for WPML/Polylang (including Polylang, which AIOSEO never localised), and a TranslatePress-aware sitemap that emits the per-language prefixed URLs.
* **Core vitals carry the canonical.** Each product's `product_url` in the core vitals table is now its SEO canonical where one exists (otherwise the existing reference is left untouched); the column was widened to 300 characters and the write is bounded, so a stray over-long canonical can never overflow or fail the catalogue rebuild — our most load-bearing table.
* **Editor blocks discoverable again.** All AIEO blocks now appear in the inserter regardless of a block theme's curated block-palette (e.g. roosterX), and every block title is prefixed "AIEO" so they're findable by search; product-context blocks (swatches, PDP messages…) stay correctly scoped to single-product templates.
* **Fixes & runtime.** Fixed a 404 / MIME-type console error from a retired product-labels stylesheet that was still being enqueued. The thin front-end **runtime plugin moves to its own 1.0 version track** and now also serves the SEO head, the sitemap and the redirects with the core plugin trimmed from the request.

= 7.2 TikTok conversions, consent carried on every event, runtime-owned measurement, in-request event delivery — and the searchable ROI / UTM reports (08–09/06/2026) =

* **TikTok added to Pixels & Conversions.** TikTok joins Meta and Google as a fully-owned platform — a browser **TikTok Pixel** and the server-side **Events API**, deduplicated on a shared event id, with the click id (`ttclid`) recovered from the captured attribution session. Same consent-gated architecture as the Facebook CAPI; spec-verified against TikTok's current docs.
* **Consent travels with every event (in-band signalling).** Beyond the consent gate, AIEO now tells the ad platforms the consent state *on each event*: region-aware **Google Consent Mode v2** defaults (deny in the EEA, grant elsewhere, emitted before any tag fires), GA4 Measurement-Protocol top-level **consent**, Google Ads per-conversion **consent**, and Meta CAPI **Data Processing Options** — so a declined category down-scopes the conversion at Google / Meta / TikTok too, not just in the browser. Consent is snapshotted onto the order at checkout so the asynchronous server sends carry the right state.
* **The runtime owns measurement when present.** When the premium runtime plugin is active it serves all three browser pixels (Meta / TikTok / Google tag) **and** the three server senders itself — even on requests where the core plugin is trimmed — by lazy-loading the core send logic by path. The core plugin stays fully functional on its own; each surface is gated so exactly one of the two serves it.
* **Event delivery rebuilt for scale.** Server-side conversions no longer queue through Action Scheduler. They flush the page response to the shopper first (`fastcgi_finish_request`, LiteSpeed too) and send in the *same* request — zero checkout latency, no WP-Cron dependency, and nothing to back up at thousands of events a minute. A **"Fire-and-forget"** toggle in Pixels & Conversions (on by default) frees the worker the instant each event is sent; switch it off to wait for and log every platform's reply (sent / failed) while validating a setup.
* **Order origin in staff e-mails.** New-order staff notifications now show where the order came from — the marketplace (Skroutz / ShopFlix / eMAG …) or the site with its marketing channel and campaign — read from the one canonical order-facts source. (This replaces the PixelYourSite origin line that frequently failed to render.)
* **Ad-connector setup links.** The Google / Meta / TikTok credential wizards now link straight to where each value is found, so the "what to ask your agency" guidance is actionable.
* **UTM Explorer (new report).** A cascading drill-down across the five campaign tags — Source → Medium → Campaign → Term → Content — where each level is a searchable multi-select that narrows the lists below it to what actually co-occurred under your choices. It lives on the ROI Wizard page (and is findable from the admin command palette by searching "utm"). The table breaks the current selection down by the next level, with orders, revenue and average order value.
* **Searchable multi-select across the whole cockpit.** Every selector in the ROI Wizard and UTM Explorer — the **Type**, the exact detected **value**, the five UTM levels and the ad-spend **ledger value** — became the same fast searchable picker used for product selection (search, tick several, Done). Choosing from hundreds of creatives or campaigns now takes seconds instead of scrolling a giant dropdown. **Type** accepts several types at once and stacks one results table per type; **Exact** offers the union of the selected dimensions' values.
* **Reco lift per channel.** A new ROI type that shows the recommendation engine's incremental orders and € *over and above* each traffic channel — of the orders Google / Meta / organic brought, what share the recommendations assisted and what they added.
* **Period comparison (both reports).** Compare any result against the **previous period** or the **same period last year**, with a green / red Δ% shown inline on every metric. Off by default.
* **Report polish.** The UTM Explorer is consolidated onto the ROI Wizard page (ROI → UTM → ledger order); From / To dates lead each row; rows are top-aligned so selecting a value no longer nudges the controls; the Ad-spend connectors moved into a renamed **Tools & Settings** group; the default date range is the last 30 days.

= 7.1 First-party measurement & consent, then the ROI Wizard & ad-spend connectors (Google · Meta · TikTok), one canonical order revenue/channel (06–08/06/2026) =

* **Pixels & Conversions (server-side measurement).** AIEO can now own the Facebook (Meta) Pixel and Google Analytics 4 end to end — a thin browser pixel **and** server-side Conversions API / GA4 Measurement Protocol, deduplicated on a shared event id, sent after the order is saved (zero checkout latency). Each platform is selectable, with master off-switches so you can keep PixelYourSite; Facebook credentials can be read from PixelYourSite if present.
* **Advertiser-grade match quality (PixelYourSite-Pro parity).** Facebook browser **Advanced Matching** (hashed client-side, consent-gated) on top of the full server-side set; **complete GA4 user-data** (name + address, Unicode-correct for Greek); a built-in **Google tag** loader (gtag.js or a GTM container, wired to Consent Mode v2); and **Google Ads Enhanced Conversions** both in-browser and **server-side via the Google Ads API** (keyed on the captured gclid).
* **Consent / GDPR — first-party CMP.** A lightweight first-party cookie-consent banner (no external CMP, no IAB TCF bloat): rich-text message, three actions (Accept all / Decline / Customize) with a per-category preferences panel, per-button theming with an equal-prominence guard, two layouts (bar or centre glass pop-up), a floating "Cookie settings" re-open button, and a policy-version re-prompt. Drives Google Consent Mode v2 and gates AIEO analytics plus the Facebook / GA4 senders, with a built-in cookie scanner.
* **Checkout timing.** Active vs idle time is measured for each successful checkout and aggregated per product, so offer timing (exit-intent, etc.) can be set from real deliberation data; coupon-completed orders are tagged and excludable from the baseline.
* **Custom Tabs + Product Tab Ordering (Product Display).** Up to five extra renamable product tabs (each with its own rich text per product, auto-hidden when empty; one-click migration from the legacy Pods usage/specification fields), plus a drag-and-drop card that orders the WooCommerce tabs together with the Custom Tabs on both block and classic themes.
* **ROI Wizard — one cockpit for "what actually drove the sale".** A new **Attribution → ROI Wizard**: pick a **type** (⭐ Recommendation engine, Offer, Channel, Campaign, Creative), then the exact detected value, then a period — and see orders, revenue, cost, net, **ROAS** and **ROI %**. AIEO's own contribution is front and centre: recommendation-assisted sales and offer effectiveness (free shipping, gifts, discounts) are quantified right next to marketing channels and campaigns. Revenue is the order AIEO computes; offers carry their *real* cost automatically (free-shipping uses the courier rate already computed in Fulfillment), and channels/campaigns use the ad spend you enter or sync.
* **Ad-spend ledger + bulk CSV.** A per-period, per-dimension ad-spend ledger backs channel / campaign / creative ROI. Enter spend inline, or **export a CSV, fill a whole quarter in a spreadsheet, and re-import** — manual entry, CSV and the connectors all land in one place, summed over your reporting window.
* **Ad-spend connectors — Google Ads, Meta, TikTok.** Connect each platform once through a guided credential wizard (with exactly *what to ask your ad agency for*); AIEO then pulls campaign spend nightly into the ledger, so ROI becomes automatic and you never leave AIEO to reconcile spend against revenue — one cockpit for spend AND your own recommendation / offer / channel attribution. Credentials are stored encrypted; the pull is read-only.
* **One canonical order revenue + channel.** A single source of truth for each order's revenue and marketing channel (`AIEO_Order_Facts`), reading from the order AIEO computes, with a documented map of where every order fact lives — including why the WooCommerce total and the ERP invoice total are *intentionally* different (the reconciliation behind pickup-store invoicing). The offer-effectiveness report now reads the canonical channel, so per-channel offer ROI no longer mislabels orders as "unattributed" when they were placed before attribution caught up.
* **Accurate engagement & attribution.** The engagement score is now one canonical formula everywhere (it previously differed between the AI-chat context and the analytics reports). Re-delivered tracking beacons can no longer double-count add-to-cart totals (idempotent, deduplicated server-side). The Attribution dashboard no longer writes thousands of rows on every page view — the channel back-fill moved to an hourly background job — and all of its channel cards now use one consistent 7-day attribution window.
* **Storefront & block editor.** Carousels (Brand Slider, recently-viewed and the like) gained an optional **"Recos carousel" slider style** — the pink scroll-progress bar matching the recommendations carousel — selectable per block; the **Google Reviews** block gained a true manual swipe-scroll mode. Fixed block-editor errors ("Invalid parameter(s): attributes") that appeared on AIEO blocks under WordPress 7 by registering the shared responsive / section-header attributes server-side.
* **Housekeeping.** The server-side conversion log now self-prunes (30-day retention). Fixed a stored-procedure installer that, because of a `DELIMITER` directive, had silently never updated the session-analytics procedures.

= 7.0 Product-page layout builder (block + classic themes), reusable product/variation picker, master Button Styles (padding/sizing/glass), side-cart mobile bar styling, wishlist & brand in the layout builder, sticky admin navigation (05/06/2026) =

* **Side-cart mobile bottom bar — fully theme-independent + styleable.** The mobile sticky bottom bar (Navigator / Search / AI Chat / Cart) gets its own controls on the Side Cart tab: bar background colour + height, icon colour, and the cart-count number + circle colours (each can differ from desktop). A new **glass effect** renders the bar semi-transparent with a frosted backdrop-blur (opacity + blur configurable) so the page shows through. New **per-option "selected" colours** (background / text / border for each of Navigator, Search, AI Chat, Cart) highlight an option while its panel is open. When ONLY the cart icon is enabled you can show it as a **floating bubble** (like the desktop cart) instead of a full-width bar, and a lone cart icon is now centred with its count badge correctly anchored.
* **Side-cart display owned by the runtime.** The whole side-cart surface (the floating shell, the mobile bar, the slide-out panel and its assets) moved into one shared class bundled in both plugins, so the runtime renders it even when the admin plugin is trimmed from a request; the admin module remains the standalone fallback.
* **Product Needs — new "Pills" display.** Alongside the stacked list, the product-needs taxonomy can now render as tag-style pills laid out side by side, with their own text size, corner radius, vertical / horizontal padding, gap, background, border (width + colour) and text colour.
* **Master Button Styles — padding, sizing and glass.** Every master button group (Primary / Secondary / Archive) now also controls **Top / Right / Bottom / Left text padding** and **min / max width + height** (0 = no constraint), plus an opt-in **glass effect** (transparent background via `color-mix` + backdrop blur, opacity + blur per group). The Secondary group gained full hover parity — a base border plus hover background / text / border colours — to match Primary and Archive.
* **Wishlist + Brand in the product-page layout builder.** "Add to Wishlist" is now a positionable element in the Display Order list with a **Beside image / Beside the product title / Under image** choice (the heart sits inline next to the title by default). Brand Display gained the same **"Beside the product title"** option, and the builder's placement is now authoritative over the per-module Brand position setting.
* **Admin polish.** Fixed the "AI Optimizer" toolbar icon occasionally stacking above its label (a theme `img{display:block}` rule). Reordered the AI Optimizer sidebar submenu to **Data Prep → e-shop Manager → AI Chat → Interactivity (IAPI) → Rec Cache** and removed the one-off Session Schema Migrator from the menu. The AIEO admin **top bar and the e-shop Manager / Analytics sub-tab navigation are now sticky**, staying visible as you scroll long settings pages.

* **Product-page layout builder — one list orders the whole product info column.** Storefront Display → Single Product Page → Dashboard now has a single drag-and-drop "Display Order" card that governs the vertical order of EVERYTHING in the product info column: the core elements (title, rating, short description, sale-eligibility and free-shipping messages, price, add-to-cart) AND the info modules (product meta, categories, brand, payment logos, trust badges, back-in-stock waitlist, free brand gifts, complementary products, product needs, role-pricing login). Each module also gets a per-item "Beside image / Under image" choice, so it can be moved beneath the gallery. The same saved order is honoured on BOTH the block (FSE) theme — via CSS `order` on the info-column flex children — and on classic themes (Botiga / FemmeFatale-V2), by re-prioritising the matching WooCommerce single-product-summary hooks (WC core templates + AIEO modules), so the two render identically. Core blocks that ignore `className` (rating, short description, add-to-cart) are now wrapped so their order always applies, and Brand Display's before/under-title placements follow the list instead of being pinned above the title.
* **Restored the product "ΚΑΤΗΓΟΡΙΕΣ" (Categories) line as its own positionable module.** When AIEO replaced WooCommerce's native product-meta block (SKU + categories + tags) with its SKU/barcode strip, the categories line was dropped. It is back as its own orderable module — a clickable comma-separated list, styled to match the SKU/Barcode rows (label and list flow as one inline stream, with uniform vertical spacing) — placeable before or after Product Meta. The Role-pricing "log in to see your price" message is likewise positionable within the info column. (Product Categories was also moved to the "Single Product Page" section of the Storefront Display menu, next to Product Meta.)
* **Reusable product / variation picker on every product-criteria field.** A shared modal browser — search by name, SKU or brand; pick simple products, whole variable products, or specific variations; drafts and deleted items shown greyed, variations badged — replaces the free-text ID/SKU/barcode boxes on the offer forms: **Product discounts, Free gifts and Free shipping** (both the "specific products" and the "excluded products" lists), plus the **Product Exchanger** feed builder and the **marketplace feed exporter**. Picked variations roll up to their parent so cart matching is unchanged, and existing saved selections migrate automatically. One shared implementation (`AIEO_DMM_Product_Picker`) drives them all.
* **Master "Button Styles" control (Tools).** A single card now sets the default background, text colour, border (colour + width), corner radius and hover state for every AIEO storefront button — with three masters: **Primary** (add-to-cart, checkout, "notify me", "add selected"…), **Secondary / neutral** (view cart, save / share cart, apply coupon) and **Archive** product-card buttons. Each button that already had its own colour picker — Back-in-Stock Waitlist, Complementary, Sticky Add-to-Cart, Side-Cart — now inherits the master by default and overrides it only when you set a value (a CSS custom-property fallback chain, so nothing you previously customised changes). The side-cart action buttons, the storefront "Save / share my cart" button, the coupon-Apply button and the variable-product multi-select "update cart" button were aligned to the same tokens. Also fixes a long-standing admin bug where the colour-picker swatches rendered blank on the DMM settings pages (a global rule forced the swatch background transparent) — every DMM colour picker now shows its colour.
* **Admin discoverability.** The Ctrl / ⌘-K quick navigator now indexes the product-page layout/positioning card and the Saved & Abandoned Carts report; the AI Insights assistant gained an abandoned-carts analysis playbook plus "where does this live" pointers for the layout builder, the carts report and the product picker.
* **Auto-restock — e-shop sales no longer counted as physical-store demand.** The "Stock Recovery" auto-restock signal mines physical-store sales from the ERP to find products that are out-of-stock online but still selling in shops. The e-shop's own sales — invoiced through the head-office branch with a distinct ERP invoice-type code — are excluded from that signal so they cannot inflate in-store demand and trigger false restocks. The contract is documented for multi-store setups (give the e-shop's ERP sales a distinct invoice type).
* **Stock Recovery — out-of-stock cancellations surfaced as a "failed restock" signal.** When an order line is cancelled with the reason "Out of stock", the affected products are reconciled against the restock activity and shown in the Failures KPI, so restocks that didn't actually prevent a lost sale are visible.