Reuse a product setup without copying mistakes

Reusable setups reduce repetitive work. They copy configuration into the product you are editing; they do not keep products permanently linked to a master template.

Choose a starting point

Open Print product setup → Start with a product. You can use a built-in product template or a named setup saved by your own shop. Built-in templates provide structure with selling prices cleared, so you must supply your own prices.

Loading a setup changes the editor's draft. It does not publish the changes immediately. Complete the relevant steps, run a fresh price check and use the normal save action when ready.

Save your own shop template

1. Build and check a representative product.
2. Use the setup library control in the first step to save it under a clear name, such as “Cards — standard stock and finishing”.
3. Open the target simple product and choose that named setup.
4. Prefer an options-only copy when prices need separate review. This clears selling-price values while retaining the setup's structure and relationships.
5. Check internal choice references, artwork sizes, production times and starting specification on the target product.

Copying prices is optional. The library guards against a mismatch in currency or inclusive/exclusive price-entry basis. Matching those settings is necessary but does not prove the source prices are commercially suitable for another product.

What stays with the target product

Its WooCommerce title, descriptions, images, categories, tax class and assigned promotion remain separate. A copied configuration does not replace those catalogue settings. Check them explicitly before launch.

The library supports up to 30 named shop templates, with bounded configuration storage. Rename, replace or remove a library entry without changing configurations already loaded into products or historical order snapshots.

Undo and changed windows

An undo is available for the draft load while it is still valid. If another action or browser window has changed the draft, follow the stale-state message rather than forcing old data over current work. Save important work before closing the browser.

Related: Drafts and saving, First product, Price checks.