Divi WooCommerce: Woo Modules, Theme Builder Store Templates and the Divi 5 Switch

No store panel, just modules

Open the Customizer on a Divi store and you will not find a tidy WooCommerce tab full of shop column counts and gallery styles. Divi's answer to every layout question is the Visual Builder, and WooCommerce is no exception. Elegant Themes' ecommerce page lists 25 Woo modules. Seventeen of them break product and shop pages into parts you can place anywhere: Product Title, Images, Gallery, Price, Add To Cart, Stock, Rating, Reviews, Tabs, Description, Meta, Information, Upsell and Related Products, plus a Products grid, Breadcrumbs and a Notice module for WooCommerce messages.

The other eight arrived in November 2021 for the money pages: Cart Products, Cart Totals and Cart Cross Sells, then Checkout Billing, Shipping, Information, Details and Payment. Elegant Themes says that when you enable the Divi Builder on the cart or checkout page, Divi converts the page into those eight modules for you. From there, every field group can be moved, restyled or wrapped in your own sections.

Theme Builder templates for product, cart, checkout and account pages

Designing one product page is a craft project. Designing every product page is a template, and that is the Theme Builder's job. A product template applies to all products or to products in chosen categories, and category templates control archive pages. For the store's fixed pages, Elegant Themes' help center lists three dedicated assignments under WooCommerce Pages: Cart, Checkout and My Account.

1. 1

   Open the Theme Builder

   Divi > Theme Builder, then Add New Template and Build New Template.

2. 2

   Pick the page type

   Under WooCommerce Pages choose Cart, Checkout or My Account, or assign a template to products or product categories.

3. 3

   Add a custom body

   Start from scratch or load a layout from the Divi Library or Divi Cloud, then place the Woo modules that page needs.

4. 4

   Keep the Notice module

   Coupon messages, stock errors and validation warnings appear through WooCommerce notices. A template without somewhere to show them leaves buyers guessing.

5. 5

   Test as a customer

   Log out, add a variable product, apply a coupon, change the shipping address and pay. Then log in and check the account pages.

Two cautions. The My Account template has no dedicated module; the help center says the Text module displays the account content, and you dress it with other modules around it. And the more of the checkout you rebuild, the more you own when WooCommerce changes. If templates stop appearing on their pages, Divi Theme Builder templates not showing walks the assignment conflicts.

There is no free Divi, and no paid store tier either

Divi has no free version, which simplifies the free vs paid question: every Woo module and every Theme Builder template comes with every plan. The upper plan adds services, not store features. As of October 2026:

Refunds are offered for 30 days. The real extra spending on a Divi store tends to happen in the third-party market: module packs for filters, swatches, mini carts and checkout extras. Before buying any of them in 2026, ask the seller whether the pack is Divi 5-ready, for reasons the next section explains. The full plan breakdown is in Divi pricing.

Divi 5 and a live store: switch on purpose, not by accident

Divi 5 went stable on February 26, 2026. It is a rebuild: content is no longer saved as shortcodes but in a block-based format, layouts gain Flexbox and CSS Grid, and the Loop Builder arrived. The move is opt-in. Divi 4 sites stay on the Divi 4 update path until someone clicks Enable Divi 5 Updates and runs the Divi 5 Migrator, and the Divi 4 line is still maintained (4.27.9 shipped on September 18, 2026).

For stores, the Woo modules came across natively rather than in a compatibility shim. Elegant Themes released 17 product modules for Divi 5 in October 2025, with cart and checkout modules following before the stable release. Their guidance splits the work cleanly: Woo product modules for single product layouts, the Loop Builder for product collections and archives. The Divi 5 changelog since launch also shows how much checkout work is still settling:

• 5.4.0: fixed Woo Cart Totals not updating after a coupon was applied on Theme Builder cart layouts.
• 5.9.0: checkout pages built with Divi checkout modules now render one consistent checkout form instead of multiple competing forms.
• 5.12.0: fixed checkout timing out or showing a payment method error on the order confirmation page.
• 5.14.0 (September 28, 2026): fixed guest checkout creating an account when Create an account? was left unchecked.

None of that is unusual for a rebuild, and all of it is fixed. It is the case for migrating a store on a staging copy, with real test orders, rather than on a Tuesday afternoon. Watch third-party Woo add-ons most closely: modules that are not Divi 5-ready run in backward compatibility mode, which loads the Divi 4 framework on those pages, needs a reload after each setting change and shows raw shortcodes if the plugin is switched off. If shortcodes are already showing, see Divi shortcodes showing.

The plugins a Divi store still installs

Divi is unusually complete as a design tool and unusually thin as a store engine, by design. A working Divi shop still needs most of this list:

• A payment gateway for each provider, which the Woo Checkout Payment module then styles.
• Tax and shipping beyond WooCommerce's basic rules: live carrier rates, multistate sales tax, local pickup logic.
• Variation swatches and wishlists. Neither appears in Divi's module list, so they come from WooCommerce extensions or Divi module packs.
• Product filtering. Divi added Loop Filter modules in 2026; check whether they cover your product attributes before buying a filter plugin.
• Subscriptions or memberships sold through WooCommerce extensions. When renewals stop, see subscriptions not renewing.
• SEO, caching, backups, security and SMTP. If receipts vanish, start with order emails not sending.

Each of those has its own settings page and update schedule, and on a Divi store each one also has to look right inside a builder layout. That second requirement is where many Divi store tickets begin.

Divi's Performance tab meets an uncached checkout

Divi ships with its speed switches already on: Dynamic CSS builds a stylesheet from the modules a page uses, Critical CSS loads above-the-fold styles first, Dynamic JavaScript loads libraries on demand, and jQuery is deferred to the footer unless a header script needs it. On cached product and category pages, those switches do their best work.

Checkout is different. Cart, checkout and My Account are built fresh for each shopper, so WooCommerce excludes them from page caching, and a heavily designed checkout template means more builder work on every uncached request. WooCommerce's own classic cart and checkout scripts run on jQuery, so on those pages the library is needed whatever Divi defers. If your header shows a cart count through the Menu module, check whether the page fires WooCommerce's fragments refresh: open the network panel and filter for get_refreshed_fragments.

Keep checkout templates plain. Every section you add there is decoration rendered on the slowest path in the store. The full set of switches, and when to change them, is in Divi speed, and if a slow store needs a second pair of hands, our theme speed optimization service starts with a measurement, not a plugin.

Where Divi stores break, and the page for each

• The builder will not open on a product or checkout template. Elegant Themes points to plugin conflicts, caching, PHP below 7.4, and limits; it recommends memory_limit 256M and max_input_vars 6000. See Divi builder not loading.
• Template edits will not save. Security plugins such as Wordfence, host firewalls, caching, Static CSS File Generation and minify plugins are the usual suspects in the vendor's own list.
• Checkout fields or payment box missing. Check that the template still contains Checkout Billing and Checkout Payment, then work through checkout not working.
• Variations will not select on a custom product template. The Add To Cart module carries the variation form; variations not showing explains how to isolate a script conflict.
• Layout scrambled after an update. Start at Divi layout broken after update, then the cross-theme WooCommerce layout broken checklist.
• Order data acting strangely after enabling HPOS. Theme templates are rarely the cause; HPOS sync issues covers the checks.

For hands-on help, our Divi repair team and WooCommerce website repair work on the theme and the store together.

Leaving Divi with a store attached

Here is the good news about moving a Divi store: the store itself is not in Divi. Products, customers and orders live in WooCommerce's tables and export cleanly. The designs are another story. Divi 4 layouts are shortcodes, Divi 5 layouts are its own block format, and neither renders anywhere but Divi, so product templates, cart and checkout designs are rebuilt rather than carried over.

Divi lets you design every pixel of the checkout, which also means you own every pixel when it breaks.

Stay on Divi if your team designs in it daily and the store sells ordinary products. Consider Next.js when checkout speed, custom pricing, quotes or member-only catalogs start to matter more than drag and drop. A Next.js store prerenders product pages and keeps checkout on a short server path, and every site we build includes Athena CMS with e-commerce built in. Weigh it in Divi vs Next.js, plan the move with WooCommerce to Next.js and Divi to Next.js, or keep Divi and let our Divi developers build the templates properly. Other theme guides live in the WordPress themes section.