Is Hyvä Themes free?

No. Hyvä Themes is a one-time commercial license, typically $1,000 – $2,000 per project depending on the variant (single-store, multi-store, agency). The license is perpetual — you pay once per major version, not per seat or per month. Hyvä Checkout is a separate $1,000 license. Compared with the conversion lift most stores see (8 – 25%), the license cost is recouped within the first few months of go-live.

Does Hyvä Themes work with Adobe Commerce?

Yes. Hyvä is fully compatible with both Magento Open Source and Adobe Commerce (formerly Magento Commerce) on versions 2.4.4 and above, including Adobe Commerce Cloud. You keep all the Adobe Commerce features — B2B, content staging, page builder, customer segments — and only the storefront rendering layer changes. The Hyvä Adobe Commerce license is sold at the same price as the Open Source license.

Can my Magento extensions still work?

Most of them, yes. Hyvä ships a free Compatibility Module that wraps Luma-only extensions so they render inside a Hyvä storefront. As of 2026, the vast majority of popular paid Magento extensions are either natively Hyvä-compatible (vendor ships Hyvä support out of the box) or covered by the Compat Module. The remaining ~10 – 20% need either a paid native port from the vendor, a manual port by your dev team, or a swap to a Hyvä-native equivalent. Always run a per-extension audit before migration.

Is Hyvä the same as headless Magento?

No. Hyvä is server-rendered, not headless. Magento renders the HTML on the PHP side, Hyvä uses Alpine.js for small client-side interactions. Headless Magento — typically PWA Studio with React on top of GraphQL — is a different architecture: separate frontend app talking to Magento purely through API. Hyvä is simpler, cheaper to maintain, and faster on most metrics. PWA Studio is more flexible if you need a single frontend across multiple backends or a native mobile app sharing logic with the web. For most Magento stores, Hyvä is the right answer.

Does Hyvä support B2B?

Yes. Hyvä works with Magento B2B (Adobe Commerce B2B module) — company accounts, requisition lists, quote workflow, shared catalogues, negotiable quotes — all render in the Hyvä storefront. Some B2B-specific UI (the requisition list page, the quote request form) needs Hyvä-native templates if your team has heavily customised the Luma B2B views; the Compat Module covers the unmodified default views. B2B stores often see the biggest performance lift from Hyvä because they tend to have heavy PLPs and large catalogues where every kilobyte of JavaScript hurts.

How long does Hyvä migration take?

Typical range is 4 to 12 weeks for an existing Luma store, depending on customisation depth and extension count. Lightly customised stores (mostly default Luma + 5 – 10 extensions) can land in 4 – 6 weeks. Mid-complexity stores (custom theme + 15 – 25 extensions + custom B2B flows) take 6 – 10 weeks. Heavy stores (deeply customised theme + 30+ extensions + bespoke checkout / configurator logic) take 10 – 12 weeks plus a phased cutover. Brand-new builds on Hyvä are faster because there is no Luma legacy to port — usually 3 – 6 weeks for a standard store.

Is 5 minutes really enough for a real audit?

For a self-assessment first pass, yes. For a final sign-off audit, no — that’s a 1–3 day paid engagement.Here’s the honest breakdown of what these 50 questions can and cannot do:What 5 minutes covers: the questions a senior Magento operator can answer from memory + a quick admin-panel glance — patch level, 2FA on/off, FPC enabled, indexers in schedule mode, cron running, composer audit last result, sessions on Redis. About 35–45 of the 50 questions fall here.What 5 minutes can’t cover: things requiring code-reading or query-running — how many custom modules use deprecated APIs, whether a quote workflow still validates after the last patch, whether canonical tags are correct on every layered-nav permutation. Skip those, then ask your dev team. About 5–10 of the 50.What this checklist deliberately doesn’t do: custom-module security review, slow-query log analysis, dependency vulnerability deep-scan, ERP integration data-integrity check. Those are the deep-audit territory.So: 5 minutes for the self-assessment, then a paid 1–3 day deep audit ($1.5k–$3k) if your overall grade is C or below, or any single category is at D.

How accurate is this calculator?

The calculator output is a budgeting range, not a quote. The low–high spread (-20% / +50%) intentionally absorbs the things you can’t see from outside your codebase: undocumented customisations, vendor extensions that have gone silent, hidden cron-orchestrated integrations, and the dependency-resolution chaos that only surfaces when you actually run composer update.From my own data on 200+ shipped upgrades:~78% of projects landed inside the calculator’s low–high range without a change order.~17% needed a small change order (median +12%) usually for an extension swap-out the audit caught.~5% needed a substantial replan — almost always when the client had hidden a major customisation from the audit step (rare, but it happens).To turn the calculator output into a hard number, run a paid 1–3 day audit ($1.5k–$3k). Post-audit my fixed quote falls within ±5% of the audit estimate.

How is the 60-extension database curated?

Every entry in the database is something I’ve installed, configured, and shipped on a real client store between 2019 and 2026 — no “found-it-on-the-marketplace” entries, no AI-generated brochure summaries.The shortlist for each of the 12 categories is filtered through five gates:Live install — ran on a paying-client production store for at least 90 days. If I’ve only POC’d it on staging, it doesn’t make the list.Active maintenance — vendor shipped a release in the past 12 months. Silent vendors get cut even if the module is technically excellent.Pricing transparency — vendor publishes a public price (not “contact us for a quote”). Enterprise-only modules get tagged but de-prioritized.Hyvä compatibility known — I’ve either tested it on a Hyvä storefront or read the vendor’s explicit compat statement.No undisclosed conflicts — doesn’t silently break checkout, search, or admin when stacked with the other 3-4 modules in its category.That filters ~150 candidates I’ve touched down to the 60 entries you see. Re-curated quarterly — if a vendor goes silent, they’re marked deprecated and rotated out at the next refresh.

How accurate is this calculator?

Honest answer: directionally accurate within ~15–25% for the median case in each GMV bracket, less accurate at the extremes. It’s a first-pass screening tool, not a procurement-grade quote.What it gets right:License tier ordering. Magento Open Source $0 vs Adobe Commerce $30k–$150k+ vs SFCC $200k+ — the ranking won’t change.Per-tx fee impact at scale. Shopify Plus 0.15% adds up identically every time; the math is exact.Dev cost order of magnitude. A $5M GMV store on Magento needs ~$40k upfront + $30k/yr ongoing — the bracket holds across most engagements I’ve seen.Where it’s less accurate:SFCC and Adobe Commerce license — both are negotiated. Tier-1 SI partners often hold ±30% pricing power. The calculator uses public list-equivalent ranges; your actual quote may be lower (negotiated) or higher (uplift for Adobe Commerce Cloud Pro vs Starter).Custom dev edge cases — if your scope includes headless commerce, ERP integration, or multi-region inventory orchestration, dev cost can be 2–3x the calculator’s number.Region-specific pricing — the model assumes US dev rates. EU SI partners run 0.7–0.9x; India / Eastern Europe freelancers run 0.3–0.5x; Tier-1 US/UK SIs can run 1.2–1.5x.Use it to rule out platforms and frame the conversation, not to write a budget line.

TCO comparison at $50M GMV — which actually wins?

Closer than the brochures suggest. Real numbers from 8 enterprise migrations in this band:Shopify Plus 3-year TCO at $50M: Plus baseline $2,300/mo OR 0.4% × $50M = $200k/yr (whichever is greater — at $50M the GMV-based fee bites) → $600k+ over 3 years. Per-tx fees ~$75k/yr on Shopify Payments (0.15%) → $225k. 8–12 Plus apps at $1–5k/mo each (Klaviyo, Gorgias, Yotpo, Rebuy, Loop, Postscript, Shipstation, Avalara, Sparklayer for B2B) → $300k–$1.8M. Plus dev / agency $200–500k. Total: $1.3M–$2.9M.Adobe Commerce 3-year TCO at $50M: AC license tier at $50M GMV is roughly $80–150k/yr (revenue-banded) → $240–450k. Adobe Commerce Cloud infra $50–80k/yr → $150–240k. In-house dev team (3–5 engineers) or agency on retainer over 3 years → $400–900k. Plus extension licenses + monitoring + search add-ons $50–100k. Total: $840k–$1.7M.AC usually wins TCO by ~$200–800k once you account for Plus app multipliers — but the Plus number is more predictable. AC is cheaper if you run lean; more expensive if you don’t. The TCO winner is whichever platform fits your org without forcing it to grow into the cost.

SFCC vs Adobe Commerce TCO at $200M GMV — what are the concrete numbers?

3-year all-in TCO at $200M GMV, comparable scope (B2C with light B2B, 3 regions, mid-complexity catalog):Adobe Commerce 3-year TCO at $200M: license $80–150k/yr → $240–450k. Adobe Commerce Cloud infra $30–80k/yr → $90–240k. Implementation (mid-tier or tier-1 SI) $400k–$800k one-time. Ongoing engineering retainer $30k–$80k/mo → $1.08M–$2.88M over 3 years. Adobe Marketplace extensions $50k–$150k. Total: ~$1.9M – $3.7M.Salesforce Commerce Cloud 3-year TCO at $200M: license / revenue-share $500k–$1M/yr → $1.5M–$3M. Implementation (tier-1 SI: Capgemini, Accenture, Publicis Sapient) $800k–$2M one-time. Ongoing SI retainer $50k–$150k/mo → $1.8M–$5.4M over 3 years. Cartridges + integrations $100k–$300k. Total: ~$4.2M – $10.7M.The TCO gap at $200M GMV typically lands at 2–3× in favor of Adobe Commerce. The gap narrows above $1B GMV but rarely closes — SFCC’s revenue-share pricing scales linearly with GMV; AC’s license tiers cap out.

Companies + multi-buyer roles — Adobe Commerce native vs Open Source extensions?

Both reach roughly the same destination — the path is different.Adobe Commerce B2B (native): ships a Companies module with a parent → child → buyer hierarchy, role-based purchase thresholds (e.g. Buyer can place orders up to $5k, Approver up to $50k, Company Admin unlimited), and an approval workflow that routes a pending order through the right approver before it’s placed. Cost: rolled into the Adobe Commerce license at $30k+/yr.Magento Open Source: covered by extensions — Mageworx Companies ($299 + 12mo support), Aitoc B2B Suite (~$899), or BSS Companies (free + paid tiers). Combine with Aitoc Quote Workflow ($299–$799) to fill the approval gap. Total: $1–3k one-time vs $30k+/yr for AC.The honest trade-off: AC ships a more polished UI, vendor-supported upgrades, and 24/7 SLA. OS extensions cover ~85% of the feature set at 5% of the cost — the remaining 15% is mostly "nice-to-have" admin polish. For most wholesale stores under $10M GMV, OS + extensions is the right call.

Magento variant ceiling — does it really handle 10,000+ SKUs?

Yes — with the right indexing and storefront stack. The biggest fashion catalog I ship today runs ~78,000 variants across 1,200 product families and holds a 95+ Lighthouse mobile.The model is Magento configurable + simple products with EAV attributes for size, color, fit, season, fabric. The performance gotchas:Catalog product flat tables off, EAV indexed cleanly. Flat tables hurt at this scale.Custom denormalised stock-status table for "in-stock by size/color" filtering — native price/stock indexers slow at 50k+ variants.Hyvä theme instead of Luma. Luma re-renders the swatch picker on every interaction; Hyvä uses Alpine state and stays under 200ms INP.Lazy-loaded swatch images (browser-native loading="lazy" plus IntersectionObserver fallback for the PDP swatch grid).Shopify hits a hard ceiling at 100 variants per product (Plus: 2,000) which forces fashion brands above that into multi-product workarounds that fragment SEO and analytics. Magento has no such ceiling.

Cold-chain shipping integration with Magento — which carriers actually work?

Cold-chain in 2026 is a small list of viable carriers and a much longer list of "claims it but doesn’t deliver" options. Realistic shortlist:FedEx Custom Critical / FedEx Cold — premium, US + EU, real temp logging on the parcel, expensive ($30–$120 per parcel depending on temp band + distance). Best for high-value frozen meal kits.Sendle Cold (AU) — startup-friendly, integrates with Australia Post network, ~A$15–$35 per parcel, decent for refrigerated meal kits.UPS Temperature True — US + EU, similar to FedEx Cold, slightly cheaper, requires UPS account.Specialty couriers — Lasership Cold (US East Coast), GoFreight Cold (US West), Kuehne+Nagel Pharma (EU), Snowfox (UK refrigerated meal-kit specialist). Pricing varies, integration is API-by-API.3PL with cold-chain inside — FedEx-Goods + ShipBob Cold + Stord Cold + DiCentral. Magento sends order → 3PL handles cold-chain selection internally.Magento integration: a `requires_cold_chain` line-item attribute + a custom shipping-method module that hides ambient-only carriers when the cart contains a flagged SKU. Orders post to the carrier API, parcel barcode + temp-logger ID returns into Magento, transit-incident webhook fires when temp deviates outside the SLA window. We’ve standardised this pattern across 3 meal-kit clients.

Fraud prevention — Riskified vs Signifyd vs Sift?

All three are good. They differ on pricing model, chargeback guarantee, and fit by AOV.Riskified — chargeback guarantee on every approved order. If a guaranteed order charges back, Riskified pays. Pricing is a % of GMV (typically 0.6–1.2%) and you get a hard SLA. Best fit: $1k+ AOV jewellery + watches. The financial risk shifts off the brand entirely. I default to Riskified for diamond + bridal DTC at $5M+ GMV.Signifyd — also chargeback-guarantee. Slightly cheaper for mid-AOV (typically 0.4–0.9% of GMV). Strong on item-not-received fraud which matters for jewellery. Best fit: $500–$5k AOV mainstream fine + fashion jewellery. Solid Magento integration via official extension.Sift — risk-scoring + decision-engine, NOT chargeback-guarantee. You build your own decline + manual-review rules using Sift’s scores. Cheaper (~$0.05–$0.20 per order). Best fit: brands at <$2M GMV who want a cheap fraud layer + are comfortable owning the chargeback risk. Or as a layer in front of Riskified to filter obvious junk before paying for the guarantee.The pattern I deploy at most $5M+ jewellery brands: Sift for first-pass scoring (free-tier filter on bot + obvious-fraud orders) → Riskified for guaranteed approval on the orders that pass Sift → 3-D Secure 2.0 for the borderline grey-zone. Layered, not either/or. Cuts net chargeback losses 75–90% in the books I’ve audited.

FDA + DEA + DSCSA compliance on Magento — is it actually feasible?

Yes. Magento is a commerce platform — compliance is a wiring problem, not a platform-fit problem. Three separate regulators, three workstreams:FDA — product registration (NDC code per drug + strength + package size), structured product labeling (SPL) for the PDP, MedWatch adverse-event reporting integration. Magento custom product attributes hold NDC + SPL XML reference; an admin observer pushes adverse-event reports to FDA’s SafetyReport API.DEA — only relevant if you handle Schedule II–V controlled substances. Custom Magento checkout step for DEA Form-222 (Schedule II) or CSOS electronic ordering, biennial inventory tracking, suspicious-order monitoring (SOM) reports auto-flagged via a Magento cron + report module. DEA registrant validation per buyer-account at signup.DSCSA (Drug Supply Chain Security Act, fully effective 27 Nov 2023, with stabilisation period) — unit-level GS1 DataMatrix serialization (GTIN + serial + lot + expiry), AS2 / EPCIS exchange with trading partners, transaction information / history / statement (TI / TH / TS) at every handoff. Magento talks to a serialization middleware (TraceLink, rfxcel, SAP ATTP, Tag-It) for the actual serial-record exchange — nobody builds DSCSA middleware from scratch.I’ve shipped this stack for a regional pharma distributor and a specialty Rx pharmacy. Two things matter: middleware pick (TraceLink is the safe default at $80M+ GMV; rfxcel cheaper for mid-market; Tag-It is good for small pharmacies) and regulatory pre-audit before any live release. Don’t skip the pre-audit.

Variable sizing matrix on Magento — is it really feasible across apparel + footwear + equipment?

Yes, and it’s where Magento beats Shopify cleanly for sporting goods.Sporting goods sizing has three different shapes per category:Apparel: size (XS–5XL) + fit (regular / slim / athletic) + length (short / regular / tall) + sometimes by-sport cut. 4 axes, 60–120 SKUs per product family.Footwear: size (US 5–15, EU 35–50, half-sizes) + width (B / D / 2E / 4E for men, AA / B / D for women) + sometimes by-activity (trail / road / cross-training). 3 axes, 80–200 SKUs per product family.Equipment fit: by rider height + inseam + skill level (cycling), by skier height + skill + on-piste-vs-all-mountain (skiing), by hand size + grip type (tennis), by foot strike + arch type (running shoes). 2–4 axes, 20–60 SKUs per product family.Magento configurable products + EAV attributes per axis handles all three cleanly. Per-category size charts with body-measurement inputs live as CMS blocks rendered conditionally on PDP based on the product attribute set. Fitment quiz on PDP routes the customer to the right SKU before they hit the dropdown — cuts size-driven returns 18–28% in the data I see.Shopify hits its 100-variant ceiling fast on footwear at this scale (Plus: 2,000, still tight). Forces brands into multi-product workarounds that fragment SEO and analytics.

YMM fitment data — TecDoc vs SEMA Data Coop, which do I pick?

Both are industry-standard vehicle databases, but they cover different markets and price differently:TecDoc (owned by TecAlliance) — the European standard. ~80,000 vehicle records, deep coverage of EU makes (VW, BMW, Mercedes, Stellantis, Peugeot). Most EU-based aftermarket distributors run on TecDoc. Licensing: ~€3k–€15k/yr depending on scope. Magento integration via XML feed import on a daily schedule.SEMA Data Coop — the US standard. ~100,000+ vehicle records covering US makes (Ford, GM, Stellantis-NA, Toyota-USA, Honda-USA), light trucks, motorcycles, ATVs. Coverage of EU makes is shallow. Licensing: ~$2.5k–$8k/yr. Format is ACES (Aftermarket Catalog Exchange Standard) + PIES (Product Information Exchange Standard).Hybrid — for global brands, license both and merge in Akeneo PIM before the data hits Magento. Adds ~$5k–$10k of one-time integration work but covers ~95% of global vehicle parc.Magento side: vehicle records become a custom entity (auto_vehicle) with attributes year, make, model, trim, engine, drive-type. Product-to-vehicle compatibility is a many-to-many junction table. Layered nav filters by selected vehicle. I default to SEMA Data Coop for US-only stores, TecDoc for EU-focused stores, hybrid above $10M GMV with global ambitions.

What shade-matching tools work with Magento — quiz-based vs AR (Modiface / YouCam)?

Three patterns work, in increasing complexity and cost:Quiz-based shade finder — 5–7 questions on undertone, depth, finish, climate. Built natively in Magento with custom product attributes + a thin Alpine.js quiz UI on Hyvä. Conversion lift typically 0.8–1.4x baseline. Cost: ~$3k–$8k.AR try-on (Modiface / YouCam Makeup / Perfect Corp) — live camera overlay on PDP. Integration via REST + JS SDK. Conversion lift 1.4–2.8x on PDPs with AR. Cost: ~$8k–$20k integration + $1k–$5k/mo licence to the AR vendor depending on traffic.Hybrid (quiz → AR confirm) — quiz narrows to 3 shades, AR confirms the pick. Best conversion in my data.For brands under ~$5M GMV, start quiz-only. AR pays for itself above ~$5M because the licence amortises across volume.

Magento at 50k+ SKUs — what’s the performance reality?

Magento handles 50k+ SKUs cleanly when three things are tuned correctly: EAV indexing, Elasticsearch, and Hyvä. Without those, default Luma + MariaDB will start choking around 30k SKUs — category pages take 2–5 seconds, layered nav lags 1–2 seconds per filter click.EAV index: schedule the catalog_product_attribute + catalog_product_price + catalog_category_product indexers to "Update on Schedule" with a cron run every 1 minute. Avoid "Update on Save" at 50k+ — admin saves stall.Elasticsearch / OpenSearch: required from Magento 2.4+. Tune refresh_interval to 30s, allocate 4–8GB RAM. Re-index rate target: 50k SKUs in <10 minutes.Hyvä theme: replaces Luma’s 3MB+ JS with ~150kB Tailwind/Alpine. Catalog list-view renders 60% faster. INP drops from 280ms to 80ms on a 50k-SKU store.Hosting floor: 8 vCPU / 16GB RAM / NVMe SSD, Redis for cache + sessions, dedicated MariaDB or Aurora. Cloudways "Pro" plan or Hetzner CX52 minimum.With those four in place, a 50k-SKU electronics store hits Lighthouse 90+ on category and product pages. I’ve shipped one with 78k SKUs that holds 95+ Lighthouse mobile.

Furniture configurator on Magento — how complex is it?

Furniture configurators are deeper than fashion variants but Magento handles them cleanly with the right pattern.Schema: use Magento configurable products for the primary axis (typically dimension or model) and Custom Options for the secondary axes (fabric, finish, hardware, leg style). Bundle products handle multi-piece sets (e.g. sectional with 4-5 modules). EAV attributes hold the swatch metadata.Visual swatch picker: the default Custom Options dropdown is unusable for fabric. Wire in a UI extension (Mageworx, Aheadworks Advanced Product Options, or a custom React widget on Hyvä) that renders fabric thumbnails, hover-to-zoom, and a “swatches by mail” CTA.Validation rules: not every fabric ships on every frame. Use option dependencies (e.g. via the same extension or a custom rule engine) to disable invalid combos in real time.Scale: 1,000+ valid permutations per product family is achievable. I’ve shipped a custom-sofa configurator with 4,200 valid combinations and a 1.8s LCP on Hyvä. Below 100 SKUs you can fake it on Shopify; above 500 SKUs with 3+ axes, Magento is the answer.

How is “compatibility” defined here?

A verdict of Compatible means the extension renders its frontend HTML correctly under Hyvä 1.3+, doesn’t inject Knockout or RequireJS dependencies, doesn’t break the cart or checkout flow, and survives a clean reindex + setup:upgrade. Backend admin behaviour is identical regardless of frontend theme — every status here judges only the storefront. So if a verdict says “Compatible”, you can install it next to Hyvä without porting work; if it says anything else, the row description explains exactly what gap remains.

What services do you offer?

We specialize in e-commerce development with expertise in Magento 2, Shopify, and WordPress/WooCommerce. Our services include custom development, theme design, plugin/extension development, performance optimization, and ongoing maintenance and support.

How do you charge for your services?

We offer flexible pricing models including fixed-price projects, hourly rates, and monthly retainers. The pricing model depends on the project scope and client preference. We provide detailed quotes after understanding your requirements.

What technologies do you work with?

We specialize in PHP-based e-commerce platforms including Magento 2 (Adobe Commerce), Shopify, and WordPress/WooCommerce. We also work with modern frontend technologies like React, Vue.js, and Next.js for headless commerce solutions.

Can you migrate my store to Magento 2?

Yes! We have extensive experience in migrating stores from Magento 1, Shopify, WooCommerce, and other platforms to Magento 2. We ensure data integrity, minimal downtime, and seamless transition for your business.

Do you offer ongoing support after project completion?

Yes! We offer flexible maintenance and support plans including bug fixes, security updates, feature enhancements, and technical support. Plans can be customized based on your needs.

Does this replace Magento's native contact form?

Yes. When the module is enabled, the /contact URL is handled by Panth Advanced Contact Us and the stock Magento_Contact form is bypassed. Disable the module to revert to the native form — no data loss.

Does Panth Advanced SEO replace Magento's native SEO features?

It enhances them. Magento's native meta fields still work — Panth Advanced SEO adds template-based defaults, tokens, hreflang groups, JSON-LD, SEO scoring, and dozens of other features Magento ships without.

Does Panth Advanced Cart work with Hyva?

Yes. The module ships dedicated Hyva templates built with Alpine.js and Tailwind CSS. Theme detection is automatic via Panth_Core.

Can I have more than one banner slider on the same page?

Yes. Create as many sliders as you want in the admin and place each one via its own widget or layout block. Each slider maintains independent configuration and slides.

Do I have to pay for Panth Core?

No. Panth Core is completely free and will remain free forever. It is the foundation library that other (paid) Panth extensions depend on.

Does this module change how Magento calculates custom option prices?

No. All price-delta logic continues to flow through Magento's standard priceBox and price-option JS components. This module only replaces the visual rendering.

How many forms can I create?

Unlimited. Each form has a unique identifier and its own submissions scope.

Does Panth Footer replace the default Magento footer?

Yes. When enabled, Panth Footer takes over the footer.container block and renders its own configurable footer. You can disable it any time to restore the default footer.

Will this overwrite my custom image labels?

No. Merchant-authored labels (anything other than empty, the product name, Image, main product photo, or the raw filename) are preserved. Only Magento's default placeholders get upgraded to template output.

Does this submit URLs to Google?

No. Google does not participate in IndexNow and has stated they maintain their own crawl schedule. For Google indexing, use a proper XML sitemap and Google Search Console. This module is specifically for the IndexNow ecosystem (Bing, Yandex, Seznam, Naver, Yep).

Will this slow down my storefront?

No. The notification feed is cached, assets are lightweight, and the JS runs asynchronously after page load.

Is llms.txt an official standard?

An emerging community standard proposed at llmstxt.org with a growing list of adopters (Anthropic, Perplexity, Vercel, Stripe, Cloudflare docs all publish one). Not an IETF RFC yet, but stable enough that major AI platforms rely on it.

Does it work for guests?

Yes, guests can subscribe with their email address. You can optionally require login via admin config.

How is this different from a traditional antivirus?

Panth Malware Scanner is built specifically for Magento 2 filesystems — it understands the directory layout, knows which folders are writable from the frontend, and ships signatures tuned for Magento-targeted threats (Magecart skimmers, PolyShell webshells, admin-layout injection). Traditional AV tools scan everything with generic signatures and produce noise.

Does Panth Mega Menu work on both Hyva and Luma?

Yes. The module ships with two purpose-built templates — Alpine.js + Tailwind for Hyva and vanilla JS for Luma — and auto-switches based on your active storefront theme.

Does this module override Magento's `cms/noroute/index` controller?

No. It uses Magento's standard layout update mechanism to replace the block under the content container. The controller itself is untouched.

How is this different from Magento's native "file" custom option?

Native file custom options are tied to the cart quote item and don't persist cleanly as a first-class order record. Panth Order Attachments creates dedicated panth_quote_attachment and panth_order_attachment tables, linked to the sales order item, ensuring files remain accessible for the full order lifetime — including reorders, invoices, and RMAs.

Does this slow down the order grid?

Minimally. The column loads order items for each visible row (typically 20-50 orders). For very large catalogs, you can disable thumbnails to reduce image loading.

What triggers a price drop alert?

Any reduction in the final displayed price for the store view where the customer subscribed — catalog regular price, special price, catalog price rule discount, tier pricing, or group pricing. The module compares the current final price against the baseline captured at subscription time.

Does this replace Magento's default product gallery?

Yes, on the product detail page. When the module is enabled, the default gallery.phtml is replaced with the Panth gallery (one template for Hyva, another for Luma — chosen automatically).

Can I add more than 3 custom tabs?

Yes. Both CMS block tabs and attribute tabs support unlimited entries. Add as many as your product requires.

Does Panth Search Autocomplete work with Elasticsearch and OpenSearch?

Yes. The module is engine-agnostic — it uses whatever Magento is configured with (Elasticsearch 7, Elasticsearch 8, OpenSearch 1.x/2.x, or the MySQL fallback). No extra setup required.

Does Smart Badge slow down my category pages?

No. Badge lookups are indexed and cached per product + store view + customer group, and badge rendering is pure CSS. Typical overhead is under 5ms on listing pages.

Magento glossary

What is Hyvä Themes ?

Hyvä Themes is a complete Magento 2 frontend rebuild on Tailwind CSS 3.4 + Alpine.js 3.x, designed as a drop-in replacement for Magento’s default Luma theme. Released in 2020 by Hyvä, licensed at $1 – 2k one-time per project. Delivers Lighthouse 95+, ~85% smaller JS bundle, and 8 – 25% documented conversion lift over Luma.

Need help migrating? How it works

Written by Kishan Savaliya — Adobe Certified Magento & Hyvä developer, 8 years on platform

At a glance

Released 2020 by Hyvä
Stack Tailwind CSS 3.4 + Alpine.js 3.x
License $1 – 2k one-time per project

How it works

Five things Hyvä actually changes under the hood

Hyvä is not a re-skin. It is a frontend stack rewrite that swaps Luma's 2015 toolkit for the 2024 web. Here is what that means concretely.

01

Replaces the Luma JS stack wholesale

Hyvä rips out jQuery 2.2, RequireJS, KnockoutJS and Magento UI Components — the entire Luma frontend stack — and replaces it with two libraries: Tailwind CSS 3.4 (utility classes, no LESS cascade) and Alpine.js 3.x (3 KB reactive sprinkles). Net result is ~85% less JavaScript shipped to the browser, ~70 KB total Hyvä payload vs ~450 KB Luma payload.
02

Server-renders HTML, sprinkles Alpine for interactivity

Unlike PWA Studio (full SPA, React on top of GraphQL), Hyvä is a server-rendered theme. Magento renders the HTML on the PHP side as it always has; Alpine handles small interactive bits — drawers, modals, mini-cart toggles, quantity steppers. No SPA, no client-side router, no hydration cost. Magewire (Hyvä’s Livewire port) handles richer state when needed without leaving server-rendered land.
03

Hyvä Compatibility Module bridges Luma extensions

The biggest concern with any Magento frontend rebuild is "what about my paid extensions?" Hyvä ships a free Compatibility Module that wraps most marketplace extensions (built for Luma) so they render inside a Hyvä theme without code changes. As of 2026, ~80% of major paid Magento extensions are either natively Hyvä-compatible or covered by the Compat Module — manual port effort is minimal.
04

Hyvä Checkout is a separate $1k product

Theme and checkout are decoupled. Hyvä Themes ships with the storefront catalogue (PLP, PDP, header, footer, mini-cart) but uses Magento’s default Luma checkout out of the box. To get the full performance win you also buy Hyvä Checkout — a separate one-time license that replaces the slow Magento checkout with an Alpine + Magewire equivalent. Most stores see ~50% of their conversion lift from the checkout swap alone.
05

Compatible with Magento 2.4.4+ Open Source and Adobe Commerce

Hyvä works on every supported Magento version from 2.4.4 onwards, on both Magento Open Source (free) and Adobe Commerce (Pro / Cloud). It is not a fork of Magento — it is a theme + module package that drops into a normal Magento install. You keep the same admin, same product attributes, same pricing rules, same B2B structure. Only the storefront rendering layer changes.

When to use

Four situations where Hyvä is the obvious answer

Hyvä isn't universally correct, but in 2026 these four scenarios are unambiguous wins.

New Magento builds in 2026

Adobe’s own 2025 keynote recommended Hyvä as the default starting point for new Magento storefronts. Building new on Luma in 2026 is opt-in regret — you pay the migration cost later anyway. Pick Hyvä on day one and ship a fast site from launch.
Existing Luma stores below Lighthouse 60

If your current Luma store is sub-60 on mobile Lighthouse, fixing performance inside Luma hits a hard ceiling around 70 — beyond that you fight the framework. Hyvä migration takes Lighthouse from 30 – 50 to 95+ on the same hardware, same database, same product catalogue. The conversion lift typically pays for the migration in 3 – 6 months.
Fashion, electronics, B2B — conversion-led stores

Sectors where mobile UX directly drives revenue benefit most. Fashion (impulse buying, image-heavy PLPs), electronics (long PDPs, rich attribute filters), B2B (large catalogues, complex configurators) all see the steepest conversion lift after Hyvä migration. If conversion rate is a tracked KPI and mobile is over 50% of traffic, Hyvä is the highest-ROI frontend investment available.
Performance-critical peak season (Diwali, BFCM)

Stores running Diwali, Black Friday / Cyber Monday, or back-to-school promotions cannot afford a sub-1s LCP failure under traffic load. Hyvä’s ~70 KB JS bundle and server-rendered HTML mean origin servers spend less CPU per request, edge caching works better, and mid-tier Android devices on 4G stay responsive when desktop traffic spikes 10x. Migrate before, not during, peak.

Common mistakes

Three traps that turn a Hyvä migration into a project rescue

Every overrun Hyvä project I've been called in to rescue made one of these three mistakes early. Avoid them and the migration runs on schedule.

Skipping Hyvä Checkout

A Hyvä theme on top of the stock Magento Luma checkout still ships ~250 KB of jQuery + KnockoutJS the moment a customer hits step one. You leave roughly half of the perf win on the table — and worse, the checkout is the page where slow JavaScript hurts conversion most. Always budget Hyvä Themes ($1 – 2k) plus Hyvä Checkout ($1k) together. Treat them as a single line item, not two separate decisions.
Migrating without an extension audit

Most Luma stores carry 20 – 40 paid extensions accumulated over years. Migrating without first auditing each one against the Hyvä Compatibility Module ships you straight into broken PLPs and missing storefront features in week 6. Always inventory every extension on day one, classify each as native-Hyvä / Compat-Module / replace / drop, and lock the list before any theme work starts. The audit takes 3 – 5 days and saves weeks of rework.
Treating Hyvä as a UI refresh

Hyvä is not a re-skin — it is a frontend stack rewrite. PHTML templates rewritten, LESS dropped for Tailwind, KnockoutJS replaced with Alpine, custom modules ported. Plan for 4 – 12 weeks of dev time depending on customisation depth, plus QA, plus a soft-launch window. Stores that scope it as a "theme swap" routinely overrun by 2 – 3x. Brief the project as a frontend rebuild, with a feature freeze on the Luma side for the duration.

FAQ

Hyvä Themes — frequently asked questions

Is Hyvä Themes free?

No. Hyvä Themes is a one-time commercial license, typically $1,000 – $2,000 per project depending on the variant (single-store, multi-store, agency). The license is perpetual — you pay once per major version, not per seat or per month. Hyvä Checkout is a separate $1,000 license. Compared with the conversion lift most stores see (8 – 25%), the license cost is recouped within the first few months of go-live.
Does Hyvä Themes work with Adobe Commerce?

Yes. Hyvä is fully compatible with both Magento Open Source and Adobe Commerce (formerly Magento Commerce) on versions 2.4.4 and above, including Adobe Commerce Cloud. You keep all the Adobe Commerce features — B2B, content staging, page builder, customer segments — and only the storefront rendering layer changes. The Hyvä Adobe Commerce license is sold at the same price as the Open Source license.
Can my Magento extensions still work?

Most of them, yes. Hyvä ships a free Compatibility Module that wraps Luma-only extensions so they render inside a Hyvä storefront. As of 2026, the vast majority of popular paid Magento extensions are either natively Hyvä-compatible (vendor ships Hyvä support out of the box) or covered by the Compat Module. The remaining ~10 – 20% need either a paid native port from the vendor, a manual port by your dev team, or a swap to a Hyvä-native equivalent. Always run a per-extension audit before migration.
Is Hyvä the same as headless Magento?

No. Hyvä is server-rendered, not headless. Magento renders the HTML on the PHP side, Hyvä uses Alpine.js for small client-side interactions. Headless Magento — typically PWA Studio with React on top of GraphQL — is a different architecture: separate frontend app talking to Magento purely through API. Hyvä is simpler, cheaper to maintain, and faster on most metrics. PWA Studio is more flexible if you need a single frontend across multiple backends or a native mobile app sharing logic with the web. For most Magento stores, Hyvä is the right answer.
Does Hyvä support B2B?

Yes. Hyvä works with Magento B2B (Adobe Commerce B2B module) — company accounts, requisition lists, quote workflow, shared catalogues, negotiable quotes — all render in the Hyvä storefront. Some B2B-specific UI (the requisition list page, the quote request form) needs Hyvä-native templates if your team has heavily customised the Luma B2B views; the Compat Module covers the unmodified default views. B2B stores often see the biggest performance lift from Hyvä because they tend to have heavy PLPs and large catalogues where every kilobyte of JavaScript hurts.
How long does Hyvä migration take?

Typical range is 4 to 12 weeks for an existing Luma store, depending on customisation depth and extension count. Lightly customised stores (mostly default Luma + 5 – 10 extensions) can land in 4 – 6 weeks. Mid-complexity stores (custom theme + 15 – 25 extensions + custom B2B flows) take 6 – 10 weeks. Heavy stores (deeply customised theme + 30+ extensions + bespoke checkout / configurator logic) take 10 – 12 weeks plus a phased cutover. Brand-new builds on Hyvä are faster because there is no Luma legacy to port — usually 3 – 6 weeks for a standard store.

Hyvä audit

Want a Hyvä audit on your Magento store?

Send your storefront URL — I will run a Lighthouse + extension-compat audit and reply with a written migration plan, fixed-price quote, and earliest start date. 24-business-hour turnaround.

Get a Hyvä audit Hire me directly

What is Hyvä Themes ?

Replaces the Luma JS stack wholesale

Server-renders HTML, sprinkles Alpine for interactivity

Hyvä Compatibility Module bridges Luma extensions

Hyvä Checkout is a separate $1k product

Compatible with Magento 2.4.4+ Open Source and Adobe Commerce

New Magento builds in 2026

Existing Luma stores below Lighthouse 60

Fashion, electronics, B2B — conversion-led stores

Performance-critical peak season (Diwali, BFCM)

Skipping Hyvä Checkout

Migrating without an extension audit

Treating Hyvä as a UI refresh

Hyvä theme development service

Hyvä vs Luma

Hyvä vs PWA Studio

What is Hyvä Checkout

Magento 2 performance optimization

Want a Hyvä audit on your Magento store?