Saved product configurations

Let customers keep a configured WooCommerce product and return to it later. The module supports products configured with POM Product Add-Ons and POM Composite Products, including add-ons attached to products selected inside a composite.

Saved values are a customer preference, not a price promise. Every time a configuration is opened, POM Tweaks resolves the current product or variation, current fields and options, current stock and availability, and the current server-calculated price.

Before you begin

• WooCommerce and POM Tweaks must be active.
• Enable Product Add-Ons, Composite products, or both under Settings → POM Tweaks → E-Commerce → Products.
• Enable Product presets and saved configurations in the same settings group.
• Enable Allow customers to save configurations to their accounts only when the store should expose customer save controls, account records, share links, and account API routes. This permission is disabled by default.
• Test the feature with the product types, languages, taxes, and pricing rules used by the store.

Chapter contents

1. Save and reuse a product configuration
2. Create product presets
3. Create and control share links
4. Understand privacy, retention, and account deletion
5. Integrate the REST and Store API contracts

Expected result

Store managers can publish product-owned presets with readable ?preset= URLs as soon as the main tweak is enabled. When the additional customer-saving permission is enabled, signed-in customers can save, open, rename, duplicate, delete, and share configurations from My account → Saved configurations. Guests can open presets and, when customer saving is allowed, permitted share links, but they must sign in before creating an account record. The feature does not create accounts or store guest configurations in the browser. Files are not saved or shared and must be selected again.

Turning off the customer-saving permission removes customer save controls, the account screen, share-link handling, and account REST and Store API contracts without removing product presets or existing account records. WordPress privacy tools continue to cover existing records.

Disabling this module removes its storefront, account, API, and expired-link cleanup handlers. It does not delete existing saved records; re-enabling it restores access to records that have not otherwise been erased. Lightweight WordPress privacy and user-deletion handlers remain available while POM Tweaks is active so export, erasure, and account deletion can still cover existing records across the network.