Skip to main content

​
General

Yes. Unlimited saved addresses, both checkout adapters, full light/dark/system theming, custom accent color, editable labels, and every developer hook are all included in the free plugin — there’s no “Pro” version withholding functionality.
Yes, natively — see Checkout Blocks. The billing and shipping selectors are registered as forced inner blocks through WooCommerce’s own Blocks integration registry and Store API, not injected after the fact.
Unwan creates no custom database tables, runs no extra queries beyond what WooCommerce already performs for customer data, caches its results for the duration of each request, and only loads its scripts and styles on checkout and My Account pages. There’s no tracking or external service call of any kind. See Architecture.
Not by default. A saved address is used for the current order without silently replacing the WooCommerce default. Store owners can opt into promoting a new checkout address to the matching default under New address defaults. See Checkout Overview.
Yes, by default (Save checkout addresses). An address matching an existing entry’s normalized first name, last name, first address line, and postcode is reused instead of duplicated — see Default Swaps & Duplicate Detection.
It stays in the address book, demoted to a plain additional address — unless it still holds the other default role, in which case nothing changes for it. Reassigning a default never deletes the address it replaces. See Default Swaps & Duplicate Detection.
Data is retained by default. Enabling Uninstall cleanup first will permanently remove Unwan’s settings and additional customer addresses on uninstall — WooCommerce’s own billing/shipping profile fields are never touched, regardless of this setting. On multisite, saved addresses are shared by the whole network, so they’re removed only when every site that uses Unwan has cleanup turned on.
Unwan ships with translations for ten languages: Spanish, French, German, Italian, Portuguese (Brazil), Dutch, Polish, Russian, Swedish, and Japanese. They cover both the customer-facing screens and the settings page, and apply automatically once WordPress is running in that language — nothing to install or configure.Labels left empty under Text and labels show their default text in each customer’s language. A label you customize is shown exactly as you typed it; on a multilingual site, WPML and Polylang can translate it. If a community translation for your locale is published on translate.wordpress.org, WordPress uses that in preference to the bundled copy.
Yes. On the admin order screen, choose a customer and a “Saved addresses” dropdown appears above the billing and shipping fields. Picking an address fills that part of the order, and staff can still edit it. Nothing is added to the customer’s address book and their default addresses don’t change. See Admin Orders.
Unwan is designed to manage the standard WooCommerce address: name, company, address lines, city, state, postcode, country, and phone. Fields that checkout field editors add to the billing or shipping address stay with your field editor rather than in the address book. At checkout they appear and work as usual, and Unwan never hides, clears or changes them. See Custom checkout fields.
Yes. WordPress’s Export Personal Data and Erase Personal Data tools include the customer’s additional saved addresses, listed as “Address book”. The billing and shipping defaults are covered by WooCommerce’s own exporter and eraser.
Yes — PSR-4 autoloading with namespaced classes, and every release is checked against the WordPress Coding Standards PHPCS ruleset (WordPress-Extra plus PHPCompatibilityWP) before publishing. See Architecture.

​
Troubleshooting

Check, in order: the customer is signed in (Unwan never offers saved addresses to guests); the relevant selector (billing/shipping) is enabled in Accounts & Privacy → Unwan; and the customer actually has at least one address in their book (a billing or shipping profile default counts). The picker deliberately stays invisible rather than rendering an empty state when there’s nothing to pick from.
This usually means permalinks need refreshing. Unwan refreshes them automatically on activation and again the first time each site loads a new version, including every site of a multisite network. If the page still shows “Page not found” (for example after a staging sync that copied the database but not the rewrite rules), visit Settings → Permalinks and click Save Changes once to force a refresh.
This should be rare given Unwan’s ID-rooted CSS reset, but if you hit a specific conflict, load your override CSS after assets/css/unwan.css and target the stable root ID (#unwan-account-list, #unwan-billing-picker, #unwan-shipping-picker) plus the relevant BEM class — that combination has enough specificity to win without !important.
This is expected behavior, not a bug: the entry you’re editing would normalize to the same first name, last name, street line, and postcode as a different existing entry. Edit or delete the other entry first if you actually want to merge them. See Default Swaps & Duplicate Detection.
Both are intentional guardrails, enforced server-side, not just visually: an address currently holding a default role can’t be deleted until it’s reassigned, and an address already holding a role can’t be “made default” for that same role again. Hovering the disabled action shows why.
Unwan settings use WooCommerce’s own settings save pipeline (WooCommerce → Settings → Accounts & Privacy → Unwan) — if changes there aren’t persisting, it’s almost always a WooCommerce-level issue (a conflicting plugin filtering woocommerce_get_settings_account, or a permissions problem), not something Unwan-specific.
Still stuck? Reach out at hello@smartwpplugins.com.
Last modified on November 5, 2026