Frequently Asked Questions

On Magento 2, through Composer from the Devexa repository: the Devexa Connector and AI Studio, nothing to copy into app/code/. The widgets come from the platform and are configured in your dashboard. Your dashboard shows these commands with your own licence key already in them:

# Magento 2: Devexa Connector + AI Studio, through Composer from the Devexa repository.
# Your dashboard (Downloads) shows these commands with your own licence key in them.
composer require devexa/connector devexa/ai-studio

bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush

# Then: Stores > Configuration > Devexa > License & Platform: paste the key.
# Medusa, Shopify and WordPress: see Documentation in your dashboard.

Go to Stores > Configuration > Devexa > License & Platform, paste your API key (starts with dxk_), and click Save. The license status should show "Valid".

Yes, after updating module files you should run bin/magento setup:di:compile followed by bin/magento cache:flush. In developer mode, you can skip di:compile but must clear generated:

rm -rf generated/code/Devexa && bin/magento cache:flush

Devexa modules include Tailwind CSS classes. For Hyva theme, you need to add the module templates to your Tailwind purge config and regenerate CSS. After generating, deploy static content with bin/magento setup:static-content:deploy.

# In your Hyva theme's tailwind.config.js, add the modules to `content`
# so their classes survive the purge. They install under vendor/, not app/code:
#   '../../../../../../../vendor/devexa/*/src/view/frontend/**/*.phtml'
# (and app/code/Devexa/**/*.phtml as well if you develop them locally)

npm run build-prod
# or
npx tailwindcss -o web/css/styles.css --minify

Make sure you've added the Devexa template paths to your Hyva theme's tailwind.config.js purge configuration and rebuilt the CSS. If using a theme override in app/design/frontend/YourVendor/YourTheme/Devexa_SmartSearch/templates/, add that path too.

1. Check if the module is enabled: Stores > Config > Devexa > Smart Search > Enable = Yes
2. Verify your license is valid: Stores > Config > Devexa > License & Platform > License Status should show "Valid"
3. Check browser console for JavaScript errors
4. Make sure the layout XML is loaded — check if smartsearch_search block exists in your theme layout

1. Run bin/magento indexer:reindex catalogsearch_fulltext to reindex Elasticsearch
2. Check if Elasticsearch/OpenSearch is running and accessible
3. Verify the search engine is configured: Stores > Config > Catalog > Catalog Search

The popup uses Magento's native Elasticsearch through SearchInterface. If you have third-party search modules (Findbar, Algolia, etc.) that override the catalog search page, results may differ. Disable conflicting modules or contact support for integration.

Clear all caches: bin/magento cache:flush. If using Hyva, make sure the Alpine.js template is properly compiled. Check browser console for JS errors.

The AI needs at least 500+ tracked events (product views, add-to-cart, purchases) before it can generate accurate recommendations. Enable all tracking options in Stores > Config > Devexa > AI Recommendations > Tracking.

Until enough data is collected, the module uses a bestseller fallback. Make sure tracking is enabled and your store has traffic.

Check the risk score thresholds in Stores > Config > Devexa > SmartShield. Default: Challenge at 50, Block at 80. You can increase these values. Also check if the customer's country is in the blocked country list.

The SmartShield JS has a safe URL whitelist that excludes /checkout/cart/, /customer/section/, /rest/, /graphql. If you have custom cart URLs, contact support.

There's a 24-hour grace period. After that, the modules will stop working. Renew your subscription to restore service immediately.

Yes, add your staging domain in the platform dashboard under Allowed Domains. Set environment to "Staging" or "Development".

Log in to ai.devexa.ro, go to your account, and click on the plan you want to upgrade to. The change takes effect immediately.

Contact us at office@devexa.ro or use the Contact page. We offer custom development services including theme integration (from €50/module or €120/all modules).

SmartShield can be configured to protect custom forms. Contact support for custom integration.

Report issues via email at office@devexa.ro or through the platform's Support page.

No. The search popup loads only when the user interacts with the search input. API calls use debouncing (300-400ms) to minimize server load. All tracking uses non-blocking sendBeacon.

The popup displays up to 50 products per search with client-side pagination. The search uses Elasticsearch which handles 100k+ products efficiently. For very large catalogs, optimize your Elasticsearch configuration (see Documentation > Search Optimization Tips).

No. It may only use facts that are in your product data or your policy blocks. Promises you haven't written are exactly what it is built to refuse.

A plain 'I can't confirm that from this product's information', never a guess. The question goes into your monthly insights report.

Every answer shows the facts it used, and the platform keeps the questions and whether they were answered, so you can review them.

No. It only recommends products found in the catalogue Smart Search synced, and Magento reloads them before they are shown: a product that is disabled, hidden or out of stock does not appear.

It is part of SmartAssist. Each message uses your plan's AI allowance, usually a fraction of a cent; searching your catalogue uses none.

Attribute suggestions are only made for attributes that are empty on that product in that store view. Text is shown for review and only replaces a field when you press Apply.

No. For dropdowns and multiple-selects it can only choose from the options you already have, so it can never add 'Beginer' next to 'Beginner'.

Then the suggestion will be wrong in the same way — which is why every value shows the sentence it came from. Implied values are never pre-ticked.

Each product is one small AI call from your monthly allowance. The page reads products only after you press Start, and you can pause at any time.

The language of the store view you are writing for. Choose the store view at the top of the page; the text is saved as that view's value.

No. It is used to make that one image and then discarded. It is never shown to anyone else and never appears in your admin or ours.

One image credit. Your plan includes a monthly amount; the admin shows how many are left.

Four gates stand in front of every image: form key, per-visitor limit, licence and your platform balance. The last one can't be edited from the browser.

Things whose size and look matter at home or on the body: furniture, lamps, rugs, wall art, cookware on a hob, hats and glasses.

No library is added: on Hyvä it uses Alpine, which is already on the page, and on Luma a 4 KB script. The CSS is printed only on pages that show a banner, animations move only transform and opacity, and they stop when the banner scrolls out of view.

Yes. Set Show From and Show Until, or a countdown that hides the banner when it reaches zero. The page cache is cleared at both times, so it appears and disappears on schedule.

Disabled, invisible and out-of-stock products are skipped in the shop, so a sold-out product never sits in your Black Friday banner.

Everything that moves on its own has a pause button, visitors whose device asks for reduced motion get a still banner, the headline is a real heading, and screen readers read the rotating words once instead of on every change.