Configure Product Designer Per Product in WooCommerce

Applies to Cmsmart Product Designer (NBDesigner) 2.18.0 · Updated October 2026. Screens below are live captures from the current demo store; this guide replaces the 2018 version, which described an older admin layout.

What does it cost when every product shares one designer configuration?

Most of the manual cost in a product-designer store traces back to this one problem:

• Wrong print area for the product shape. A business-card template carrying a t-shirt's design area produces files your press team has to fix by hand before they can run.
• Wrong resolution for the output. A low-DPI canvas looks fine on screen and prints soft; a photo-print DPI setting is overkill and slow to render for a simple sticker.
• Pricing that doesn't match the product. Quantity-break pricing built for apparel doesn't apply cleanly to business cards, so staff override prices by hand.
• Staff time re-explaining the same thing. Every mismatched canvas becomes an email thread: "can you resend at higher resolution," "this isn't the right side layout."

The web-to-print software category exists because this is a widespread, recurring cost: the global market is valued at roughly USD 1.43 billion in 2025, projected to reach USD 3.13 billion by 2034, as more stores move from one generic canvas to configured, self-serve design tools.

What does per-product design configuration look like for buyers?

Example scenario. A buyer opens an invitation product. That product is configured for templates with no extra print options, so the page offers only "Upload a full design" or "Design here online." A few products over, a buyer opens a business card configured with a Printing Options set: the page shows a custom-dimension field with width and height limits in inches, plus an orientation selector — fields the invitation product never shows, because they were scoped to the business card alone.

That consistency matters commercially, not just operationally: in Deloitte Digital's 2026 personalization research, 52% of consumers say they are more likely to buy from brands that personalize their experience, and they report spending 30% more with those brands.

How does Cmsmart's platform treat every product differently?

The building blocks, and what's built-in today versus custom development:

• Storefront product page — a WooCommerce product with the design button shown only when that product's designer is enabled. In the plugin today.
• Product manager — the admin list of every designer-enabled product, with base price, status and a direct edit link into each product's configuration. In the plugin today.
• Per-product production specs — material, bleed area, print resolution and color profile, plus the Online Designer toggle and a 1-sided/2-sided preset, scoped to one product. In the plugin today.
• Printing Options price matrix — fields (sides, custom dimension, DPI, area design shape, orientation, quantity breaks) that an option set applies to specific Products rather than every product. In the plugin today.
• Cmsmart Cloud rendering and AI preflight — the canvas, pricing and output a product is configured for all flow into the same cloud renderer and an optional AI preflight check before production. In the plugin today.
• Catalog-wide rollout and governance — pushing the right production specs to hundreds of SKUs from a PLM/ERP, or enforcing brand design rules across whole categories automatically. Custom development — see below.

What's the business value of configuring the designer per product?

Benefit	How it shows up in your business	KPI to track
Fewer manual proof corrections	Staff stop fixing bleed/DPI/side mismatches by hand before sending to print	Manual corrections per 100 orders
Lower reprint rate	Files already match the product's production specs when the order is placed	Reprints as % of orders, by product
Faster new-product rollout	Cloning a configured product beats rebuilding canvas settings from scratch	Minutes from "add product" to "designer live"
Pricing that matches the product	Quantity breaks and print fields apply only where they make sense	Manual price overrides per month

How do you configure product designer per product in WooCommerce?

1. Open Product manager (Cmsmart admin menu). This lists every product with the online designer enabled, its base price, status and template count, with a direct edit link into each product's configuration.

2. Open the product and set Production specs. On the product's General tab, set Material, Bleed area (mm) and Production time — these are specific to this product, not global.

3. Set Print resolution and Color profile for this product's output. Pick 300 DPI for print or a lower setting for web-only mockups, and CMYK for print production versus RGB for on-screen previews. A sticker and a photo print rarely need the same values.

4. Turn on the Online Designer and pick a sides preset. Check Enable the Online Designer for this product, choose 1-sided or 2-sided, then open Designer config from the same screen for full side, area and template setup.

5. Create or edit a Printing Options set (Cmsmart > Printing Options). Choose the design and print fields this product needs — sides, custom dimension, DPI, area design shape, orientation, quantity breaks.

6. Scope that option set to this product. Set Apply for to Products (not Categories) and search for this product by name, instead of leaving the set store-wide.

7. Set quantity-break pricing for this product's typical order size, if relevant — a percentage or fixed discount per break, scoped to the same option set.

8. Preview as a buyer. Open the live product page, confirm the design chooser, canvas and price fields match what you configured, and check the price updates as options change.

For the price matrix itself in more depth, see our guide to building a price matrix table with printing options; for per-product settings beyond the designer canvas, see individual product settings in NBDesigner. The online designer product page has the full feature list if you're comparing before you buy.

How can Cmsmart build beyond per-product configuration?

Per-product configuration solves the single-product problem. It doesn't solve catalog-scale governance on its own. Extensions we build on top:

• Bulk/ERP-driven configuration. Business reason: a catalog of hundreds of SKUs can't be configured one product at a time by hand. Cmsmart builds an import/sync pipeline that pushes production specs (bleed, DPI, color profile) from your PLM or ERP into Product manager automatically when a new SKU is added.
• Category-level design governance. Business reason: a franchise or multi-brand store needs consistent bleed, safe-zone and font rules across every product in a category, enforced automatically rather than configured product by product. Cmsmart builds rule templates and an admin approval step layered on top of per-product configuration.
• 3D/AR preview tied to a product's specs. Business reason: car wraps, packaging mockups and apparel benefit from a 3D or AR preview that reads the same production specs as the print file, so what the buyer sees matches what prints. Cmsmart builds this as a custom front-end layer that consumes the product's existing configuration.
• Custom pricing rules beyond the price matrix. Business reason: rush fees tied to current press-queue load, or cost-plus pricing synced from ERP cost data, go beyond quantity-break pricing. Cmsmart builds these as a pricing-engine extension that still respects each product's scoped Printing Options.

Delivery follows the same path for all of these: discovery → solution design → sprints → QA → launch → support, the same model behind our ecommerce project case studies. If your catalog needs more than per-product configuration out of the box, see the product designer customization service for the full scope of what we build.

Plan my per-product designer rollout

Why work with Cmsmart on your product designer rollout?

Cmsmart has been building web-to-print and ecommerce customization as a Netbase JSC division since 2012, with 6,300+ client projects and 1,800+ live stores running today, rated 4.2 on Trustpilot (404 reviews). Product designer rollouts are one part of the wider web-to-print storefronts Cmsmart builds for print shops and POD brands.

Store owners who run multi-product catalogs on Cmsmart Product Designer describe exactly this per-product fit:

"The designer works exceptionally well across all devices and allows us to create the exact customisations required to perfectly fit our products and our business model." — Web Developer, Trustpilot review, Sept 2026

"We sell a wide variety of products from mugs, custom tees, name badges, canvas print and more. NBDesigner has lots of variable options, including colour and image swatches and pricing tables and much much more." — Ray Barlow, Trustpilot review

WooCommerce is also the platform most of this catalog work happens on: it powers 47.6% of e-commerce websites tracked by W3Techs as of October 2026, which is why Cmsmart builds directly on top of it rather than a separate storefront.

Frequently asked questions

Do I have to configure every product individually?

Yes, the designer, production specs and price matrix are set per product (or per category for Printing Options), but cloning an already-configured product as your starting point is much faster than building each one from scratch.

Can two products share the same Printing Options set?

Yes. A Printing Options set can be applied to several specific products, or switched to apply by Category instead, from the same Apply-for setting in the option editor.

What happens if I don't set a bleed area or print resolution for a product?

The product falls back to the designer's default production settings, which may not match that product's actual print process — the shared-canvas mismatch described above.

Can Cmsmart connect per-product configuration to our ERP or PIM?

Not out of the box. That's a custom-development integration Cmsmart builds on request so new SKUs arrive in Product manager with the right specs pre-filled.

Does per-product configuration affect the print-ready PDF a buyer's order generates?

Yes — the bleed, DPI and color profile set on the product carry through to the order's print-ready PDF, so the output matches what was configured, not a generic default.