Pricing Table
Make the choice between plans obvious
Columns of plans, each with a price, a list of what it includes and a button of its own — one plan highlighted, and that one first when the table stacks on a phone.
Boxed, three plans, the middle one highlighted.
One plan that stands out
A highlight switch puts a badge on a plan, paints its border in your accent colour and moves it to the top of the stack on a phone. Shoppers who are given a recommendation take it.
Feature lists that read as yes and no
Every feature is a row with a tick, a cross or neither, and a row a plan does not include can be dimmed. The comparison is legible without a legend.
Prices you write, not prices a formatter decides
"49", "1 299" and "Free" are all valid, with the currency symbol and the suffix as fields of their own. Nothing is parsed, so nothing is reformatted behind your back.
Use cases
Where shops put it
Subscription or membership tiers
Three plans, the middle one badged "Most popular", each button going to the product that starts that subscription.
Service packages
Installation, extended warranty and a care plan as three columns, with the ticks and crosses doing the comparison your table of specifications was doing badly.
Trade and wholesale tiers
On a B2B page, four columns of order volumes and terms — with "Contact us" as the button on the largest, and no price at all where a price does not belong.
- Columns
- Automatic (as many as there are plans, up to four) or a fixed 2, 3 or 4.
- Accent colour
- Which paints the highlighted plan's border, its badge, the feature ticks and the primary buttons — one setting for the whole table.
- Appearance
- Boxed (a card per plan) or Flat (no cards, plans divided by a hairline).
- Per plan
- Name, one-line tagline, price with a prefix and a suffix, a billing period, a highlight switch with its own badge text, and a button (text, link, style).
- Per feature
- The text, a tick, a cross or no icon at all, and a dimmed row for what the plan does not include.
- Drag to reorder
- Plans, and features within their plan; duplicate or delete either.
- Advanced tab
- On the table, on each plan and on each feature.
Shown in the demo store
Flat, four plans, columns set to automatic.
Two plans, what is included and what is not.
On a phone, where the highlighted plan moves to the top.
Native and honest
Your content is written in Magento's own format
Each plan is stored as a readable block and each feature list as a real <ul> — so a plan is still a plan to anything reading the page, with or without our stylesheet.
Every element saves itself the way native Page Builder saves its own: a plain <div data-content-type="wrizu_…"> with its settings in data-* attributes, stored with the page. There is no proprietary database table, no shortcode, no second editor and nothing that has to be converted later.
That has a practical consequence. Disable the module and the storefront keeps serving those pages: headings, copy, images, links and buttons stay visible and clickable, and the styling you set per element — alignment, colours, spacing — stays with them, because it lives in a <style> block stored with the page rather than in our stylesheets. What you lose is what our CSS draws: the layouts, the borders and shadows, the button variants and the bundled icons.
One honest warning
With the module switched off, do not open and save a page that contains Wrizu elements — Page Builder flattens any page holding a content type it does not know into a single HTML Code block, and that save cannot be undone. It behaves that way with every unknown content type, not only with ours, and the storefront is unaffected either way; the rule is simply to leave those pages alone until the module is back on.
Works with any Luma-based theme
The elements are built on the same front-end stack the native Page Builder uses: jQuery and the libraries Page Builder already loads. They target Luma-based themes — Magento Blank, Luma, and the custom themes shops build on either of them.
Buttons use Luma's own button mixins, so a Wrizu button looks like a button from your theme rather than like a button from a plug-in. All of the module's CSS is scoped to [data-content-type^="wrizu_"], so it styles our elements and nothing else in your theme.
Requirements
- Magento Open Source or Adobe Commerce 2.4.6 or newer, with the
Magento_PageBuildermodule enabled - PHP 8.1 to 8.5 — whichever your Magento version supports
- No other extension, no external icon font, no CDN dependency
Questions about this element
Conversion & trust
More in Conversion & trust
Auto Popup
The same window with no trigger: it opens itself after a delay you set.
Comparison Table
Two to five things side by side, a row per feature, one column recommended.
Countdown Timer
Days, hours, minutes and seconds down to a deadline you set.
Coupon Code
A discount code on a ticket, in a line or on a banner, with a button that copies it.
CTA Box
A call-to-action band with a heading, a subheading and up to two buttons.
CTA Popup
A button or a text link that opens a window holding real Page Builder content.
Logo Cloud
A row of brand, partner or payment marks, as a grid or a carousel — or a row of social icons.
Newsletter Signup
Your store's own newsletter subscription as a bar, a card or a full-width band.
Star Rating
A score in stars — to a tenth of a star, out of five or ten — with the number and a caption.
Testimonials Slider
A carousel of customer quotations with photographs and star ratings.
Thirty-five conversion elements for the Page Builder you already have
Wrizu Page Builder Extensions adds them to the native Magento 2 Page Builder — no second editor, no proprietary format, no content held hostage.