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
- Go to Settings → POM Theme → E-Commerce → Cart and checkout → Checkout behavior.
- Decide whether customers can use multiple addresses.
- Choose whether checkout labels are displayed.
- Configure the supported native fields:
- Company name;
- Address line 2;
- Phone.
- Choose how required fields display their asterisk.
- Write the terms checkbox text and checkout privacy text.
- Save the settings.
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;
- Checkout field editor for supported custom billing fields;
- Google address finder for address-search messaging when its integration is available.
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.
Control order attribution with cookie consent
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.
- Open Settings → POM Theme → Integrations → Cookies → Cookie notice.
- Under Cookie groups, review Cookies in this group and Cookie type. Each cookie row uses
Name|Origin|Type|Expiration; a name such assbjs_currentorsbjs_*associates Sourcebuster with that group. - 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.
- 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. - 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:
- guest checkout;
- returning-customer login;
- account creation during checkout where enabled;
- billing and shipping addresses;
- every shipping method;
- every payment method in safe or test mode;
- valid and invalid coupons;
- missing required fields;
- invalid email, phone, postal code, and custom-field input;
- payment failure and retry;
- successful order confirmation;
- order email and My Account order details;
- 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.