Syncs connects your Sharper system to another Sharper system so the two can share customer records. It is used by properties that operate more than one business on separate Sharper installations and want a guest to exist once, not twice.
This is not the accounting sync. Syncs has nothing to do with QuickBooks or Sage. Accounting syncing is handled under Accounting → Accounting Sync and System Settings → Accounting Integration. Syncs only moves customer records between Sharper systems.
What a Sync Actually Does
Each row on this screen represents one other Sharper system that yours pulls customers from. Every few minutes, Sharper contacts that system, asks for customers whose records changed since the last check, and brings them across.
When a customer arrives, Sharper tries to match them to someone you already have:
First it looks for a customer already linked to that same record on the other system. If found, that customer is updated.
If not, it looks for a customer with the same email address. If found, that existing customer is linked and updated rather than duplicated.
If neither matches, a new customer record is created.
The details brought across are the customer's contact and identity information — name, display name, email and CC emails, phone and alternate phone, full address, company, house account, and whether the record is active.
Customer portal logins travel with the record. A guest's saved password is part of what syncs, so someone who set up a portal login at one of your properties can sign in at the other with the same details. This is usually the point of turning a sync on — but it also means a password change on one system becomes the password on both.
The sync is one-way: your system pulls from the other one. If both systems should share customers in both directions, each needs its own sync pointing at the other.
Only customer records move. Reservations, invoices, payments, and balances stay where they were created — a guest synced from another property arrives with no financial history attached.
What You See on a Sync
Field | What it is |
Name | A label for the system being synced from — normally the other property's name. Required, and used only so the list is readable. |
Configuration String | The connection details — the other system's address and the security token used to authenticate. Configured by your Sharper team. |
Customer | The switch that turns customer syncing on for this connection. |
The Customer toggle is the only switch that does anything today. With it off, the connection stays configured but nothing is pulled — the sync runs and does no work. If customers have stopped appearing from another property, this toggle is the first thing to check.
Do not edit the Configuration String. It holds the address and security token that authenticate your system to the other one, and both are issued as a pair during setup. Changing or clearing either value stops the sync silently — Sharper skips a connection with missing details rather than reporting an error. If a sync needs to be repointed at a different system, that is a setup task for your Sharper team.
Checking That a Sync Is Working
The sync runs on its own roughly every five minutes. There is no "run now" button and no status column on this screen, so you confirm it a different way:
Confirm the connection is listed here and its Customer toggle is on.
Go to System Settings → Cron Events and find Company Sync. This shows when the job last ran and whether it finished cleanly.
Change a customer's details on the other system, wait a few minutes, then search for that customer in your CRM → Customers list. The change should appear.
Only customers whose records have changed since the last run are collected each cycle. A customer nobody has touched on the other system will not come across just because you are waiting for them — edit and save the record there to bring them over.
If Customers Are Not Coming Across
Work through these in order:
What to check | Why it matters |
The Customer toggle is on | With it off nothing is pulled, and there is no warning anywhere that this is the reason. |
The record was actually changed on the other system | Only records modified since the last run are collected. |
Company Sync in Cron Events is running | If the job is not completing, no connection on this screen is being processed. |
The customer already exists under a different email | Matching falls back to email. A guest whose two records use different addresses will arrive as a second, separate customer rather than merging. |
If a guest has ended up as two records because their email differed between systems, see CRM - Merging Duplicate Customers.