WooCommerce Customer CRM Print Shop Guide (NBDesigner)

Applies to Cmsmart Product Designer (NBDesigner) 2.17.0 · Updated October 2026. Covers the built-in Sales → Clients customer CRM shipped in 2.10.0 and still part of the plugin today, verified against the official changelog.

In short

  • Cmsmart Product Designer (NBDesigner) ships a built-in WooCommerce customer CRM — Sales → Clients — so a print shop can see who its repeat buyers are without a separate plugin.
  • It resolves one customer record across guest and registered orders, scores a lifecycle segment (new, active, at-risk, lapsed, VIP), and surfaces tags, merges and a daily care digest of who needs attention.
  • Setup is a checklist inside the plugin you already run; going further — ERP sync, win-back SMS, loyalty credit — is custom development Cmsmart builds on top.

What does it cost a print shop to lose track of repeat customers?

Cmsmart Product Designer's Clients CRM turns scattered WooCommerce order data into one customer record per buyer, so a print shop stops paying — in missed reorders and manual lookups — for information it already has.

Most WooCommerce print shops run customer management out of the order list, a spreadsheet, and whichever staff member remembers the regulars. That costs real time and real revenue:

  • Manual lookups. Checking whether a customer has ordered before means searching orders by email, one at a time.
  • Guest checkout blind spots. A shopper who orders as a guest twice looks like two different people unless someone manually checks the email address — and requiring an account first costs orders: on Baymard Institute's checkout research, 18% of US online shoppers have abandoned a cart because the site wanted them to create an account first (Baymard Institute, 2025).
  • No who-needs-attention view. A customer who hasn't ordered in four months, or whose proof has sat unapproved for a week, doesn't raise a flag — someone has to notice.
  • Broadcast-only email. Without segments, emailing just your best customers means exporting all orders to a spreadsheet and guessing who counts.
  • Staff time on reporting. Pulling a top-20-customers-this-quarter list by hand from the orders screen is slow enough that most shops just stop asking the question.

None of this shows up as a line item on a P&L, but it is a cost: every hour spent hand-searching orders is an hour not spent calling a lapsed customer back.

What would it look like if every repeat customer got the right follow-up automatically?

With Cmsmart Product Designer's Clients CRM, every order — guest or logged in — lands on one customer record with a lifecycle segment, so a print shop's morning routine starts with a short, accurate list of who to call, not a spreadsheet to rebuild.

Example scenario. A print shop owner opens Sales → Clients before coffee: one VIP flagged at-risk after five quiet weeks, two overnight signups who started a design but never checked out, one proof waiting on a decline reason. They tag the VIP for a personal call, bulk-email the two abandoned-design shoppers from a saved segment, and move on — fifteen minutes instead of an afternoon.

Cmsmart insight: in our delivery work, the shops that get the most out of a customer CRM are the ones that act on the "at-risk" and "design abandoned" segments weekly, not the ones with the most tags. A segment nobody reads is just another report.

How does Cmsmart build the WooCommerce customer CRM print shop teams rely on?

Cmsmart Product Designer resolves every WooCommerce order — guest or registered — into one customer record, then layers segments, tags and a care digest on top, all inside the Sales menu you already use for orders and files.

The Clients CRM is not a bolt-on plugin reading your orders from the outside; it is built from the same order data Cmsmart Product Designer already manages for print production. The building blocks, per the 2.10.0 release notes:

  • Identity resolution. Guest and registered orders that share an email are resolved into one customer record, instead of looking like separate buyers.
  • Lifecycle segments. Every customer is classified automatically — new, active, at-risk, lapsed, VIP and a design-abandoned segment for shoppers who started a design but never ordered.
  • Tags and merge. Staff can tag customers (e.g. wholesale, repeat — business cards) and merge two records that turn out to be the same person.
  • Bulk actions and bulk email. Act on a whole segment at once — tag it, email it, or export it. Segmented email like this consistently outperforms one-size-fits-all blasts: HubSpot reports segmented campaigns drive 30% more opens and 50% more clickthroughs than unsegmented ones (HubSpot, 2026).
  • Care digest. A standing view of who needs attention. The 2.10.0 changelog entry describes this as "a care digest of who needs attention" without itemizing it; based on the segments and events the CRM tracks elsewhere, that is likely to include lapsing VIPs, unapproved proofs and abandoned designs.
  • AI as a lead channel. A shopper who uses an AI design tool and signs up shows up in Clients on its own AI channel, so those leads don't get lost outside the CRM.
  • CSV export. The full list exports to CSV for anything the built-in views don't cover.

This job's own captures of the demo store don't include a screenshot of the Sales → Clients screen itself — the steps above are sourced from the official 2.10.0 changelog, not a UI walkthrough, and we're not showing a mockup of what we haven't captured. What the captures do show is the order data the CRM is built from, and the artwork-review event that feeds its care digest:

WooCommerce customer CRM print shop order list in Cmsmart Product Designer, showing customer, total and status per order
Cmsmart › Orders: the order list the Clients CRM resolves into customer records. This is the orders screen, not the Clients CRM screen itself.
WooCommerce order detail showing the customer name, email and phone Cmsmart resolves into a CRM record
Order detail: name, email and phone per order — the fields the Clients CRM matches across guest and registered orders to build one customer record.

The approved-artwork lock (2.17) is one of the events the care digest watches: once a customer accepts or declines a proof in the Customer Design box, that status change is what the digest reads to flag a stalled approval.

Customer Design approval box in WooCommerce with artwork accepted, the event the Clients care digest tracks
Customer Design box, approved: this accept/decline event is one of the signals the Clients care digest surfaces per customer.
Without a CRMWith the Cmsmart Clients CRM
Guest and registered orders look like different customersOrders are resolved into one customer record by email
Finding who hasn't ordered lately means scanning the order list by dateLapsed and at-risk customers are segmented automatically
Emailing repeat buyers means exporting orders to a spreadsheetBulk email goes straight to a saved segment or tag
Two accounts for one customer stay separate foreverMerge combines duplicate records into one
A stalled proof approval is easy to missThe care digest flags it against that customer's record

What's the ROI of a built-in customer CRM for a print shop?

The Clients CRM pays back in staff hours saved per week and in repeat orders a shop would otherwise miss, because repeat buyers already carry a disproportionate share of ecommerce revenue.

BenefitHow it shows up in your businessKPI to track
No separate CRM subscriptionCustomer data stays inside the plugin that already runs your storeTools/plugins billed per month
Faster who-to-call decisionsCare digest replaces manual order-list scanningMinutes/day on customer lookups
Fewer missed repeat ordersAt-risk and lapsed segments trigger outreach before a customer leaves for goodRepeat-order rate, reorder lag (days)
Recovered abandoned designsDesign-abandoned segment targets shoppers who built a product but didn't buyAbandoned-design recovery rate
Cleaner customer listMerge removes duplicate guest/registered records before they skew your numbersDuplicate-customer rate

Rough-cut worksheet (use your own numbers): if staff spend H hours a week manually checking "has this customer ordered before" at an hourly cost of C, the care digest removing that lookup is worth roughly H × C × 52 a year in staff time alone — before counting a single recovered reorder. Repeat customers are worth protecting: on ecommerce platform Gorgias's own customer data, repeat buyers are only 21% of customers but generate 44% of revenue and 46% of orders (Gorgias, 2025).

How do you set up and use the Clients CRM in Cmsmart Product Designer?

Cmsmart Product Designer's Clients CRM runs on the orders your store already takes — there's no separate install or sync to configure, just a short checklist to start using the segments and digest it builds automatically.

We don't have a fresh screenshot of the Sales → Clients screen from this job's demo-store capture run, so the steps below are written from the 2.10.0 release notes and the plugin's own menu structure, not a verified screenshot walkthrough. Confirm the exact field names on your own install before relying on this as a click-by-click guide.

  1. Confirm Cmsmart Product Designer (NBDesigner) is active under Plugins, with a valid license applied, and that the version is 2.10.0 or later (Clients shipped in that release).
  2. Open Sales → Clients in wp-admin.
  3. Let the first load run: the CRM builds its customer index from your existing WooCommerce order history, both guest and registered orders.
  4. Scan the care digest for the day's flags — lapsing VIPs, abandoned designs, stalled proof approvals.
  5. Open a flagged customer record and check which lifecycle segment they're in (new, active, at-risk, lapsed, VIP or design abandoned).
  6. Add a tag for anything your team tracks manually today, such as wholesale or a product line.
  7. If the same person shows up twice — once as a guest order, once as a registered account — use merge to combine the records.
  8. Filter the list to a segment (e.g. at-risk) and use bulk email to send one message to everyone in it.
  9. Export the list to CSV if you need it in a spreadsheet or another tool for now.
  10. Check back on the care digest on a fixed schedule — daily or weekly — so flags don't go stale.

Two adjacent screens back the data this checklist relies on. Neither is the Clients screen itself, but both feed it: the order list Clients resolves into customer records, shown earlier, and the proof-approval event below, which is exactly the kind of signal the care digest surfaces per customer.

Customer Design box with artwork pending review, before the approval event the Clients CRM care digest tracks
Customer Design box, pending: before a decision, this is the kind of stalled item the care digest would flag against the customer's record.

For the plugin and version half of step 1, this is what an active install looks like on the Plugins screen (license status isn't shown on this screen — check that separately under the plugin's License tab):

Cmsmart Product Designer (NBDesigner) plugin active on the WordPress Plugins screen
Cmsmart Product Designer (NBDesigner), shown active on the demo store's Plugins screen.

Deeper settings for the designer itself — upload rules, output and print options — are covered in our Cmsmart Product Designer plugin guide rather than repeated here.

Going further: what can Cmsmart build on top of the Clients CRM?

Where the built-in Clients CRM stops, Cmsmart builds for merchants as custom development — connecting it to the tools and workflows a growing print shop actually runs on.

The core CRM covers identity resolution, segments, tags and a digest. For shops that need more, these are real extensions Cmsmart builds as custom development, not features of the stock plugin:

  • ERP/MIS or accounting sync. Business reason: finance and production teams need customer and order data outside WordPress. Cmsmart builds the integration that pushes Clients records and order status to your ERP, MIS or accounting system.
  • Automated win-back messaging. Business reason: a flagged at-risk or lapsed segment is only useful if someone acts on it fast. Cmsmart builds automated SMS or WhatsApp sequences triggered by segment changes, on top of the CRM's existing classification.
  • Loyalty or reorder credit. Business reason: repeat buyers already drive a large share of revenue (see the ROI section above); a visible reward keeps them ordering direct instead of shopping around. Cmsmart builds points, credit or tiered pricing rules layered on the customer record.
  • B2B company accounts. Business reason: wholesale and corporate buyers often have several people ordering under one account. Cmsmart builds a company-level view over individual Clients records so a B2B buyer's whole team rolls up to one relationship.

Each follows the same delivery path — discovery, solution design, build, QA and launch with support afterward — as the work in our ecommerce project case studies.

Get a custom CRM workflow quote

Why work with Cmsmart for your print shop's customer data?

Cmsmart has built and supported WooCommerce print-shop stores since 2012, so the Clients CRM ships as part of a plugin backed by an active delivery team, not a one-off extension.

Cmsmart is a Netbase JSC division running web-to-print and custom ecommerce projects since 2012, with 6,300+ client projects and 1,800+ live stores, rated 4.2 on Trustpilot across 404 reviews. One long-time user sums up what that support looks like day to day:

"We have had the NB Designer plugin installed for three years and have experienced absolutely no problems during that time. It is wonderful to see their commitment to continuous development, with new features being added frequently to keep the software current and highly capable. […] the level of support is outstanding." — Web Developer, Trustpilot review

See related delivery work in our ecommerce project case studies, or start with the web-to-print solutions hub if you're still scoping a full storefront rebuild, not just the CRM piece. For hands-on design-feature customization, our product designer customization service covers everything from editor tweaks to the CRM extensions above.

Two related reads if you're setting up the wider order-to-production flow around your customer data: our comparison of Cmsmart vs. Zakeke on approval and print-ready PDF, and our guide to setting up advanced artwork uploads, which feeds the same order and design data the Clients CRM reads.

Frequently asked questions

Do I need a separate plugin to get a customer CRM in WooCommerce?

Not if you're already running Cmsmart Product Designer 2.10.0 or later — Sales → Clients is built in. You'd only add a separate CRM plugin if you need capabilities beyond segments, tags, merge and bulk email, such as full marketing automation.

Does the Clients CRM track guest checkout orders, or only registered customers?

Both. Identity resolution matches guest and registered orders that share an email address into one customer record, which is the main gap a plain WooCommerce order list has.

Can I email a group of customers directly from the CRM?

Yes — filter to a segment or tag, then use the bulk email action. You can also export any list to CSV for a dedicated email platform if you prefer to send from there.

How is this different from a general-purpose CRM or email tool like Mailchimp?

The Clients CRM is scoped to what a print-on-demand store needs: order-based segments and a care digest tied to the design and approval workflow, not a general marketing automation suite. Deeper automation or a dedicated CRM sync is the kind of integration Cmsmart builds as custom development.

Can Cmsmart connect the Clients CRM to our own CRM, ERP or help desk?

Yes, as a custom integration — Cmsmart builds the sync between Clients records and external systems on a project basis; see the going-further section above.

How long does it take to start using the Clients CRM after updating the plugin?

The customer index builds from your existing order history on first load, so there's no data migration step — you're looking at segmented customers as soon as the index finishes building, which depends on your order volume.