Requirements and compatibility

Review the platform and the intended tweaks before installing POM Tweaks. The plugin package contains many independent features, so compatibility is determined both by the plugin’s base requirements and by the integrations used on the site.

Base platform

The current private release metadata requires:

Use a production release ZIP. The package includes POM Framework and the other Composer runtime dependencies used by settings, licensing, images, and PDF generation. A repository source archive or incomplete copy can activate without all production files and is not a supported substitute.

Administration permissions

On a single-site installation, an administrator with manage_options can open both settings interfaces.

On multisite:

• network settings under Network Admin → Settings → POM Tweaks require network settings permission;
• the shared POM Tweaks license can be changed only by a network administrator;
• a site administrator can manage the current site’s available settings but cannot replace the network license;
• the local updater requires POM Tweaks to be network-active or active on the main site.

Plan the activation mode before configuration. A setting saved for one site is not evidence that the same feature is configured for every site in the network.

Optional product dependencies

POM Tweaks itself does not require WooCommerce, WooCommerce Bookings, or Polylang Pro. Their related controls are conditional:

• WooCommerce features are useful only where WooCommerce supplies the relevant product, cart, checkout, order, email, or account workflow.
• Enhanced availability finder is added to the modern catalog only while woocommerce-bookings/woocommerce-bookings.php is active.
• The modern Default language SEO setting is added only while polylang-pro/polylang.php is active.

WooCommerce modules depend on the commerce environment even when their settings were saved earlier. Verify the exact dependency in the feature guide rather than assuming that a visible switch proves the integration is ready.

Compatibility review by change type

Before enabling a tweak, identify the system it touches:

• Administration and login: test every affected role, the main dashboard, network administration where relevant, and account recovery.
• Content, SEO, redirects, and RSS: test public URLs, status codes, metadata, archives, feeds, sitemaps, and multilingual variants used by the site.
• Media: confirm filesystem write access, backups of originals, generated sizes, attachment references, and the image formats supported by the server.
• Email: use the real sending path and verify headers, HTML, plain-text behavior, recipients, and deliverability.
• WooCommerce: test simple and variable products, taxes, shipping, coupons, cart, checkout validation, payment completion, orders, refunds, subscriptions, and emails where the chosen tweak can affect them.

Theme and plugin customizations can use the same WordPress or WooCommerce hooks as POM Tweaks. Compatibility therefore needs a representative staging test even when every product meets its advertised version requirement.

Pre-install decision

Proceed when:

• WordPress, PHP, and JSON meet the baseline;
• the official release package is available;
• the administrator knows whether the plugin will be site-active or network-active;
• every intended integration is installed and supported;
• a staging or rollback path exists for persistent changes;
• the site owner can obtain and manage the required POM Tweaks subscription and license.

Then follow Install and activate POM Tweaks.