Guide · Web-to-print
WooCommerce Product Designer Templates Setup Guide
WooCommerce Product Designer templates setup: configure Template, Template Tags and Template Fields, then check the storefront result. Get a custom qu...
Table of contents
Was this tutorial helpful?
Written by
Cmsmart Web-to-Print Solutions Consultant
Plans online print storefronts: product setup, pricing rules, proofing and print-ready files.
The team behind it
Account Manager
Project Manager
Business Analyst
Developers & QA
In short
A WooCommerce file upload print shop that still takes artwork by email is running two systems at once: the store that takes the order, and an inbox that takes the file, the size complaints and the "can you resend that" replies. Cmsmart Product Designer's File Upload module puts the file on the order itself, with the file-type, size and resolution checks run before a job reaches the press. The global commercial printing market is worth USD 510.3 billion in 2025, and the share of it ordered online keeps growing — which is exactly why the file attached to an order matters as much as the price.
What's the real cost of taking print files by email?
Email-based proofing costs a print shop staff time on every order, not just the bad ones: someone has to open the thread, match it to the right order number, check the file is usable, and chase the customer when it isn't. Cmsmart Product Designer removes that matching step by attaching the file to the WooCommerce order itself.
A typical week on a print shop's order desk shows the same frictions:
None of this needs a bigger team — it needs the file and its checks moved onto the order, which is what File Upload does.
What would a built-in upload-and-check flow look like for your shop?
Picture a product page where the customer attaches their own print-ready file, sees it listed against the order immediately, and never has to open a separate email thread. Cmsmart Product Designer does this by making File Upload a configuration on the product, not a manual process your staff runs.
Example scenario. A buyer opens a print shop's door-hanger product at 9 p.m., picks a size, attaches the print-ready PDF already sitting on their desktop, and pays. The file is too small for the shop's 300 DPI minimum, so the page flags it before checkout instead of after. They swap in the right file and the order goes through; by the time the shop opens the next morning, the order is sitting in Awaiting review with a file that already passed the size and resolution rules — no email thread, no guessing which attachment belongs to which order.
How does Cmsmart turn an upload into a production-ready order?
Cmsmart Product Designer treats an uploaded file the same way it treats a design built in the online editor: both land on the order with a print-ready PDF, a preflight check and an approval step. That shared pipeline is the solution to running upload-only and design-your-own products from one admin screen.
The building blocks, in the order a job moves through them:
Cmsmart insight: the DPI field on the Upload design tab only screens JPG/JPEG files at the moment of upload. A PDF, AI or PSD file passes that gate regardless of its internal resolution — the real quality check for those formats is AI Preflight's "Required DPI" setting, which runs after the file is already on the order. Treat the two as separate checks, not one.
Want a second opinion on how this fits your current storefront before you touch a setting? Talk to an ecommerce expert first — the setup below still works whether you do it yourself or have Cmsmart do it with you.
What's the ROI of catching bad files before they hit the press?
Cmsmart Product Designer's value for a print shop is mechanical, not promotional: fewer staff-hours spent chasing files, fewer reprints from files that should never have been accepted, and a shorter gap between "ordered" and "in production" once the file is checked at the door instead of on the press.
Rough-cut ROI worksheet (use your own numbers):
Hours saved/month = orders/month with uploads × minutes spent chasing a file ÷ 60 × hourly staff cost.
Reprint savings/month = jobs/month × reprint rate × share caused by file errors × cost per reprint.
Add both and compare against the time to configure File Upload and AI Preflight.
How to set up a WooCommerce file upload print shop workflow
Setting up File Upload in Cmsmart Product Designer means configuring the upload rules once, turning the feature on for the products that take customer artwork, and checking the first few orders against the print-ready PDF and AI Preflight screens before you trust the queue unattended.
If you haven't installed and activated the plugin yet, start with the Cmsmart Product Designer installation guide — the steps below assume WooCommerce and the plugin are already active.
1. Set your file rules (WP Admin > Cmsmart > Settings > Upload design):
2. Turn on the quality net for every file format (WP Admin > Cmsmart Cloud > AI Tools):
3. Enable File Upload on a product, then check the order flow:
For the DPI math behind that Required DPI field, see how DPI affects print quality.
Going further: what can Cmsmart build on top of File Upload?
File Upload ships the rules, the preview and the print-ready pipeline; what it doesn't do out of the box is talk to your MIS, score reprint risk per substrate, or run a wholesale approval chain — that's custom development Cmsmart builds around the same order data.
This kind of work falls under Cmsmart's product designer customization service, delivered the same way as every custom build: discovery call, a written solution design, sprints with milestones you approve, QA/UAT, launch, then ongoing support — the full model is on the ecommerce project delivery page.
Plan my print shop's upload workflow
Why work with Cmsmart on your print shop's storefront?
Cmsmart has built WooCommerce print and personalization stores as a Netbase JSC division since 2012, with File Upload, the online designer and the print-ready pipeline running on the same plugin a shop can set up itself or hand to Cmsmart to configure and extend.
Some real numbers, as published: 6,300+ client projects and 4,600+ projects delivered since 2012, 1,800+ live stores today, across 80+ countries. Cmsmart's plugin rating sits at 4.2 on Trustpilot (404 reviews):
Configure File Upload yourself with the Cmsmart Product Designer plugin, or ask Cmsmart to build the custom pieces around it — the same team maintains both.
Frequently asked questions
What file types can a print shop accept through File Upload?
Whatever you list in Allowed file types on the Upload design tab. Common print source formats — PDF, AI, EPS, PSD and TIFF — are accepted by default since version 2.9.1, alongside JPG and PNG; SVG uploads are allowed but sanitized on the server before they're stored.
Does Cmsmart check resolution before accepting a file?
Yes, in two places: the Upload design tab's minimum DPI applies to JPG/JPEG files at the moment of upload, and AI Preflight's Required DPI setting scans the order file (any format) before production, catching low-resolution images that the upload gate doesn't screen.
What happens if a customer's file fails the checks?
A file outside your allowed types or size limits is rejected at upload. A file that fails preflight (low DPI, wrong color mode, missing bleed) can be declined from the Customer Design box, with a notification asking for a replacement.
Can a customer replace a file after they've ordered?
Only if you allow it. The General settings toggle for letting a customer re-design or re-upload after an order controls this, and once an order item's artwork is approved, the approved-artwork lock (2.17) blocks further edits to that file.
Can File Upload work alongside the online designer on the same product?
Yes. A product can offer "upload only," the full online designer, or both, so a customer who already has a print-ready file can skip the design tool entirely while another customer on the same product designs from scratch.
Can Cmsmart connect File Upload to our print MIS or ERP?
Not out of the box — that's custom development. Cmsmart builds the connector that pushes approved files and order data into your production system; see the custom-development section above for how that work is scoped and delivered.