Customer Artwork File Rules for WooCommerce Print Shops

Applies to Cmsmart Product Designer (NBDesigner) 2.17.0 · Updated October 2026. Covers WooCommerce > Settings > Cmsmart > Upload design, the Files dashboard and the order-level approval and download tools.

A customer uploads a phone photo or a layered design file, and three days later it turns up unprintable — wrong format, too small, too low-resolution — after the order is already paid and queued. Cmsmart Product Designer lets a WooCommerce print shop set clear customer artwork file rules up front, and lets buyers download their own finished files back without a support ticket. Result: fewer unusable files reach production, fewer staff hours chasing replacements.

Most shops that let customers supply their own artwork — business cards, labels, packaging proofs, signage — learn the hard way that "just let them upload a file" is not a policy. A packaging label and a wedding invitation have different acceptable formats, sizes and resolutions, and the rules that protect one product can block a legitimate order on another. Order volume with a customer-supplied file keeps growing with it: the global print-on-demand market alone was valued at $10.8 billion in 2025, projected at a 23.6% CAGR through 2033 (Grand View Research, 2025) — so a loose upload policy gets more expensive every month you run it.

What's the real cost of accepting any file a customer sends?

If your product pages accept uploads with no rules at all, the cost shows up later, usually after the order has already been paid:

• Wrong format. A customer uploads a .heic phone photo or a layered .psd to a product that only your prepress software can open, and someone has to convert it by hand before the job can be queued.
• Too low to print. A logo saved for a website (72 DPI) looks fine on screen and comes out soft and pixelated at business-card size. 300 DPI at final print size is the widely used minimum for crisp commercial print output, and most screens display at a fraction of that (PrintingForLess, 2026).
• Oversized or missing files. A 400 MB scan ties up server resources, or a buyer skips the upload step entirely because the product needs a file to price correctly.
• No record of what was accepted. Without a central view of upload quality, "who approved this file" and "was it ever checked" become email archaeology, not a two-click lookup.
• Reprints. Each one of the above, caught after the press run instead of before it, is a reprint: materials, machine time and a delayed delivery date, on a job you already quoted at full price.

None of this is a volume problem — a single bad file in a 10-order week can cost more staff time than the other nine orders combined, because nobody budgets time for "fix a customer's file" on the calendar.

What does it look like when your upload rules are dialed in?

Example scenario. A buyer orders a box of 500 die-cut labels at 11 p.m. and uploads a vector file straight from their design software. The upload form only accepts the formats your press can run, checks the file is within your size and resolution limits, and confirms on the spot — no "we'll email you if there's a problem." The order lands in your queue already proof-ready. A second buyer on the same night tries to upload a screenshot for the same product; the form tells them immediately that the file is below your resolution minimum, with a plain explanation of why, instead of letting the order through and surprising your prepress team in the morning.

Talk to an ecommerce expert if you want this tuned per product category rather than store-wide — start a conversation about your upload policy.

How does Cmsmart's upload and file-governance architecture work?

The architecture has four building blocks, and all four ship in the plugin today:

• Upload rules (in the plugin). WooCommerce > Settings > Cmsmart > Upload design: allowed/disallowed extensions, minimum and maximum number of files, minimum and maximum file size, and a minimum DPI for JPG/JPEG uploads. Rules apply globally, with per-product overrides where a product needs stricter limits.
• Files dashboard (in the plugin). Every upload is indexed with its order, customer, preflight status and DPI, with store-wide totals for not-checked, print-ready and low-DPI files, so you can see your backlog instead of guessing at it.
• Approval and lock (in the plugin). The Customer Design box on the order screen accepts or declines the artwork; once approved, the design is locked on the server, so a later edit no longer silently replaces what you printed from — Cmsmart calls this the approved-artwork lock (2.17).
• Print-ready output (in the plugin). The same renderer that powers automatic export also powers the manual Create PDF button, so the print-ready PDF that matches the order (2.17) is the file your press receives, including custom sizes — not a generic template render.

What's the business value of controlling customer uploads?

Benefit	How it shows up in your business	KPI to track
Fewer reprints	Bad files are rejected before the press run, not after	Reprint rate (reprints ÷ orders placed)
Less staff time per order	No manual "please re-send your file" email chains	Average minutes spent on file follow-up per order
Cleaner production queue	Only print-ready files reach the order's print-ready status	% of orders print-ready on first render
Faster customer support	One Files dashboard instead of searching email	Time to answer "is my file OK?"

How do you set up customer artwork file rules in Cmsmart Product Designer?

Set the store-wide defaults once, then tighten individual products that need stricter rules:

1. Go to WooCommerce > Settings > Cmsmart > Upload design.
2. Under Allowed file types, list the extensions your press can actually run (for example jpg,pdf,psd,ai). Leave it empty to allow everything except what you list under Disallowed file types.
3. Set Min files uploads and Max files uploads so a product that needs artwork can't be ordered with zero files, and a simple product isn't flooded with uploads.
4. Set Min upload size and Max upload size in MB to block empty files and oversized scans alike.
5. Set Min. resolution DPI for JPG/JPEG image to your production floor — many print shops use 300 DPI at final size as the baseline, raising it only for products with no safety margin.
6. Decide Login Required based on whether you want every uploader identified before they can submit a file.
7. Review Upload file mode (Simple vs Advanced) and the cloud/social import sources (Dropbox, Google Drive, Facebook, Instagram) against what you actually want customers using.
8. Click Save Options, then place a real test order with a file that should fail (wrong type or too small) and one that should pass, to confirm the rule behaves the way you expect.
9. Open Cmsmart > Files after a few live orders and check the low-DPI and not-checked counts — that is your real backlog, not a guess.
10. On an order, use the Customer Design box to accept or decline the artwork; download the finished file in SVG, PNG, CMYK/ICC JPG or PDF from the design's Download design tab once it's approved.

A print-ready file (often built to the PDF/X family of standards) packages fonts, color and page geometry so a press can run it without guesswork (Datalogics, 2026). Cmsmart's own Output settings (CMYK/ICC profile, bleed, AI preflight) sit one tab over from Upload design, and are covered in our DPI configuration guide if you want the resolution number to display to the buyer as well as enforce it server-side.

Going further with custom development

The built-in settings cover most stores. For a few business models, the policy itself needs to be smarter than "same rule for everyone":

• Per-customer-group file rules. A B2B account with its own prepress team might be trusted with looser limits than a first-time retail buyer. Cmsmart builds role- or account-based upload rules on top of the standard settings.
• Automated correction workflow. Instead of a flat rejection message, Cmsmart builds a guided fix-it flow — resize, convert or re-upload in place — so a rejected file doesn't mean an abandoned cart.
• ERP/MIS-connected intake. For shops running a print MIS, Cmsmart builds a pipeline that pushes approved, print-ready files straight into your production system the moment they're accepted, with no manual export.
• Bulk and API intake for repeat accounts. Wholesale and marketplace sellers who place many design-attached orders at once can get a bulk-upload or API path that applies the same DPI and format checks without a one-file-at-a-time storefront flow.

Projects like these follow the same delivery model as the rest of our ecommerce project work: a short discovery call, a written solution design, build in sprints you can review, QA against your real catalog, launch, and support afterward.

Get a custom file-governance quote

Why work with Cmsmart on your upload policy?

Cmsmart Product Designer is used across 1,800+ live stores in 80+ countries, and the same team that builds the plugin also takes on the custom-development work above. A long-time user summed up the day-to-day experience on Trustpilot:

"We have had the NB Designer plugin installed for three years and have experienced absolutely no problems during that time. [...] 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

If your store lets buyers add their own photo as a design element inside the online editor, rather than upload a finished print file, our guide on the background tab and image upload feature covers that side of the designer. See also the web-to-print solutions hub and our AI integration services if you want AI preflight added to the same workflow. The plugin itself lives on the Cmsmart Product Designer product page.

Further reading

• WooCommerce documentation
• WordPress.org