Welcome to AI eShop Optimizer, the premier AI-driven solution for intelligent customer engagement powered by the latest AI models from Anthropic and OpenAI.<\/p>\n\n
Works with or without WooCommerce<\/strong> - Perfect for:\n- E-commerce sites with WooCommerce for product recommendations\n- Corporate and content sites for intelligent chat assistance\n- Merchant information sites that need AI-powered customer support<\/p>\n\n The plugin provides advanced AI chat capabilities with semantic search powered by state-of-the-art embedding engines. For WooCommerce sites, it also enables product recommendations through our graph-database powered service at https:\/\/eshop-optimizer.com.\nOur advanced AI tools uncover latent patterns and consumer preferences, empowering you with strategic upsell and cross-sell propositions.\nThe plugin also enables you to import with one click our recommendations - or any product recommendations in a csv file that conforms to our format - and to also monitor their performance using google UTM tags (which you may also use to monitor your own recommendations performace).<\/p>\n\n Export and Back-Up Current Pairings\nSafely export existing upsells and cross-sells, which doubles as a reliable back-up. The Pro version also takes your current selections into account, potentially enhancing the AI's output.<\/p><\/li>\n Accelerated Order Export (Enabled HPOS Required)\nSwiftly export up to 100,000 order items. The Pro version lifts the cap on orders, including comprehensive details like Order ID, Product ID, sequence, and more.\nExclude product titles and prices at will.\nMaintain customer anonymity by withholding CustomerIDs, albeit with a slight compromise on recommendation precision.\nOpt for a seasonal sales analysis, focusing on trends pertinent to the current time of year.\nRefine Your Data with Our AI Engine\nRegister at eshop-optimizer.com and submit your data. Within moments, receive refined upsell and cross-sell strategies for your leading products. Full catalog analysis available with the Pro version.\neshop-optimizer.com respects your privacy and adheres to strick privacy guidelines. Our company's, Oxford Metadata Ltd, privacy provisions has been approved by both Google and Facebook. For further details please visit: https:\/\/eshop-optimizer.com\/compliance<\/p><\/li>\n Import Tailored Upsell and Cross-sell Strategies\nImplement the AI-crafted upsell and cross-sell suggestions via an easy-to-upload CSV file.<\/p><\/li>\n Witness Enhanced Sales\nMarvel at the accuracy of our AI-driven recommendations and observe how they can boost your sales figures. We're so confident in our service that we offer free initial analyses - we believe you'll be eager for more and enthusiastic to spread the word!\n Experience the relevance of our recommendations and discover how AI can improve your store's sales. We offer free analyses, and we are confident that you'll want more and share our plugin with your friends!<\/p><\/li>\n<\/ul>\n\n For any queries or support, contact us at support@eshop-optimizer.com<\/a>.<\/p>\n\n\n\n Website: (https:\/\/eshop-optimizer.com)<\/p>\n\n\n Extract the contents of this plugin zip file into your wp-content\/plugins\/ directory locally.\nUpload the extracted folder to your website.\nNavigate to wp-admin\/plugins.php on your dashboard.\nFind 'AI eShop Optimizer' and activate the plugin.\nAlternatively, install directly through WordPress:<\/p>\n\n Go to the 'Plugins' menu in WordPress.\nClick 'Add New' and search for 'AI eShop Optimizer.'\nInstall and activate directly from your dashboard.<\/p>\n\n\n Day-after follow-up to 5.6 \u2014 runtime-only brand blocks, engagement-gated Web Push, plus three small admin polish items<\/strong><\/p>\n\n Web Push \u2014 engagement-gated banner (Chrome quiet-UI mitigation)<\/strong>\n* NEW: the opt-in banner no longer mounts on a flat Brand blocks now runtime-resolvable \u2014 admin plugin no longer required for storefront pages that render Fix \u2014 Session Tracker JS 404 + MIME-type refusal on every front-end page<\/strong>\n* Fixed: Critical fix \u2014 Web Push: opt-in pipeline broken by deferred JS + Service-Worker 404 + silent localStorage throws<\/strong>\n* Fixed: Data Prep Schedule \u2014 Google Reviews \u2014 single-location auto-fallback + clearer empty states<\/strong>\n* NEW: when the Google Reviews \u2014 shortcodes for non-FSE themes + runtime-only exposure<\/strong>\n* NEW: Data Prep Schedule<\/strong>\n* NEW: Admin polish<\/strong>\n* Fixed: Database Performance Optimization card no longer hardcodes \"MariaDB 11.4+ detected!\" \/ \"MySQL 8.0+ detected!\" \u2014 now interpolates the actual detected version from Same-day follow-up to 5.5 \u2014 Fulfillment UX polish + two production hotfixes + CSV round-trip cleanup<\/strong><\/p>\n\n Production hotfixes<\/strong>\n* Hotfix: Fulfillment \u2014 order-edit meta box<\/strong>\n* Fixed: Add Voucher carrier dropdown was showing every registered carrier including disabled ones. Now filters to operator-enabled carriers + custom carriers only (matches the rest of the admin)\n* Fixed: pressing Enter in the tracking-number input was submitting the order's outer form, navigating to the \"Downloaded products\" panel. The AIEO meta-box inputs now suppress Enter and trigger the explicit Save button instead\n* Improved: ACS (and any carrier already mapped via Fulfillment \u2014 Carriers without API admin<\/strong>\n* NEW: inline Edit button next to Remove on every row \u2014 label and tracking-URL template editable in place; Save \/ Cancel pair posts to the same upsert AJAX endpoint\n* Fixed: Fulfillment \u2014 Settings<\/strong>\n* NEW: \"Backfill customer shipping paid\" card \u2014 one-shot retrospective pass that fills Shipment Cost reports<\/strong>\n* NEW: sortable column headers on the results table \u2014 click to sort by orders \/ income \/ our cost \/ free-shipping subsidy. In-memory client-side sort (the result set is already paginated server-side)<\/p>\n\n Role-based pricing \u2014 CSV round-trip<\/strong>\n* Fixed: import now strips a leading UTF-8 BOM from the uploaded file before parsing (Excel-on-Windows exports leave one). Previously caused \"must include sku column\" errors when the actual header was Critical fix \u2014 Social Login settings silently wiped on every Save<\/strong>\n* Fixed: Features<\/h3>\n\n
AI Product Recommendations<\/h3>\n\n
\n
Products for the Same Needs<\/h3>\n\n
\n
Insights Chat \u2014 Claude-powered (NEW in 5.0)<\/h3>\n\n
\n
Joint Session \u00d7 Attribution Analytics (NEW in 5.0)<\/h3>\n\n
\n
Insights Remote DB Streaming (NEW in 5.0, Pro)<\/h3>\n\n
\n
Star Ratings \u2192 SEO Schema (NEW in 5.0)<\/h3>\n\n
\n
Custom Slots + Tolstoy + Recommendations Ordering (NEW in 5.1)<\/h3>\n\n
\n
\n
<tolstoy-widget><\/code> tag and defer-loads the gotolstoy.com CDN script once per page<\/li>\n[products limit=\"6\" orderby=\"popularity\"]<\/code>)<\/li>\n<\/ul><\/li>\nsource='tolstoy'<\/code> in wp_aieo_addcart_events with source_meta = {slot_id, tolstoy_widget_id, clicked_url}<\/code> so reports can pivot on widget, carousel, or source product<\/li>\n.ff-recommendations-cluster<\/code> flex container + inline CSS order:<\/code> rules) AND classic themes (via dynamic re-prioritisation of WooCommerce woocommerce_after_single_product_summary<\/code> action hooks)<\/li>\n<\/ul>\n\nIAPI (Interactivity API) \u2014 WC Cart \/ Checkout block parity (NEW in 5.1)<\/h3>\n\n
\n
@aieo\/swatches-iapi<\/code> module when IAPI is on, jQuery bundle otherwise) with a single DOM contract<\/li>\nwc\/store\/cart<\/code>) endpoints recognised by the side-cart, attribution log, and waitlist subscribe flows so block-checkout actions are captured the same as classic checkout<\/li>\nwoocommerce_blocks_loaded<\/code> so they're available in block-themed cart\/checkout templates via the Site Editor<\/li>\n<\/ul>\n\nFloating Mini-Cart + Free-Shipping Bar (NEW in 5.0)<\/h3>\n\n
\n
Pricing Engine + Conversion Boosters (NEW in 5.0)<\/h3>\n\n
\n
Marketplace Connectors & Shipping (NEW in 5.0)<\/h3>\n\n
\n
Customer Intelligence + Web Push (NEW in 5.0)<\/h3>\n\n
\n
AI-Powered Chat (FREE)<\/h3>\n\n
\n
\n
\n
Advanced Session Analytics<\/h3>\n\n
\n
How to Use<\/h3>\n\n
\n
5.7 - 2026-05-24<\/h4>\n\n
setTimeout(SHOW_DELAY_MS)<\/code>. It now waits for AIEO Session Tracker to dispatch an aieo:engagement<\/code> CustomEvent on document<\/code> at one of these milestones: pageviews-2<\/code>, pageviews-3<\/code>, scroll-25<\/code>, scroll-50<\/code>, scroll-75<\/code>, add-to-cart<\/code>, time-30s<\/code>. The \"Show delay (ms)\" admin setting becomes a minimum-wait floor (banner never appears before that even if scroll fires at 2s)\n* NEW: hard-cap fallback at 90s \u2014 visitors who never hit a milestone but also don't bounce still see the banner eventually\n* Graceful degradation: when AIEO Session Tracker is absent (operator disabled it OR runtime-only install without the admin asset), falls back to the original flat-timeout behavior so no install regresses\n* Why this matters: Chrome's quieter notification permission UI<\/a> auto-denies prompts on domains with low acceptance rates. Asking bounce visitors on first-page-load poisons the reputation \u2014 every silent auto-denial counts as a \"Block\" signal. By only prompting engaged visitors, the acceptance rate per prompt climbs and Chrome's quiet UI fires less aggressively over time\n* Engagement signal source: AIEO_SESSION_TRACKER.pageViewsInSession<\/code> (new public property, sessionStorage-backed, incremented eagerly even for bounce visitors so counts are accurate). New aieo:engagement<\/code> CustomEvent is also dispatched from inside trackAddToCart<\/code> and trackScrollDepth<\/code> so other consumers can hook in too \u2014 no new tracker, just extends what's already there<\/p>\n\naieo\/brand-*<\/code><\/strong>\n* NEW: AIEO_Runtime_Brand_Blocks<\/code> delegate in the runtime plugin registers the six brand-related server-rendered blocks (aieo\/brand-azindex<\/code>, brand-slider<\/code>, brand-rails<\/code>, brand-related<\/code>, brand-archive-hero<\/code>, brand-story<\/code>) at init<\/code> priority 29 so they're available even when the admin plugin isn't in the request's plugin whitelist. block.json + render.php files stay in the admin plugin's directory (single source of truth); AIEO_Core_Brand_Vitals<\/code> autoloads via the mu-plugins autoloader regardless of admin being active\n* AIEO_Blocks_Loader::register_blocks()<\/code> now consults WP_Block_Type_Registry::is_registered()<\/code> before each register_block_type()<\/code> call \u2014 when both plugins are active the runtime registration at init@29 wins, and admin's loop at init@30 silently skips already-registered blocks (no more _doing_it_wrong<\/code> notices from duplicate registration)\n* Shared style handle aieo-article-cards<\/code> (needed by brand-related) is also registered by the runtime delegate so brand-related renders correctly in runtime-only mode\n* Use case: pages with brand sliders \/ brand A-Z directory \/ related-brands rails on category, blog, and landing pages no longer require the full admin plugin on every request \u2014 same render output, ~40 ms saved per page on cold-cache fetches<\/p>\n\naieo-session-tracker.js<\/code> returned HTTP 404 with text\/html<\/code> body because the class was moved to the runtime plugin (Phase 1.5) but the JS asset was left behind in the admin plugin. plugin_dir_url(__FILE__) . '..\/assets\/js\/aieo-session-tracker.js'<\/code> from the runtime class resolved to runtime\/assets\/js\/aieo-session-tracker.js<\/code> \u2014 which didn't exist. Browsers logged \"Refused to execute script from ... because its MIME type ('text\/html') is not executable\" on every page load. The asset now ships alongside both plugin copies of the class so the runtime-first autoloader path finds its own asset<\/p>\n\nAIEO_DMM_Web_Push<\/code> now registers rocket_delay_js_exclusions<\/code> on activation so WP Rocket's \"Delay JavaScript execution\" feature stops treating aieo-push-optin<\/code>, aieoPush<\/code>, aieo-push-sw<\/code> and aieo-magic-link-modal<\/code> as deferred-until-interaction scripts. Without this, the opt-in banner JS only ran after a mouse-move \/ scroll \/ click that lands inside the page \u2014 bots, remote-desktop sessions, and visitors who follow a deep link straight to a product page never triggered it, so the subscribe POST never fired. Now Just Works on every install with no operator config\n* Fixed: aieo-push-optin.js<\/code> silently died on Edge's Tracking Prevention (and Safari ITP) when localStorage.getItem()<\/code> threw \u2014 the unguarded call killed the entire IIFE before the banner could even render. Now wrapped in try\/catch; blocked storage is treated as \"no cooldown set\" so the banner still appears\n* NEW: silent re-subscribe path \u2014 when Notification.permission === 'granted'<\/code> from a prior visit but no wp_aieo_push_subscriptions<\/code> row exists (e.g. the earlier SW-404 bug killed the original POST), the JS now silently registers the SW, calls pushManager.subscribe()<\/code> and POSTs the result on page load. No banner re-prompt, no operator action \u2014 historical \"granted but never recorded\" users heal themselves on next visit\n* Improved: postSubscription()<\/code> now checks response.ok<\/code> and throws on non-2xx so the outer try\/catch records the failure instead of fire-and-forget. CFG.debug-gated console output for the operator who wants to dig in\n* See docs\/WEB_PUSH_INSTALL.md \u00a74<\/a> for the Nginx location = \/aieo-push-sw.js<\/code> block \u2014 the third leg of this trio (404 SW URL was the upstream root cause on the FF prod incident 2026-05-23)<\/p>\n\nproduct_attributes<\/code> stage added so brand blocks self-populate without the manual rebuild<\/strong>\n* NEW: hourly data-prep cron now runs a product_attributes<\/code> stage between category_hierarchy<\/code> and product_vitals<\/code>. This stage calls the AIEO_InsertCoreProductAttributes<\/code> stored procedure with the operator's configured brand \/ vendor \/ size \/ color attribute taxonomies \u2014 resolving parent brand_id<\/code> from wp_term_relationships<\/code>. The existing propagate_brand<\/code> stage then copies parent \u2192 variations as before\n* Why it matters: brand blocks (aieo\/brand-azindex<\/code>, brand-slider<\/code>, brand-rails<\/code>, brand-related<\/code>, brand-archive-hero<\/code>, brand-story<\/code>) used to render empty on sites where the operator hadn't ticked \"Please recreate the product core attributes and principal categories\" in the Operational Efficiency Settings UI. That checkbox is now correctly scoped as a manual intervention only \u2014 the hourly schedule covers the day-to-day case\n* Defensive: the new stage uses information_schema.ROUTINES<\/code> to verify the SP exists before CALLing it \u2014 older installs without the SP get a clean no-op instead of breaking the whole tick<\/p>\n\naieo\/google-reviews<\/code> block (or [aieo_google_reviews]<\/code> shortcode) is in \"Single location\" mode but no slug is set AND the page can't auto-resolve a location from context, the block now falls back to the operator's only configured location if exactly one exists. Most SMB stores have a single physical shop \u2014 they no longer need to pick a slug for every block instance, the block just works\n* Improved: the empty-state message now shows the actual number of locations configured and steers the operator to the right next step. \"No Google Reviews locations configured yet \u2014 add one under...\" (when 0 exist) vs \"You have N locations configured \u2014 pick one via the block's sidebar, or switch to All-locations \/ Cards grid mode\" (when 2+ exist). Replaces the old cryptic \"Set a location slug, or place this block on a page bound to a location row\"\n* The admin Settings tab now carries a full \"How to display the reviews on the storefront\" help card explaining the FSE block, the three shortcodes, all 11 attributes, and a do_shortcode()<\/code> PHP-template snippet \u2014 so operators on classic themes \/ page builders find the docs without leaving the admin<\/p>\n\n[aieo_google_reviews]<\/code> shortcode \u2014 wraps the same render path the aieo\/google-reviews<\/code> block uses, so classic themes \/ widget areas \/ page-builder pages can drop in Google Reviews without needing FSE block-template editing. Single-location mode when a location<\/code> attribute is supplied ([aieo_google_reviews location=\"downtown\"]<\/code>), all-locations mixed-feed otherwise ([aieo_google_reviews]<\/code>). All block attributes are exposed in snake_case: min_rating<\/code>, max_count<\/code>, layout<\/code> (grid\/list\/carousel), presentation<\/code> (static\/slider\/rotator), autoplay_sec<\/code>, show_overall<\/code>, show_rate_us<\/code>, show_maps_button<\/code>, heading<\/code>, mode<\/code> (single\/all_mixed\/cards_grid)\n* NEW: [aieo_google_locations_grid]<\/code> shortcode \u2014 convenience alias forced to mode=\"cards_grid\"<\/code> for the per-location cards layout. Accepts the same attributes\n* Single source of truth: both shortcodes call AIEO_Google_Reviews_Block::render()<\/code> directly, so the cache, the markup, and the CSS handle are identical to the block output \u2014 operators can mix-and-match blocks (FSE) and shortcodes (classic) on the same site without divergent rendering\n* NEW: AIEO_Runtime_Google_Reviews<\/code> delegate exposes the block + shortcodes to runtime-only contexts \u2014 admin's AIEO_DMM_Google_Reviews<\/code> module is no longer required on the frontend. block class files stay in admin's includes\/dmm\/google-reviews\/<\/code> (single source of truth); the mu-plugins autoloader resolves them on demand. The block class is now idempotent (AIEO_Google_Reviews_Block::register()<\/code> guarded by a $registered<\/code> flag) and admin's call is gated behind ! defined( 'AIEO_RUNTIME_OWNS_AJAX' )<\/code> so runtime is exclusive when both plugins are active. Same aieo\/store-info<\/code> block also exposed<\/p>\n\nproduct_attributes<\/code> stage runs hourly between category_hierarchy<\/code> and product_vitals<\/code> \u2014 calls AIEO_InsertCoreProductAttributes<\/code> automatically so parent brand_id<\/code> populates without ticking the manual \"Recreate product core attributes\" checkbox\n* NEW: per-stage Notes column in the Last-run table \u2014 shows useful metrics per stage (e.g. \"4921 \/ 13513 with brand \u00b7 194 distinct brands\")<\/p>\n\naieo_check_mariadb_version()<\/code> (e.g. \"MariaDB 11.8.7 detected!\"). Falls back to the prior threshold strings if version_number<\/code> is somehow missing\n* Fixed: Google Reviews \u2192 Locations admin no longer uses Femme-Fatale-specific placeholder text (piraeus<\/code> slug, Femme Fatale \u03a0\u03b5\u03b9\u03c1\u03b1\u03b9\u03ac\u03c2<\/code> display name). All four placeholders are now generic + translatable (e.g. main-store, downtown, branch-2<\/code>, Customer-facing label for this location<\/code>, etc.) so the form isn't shipping client-branded examples<\/p>\n\n5.6 - 2026-05-23<\/h4>\n\n
Undefined constant \"AIEO_VERSION\"<\/code> fatal in AIEO_Wishlist::enqueue_assets()<\/code> on category pages when AIEO Runtime loads before the main plugin's constant definition. Defensive defined()<\/code> fallback chain in the runtime: AIEO_VERSION<\/code> \u2192 AIEO_RUNTIME_VERSION<\/code> \u2192 '0.0.0'<\/code>. Same pattern for AIEO_FILE<\/code>. Surfaced on prod femme-fatale.gr \/me-ammonia\/<\/code> as a site-wide HTTP 500 immediately after the 5.5 upgrade\n* Performance: new AIEO_Perf::strip_aioseo_product_schema_on_archives()<\/code> short-circuits AIOSEO Pro's Product \/ WooCommerceProduct \/ Offer \/ AggregateOffer schema graphs on archive and taxonomy pages. AIOSEO was iterating every product in the loop and calling $product->get_available_variations()<\/code>, which on Iconic Variation Swatches triggers a $wpdb->get_results()<\/code> per variation \u2014 ~900 queries per render on a 15-variable-product category. Single-product pages are unaffected (full JSON-LD still emitted where Google rich results actually matter). Prod render time on \/me-ammonia\/<\/code>: 9.4s \u2192 3.2s<\/p>\n\nget_carrier_for_order()<\/code>) is pre-selected when the modal opens, instead of defaulting to the alphabetical-first carrier\n* Improved: button labels now reflect what will actually happen \u2014 \"Save tracking\" \/ \"Generate voucher\" by mode, with a paired \"Save + mark completed\" \/ \"Generate voucher + mark completed\" for the common single-click flow\n* Fixed: custom carriers with create_mode = 'manual'<\/code> (no API integration) no longer error with \"driver does not support create_voucher\". The manual flow now persists the tracking number directly and fires the customer email, bypassing the driver call<\/p>\n\ntracking_url_template<\/code> field was being silently ignored by the courier-driver base when an operator overrode the per-carrier default. AIEO_Courier_Driver_Base::tracking_url()<\/code> now consults the operator-saved template first\n* NEW: filter aieo_custom_carriers<\/code> \u2014 themes \/ plugins can register carriers from functions.php<\/code>, same pattern as WooCommerce Shipment Tracking's wc_shipment_tracking_get_providers<\/code><\/p>\n\n_aieo_customer_shipping_paid<\/code> on historical orders so the Shipment Cost reports' income column is populated for past periods (not only orders placed after the cost-tracking went live)<\/p>\n\n\\xEF\\xBB\\xBFsku<\/code>\n* Fixed: import auto-detects the separator (,<\/code> vs ;<\/code> vs \\t<\/code>) by counting candidates in the first line. Greek-locale Excel exports use ;<\/code>; the previous hardcoded ,<\/code> parser produced unparseable single-column rows\n* Improved: import error messages now state the detected separator and the header row that was parsed, so operators can see exactly why their file was rejected\n* Fixed: export no longer prepends a UTF-8 BOM. Cross-environment round-trips (export from one site, import into another) used to fail until the import learned to strip BOMs; now the file is BOM-clean from the start, keeping cat<\/code> \/ awk<\/code> \/ diff<\/code> output untouched as well<\/p>\n\n