What are the minimum system requirements for WP Optix?

WP Optix requires WordPress 5.8+, WooCommerce 7.0+, PHP 8.0+, and HTTPS enabled on your domain. HPOS (High-Performance Order Storage) is supported but not required.

How do I install WP Optix on my WooCommerce store?

Upload the plugin ZIP via WordPress admin under Plugins > Add New > Upload, activate it, enter your license key in WP Optix settings, then map your lens category rules and run a test purchase.

Does WP Optix work with page caching plugins?

Yes, but you must exclude cart and checkout pages from caching to avoid stale prescription data. Most caching plugins like WP Super Cache and W3 Total Cache support page exclusion rules.

Can I use WP Optix with WPML or Polylang for multi-language?

Yes. WP Optix Professional and Agency plans include multi-language support. All prescription labels, validation messages, and UI strings are translatable through standard WordPress localization.

How do I handle different prescription ranges per lens brand?

Use category-level rule inheritance. Set default ranges at the contact lens category level, then override specific values per product family. This keeps your catalog consistent while supporting brand-specific parameters.

WP Optix Documentation | Setup and WooCommerce Implementation

Quick start

1. Requirements

WordPress 5.8 or newer
WooCommerce 7.0 or newer
PHP 8.0 or newer
HTTPS enabled for checkout security

2. First deployment

Install plugin ZIP in WordPress admin
Activate license in WP Optix settings
Map lens category rules
Run a complete test purchase

Operational guides

Prescription logic

Set valid ranges for sphere, cylinder, and axis by product family and enforce safe combinations.

Pricing and discounts

Create quantity-based incentives across left and right eye totals without custom code.

Catalog governance

Apply category-level defaults and exceptions to keep large catalogs operationally consistent.

Deep-dive technical documentation

WooCommerce left and right eye cart

Implement separate line-item logic for bilateral prescriptions and fulfillment safety.

WooCommerce dual eye prescription

Configure independent eye fields with guided UX and server-side validation.

Separate cart items same product

Model one product as multiple cart entities when eye configurations differ.

WooCommerce cascade dropdowns plugin

Use dependency-based option selectors instead of oversized variation matrices.

Conditional variations for prescriptions

Apply rules that expose only valid optical combinations by context.

Sphere cylinder axis plugin workflow

Capture and validate clinically relevant values by product family.

Dynamic pricing for contact lens boxes

Deploy tier-based pricing logic aligned with bilateral quantity behavior.

WooCommerce HPOS optical readiness

Preserve metadata integrity and performance on modern order storage.

Compatibility and environment

Tested hosting providers

WP Optix is tested on major managed WordPress hosts including Cloudways, Kinsta, SiteGround, and WP Engine. Any host running PHP 8.0+ with standard WordPress and WooCommerce configurations will work.

Theme compatibility

WP Optix works with any WooCommerce-compatible theme. It hooks into the product page, cart, and checkout without requiring theme-specific templates. Popular themes like Astra, GeneratePress, Flatsome, and Storefront are fully supported.

Plugin compatibility

Tested with WPML, Polylang, WooCommerce Subscriptions, WooCommerce Shipping, and major payment gateways including Stripe, PayPal, and Mollie. HPOS (High-Performance Order Storage) is fully supported.

Performance impact

WP Optix adds less than 15KB to your frontend bundle. Cascade selectors load asynchronously, prescription validation runs server-side, and all metadata is stored in native WooCommerce order meta fields without additional database tables.

Troubleshooting

Re-save permalinks if routing conflicts appear after installation.
Disable caching on cart and checkout pages to avoid stale prescription payloads.
Verify theme overrides do not alter required WooCommerce line-item metadata.
For checkout modal tests, run the site on http/https, not file://.
If cascade dropdowns show blank options, verify that product-level prescription ranges are configured in the WP Optix settings tab.
Order metadata not appearing? Ensure your theme uses standard WooCommerce order templates and not custom overrides that strip item meta.

Open support Contact sales engineering

Frequently asked questions

What are the minimum requirements?

WordPress 5.8+, WooCommerce 7.0+, PHP 8.0+, and HTTPS enabled. HPOS is supported but not required for installation.

How do I install WP Optix?

Upload the ZIP via Plugins > Add New > Upload in WordPress admin, activate it, enter your license key, map lens category rules, and run a test purchase.

Does it work with caching plugins?

Yes, but exclude cart and checkout pages from caching to prevent stale prescription data. WP Super Cache and W3 Total Cache both support page exclusion rules.

Can I set different ranges per lens brand?

Yes. Use category-level rule inheritance for default values, then override specific ranges per product family. This scales well across large catalogs with multiple manufacturers.

Is multi-language supported?

Professional and Agency plans include multi-language support. All UI strings, labels, and validation messages are translatable through standard WordPress localization files.

Where is prescription data stored?

All prescription values are stored in native WooCommerce order item meta. No custom database tables are created. This ensures compatibility with all standard WooCommerce export, reporting, and fulfillment tools.