Skip to main content

Verifiable compatibility

Compatibility and installation

The demo works without installing anything. Before activating Flatzer on your store, we verify the platform, theme, security policy, and removal plan.

This matrix separates the widget available today from integrations that need managed validation and capabilities that we do not yet offer as a general product.

How to read the matrix

Each status describes what we can state and activate today, not a future promise.

  • Available

    It exists in the current product and can be used when its stated requirements are met.

  • Managed validation

    A technical path exists, but we activate it only after checking the specific store and its limits.

  • Not productized

    We do not present it as a general capability or include it without a specific scope.

Options by platform

The web widget is the common foundation. Native integrations are validated per platform before we commit to an activation.

Generic web script

Available

The widget can be added to a website that allows Flatzer's public script to be inserted.

Activation requires the correct hostnames to be allowed and confirmation that the theme and security policy permit the script and its connections.

Shopify

Managed validation

We validate installation on the store's theme before activating the widget.

Public catalog extraction is available only when the store exposes products.json. A complete native integration is not offered as universal compatibility.

PrestaShop

Managed validation

An installation module exists, but the version, theme, multistore setup, and removal path must be tested in the real environment.

The availability of a package does not mean automatic compatibility with every store or customization.

Adobe Commerce / Magento

Managed validation

An installation package exists, subject to validation of the version, cache, theme, and uninstall process.

Complete native productization remains under validation; we do not claim universal Magento installation coverage.

WooCommerce and other platforms

Managed validation

We can assess the web script or the appropriate installation asset based on how the store is built.

We do not assume a complete native connector exists. We confirm the method and its limits before activation.

Data and actions: current limits

Installing the widget does not by itself grant universal access to commerce systems, checkout, or live data.

Themes and Content Security Policy

Managed validation

Custom themes, tag managers, and CSP rules can change how the widget must be loaded.

We check the insertion point, allowed hostnames, and required connections without replacing the site's existing security policy.

Checkout and cart

Not productized

Flatzer does not complete checkout or add products to every cart through a universal integration.

Page actions are configured only for approved elements on a specific site and are not a general native cart or payment integration.

Configured catalog

Available

The agent can answer and recommend from the catalog and content imported or configured for the store.

On Shopify, public information can be extracted when products.json is exposed. Answers remain limited to the available knowledge.

Live stock and synchronization

Not productized

Flatzer does not read live stock or promise scheduled catalog synchronization.

The method and frequency for updating knowledge must be agreed and validated for each activation.

Installation, updates, and removal

Compatibility covers how the widget goes in and how it comes out. We do not consider activation complete without a testable procedure.

  1. 01Available

    Installation

    The base path loads the web widget with a public key and allowed hostnames.

    The demo installs nothing. The final method is chosen after reviewing the platform and environment.

  2. 02Managed validation

    Updates

    We review who owns the installation point and how changes will be tested.

    A widget update does not imply automatic catalog synchronization or universal module updates.

  3. 03Not productized

    Automated rollback

    There is no universal automated rollback. We agree how to manually disable or remove the script, block, or module used.

    The removal procedure depends on the validated installation method.

Technical detail, when you need it

These checks help your technical team decide without filling the first evaluation with jargon.

Script, hostnames, and CSP

The loader is served from flatzer.com and uses a public widget key. The store hostname must be allowed. Where CSP is present, we review at least the required script, connection, and image sources; they are merged into the existing policy, not used to replace it.

Themes, versions, and environments

We ask for the platform, version, theme, customizations, cache, and a test environment when one exists. An available package or snippet does not by itself prove compatibility with every combination.

Checkout and page actions

The widget can navigate to approved routes and execute configured actions on specific elements. This does not turn Flatzer into a universal cart, payment, or checkout integration.

Catalog and knowledge updates

The agent answers from imported or configured content. Public Shopify extraction depends on products.json being exposed; live stock and scheduled synchronization are not part of the current promise.

Request a validation

Send us the minimum context and we will tell you what is available, what needs testing, and what is out of scope before anything is installed.

  • Public URL or hostname to be activated
  • Platform, version, and theme if known
  • Relevant customizations, tag manager, or CSP
  • Availability of a test environment and technical owner
Request validation · [email protected]

Do not send passwords, private keys, or administrator access by email. We will request an appropriate channel if a test needs additional access.