Konnectryx keeps Lightspeed synchronised with Salesforce in near real time, so every tune-up, accessory and new bike you ring up builds a record of the rider behind it. This is the POS CRM integration for bike shops: no exports, no overnight batch, no wondering who is due for service.
Polls Lightspeed as often as every five minutes. Salesforce edits queue instantly.
A bike shop lives on the repair bench first, then on bikes and accessories, then on the rides and demo days that build a following. The connector treats them all alike: whatever is rung through Lightspeed is attached to a person, so the bench stops being a black box.
A flat fix, a suspension service and a full overhaul are all sales at the register. Once they sync, the rider's record shows what was done and when, so a reminder before spring is a Salesforce list, not a guess.
Every bike, helmet, light and rack lands in Salesforce as a Closed Won Opportunity with its line items. You can see who bought an e-bike and has never bought a charger or a lock, and make that offer once.
Ride entries, demo day sign-ups and maintenance clinics are bought at the counter too. With those on the record, last season's riders are one Salesforce list away from this season's invitation.
The connector runs in two modes depending on which way the data moves. Whether it is a repair ticket paid on a busy Saturday or an email corrected by the service manager in Salesforce, nobody presses a button.
Insight asks Lightspeed for anything that changed since it last looked. You choose the interval, down to five minutes.
Any Account or Contact update in Salesforce is queued immediately and sent as fast as Lightspeed's API will accept it.
Insight polls Lightspeed on your interval, as often as every five minutes.
Changed customers, sales, quotes, items, employees, registers and shops are collected.
Records are compared against Salesforce so duplicates are not created.
Sales land as a Closed Won Opportunity and an Activated Order, line items included.
An Account or Contact is updated in Salesforce and saved.
That record is queued immediately, no waiting for the next poll.
Insight sends it as quickly as Lightspeed's API will accept changes.
Bulk updates are paced deliberately, so a mass edit does not overrun the queue.
Here is one illustrative rider moving through a bike shop. The record shown under each step is sample data, to explain how the Salesforce profile builds up as sales are rung through Lightspeed.
A rider leaves a bike for a tune-up. When it is paid for, that sale creates the customer in Salesforce without anyone typing a name twice.
An overhaul and a new chain follow. Each one attaches to the same record, so the shop can see what was done to the bike and when.
A Salesforce list of riders whose last tune-up was ten months ago becomes the spring reminder. The rider books before the rush instead of during it.
With the bike and its history on file, an offer for lights or a rack is relevant. The sale at the counter adds to the same record.
Then the follow-up is easy: a Salesforce list of riders who service here, own an e-bike and have not been on a group ride yet. The connector delivers the data. Your Salesforce does the reminding.
These are the real mappings from the product overview, not a marketing summary. Open any card to read the field level detail, including the Person Account variants that many bike shops use for individual riders.
Type a Lightspeed field, a Salesforce label, or an API name. If your team has ever argued about where the rider's email ends up, this settles it.
| Object | Lightspeed field | Sync | Salesforce field |
|---|
Insight cannot sync Lightspeed custom fields. Everything else above is standard.
A rider gives one phone number at drop-off and another when they email about a quote. Two way sync only works if disagreements are handled honestly, so the connector flags them instead of guessing, and compares records before writing so one rider never becomes two.
Account and contact details are compared before creation, so the same customer does not appear twice.
When the same field is edited differently in each system, the record is held for a human decision.
Choose the correct value and Insight writes it to both platforms. The conflict closes.
Configuration decides what is in scope. Anything you leave out simply does not move.
Mobile phone was changed in both systems since the last sync. Pick the value that should win.
Every repair ticket is the start of a longer relationship.
Short walkthroughs of the connector moving live data between Lightspeed and Salesforce.
Move the sliders to match your bike shop. This is your own arithmetic, not ours, so bring it to the call and we will pressure test it together.
New riders, edited contact details, and repair and sales tickets that need to reach Salesforce.
Find the rider, retype the details, check the ticket, fix the typo.
Pay plus overhead for whoever currently does the data entry.
Duplicate riders, stale emails, tickets credited to the wrong register.
Year one uses the published $1,500 installation and $8,500 annual subscription. Rework is costed at three times a single manual entry, since somebody has to find the problem before fixing it.
One installation fee and one annual subscription, whether you run a single bike shop or several. No per seat pricing, no per record metering.
For a basic configuration. Advanced data mapping may incur additional fees.
Everything running, monitored, and supported by a dedicated team member.
Insight can be customised to meet your exact needs. Bring the awkward requirement to the call.
Questions before you commit? A dedicated team member is available Monday to Friday, 8:30am to 5:00pm Pacific.
The best season starts with a rider who already knows your name.
Thirty minutes, screen shared, on your data. We will map your Lightspeed fields to your Salesforce org live and tell you honestly where the awkward parts are.
