WooCommerce gives store owners several separate decisions about accounts and privacy. A customer may be allowed to place an order without a WordPress account, an existing customer may be offered a login form during checkout, and account creation may be presented during checkout, after the order or from the My Account page. These choices affect the checkout path, but they are not the same setting.
The relevant controls are centralized under WooCommerce > Settings > Accounts & Privacy. This section also includes privacy notices and personal data retention. The practical task is not to find one universal configuration, but to match each option to the store’s products, customer workflows and data requirements. This guide explains the differences, shows how to configure the settings and provides a verification checklist before changing a live store.
What WooCommerce Accounts & Privacy Controls Do
The admin path and setting groups
Open WooCommerce > Settings > Accounts & Privacy to find the controls discussed in this article. The page brings together settings for guest checkout, login during checkout, account creation, privacy-related notices and personal data retention. Keeping these areas together makes it easier to review the customer journey and the later handling of customer and order data as one configuration.
It is useful to separate the decisions into two groups. Checkout and account settings determine whether a customer needs an account, can log in while ordering and when registration is offered. Retention settings determine how long selected categories of account and order data are kept and what cleanup actions WooCommerce can perform. The exact presentation can depend on the store’s checkout configuration, theme and extensions, so changes should be verified in the actual environment rather than assumed to behave identically everywhere.
Guest Checkout vs Checkout Login
Two separate controls
Guest checkout answers this question: can a customer place an order without creating a WordPress account? When the guest-checkout option is enabled, customers can complete an order without an account. A guest order is not tied to a WordPress user account.
Checkout login answers a different question: can an existing customer authenticate during checkout? When log-in during checkout is enabled, WooCommerce can display a login prompt and form to a customer who is not currently logged in. This allows a returning customer to use an existing account without treating login as the same thing as the guest-checkout decision.
The two controls can therefore work independently. A store may permit guest orders and also show a login option for returning customers. Alternatively, a store may require accounts while still allowing existing customers to log in during the checkout process. Do not infer that one arrangement automatically improves conversion, security or customer value. Those outcomes are not established universally by the documented settings and should be treated as store-specific hypotheses to test.
Test both perspectives after configuration: use a logged-out browser session to check the guest path, then use a returning customer account to check whether the checkout login prompt, form and subsequent order process work as intended. Themes, checkout blocks and extensions may affect how the options appear.
How to Enable or Disable Guest Checkout
Configuration and verification steps
To configure the option, go to WooCommerce > Settings > Accounts & Privacy and locate the guest-checkout control. Enable it when the store should allow customers to place orders without creating a WordPress account. Disable it when the store’s process requires an account before an order can be placed. The direct consequence of disabling guest checkout is that an account may be required to complete the purchase.
Before selecting a setting, consider the products and workflows involved. Some processes may require an authenticated customer account, including subscriptions when such a process is present in the store. That does not make one choice universally correct; it means the account requirement should be checked against the actual purchase and fulfillment flow.
Save the setting, then run a complete test order as a logged-out customer. Check the checkout fields, payment flow, order confirmation and customer emails. Also verify how the order is handled in the administration area. Repeat the test with a returning customer if checkout login is enabled. Perform these checks on a staging site or with test orders before applying the change to the live store.
When to Offer Customer Account Creation
During checkout, after checkout or My Account
WooCommerce can offer account creation at several points. Registration can be available during checkout, offered after checkout or provided from the My Account page. During-checkout registration offers the customer an account before the order is completed. After-checkout registration presents the account option after the purchase, while My Account provides a separate place for registration.
The choice should reflect the store’s process. An account before purchase may be relevant when authenticated features are needed before the order is placed. Offering registration after purchase may fit a store that wants to complete the initial order without making account creation part of that step. Repeat purchases, subscriptions and access to account-based functions are useful factors to evaluate, but they do not prove that one timing will produce better conversion or retention for every store.
Choose a starting configuration, then test the complete experience with the products and customer journeys that matter to the business. Review not only the registration screen but also what the customer sees after ordering and when returning to My Account.
Password setup and email-based login
Additional account settings influence the registration experience. WooCommerce can be configured to send a link for setting up a password. It can also use the customer’s email address as the account login. These choices affect the instructions customers receive and the information they use when signing in.
After changing them, test registration, the password-setup link, login and related emails. Confirm that the wording and sequence are understandable in the store’s actual checkout configuration. Do not describe a particular account-creation method as guaranteed to improve results; the documentation provides the available controls, not a universal performance comparison.
How to Configure WooCommerce Personal Data Retention
Retention categories and units
Open WooCommerce > Settings > Accounts & Privacy > Personal data retention. Retention can be configured separately for inactive accounts and for different order statuses. The documented categories include pending, failed, canceled and completed orders. This separation allows the store owner to consider each category rather than applying one undifferentiated period to every record.
WooCommerce lets you express a retention period in days, weeks, months or years. Enter a period only after reviewing the store’s documented data policy and the obligations that may apply to its operations. Privacy, tax, accounting, payment and consumer-protection requirements may differ by jurisdiction and business context. Order, invoice, tax, payment or warranty records may need to remain available, so automatic cleanup should not be enabled without checking those requirements.
Also review data outside the basic WooCommerce workflow. Payment gateways, invoicing tools, subscription systems, analytics tools, custom checkout fields and other extensions may store personal data separately. Their privacy integrations, exporters and erasers need to be checked independently. The core retention controls should not be treated as proof that every record in the wider store environment will be handled automatically.
What a blank field means
A blank personal-data-retention field means WooCommerce retains the relevant category of data indefinitely, according to the documentation. Leaving a field empty should therefore be an intentional decision, not an assumption that no setting is required.
Before leaving a field blank, connect the decision to the store’s documented retention policy and applicable obligations. Before entering a period, confirm that removing or anonymizing the data will not conflict with records that must be preserved for accounting, tax, payment, warranty or other operational reasons. WooCommerce provides configurable controls, but it does not determine the legally correct period for every country, industry or payment method.
Cleanup, Erasure and Pre-Launch Checklist
What scheduled cleanup changes
When retention cleanup is enabled, WooCommerce runs the cleanup daily. Failed, pending and canceled orders may be moved to the trash. Completed orders may be anonymized so that sales statistics remain accurate. Inactive customer or subscriber accounts may be deleted. These are operational effects of the configured retention rules, so review them before saving a live-store configuration.
WooCommerce supports more than scheduled cleanup. Administrators can respond to account-erasure requests, use scheduled personal-data retention and optionally remove personal data in bulk from the Orders screen. Bulk personal-data removal can be irreversible and cannot be undone. Use it only after confirming that the selected records may be removed and that required business documentation has been addressed.
Data export and erasure workflows use WordPress confirmation processes. The exact data handled depends on registered exporters, erasers, store settings and compatible extensions. A record stored by an extension that does not integrate with the WordPress privacy tools may require separate handling. Do not assume that deleting or anonymizing a WooCommerce record removes every related copy elsewhere.
Final testing checklist
Before publishing account, checkout or retention changes, use a staging site or test orders and work through the complete customer and administrator journeys.
- Test a logged-out customer with guest checkout enabled or disabled, according to the planned configuration.
- Test an existing customer using the checkout login prompt and form.
- Test account creation during checkout, after checkout and from My Account when those options are enabled.
- Check password-setup links, email-based login and order-related emails.
- Review payment, downloads, subscriptions and other workflows used by the store.
- Confirm the selected retention periods, units and deliberately blank fields.
- Check whether invoices, tax, payment, warranty or accounting records must be retained.
- Review privacy exporters and erasers supplied by third-party extensions.
- Confirm that any manual or bulk removal is intentional before performing it.
After testing, document the chosen configuration and the reasons for it. Recheck the result after extension or checkout changes, because the behavior and presentation can depend on the wider store setup.
WooCommerce guest checkout and checkout login solve different problems: one controls whether an account is required to order, while the other lets an existing customer authenticate during checkout. Account creation can be offered during checkout, after purchase or through My Account, with password and email-login settings shaping the experience. Retention should be configured separately for inactive accounts and order statuses, with blank fields understood as indefinite retention. Because cleanup can move, anonymize or delete data, verify business obligations, extension behavior and test orders before going live. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.