If your store runs on Adaptive, the question is narrow and practical: can you put a clienteling tool on top of it without disturbing anything that already works?
Yes. Clientbook connects to Adaptive through BIG, the integration partner that collects point of sale data on a store's behalf and passes it to Clientbook. Once that connection is live, your client records, products, and sales history land inside Clientbook, and your associates text clients, follow up, and track relationships from there while Adaptive keeps running the store.
Here is what Adaptive is, how the connection works, and where the honest limits sit.
What Adaptive Is
Adaptive is jewelry software from Adaptive Business Solutions, based in Boca Raton, Florida. Adaptive describes its platform on justjewelrysoftware.com as end to end business software for jewelry retailers and manufacturers, built on Microsoft Dynamics 365 Business Central.
The retail side is deliberately broad. Adaptive's product page lists financial management, inventory and shipping, purchasing, special order management, consignment, returns and repairs, POS and store management, a Lookbook inventory search tool for associates, Power BI analytics, and a CRM and clienteling web application. Adaptive also covers the manufacturing side, with style configuration, operations planning and forecasting, and diamond and gemstone supply. Adaptive's site cites over 20 years of jewelry industry experience.
That scope tells you who Adaptive is built for: operations with real complexity. Multi-store retailers, stores that manufacture as well as sell, and businesses that want accounting, inventory, and the sales floor inside one Microsoft-based system.
One clarification, because the word gets used loosely. Adaptive here means the jewelry ERP and POS from Adaptive Business Solutions, not adaptive retail as a general concept, and not a Microsoft product despite running on Business Central.
How Clientbook Connects to Adaptive
Clientbook reaches some point of sale systems through a direct connection and others through BIG, Buyers Intelligence Group. Adaptive is on the BIG side, and Adaptive's own site lists Clientbook among its integration partners. Paths do move as versions change, so confirm the path for your version with onboarding.
Our integrations documentation describes the arrangement plainly: BIG integrations are managed by BIG, who collects data from your point of sale system and sends it to Clientbook on your behalf, and setup and data syncing are handled through their system.
For an Adaptive store coming onto Clientbook, the shape of the process is:
You fill out the BIG permission form so BIG can share your data with Clientbook.
BIG emails you a scheduling link for an installation call.
On that call, a BIG technician helps install the BIG applet on your server.
BIG prepares your data and sends it to Clientbook, and our support team validates that clients, products, and sales all arrived.
Your team is not doing the technical work. You need someone who can grant access to your server and a few hours for training once the data lands. Timing and the exact field list come from our onboarding team, because both depend on your Adaptive configuration and BIG's scheduling.
What flows across
Client records. Names, phone numbers, email addresses, and mailing addresses. When a customer profile changes in your POS, BIG sends the updated record in the next day's client file.
Products and product images, where images are available from your POS.
Sales transactions. Some integrations import up to five years of history, and all of them keep syncing new sales going forward.
Repair and service transactions, where the integration supports them.
Cadence matters when you set expectations with your team. On a BIG-routed integration the data arrives as a daily file, so a change made in Adaptive today shows up in Clientbook tomorrow. That is a once-a-day rhythm, not a live mirror, and it is worth saying out loud to associates before they go looking for a sale they rang an hour ago.
Which columns apply to an Adaptive store, including whether birthdays, anniversaries, spouse links, and POS-side wishlists come across, is shown on the integration chart inside your Clientbook dashboard. Ask onboarding to walk you through your row before you go live.
What Changes on the Sales Floor
Every profile arrives with history attached
Nobody starts from a blank screen. Open a client in the Clientbook app and the purchase history is already there, pulled from Adaptive through the integration.
That only works if the store is capturing contact details at the counter, the quiet failure point in most jewelry retail. Wilson Diamonds increased contact capture from under 5 percent to 90 percent after rolling out Clientbook. A profile with no phone number cannot be followed up on, no matter how good the POS data is.
Wishlists, collections, and texting in one place
Associates group products into collections on a client's profile to track what that person is interested in, then share the collection to the client by text. A client deciding between three settings gets all three, and the associate has a reason to follow up next week that is not just checking in. The message, the purchase history, and the collection sit on the same record, so whoever picks up the reply has the context.
Follow-up that fires off real sales
Once sales data is flowing, Clientbook's sales triggers do the remembering. A trigger watches for a purchase in the product categories you choose, within a price range you set, then sends an automatic reminder to the associate or an automatic message to the client. Categories come from your point of sale through the integration, so a bridal trigger is built on your own category structure rather than a generic list.
Most stores start with three: a post-purchase thank you, a clean and check reminder timed off the purchase date, and a follow-up on higher-ticket categories.
Credit that lands on the right associate
During setup, each associate's identifier from your sales data is mapped to their Clientbook profile, which is what lets sales attribute back to the person who did the outreach. Managers get a clienteling leaderboard covering clients added, client calls, messages sent, wishlists shared, and store visits.
The point is not the standings. It is that clienteling stops being invisible work. Adorn saw 54 percent of associates clientele daily and 86 percent at least twice a week, the kind of adoption that happens when the activity is visible and the data is already in the app.
Honest Limits
A BIG-routed integration suits an Adaptive store well, but it is not identical to a direct one.
Setup runs on a partner's schedule. BIG drives the install call and the data preparation, so we do not quote a fixed timeline the way we can for a direct integration.
Data moves primarily from your POS into Clientbook. Edits made in Clientbook are not designed to write back into Adaptive for most fields. Adaptive stays the system of record for transactions and inventory.
Birthdays and anniversaries do not update after the fact. If those dates change in your POS after the initial import, correct them on the Clientbook profile.
Removing data in your POS does not remove it in Clientbook. Delete an email address on the POS side and Clientbook keeps the value it has.
Sales triggers need a day of headroom. Because sales arrive in the next day's file, a trigger set to fire zero days after the sale will go out the following day. Build the delay into the trigger rather than fighting it.
Sales opportunities are Clientbook only. They do not sync to any POS.
Client records arrive exactly as your POS stores them. Cleaning up duplicate and malformed records in Adaptive before the sync is time well spent.
Who this actually fits
Adaptive includes its own CRM and clienteling web application, and some stores run manager-level client work there. Clientbook is a different layer: the app in the associate's hand on the sales floor, built around texting, wishlists, and automated follow-up.
Stores that get the most from pairing them have several associates, a client base too large for anyone to hold in their head, and a real interest in repeat business. For the wider view of the stack, we keep an honest guide to jewelry store management tools by layer and a deeper explanation of the category in our guide to jewelry store clienteling software.
Frequently Asked Questions
Does Clientbook integrate with Adaptive POS?
Yes, through BIG. Adaptive lists Clientbook among its integration partners on its own site, and BIG handles the collection and delivery of your data to Clientbook. Confirm the path for your version with onboarding before you plan around it. Our full guide to the BIG integration bridge explains how that layer works across the long tail of jewelry POS systems.
Why do my sales appear in Clientbook the next day instead of immediately?
Because BIG delivers your data as a daily file rather than streaming each transaction. A sale rung up this afternoon arrives in tomorrow's file and shows up in your sales log and sales report then. That is how the bridge is built, not a fault in your setup.
Does the integration change how sales triggers work?
It can. Because your data arrives as a daily file, a trigger set to go off zero days after the sale will not fire until the next day, when that file lands. That is expected on a BIG-routed integration and easy to design around.
What information does not sync?
The integration chart in your dashboard shows everything that moves between your POS and Clientbook. If a data type is not on the chart, it does not sync. The most common question is sales opportunities, which are managed only in Clientbook.
Can I switch from Adaptive to another POS later without losing my client data?
Yes. Clientbook has a POS migration process built to move a store from one point of sale system to another while minimizing data loss. Tell support before you switch and they will run the steps with you. Not sure which system you are on? Start with the full list of jewelry POS systems Clientbook supports. If you are weighing a specific system, we have written up how Clientbook connects to Jewelry Shopkeeper and how it connects to Logicmate JewelMate.
See It With Your Own Adaptive Data
Book a demo at clientbook.com/demo and tell us you are on Adaptive. We will confirm your integration path, walk through what your associates would see on day one, and answer your team's questions about the hand-off with BIG.
Related reading:
Does Clientbook Work With My Jewelry Store POS? (Yes, and Here's the Full List.)
Clientbook + BIG: How the Integration Bridge Connects Clientbook to Your Jewelry POS
The Best Jewelry Store Clienteling Software in 2026: An Independent Jeweler's Guide



