%202%20(2).png){kind=avatar}
Most jewelry POS conversations end with the same question: "Do you work with mine?" If your store runs on one of the larger systems like The Edge, Lightspeed, Shopify, or Jewel360, the answer is yes through a direct integration. But independent jewelry retail runs on dozens of less-common POS platforms too. That is where BIG comes in.
BIG (Buyers Intelligence Group) is an aggregator that connects Clientbook to the long tail of jewelry POS systems through one shared API. If your POS is not on our direct integration list, there is a strong chance BIG covers it.
This guide explains what BIG is, which POS systems it bridges, what data flows through it, and how to know whether you should ask for a direct integration or a BIG-routed one.
What BIG Is and Why It Matters for Jewelry Clienteling
BIG sits between Clientbook and the jewelry POS systems that did not build their own direct connection to us. Instead of every small POS vendor having to build and maintain a Clientbook integration, BIG handles the API plumbing for many of them at once. We connect to BIG. BIG connects to your POS. Your data flows.
For your store, the experience is the same as a direct integration in most ways. Customer records, purchase history, and product data move from your POS into Clientbook. Your associates see the full client picture in the Clientbook app. Automations fire on real sales activity. The plumbing underneath is just routed differently.
Which POS Systems BIG Bridges
BIG-routed integrations cover a wide swath of jewelry-specific and general retail POS platforms. The list grows over time, but here are the systems we connect to today through BIG:
ACCEO Smart Vendor, Ace, Adaptive, AIMS, Amber, ARMS, Artisan, ASC, Bravo, BridalLive, Business Mind, Chaindrive, Clarity, Clover, Counterpoint, Crystal, DCI, Diamond Counter, Diaspark, Easy Pro, Epass, ERP, Executive, EZ Process, FileMaker, Flawless, Gemini, Gem of the Net, Genesis, Gers, Guild Jeweler, Heartland, HubSpot, IMC, Incom, JCS, Jewel2000, Jewel Master, JewelMate, JM20, JM2000, JM9, KWI, Luxe, Mi9, Myriad, NetSuite, Newstore, Oracle, PC America, PROFIT Systems, QuickBooks, QuickBooks POS, Renaissance, Repair Shopper, Retail Pro, Retail Profit Systems, RETAIL Vantage, RunIt, Salesforce, ShopKeep by Lightspeed, Shopkeeper, SMRT Systems, SmythRetail, SoftGem, Square, SwipeSimple, Teamwork, Tritech, Verifone, White Diamond, WinCDS, Windward, WinJewel, Winstore, Wix, WJewel, Zoho, Jewelry Master, SAP, Prism, RTI, and more.
If your POS is on this list and not on our direct list, BIG is the path. If you do not see your POS at all, contact us. We add new systems regularly, and our integrations team can confirm whether BIG covers it before you commit.
How the BIG Integration Works
The architecture is straightforward.
Your POS sends data to BIG on its normal cadence.
BIG normalizes that data and passes it to Clientbook through our shared API.
Clientbook stores the data in your client profiles and triggers any automations tied to it.
Your team does not interact with BIG directly. They work in Clientbook. BIG is plumbing.
What Syncs Through BIG
The data set BIG-routed integrations cover is more conservative than what flows through our direct connections, but it is enough to power the core clienteling workflows for most stores.
Client records, including names, contact details, and the relationships you have on file
Sale transactions, so every purchase shows up in the client profile
Product information, so your team can reference what was sold and when
Birthdays and anniversaries when your POS captures them
What is more limited compared to direct integrations: real-time bi-directional sync of edits made in Clientbook back to your POS. With BIG, the data flow is primarily one direction (POS to Clientbook) for most fields. Direct integrations like The Edge support full bi-directional sync of clients, wishlists, and notes.
For most stores, that limitation is invisible. Your team uses Clientbook for client outreach and your POS for transactions, and the data they each need stays current in both places.
Direct Integration vs BIG: Which to Ask For
If your POS appears on both our direct integration list AND on BIG's coverage list, ask for the direct integration. Direct gives you bi-directional sync, faster data refresh, and a slightly broader feature set. The Edge, Lightspeed, Shopify, Jewel360, RAIN, ASC, LogicMate, and MusicShop360 are the current direct partners.
If your POS is only on the BIG list, that is the right path. The integration setup is just as straightforward, and the clienteling outcomes are nearly identical for day-to-day workflow.
If you are evaluating Clientbook before choosing a POS, this is worth knowing: a direct integration is generally preferable to a BIG-routed one, but the BIG-routed list is broad enough that you do not need to switch POS systems just to use Clientbook.
What Connected Data Unlocks for Your Team
Complete client profiles, ready on day one
Once your POS data has flowed through BIG into Clientbook, your associates open the Clientbook mobile app and see complete profiles for every client your store has ever served. Purchase history, contact details, the relationships you have tracked. No more starting from a blank slate or pulling reports out of your POS to prep for a follow-up call.
Automated outreach tied to real sales activity
Clientbook automations fire on the events that flow in from your POS through BIG.
Post-purchase thank-yous after a sale rings up.
Anniversary and birthday reminders when those dates are captured.
Dormant-client outreach when a client has not bought in a configurable number of days.
Clean-and-check or service-due reminders based on purchase date.
None of that requires your team to remember or pull a list. The data flowing in powers the outreach automatically. See how Clientbook automations work.
Brand catalog images right in the messaging app
Inside Clientbook, associates can browse and text high-quality product images from major designer catalogs including Tacori and A.JAFFE. AI-powered recommendations match catalog items to client purchase history, which Clientbook gets from your POS. This works the same whether your POS connects directly or through BIG.
Associate performance tied to real sales
When an associate sends a Clientbook text and that client comes in and buys, the sale ties back to the original outreach. Managers see who is driving repeat business with real numbers, not guesses. The attribution works the same whether the underlying sale data came in through a direct integration or through BIG.
Setup: What to Expect
Setup for a BIG-routed integration follows roughly the same timeline as a direct integration.
Day 1: Our integrations team coordinates with BIG to authorize your store on their side. Initial historical sync starts.
Day 2: Historical data finishes flowing in. Your team gets training on the Today page, the mobile app, and the automations you want turned on at launch.
Day 3: Live. Associates using Clientbook on the sales floor.
You do not need to be technical to make this happen. You need an admin on your POS who can grant BIG access if it is not already in place, and a few hours of your team's time for training. Our team handles the rest.
Frequently Asked Questions
Do I have to be a current BIG customer to use this integration?
Not necessarily. Some stores already use BIG for other purposes (industry data, vendor analytics) and the Clientbook connection layers on top. Stores without an existing BIG relationship can still get the integration set up. Our team walks you through what's needed.
How is the data refresh cadence different from a direct integration?
Direct integrations like The Edge sync close to real time. BIG-routed integrations typically refresh on a slightly longer cadence. For day-to-day clienteling work, the difference is rarely noticeable. If a client buys at noon, the data is in Clientbook well before the next outreach window.
Will my data be secure flowing through BIG?
Yes. BIG operates as a data passthrough with security standards appropriate for retail data, and Clientbook stores everything on the same secure infrastructure as our direct-integration data.
What if my POS is on neither list?
Contact us. We add new POS systems to BIG and to direct integration regularly. There is also a path where smaller POS vendors build to our open API, which we welcome. Either way, we can usually find a route.
Can I switch from a BIG-routed integration to a direct one later?
If your POS develops a direct integration with us in the future, yes. The transition is something our integrations team handles, and your client data does not get lost in the move.
Is the price different for BIG-routed vs direct integrations?
Clientbook pricing for the platform itself is the same regardless of integration path. There may be separate BIG-side fees depending on your existing relationship with them. Talk to our team about specifics for your store.
What about my POS being on the direct list AND the BIG list?
Always ask for direct in that case. You get bi-directional sync, faster refresh, and broader field coverage. See the full list of direct integrations and BIG-supported systems.
See It Working With Your POS
The fastest way to know whether BIG covers your specific POS is to ask. On a demo, we will look up your system, walk through what the integration would look like, and pull in your specific store scenarios so you can see Clientbook in action.
Book a demo at clientbook.com/demo and tell us what POS you use. We will tell you within minutes whether direct or BIG is the path, and what your store would see on day one.
Related reading:
Does Clientbook Work With My Jewelry Store POS? (Yes, and Here's the Full List.)
Clientbook + The Edge: The Complete Integration Guide for Jewelry Stores
The Best Jewelry Store Clienteling Software in 2026: An Independent Jeweler's Guide
