Help4 Builder Pricing Comparison Tutorial
Before the first click
Confirm what you are editing and where each kind of change belongs.
Read the page or template title first, select the exact element in the canvas or Navigator, then use the inspector tab that matches the job. This prevents a content change from becoming an accidental layout change.
Content
Change words, links, images, icons, data sources, shortcodes, and element-specific information.
Design
Change colors, typography, spacing, borders, radius, alignment, states, and desktop, tablet, or mobile values.
Advanced
Change labels, anchors, classes, attributes, visibility rules, motion, and other expert controls.
Page Settings
Use page-wide history, globals, publishing, template assignment, and recovery controls instead of editing one element.
Visual orientation
Match the screen before following the steps.
Open each image at full size. The numbered notes explain what the screen controls and what to confirm before changing customer content.
Screen 1
Templates in Studio
Browse reusable structures and choose an insertion or replacement path intentionally.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 2
Template Library
Search page-purpose starters, insert a section, or deliberately replace a page instead of beginning from an empty screen.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 3
Current Studio workspace
See the element library, device controls, live page frame, inspector, performance guidance, and save state together.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 4
Builder Studio
Use the live page frame, element library, template library, inspector, responsive controls, performance guidance, and save state in one workspace.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 5
Commerce operations
Review catalog, orders, customers, subscriptions, payment routing, and store health from the native commerce hub.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 6
Commerce dashboard
Review products, orders, customers, subscriptions, gateway routing, imports, and migration tools from one commerce hub.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Watch the real workflow
Watch the clicks before making the change.
Use the narrated walkthrough first, then follow the written steps and verification checks on this page.
Lesson 38
Build a Five-Plan Pricing Comparison
Compare as many as five offers with semantic rows, honest distinctions, clear actions, and a deliberate narrow-screen order.
Read the complete transcript
- Start with the Decisions
List the decisions a customer actually needs to make before choosing a visual pattern. Give each plan a clear audience, price basis, included work, important limits, and one destination. Use a pricing comparison starter only after verifying it can represent every approved plan without hiding material differences in tiny text.
- Build Semantic Plan Content
Use headings, price text, real lists, buttons, and optional badges inside stable plan containers. Do not build the comparison as one pasted image or a maze of manual line breaks. Meaningful elements remain editable, searchable, accessible, and easier to reorder when a package changes.
- Set an Intentional Order
Choose the desktop grid and the tablet and mobile order deliberately. Five plans usually need a smaller grid or one-column sequence on narrow screens. Make the visual order match the document and keyboard order, keep plan names attached to their features, and avoid using CSS positioning to create a different inaccessible reading sequence.
- Test Prices and Actions
Verify every approved price, billing period, setup fee, feature allowance, exclusion, button label, and checkout or contact destination. Check wrapping at all responsive boundaries, keyboard focus, contrast on highlighted plans, and the public page. A pricing layout is not ready if one plan is clipped or a customer cannot tell what happens after clicking.
Lesson 12
Commerce Products, Quantity, and Checkout
Create a native product, configure purchase and quantity rules, and verify the checkout and order path.
Read the complete transcript
- Open Native Products
Open Commerce, then Products. Native Catalog mode lets you create simple, service, digital, booking, variable, and subscription products without adding a separate store plugin.
- Describe the Product
Set the name, SKU, status, price, stock, description, image, tax behavior, fulfillment, and customer requirements. Use variants when options need their own price, stock, image, or SKU.
- Set Quantity Rules
Turn off customer quantity when a configured package must stay one unit per cart line. Customers can still add another separately. Use the order-limit option only when the whole order may contain one.
- Test the Full Order
Run a test from product display through cart, payment routing, confirmation, inventory, customer record, and order status. Verify both normal quantity products and fixed one-per-line products.
Pricing workflow
Make differences easy to understand and hard to misread.
A comparison should help someone choose. Do not fill cells with vague checkmarks when the actual limit, service level, or billing term matters.
Avoid fake savings
Only show crossed-out prices or savings when the comparison is accurate and supportable.
Explain symbols
Use text such as Included, Not included, Up to 10, or Custom instead of unexplained icons.
Keep rows aligned
Dynamic content and wrapped labels must not detach a value from its feature.
Guided walkthrough
Make one verified change at a time.
Each step includes the action, why it belongs in this order, and the checkpoint to verify before moving forward.
-
Name each plan
Use names tied to customer fit and add a short best-for line instead of unexplained tier labels.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe name each plan result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
State the price honestly
Show currency, billing interval, setup fees, usage limits, renewal behavior, taxes, and whether checkout begins immediately.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe state the price honestly result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Choose comparison rows
Compare the decisions customers ask about: sites, storage, traffic, products, edits, support, security, backups, migrations, SEO, and response time.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe choose comparison rows result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Use accessible markup
Keep plan headers and feature labels programmatically associated with their values; do not communicate availability by color alone.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe use accessible markup result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Transform for mobile
At tablet and phone widths, use labeled plan sections, a controlled horizontal comparison, or a plan selector rather than five compressed columns.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe transform for mobile result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Connect the action
Give each plan a distinct destination and preserve the selected plan through checkout or contact handoff.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe connect the action result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Test edge content
Use the longest plan name, translated labels, large prices, unavailable features, footnotes, and 360px width.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe test edge content result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
How to know it worked
Verify the edit in Studio and on the real page.
A successful edit stays visible when the element is reselected, matches the intended responsive view, survives publish, and appears on the public URL without clipping or lost styling.
Studio preview
Reselect the element and confirm the saved value and visual result are still present.
Responsive preview
Check desktop, tablet, 390px, and 360px widths for overflow, squeezed controls, and inherited values.
Public page
Open the public route in a new tab after publishing and confirm content, interactions, assets, and spacing.
Recovery
If the result is wrong, stop editing and use History or a known-good revision instead of rebuilding the page.
Avoid the expensive mistakes
Stop when the page stops behaving predictably.
More edits do not repair a bad state. Preserve the evidence, return to a known revision, and reproduce the smallest failing action.
Changing several controls at once
Change one content, design, or responsive value, then confirm it in the preview. A small edit is easier to understand and recover.
Editing the wrong layer
Use Navigator and read the inspector heading. Deleting a parent section can remove every child even when the selected text or image looked harmless.
Checking only desktop
Review tablet, 390px, and 360px before publish. Width, gap, padding, type, alignment, controls, and menus can inherit differently.
Publishing before values persist
Reselect the element and reopen the responsive view. If the value disappears or another tab has a newer revision, reconcile it before publishing.
Continue learning
Use the next guide that matches the work in front of you.
The full tutorial hub remains available without repeating dozens of unrelated cards on this page.
Start here
Install and setup
Download the ZIP, activate Builder Suite, understand the blank-theme path, and run the first clean check.
First page
Build a page safely
Open Builder Pages, launch Studio, build structure first, check mobile, then publish or hand it to Help4.
Editor controls
Know which tab changes what
Use Content for information, Design for appearance and responsive values, and Advanced for identity, attributes, visibility, and motion.
Recovery
Edit without losing work
Replace media safely, recognize stale drafts, and restore a known-good page snapshot from Page Settings History.
Responsive
Control every viewport
Set spacing, widths, columns, alignment, and typography independently for desktop, tablet, and mobile.
Templates
Choose a starter
Pick a starter spec by page job: service, product, support, recent work, local SEO, launch, or checkout recovery.
Need help with this step?
Send Help4 the page, screenshot, or site goal.
Include the URL, what you are trying to build, what looks wrong, and whether this is a draft, staging site, or live customer page.