Help4 Commerce Getting Started
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
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 2
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.
Screen 3
Product quantity rules
Choose selectable quantity, fixed one-per-line packages, whole-order limits, minimum, maximum, and quantity steps.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 4
Commerce products
Create products, variations, subscriptions, product images, quantity rules, catalog fields, and checkout context.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 5
SEO Control
Review metadata, social sharing, schema, readability, indexing, and site-level discovery signals.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 6
SEO score playbook
Understand search, readability, analytics-readiness, content-quality, and business-intent scores, then act on page-specific checks.
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 20
Checkout, Payment Routing, and Orders
Connect payment processors, validate routing and totals, and test the complete order lifecycle before accepting a live payment.
Read the complete transcript
- Configure Gateways Safely
Open Gateways and configure only the processors the store will use. Keep test and live credentials separate, choose supported currencies, and verify webhook destinations. Never place secret keys in screenshots, page content, Builder settings, support messages, or browser-visible source.
- Set Routing Rules
Build the narrowest routing rule for product, currency, country, subscription, or other supported context, then define a safe default. Review rule priority so one order cannot match several conflicting accounts. A route should explain why the selected processor received that checkout.
- Verify Cart and Totals
Test product selection, variations, quantity behavior, promotions, shipping, tax, and customer fields before payment begins. Compare the displayed subtotal, discount, shipping, tax, and total with the order record. Failed payment initialization should not create a false completed order or consume inventory.
- Complete the Order Matrix
Use approved test transactions for success, decline, retry, webhook delay, duplicate event, cancellation, refund, subscription renewal, and mobile checkout. Confirm order status, inventory, customer history, email notices, payment references, and idempotency remain correct after refresh or repeated callbacks.
Lesson 19
Commerce Variations, Subscriptions, and Customer Fields
Configure product options, recurring terms, quantity behavior, and reusable customer data across checkout and account workflows.
Read the complete transcript
- Choose the Product Model
Open the product editor and choose the type that matches the offer: simple, service, digital, booking, variable, or subscription. Add variants only when an option needs its own price, stock, SKU, image, fulfillment, tax, or availability instead of hiding those differences in description text.
- Set Quantity and Recurring Rules
Decide whether the customer may change quantity, whether one configured package must stay one unit per cart line, and whether the entire order is limited to one. For subscriptions, state the interval, trial, setup amount, renewal behavior, and cancellation path before testing payment.
- Define Customer Fields Once
Use Customer Fields for information needed across checkout, accounts, orders, support, exports, and privacy tools. Choose the correct field type, placement, requirement, validation, conditional logic, and visibility. Never collect sensitive information merely because a text field makes it possible.
- Test Different Product Paths
Run simple, variable, subscription, and fixed-quantity examples through catalog, cart, checkout, payment, confirmation, customer account, inventory, email, refund, and renewal states. Confirm customer fields persist only where intended and a fixed one-per-line item never exposes a quantity control.
Commerce path
Build commerce around catalog data first, then checkout.
A store only works when product data, variations, subscriptions, checkout routing, emails, support, and order status all agree.
Catalog first
Good commerce starts with product data, not a pretty checkout button.
Routing second
Payment rules should follow product, subscription, customer, and processor reality.
Support always
Customers need receipts, statuses, policies, and a clear help path.
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.
-
Choose the product model
Simple products, variations, subscriptions, digital goods, service packages, and imports need different defaults.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe choose the product model result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Clean catalog fields
Titles, SKUs, descriptions, images, categories, prices, stock, variation labels, and subscription terms must be consistent.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe clean catalog fields result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Set payment routes
Use routing rules when products, subscriptions, regions, or processor fallbacks need different payment paths.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe set payment routes result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Test checkout context
Checkout should know product, variation, subscription, customer, price, tax/shipping needs, and return path.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe test checkout context result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Add trust signals
Policy links, support links, SSL, security headers, reviews, FAQs, and fulfillment notes reduce confusion.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe add trust signals result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Load-test big catalogs
Large stores need import checks, search checks, image checks, cache checks, and admin edit checks.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe load-test big catalogs 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.