Oxygen WordPress Page Builder-beta.4

05/25/2026

Version: 6.1.0-beta.4

Category: Temporary

View Changelog

Previous Versions

-95%

Original price was: $99.00.Current price is: $4.99.

He Oxygen WordPress Page Builder It's a high-performance visual page builder geared towards designers and developers who need complete control over markup, styles, and structure without relying on pre-built themes. Ideal for agencies and WooCommerce stores seeking true page load speed, clean code, and design flexibility without compromising front-end stability.

Introduction to Oxygen WordPress Page Builder

He Oxygen WordPress Page Builder It eliminates the friction that arises when a developer tries to build complex layouts with tools that generate bloated code, redundant classes, and theme dependencies that clash with WooCommerce templates on checkout, product pages, and account views.

Its technical nature relies on a component-based construction approach using reusable components and centralized global styles, which drastically reduces visual consistency errors when a team works in parallel on different sections of a store. The developer's workload is lower because design changes don't require modifying theme files or overwriting accumulated CSS.

A technician managing a store with a large catalog opens the builder, locates the category page template, adjusts the product grid with direct visual controls, and applies conditional classes without touching the code editor — the change is reflected in real time and does not break the integration with the WooCommerce filters active in that same view.

Product overview

The functional area of this builder ranges from the design of individual pages to the management of global templates for taxonomies, custom entry types, and WooCommerce flows, with a direct impact on the visual stability and response speed of the front-end in stores that are growing in catalog and traffic.

Before implementing this tool, many teams managed custom CSS layers on top of third-party themes, conflicts between layout plugins, and broken WooCommerce templates after every update. With the plugin active, the design workflow becomes centralized in a single environment that controls both the layout and the scripts loaded per page.

Without the add-on: Checkout and product templates inherit styles from the active theme, generating visual inconsistencies that are difficult to debug and high loading times due to unoptimized assets.
With the active add-on: The designer builds the checkout template directly from the builder, assigns specific styles to the payment form, and controls which scripts are loaded at that specific URL.
Observable result: The checkout has a consistent look with the brand identity, loads faster, and generates fewer abandonments due to visual confusion in the purchase process.

Requirements and compatibility

For this builder to work correctly, you need a functional WordPress installation with WooCommerce active if you intend to use the store templates. You also need to verify that there are no other page builders loading their own assets globally, as the coexistence of multiple builders creates script and style conflicts that are difficult to isolate.

Main dependency: WordPress as the base CMS; WooCommerce required only for the shop, cart, checkout, and customer account templates.
Functional compatibility with standard payment gateways, shipping systems, coupons, taxes, and user roles managed from the WooCommerce back office without additional modifications.
In stores with advanced checkout customizations — extra fields, conditional logic, or third-party integrations — it's advisable to validate the behavior in a staging environment before publishing changes to production.

Key benefits for your operation

Full control over HTML markup: Many developers waste hours fixing unnecessary divs generated by their current constructor. This extension produces clean, semantic code, making maintenance easier, improving indexing, and reducing debugging time when something goes wrong in production.
Global styles without external CSS files: Maintaining visual consistency across a store with dozens of templates is costly if every change requires editing multiple files. This module centralizes color, typography, and spacing variables in a single panel, so a branding adjustment is applied across all pages without the risk of oversight.
Dynamic templates for WooCommerce: Building a product template once that works for the entire catalog is exactly the kind of scalability a technical team needs. This tool allows you to create dynamic layouts that directly consume product data, without duplicating templates for each category.
Selective loading of scripts per page: Excessive JavaScript is one of the biggest performance bottlenecks in stores with many plugins. The builder allows you to disable its own assets on pages where they aren't used, reducing the front-end's weight without the need for additional optimization plugins.
Reuse of components between projects: Agencies that manage multiple stores can export components designed in one project and import them into another, maintaining operational consistency and reducing build time for each new client.
Edit in context without changing screens: The typical workflow of opening the back office, editing a shortcode, saving, and previewing interrupts the designer's focus. With this plugin, visual adjustments are applied directly to the actual front end, shortening review and approval cycles with clients.

Key features of Oxygen WordPress Page Builder

Builder based on reusable components: It allows you to create sections, headers, footers, and content blocks as independent components that are updated in all instances from a single editing point, eliminating the problem of updating the same element on twenty different pages.
Native integration with custom content types: The tool reads custom fields from plugins like ACF or MetaBox and exposes them directly in the builder as draggable elements, allowing a developer to build dynamic templates for catalogs, portfolios, or directories without manually writing PHP template code.
Display conditions per rule: Each template can be assigned to specific URLs, taxonomies, user roles, or query results, giving the operator granular control over which layout each visitor segment sees — useful for showing special prices or offer banners only to users registered in the store.
Integrated CSS editor with autocomplete: For those who prefer to write styles directly, the module includes a CSS editor linked to the selected element with real-time suggestions, preventing typos in property names and speeding up the fine customization work.
Customizable breakpoint selector: Modern stores receive traffic from devices with widely varying screen widths. This plugin doesn't limit breakpoints to the three standard ones; the designer can define their own breakpoints and adjust the layout independently for each one, without changes to one breakpoint affecting the others.
Managing global and local CSS classes: Unlike other builders that apply inline styles, this extension works with reusable real classes, making the generated CSS lighter, easier to audit, and more compatible with workflows that include code version control.

Who is this product for?

This builder is designed for those who feel their current layout tools impose too many visual restrictions or generate accumulated technical debt. It's not a solution for users who want to drag and drop blocks without understanding what's happening underneath; it's for users who want to design with precision and maintain control over the resulting code.

Administrators and developers who need traceability over every design decision, control over which scripts are loaded on each URL, and the ability to audit the markup generated by the builder.
Agency teams managing multiple simultaneous projects need to reuse components, maintain consistency across stores, and reduce delivery time without sacrificing technical quality.
UX and conversion optimization professionals who rely on clean layouts, controlled load times, and the ability to customize checkout or product pages without touching the base theme code.

Real-world use cases

Redesigning the checkout without breaking the WooCommerce integration: A fashion store needs a single-page checkout with reorganized fields and an order summary that's always visible on desktop. With the builder active, the technician creates a specific template for the checkout URL, reorganizes the form blocks using the module's grid system, and applies the brand's own styles—without altering the WooCommerce PHP or breaking the payment gateway hooks. The result: a checkout with its own identity that keeps all the transactional logic intact.
Dynamic catalog templates with thousands of products: A wholesale distributor has categories with hundreds of product references and needs each product page to display specific technical attributes based on the item type. The developer builds a dynamic template that reads the product's custom fields and presents them in a structured layout without duplicating templates. Each new product automatically inherits the template, without manual intervention.
Customizing the account area by user role: A membership platform wants to display different content on the account page depending on whether the user has an active subscription. Using the builder's display conditions, the team assigns two distinct layouts to the same URL with role-based rules, eliminating the need for an additional access control plugin for that specific case.
Header and footer components shared across agency sites: A team manages eight online stores for different clients, each with distinct visual identities but a similar navigation structure. They export the header component from the base project, import it into each new store, and adjust only the color and logo values. The header build time drops from hours to minutes, and any future structural improvements can be replicated in the same way.

Frequently Asked Questions about Oxygen WordPress Page Builder

Does it work well with WooCommerce or do I need additional plugins for the store templates?

WooCommerce integration is native for the store's main templates: shop, product, cart, checkout, and customer account pages. No intermediary plugins are needed to build these layouts. However, if the store uses very specific WooCommerce extensions—such as third-party multistep checkouts—it's advisable to verify in a staging environment that the hooks of these extensions continue to function correctly with the new template before publishing to production.

Does the end customer's experience affect the buying process?

It depends on how it's used. When the builder generates clean code without unnecessary scripts at checkout, the experience improves: faster pages, fewer distracting visuals, and a form that's more consistent with the brand. The risk arises if resource-intensive animations are added or a functional element of the form is accidentally removed during design. Reviewing the entire mobile checkout flow before publishing prevents this scenario.

Can I create rules or conditions to show different content based on user behavior?

Yes. The builder allows you to assign templates and components based on conditions such as user role, visited URL, content taxonomy, or the result of a custom query. This allows you to display offer banners only to unregistered users, special prices to wholesalers, or different calls to action depending on the product category the visitor is viewing, without needing external plugins for that display logic.

Does it interfere with WooCommerce Subscriptions renewal flows or failed payments?

The builder operates at the presentation level, not the transactional logic level. Automatic renewals, payment retries, and failed payment notifications occur in the WooCommerce backend regardless of the active frontend layout. However, it's important to verify that the account page template correctly displays pending renewal notices and payment method update links, as these elements depend on how the account layout was built.

Are coupons, taxes, and shipping costs still calculated correctly with a custom template in the shopping cart?

WooCommerce's calculation logic operates on the server and is independent of the page builder. Taxes, shipping, and discounts are calculated the same way regardless of the active visual template. The key point is to ensure that the cart template includes the correct functional blocks—totals, coupon field, shipping selector—and hasn't replaced them with static elements that don't dynamically update values.

How does the tool perform in stores with high traffic volume or very large catalogs?

The performance impact depends directly on how the templates are built. A well-constructed layout using this module, with CSS classes instead of inline styles and avoiding unnecessary scripts, tends to produce lighter pages than those generated by builders that load assets globally. That said, for very large catalogs with complex dynamic templates, it's advisable to combine the builder with an appropriate caching layer to avoid repeated server queries on each product page load.

Is it viable to use it in a multisite environment or to manage the design of several stores from a central point?

The builder is compatible with WordPress multisite installations, although managing templates across sites requires manual export and import of components rather than centralized automatic synchronization. For agencies that maintain multiple independent stores—not necessarily on a multisite—the workflow of exporting components from a base project and importing them into each new store works practically and significantly reduces repetitive build time across similar projects.

How do I verify that the builder is working correctly in my store?

A practical checklist includes: verifying that the template assigned to each key WooCommerce URL loads correctly in the browser inspector, confirming that there are no JavaScript errors in the console related to builder assets, checking that the entire checkout flow works on mobile and desktop without broken visuals, verifying that global styles are applied uniformly across all pages using shared components, and finally, validating that the load time of the main pages has not increased from the previous baseline.

Short description

Visual page builder for WordPress with full markup control, dynamic WooCommerce templates, and selective script loading — the solution for those who need precise design without technical debt or bloated code.

Latest update: 25/05/2026

Get your questions answered here

We answer your questions so you can buy in an informed and confident manner.

Does my purchase include updates?

Yes. Every product purchase includes lifetime updates, so you won't have to pay extra under any circumstances.

Is there a daily download limit?

No, not at all. After your purchase, you can download it as many times as you need, without any problem.

On how many websites can I use the products?

You can use your purchases on as many domains (websites) as you want, without any problems.

Does it include technical support?

Yes. We offer technical support Monday through Friday, during business hours UTC -3. This support includes assistance with issues related to download problems, installation problems, or errors with the purchased product.

Furthermore, support does not include configurations, customizations, tutorials, or services associated with the author.

Does my purchase have a warranty?

Yes, of course. If you have any problem that we can't solve, or if there's an external issue that doesn't have a general solution related to our service, you'll receive support and, if necessary, a full refund.

How do I access support?

After your purchase, from your user account, you can access the support section, where you can open a ticket and our team will assist you with whatever you need.

View all Frequently Asked Questions