Configure checkout

Checkout combines WooCommerce's commercial rules with POM presentation and supported field controls. Configure the transaction in WooCommerce first, then refine the customer experience in POM Theme.

Prerequisites

Confirm that taxes, shipping zones and methods, payment methods, guest checkout, account creation, privacy, and the Terms and conditions page are configured in WooCommerce → Settings. Complete one test order before changing the layout.

Configure checkout behavior

  1. Go to Settings → POM Theme → E-Commerce → Cart and checkout → Checkout behavior.
  2. Decide whether customers can use multiple addresses.
  3. Choose whether checkout labels are displayed.
  4. Choose how required fields display their asterisk.
  5. Write the terms checkbox text and checkout privacy text.
  6. Save the settings.

The label visibility setting also applies to the alternative shipping address. When labels are hidden visually, shipping fields retain associated labels for assistive technology. Placeholders remain hints rather than replacing those labels. Verify the country, province, optional fields and any extension fields after expanding Ship to a different address?.

Field requirements and custom billing fields are managed by POM Tweaks, at Settings → POM Tweaks → E-Commerce → Checkout → Checkout fields customizer. Enable that control to configure Company name field, Address line 2 field, Phone field, billing tax ID, order notes, age, gender and the custom-field repeater. Conditional fields and signatures require classic checkout. POM Theme continues to provide checkout layout and styling.

The Terms and conditions page is assigned under WooCommerce → Settings → Advanced. The Privacy Policy page is assigned under Settings → Privacy. The visible text should accurately describe the store's real processing and policies.

Configure optional presentation groups

Depending on the enabled feature sections, POM can provide:

  • Checkout layout for the page structure, shipping-address fallback, stepper style, cross-sells, and login or guest text;
  • Checkout labels for billing, payment, order-review, and payment-button labels;
  • Order details layout for order presentation and product images;
  • Google address finder for address-search messaging when its integration is available.

The Login form text and Guest checkout text controls accept formatted content. If saved content is unavailable, the login form uses WooCommerce's introductory message and guest checkout uses its standard prompt. The guest checkout button remains available according to the store's account settings.

Collect only data required to fulfil or legally administer the order. Give custom fields unique names, clear labels, an appropriate input type, sensible priority, and an explicit required state. Define select or radio options completely before testing.

Translate checkout text

Fixed text supplied by POM Theme uses its pom gettext catalog. Configurable headings, Shipping address fallback, Guest checkout button label, and the formatted login and guest messages use the theme's Polylang integration. Save the relevant settings group, then open Languages → Translations and translate the configured text. Check both the ordinary checkout and any enabled multi-step layout in each storefront language.

Payment gateways and tax extensions own their field labels, help text and validation messages. Maintain those translations through the respective extension or its supported multilingual integration. Theme translations do not replace payment or tax behavior.

WooCommerce Order Attribution records the source of a visit using sbjs_* cookies. When both Order Attribution and POM's cookie notice are enabled, POM allows this tracking only after valid consent for the relevant optional cookie category. Checkout remains available when attribution is declined.

  1. Open Settings → POM Theme → Integrations → Cookies → Cookie notice.
  2. Under Cookie groups, review Cookies in this group and Cookie type. Each cookie row uses Name|Origin|Type|Expiration; a name such as sbjs_current or sbjs_* associates Sourcebuster with that group.
  3. Use the optional Analytics or Ads type that matches the site's disclosed purpose. Leave Disable checkbox off so visitors can decline or withdraw that choice.
  4. If no group lists sbjs_* cookies, attribution follows Ads, corresponding to WooCommerce's marketing category. If the cookies are listed in several groups, all those categories must be accepted. A required or locked attribution group, or a missing fallback Ads group, keeps attribution disabled.
  5. Save and clear the page cache before verifying the public site.

A checked-by-default box does not authorize tracking before the visitor saves a choice. Saved consent is validated on each page load, independently of the banner's display delay. Declining or withdrawing the relevant category clears attribution cookies, including cookies shared with parent domains, and clears attribution data in the classic checkout and Checkout block. Google consent choices continue to follow their own Analytics and Ads categories.

Verify in a clean browser session: before making a choice there should be no sbjs_* cookies; accepting the relevant category allows them; rejecting or withdrawing it removes them immediately and they remain absent after a reload. Also reload after acceptance and confirm attribution remains available. If it stays disabled, check the cookie group's type and checkbox setting, and whether another integration prohibits attribution.

This integration applies while POM's cookie notice and WooCommerce Order Attribution are active. Disabling POM's notice leaves WooCommerce and any other consent integration responsible for tracking. Script optimizers must preserve the consent script's execution before Order Attribution. See WooCommerce's Order Attribution guide for the feature's scope and settings.

Test the complete flow

Run separate tests for:

  1. guest checkout;
  2. returning-customer login;
  3. account creation during checkout where enabled;
  4. billing and shipping addresses;
  5. every shipping method;
  6. every payment method in safe or test mode;
  7. valid and invalid coupons;
  8. missing required fields;
  9. invalid email, phone, postal code, and custom-field input;
  10. payment failure and retry;
  11. successful order confirmation;
  12. order email and My Account order details;
  13. sidebar layouts with short and long order reviews, confirming the summary remains sticky without jumping or covering the fixed header.

Repeat with a digital-only order and a shippable order if the store sells both.

Expected result: the totals and required information remain understandable from Cart through order confirmation, and a failed validation never erases valid customer input unnecessarily.

Troubleshooting

If a field appears twice, remove overlapping field customizations from another extension before changing its CSS. If shipping or payment options are missing, diagnose the WooCommerce zone, customer address, cart contents, currency, and gateway rules first. If address search is unavailable, confirm the integration and its configuration rather than making the address fields unusable without it.

Delivery dates and collection

Use Settings → POM Tweaks → E-Commerce → Shipping → Delivery time rules to configure delivery estimates, date and time choices, pickup or home-delivery selection, and collection points. POM Tweaks owns these controls; they are not theme shipping options. They work with classic WooCommerce checkout, including POM Theme's checkout layouts. Assign each rule to the relevant shipping method in WooCommerce → Settings → Shipping → Shipping zones.

Verify both pickup and home delivery, a future date, a blocked date, and the order's saved delivery information. A site using the Checkout block needs a scheduling integration designed for blocks; changing the theme layout does not add classic delivery controls to that block.

Configure the cart
Previous
Configure gift vouchers
Next