%202%20(2).png){kind=avatar}
If your store runs on Shopkeeper, you can text your customers without leaving your point of sale behind. Clientbook connects to Jewelry Shopkeeper, pulls your client list, products, and sales history across, and gives associates a texting and clienteling layer on top of it.
This guide covers which Shopkeeper we mean, what the integration moves, how setup works, what your team can send, and where the honest limits are.
First, Which Shopkeeper Are We Talking About?
At least three unrelated products use some version of the name, and a search for texting apps turns up all of them.
Jewelry Shopkeeper (jewelryshopkeeper.com), also referred to as Visual Jewelry Shopkeeper, or VJS in the software itself, from Compulink in Scarsdale, New York. Their site calls it the complete jewelry store management software, built for full-service independent jewelers, and its documentation covers point of sale, inventory, repair tracking, appraisals, accounting, and tag printing. This is the one this guide is about.
Shopkeeper POS (shopkeeperpos.com) is a different company and product, a general point of sale, inventory, and bookkeeping platform for shops, boutiques, cafes, and restaurants.
ShopKeep is a third product, a general retail system acquired by Lightspeed and since folded in as Lightspeed POS (S-Series).
Does Clientbook Work With Jewelry Shopkeeper?
Yes. Compulink builds the connection to Clientbook from inside Shopkeeper, so on current builds your store's data moves straight into Clientbook, the way it does for The Edge, RAIN, and Logicmate. Some older lists group Shopkeeper with the systems that reach Clientbook through the BIG bridge, so confirm the path for your version with onboarding. Compulink lists Clientbook on its own technology partners page, and Shopkeeper's help documentation includes step by step instructions for connecting a store's Clientbook account.
Plenty of tools can send an SMS. The reason Clientbook is the answer Shopkeeper jewelers land on is that the texting sits on top of the purchase history, so an associate opening a conversation already knows what that client bought, when, and from whom.
What moves from Shopkeeper into Clientbook
Per Clientbook's integration documentation, a connected store sends across:
The full client list, so every customer your store has served has a profile.
Product updates and product images, so associates can pull up and share what you carry.
Sales history, with filters you control: a minimum dollar amount, how many years of history to load, and which major classes to include.
Repair and thank you messages, so notifications your team sends by hand can run through the same system.
Client and product data refreshes roughly every fifteen minutes, and the transfer runs one direction, from Shopkeeper into Clientbook.
How Setup Works
Setup is a guided job handled with your onboarding team, not a self-serve toggle, and the exact steps depend on your Shopkeeper version. Treat this as the shape of it.
Your Clientbook account is set to Shopkeeper as the point of sale type, and associates are added with names matching exactly how they appear in Shopkeeper. That match is what keeps assignments and sales attribution correct later.
Inside Shopkeeper, an admin opens Web Services Settings and configures the Clientbook account with the credentials your onboarding team issues. Compulink's guide describes a store ID requested from Clientbook, plus a credential handshake initiated from the Shopkeeper side that authorizes Shopkeeper to send data across. Our documentation and Compulink's describe that credential step slightly differently, so use whichever your onboarding team gives you.
You choose what history to load: minimum sale price, how many years back, and which product classes. Then the initial upload runs.
Your team validates the result in the Clientbook dashboard: clients, products, product images, sales, sales categories, and associates with assigned clients.
Moving to Shopkeeper from another point of sale while already on Clientbook is a migration, not a fresh setup. Support pairs your old client IDs with the new Shopkeeper ones so client records are not duplicated, then clears and re-sends products and sales from the new system. One thing to plan for: product collections already saved on client profiles are not restored by that process, so capture anything you need before the switch.
What Your Team Can Send Once It Is Connected
Two way texting from the client record
Every conversation lives in a thread attached to a client. In the dashboard inbox, an associate opens the client details panel from the thread and sees contact information, life events, upcoming automated messages, payment requests, and associate assignments without switching screens. Replies land in the same thread, so the store owns the conversation instead of somebody's personal phone.
Message templates so the team is not writing from scratch
Admins and managers build templates from the web dashboard. Each gets a name, so associates can swipe through options and pick the right one, plus a scope controlling where it appears, including a single location for multi-store retailers. Templates also feed automated reminders for sales triggers, opportunities, and life events, so the same approved wording gets used whether a person or the system sends it.
Mass messaging with a real audience builder
For a trunk show or a holiday push, the audience starts at zero recipients and you build it with filters: include tags, exclude tags, store locations, contact methods, and when a client was last contacted. The count updates as you adjust, and the audience is evaluated at send time, so a tag you clean up on Monday is reflected in Tuesday's send. The confirmation dialog then asks you to type the recipient count, a useful guardrail.
Clientbook's guidance leans on exclude tags: skip clients who just purchased, were messaged recently, or are mid conversation with an associate. Over-messaging is the fastest way to lose the opt-in you worked for.
Automated follow-up tied to real Shopkeeper sales
Sales triggers turn a purchase into a scheduled follow-up. You name a trigger, pick the product categories it applies to (those come from your point of sale through the integration), set a minimum and maximum sale price, and choose the action: an automatic message, or a reminder on an associate's list. That is how a bridal purchase becomes a check-in weeks later with nobody keeping a paper list.
Payment requests over text
From a conversation thread in the mobile app, an associate taps the dollar sign icon next to the message box, enters an amount and a short description, adds line items if needed, previews it, creates the link, and sends it in the thread. The request shows up on the Today page so status can be tracked. Useful for repair balances, special orders, and holds.
Texting done this way gets read. Wilson Diamonds sees a 98 percent read rate on messages and over 71 percent response rate using Clientbook, which is the gap between a message that gets answered and an email that sits unopened.
The Honest Limitations
The sync runs one direction. Shopkeeper sends data to Clientbook. Notes, tags, and edits your team makes in Clientbook stay there and do not write back. For most stores that is a non-issue, since the point of sale remains the system of record. But a wishlist added on the sales floor will not appear in Shopkeeper.
It refreshes on a cycle, not instantly. Roughly every fifteen minutes for client and product data is quick enough for the afternoon follow-up window, and slow enough that it is not a live mirror.
Shopkeeper is a newer pairing than The Edge. That integration has been in the field far longer, carries broader two way behavior, and has a longer track record to quote. The Shopkeeper connection is still maturing, and a few field level behaviors, including how birthday and anniversary dates and associate assignments come across, are confirmed store by store during setup rather than promised in advance. Ask your onboarding team to confirm current field coverage for your Shopkeeper version before building a workflow around a specific field.
Shopkeeper has other texting partners. Compulink's partners page also lists FrogSwing, Chekkit, and Podium, and its help center documents Red Oxygen. Those are reasonable choices if what you want is SMS and review requests. The distinction is scope, not quality: they are messaging and reputation tools, while a clienteling platform adds client profiles, wishlists, associate attribution, and outreach that fires off purchase history. More on why jewelry store texting tools are not clienteling platforms.
Who This Fits
The stores that get the most from this pairing share a few traits. Years of customer and repair history in Shopkeeper that nobody mines. Associates who know their customers but have no shared place to record it. Texting already happening from personal phones. And no appetite for replacing a point of sale that works.
If that is your store, this is additive. Shopkeeper keeps doing inventory, repairs, appraisals, and the register. Clientbook becomes the layer your team lives in between sales, the way hundreds of jewelry retailers already run it.
Frequently Asked Questions
Do I have to switch off Shopkeeper to use Clientbook?
No. Clientbook is not a point of sale and does not replace one. Your team keeps ringing sales, tracking repairs, and managing inventory in Shopkeeper. Clientbook handles the relationship and the outreach.
Can I control how much sales history comes over?
Yes, and decide before the first upload. You set a minimum sale amount, how many years back to pull, and which major classes to include. Stores with decades of data often start with a narrower window and a price floor so client profiles stay useful rather than noisy.
Do birthdays and anniversaries come across?
Shopkeeper's setup guide asks for the anniversary code and birthday code your store already uses for customer events, entered when the connection is configured. Because those codes are store specific, confirm with your onboarding team that yours are mapped correctly before switching on life event automations.
Will my associates get credit for the sales their texts drive?
That is what the associate name matching in setup is for: associates are added to Clientbook with names matching exactly how they appear in Shopkeeper. Associate assignment is one of the things your onboarding team validates after the first upload, so confirm on that call that your team is mapped the way you expect before you build reporting around it.
What if I run a different jewelry point of sale?
Clientbook connects directly to several jewelry systems and reaches many more through the BIG bridge. The full list lives in our guide to whether Clientbook works with your jewelry store POS. If your system is not there, ask us. New ones get added regularly. Two we have written up in detail are how Clientbook reaches Adaptive through the BIG bridge and how it connects to Logicmate JewelMate.
See It Running on Your Own Shopkeeper Data
The fastest way to know what this looks like is a demo using your scenarios: repair volume, bridal customers, clients who have not bought in two years.
Book a demo at clientbook.com/demo and mention you run Shopkeeper. We will walk through what the first sync brings over and what your team sees on day one.
Related reading:
Why Jewelry Store Texting Tools Are Not Clienteling Platforms
The Best Jewelry Store Clienteling Software in 2026: An Independent Jeweler's Guide
