Integrations

Lightspeed Retail (R-Series)

Each shop authorises bike.tools once, through Lightspeed's own sign-in (Settings → Connect Lightspeed). From then on bike.tools:

• reads your shops, workorder statuses, employees, customers, items, and workorders, polling for changed workorders every five minutes (R-Series has no way to push changes), and within seconds when the bike.tools extension sees someone save a workorder, customer, bike or item in Lightspeed, and looks up items by barcode for Scan part;
• writes customers, serialized bikes, workorders and their labor and part lines for bookings, Quick Book, presets and scanned parts, status changes you make through bike.tools (Receive, status buttons, approvals, cancellations), approved contact changes, workorder photos (if you ask for them in Lightspeed too);
• never changes a status's colour (Lightspeed's API won't allow it) or rings up a sale. Lightspeed's API terms forbid acting as a checkout or reporting on which items or services a shop sold, and bike.tools doesn't.

Lightspeed's rate limits are per shop, so one shop's use never slows another's, and a large sync can take a few minutes. Tokens are stored encrypted.

What bike.tools keeps

bike.tools keeps a copy of your Lightspeed workorders (with their lines), customers, bikes and items, so status pages, search, reports and the AI tools work without asking Lightspeed every time. It's only ever used for your shop, never shared with or compared against another. Under Settings → What bike.tools keeps (an owner or admin):

• Keep our full history: you're asked when you connect. On, bike.tools reads every workorder you've had, in the background, and Settings shows how far it's got. Off, it reads the last 30 days, and anything it hasn't read from Lightspeed in 60 days is deleted within the hour; Lightspeed's terms need your say-so to keep it longer.
• Read internal notes: on unless you turn it off. Internal notes give Quick Book the context your staff wrote down; they're never shown to customers. Off, bike.tools stops reading them and deletes the ones it kept.

Disconnect (the owner, under Settings) stops bike.tools reaching Lightspeed, revokes its access, and deletes its copy of your Lightspeed data. Your bookings, services and settings stay, ready for when you reconnect. The privacy page lists everyone bike.tools shares data with.

Bike Archive

Bike Archive is the non-commercial bike database. bike.tools reads it through its API for every shop, free: the bike's name and specs, a link to its page and to its torque specs. Those go into the extension's bike picker and bike card, the workorder ticket page (torque specs, derailleur hanger and frame standards), Quick Book's drafts, and, with the Booking page, the bike search customers use when they book, the staff booking page and the booked workorder's internal note. bike.tools never shows or stores Bike Archive's images, and credits it as "Bike data from Bike Archive". Add-on subscriptions help fund it.

Email

bike.tools emails from no-reply@bike.tools: staff sign-in codes, "your shop is ready", and, with the Booking page, the customer's booking confirmation and cancellation. A customer replying to an email reaches your shop's address, not bike.tools.

Paying for add-ons

Add-ons are monthly subscriptions through Stripe, under Add-ons. The owner turns them on and off, pays by card in Stripe's checkout, and sees an overdue payment there. bike.tools never handles your customers' payments: they pay for the work in your shop, through Lightspeed. See Add-ons and pricing.

AI models

Instant quotes, AI Quick Book and its style guide can use AI models when they're turned on for bike.tools: open models that Cloudflare runs (Workers AI). They are kept on a short leash: they may only suggest services from your own menu, they never write to Lightspeed on their own, and what they send back is checked before it's used. If a model is slow, gives an answer that doesn't fit or is unavailable, another model takes over (the chat shows Trying another model), and if none answers the built-in parser drafts instead, so a check-in is never blocked. Without AI, the same features work with keyword matching.

Your website

A one-line snippet goes on your own site:

• The booking form (Settings → Share your booking page, with the Booking page): an iframe that sizes itself to the form, placed where you paste the tag. Or simply link to https://bike.tools/b/your-shop.

It runs inside a frame from bike.tools, so nothing on your site can read a booking, and nothing in it can touch your site.

Your own booking address

With Custom branding, serve your booking and status pages at an address like book.yourshop.com or status.yourshop.com. Under Settings → Your own booking address, add the hostname, create the DNS records it shows at your domain registrar, and press Check. Once verified, that address serves your customer pages; the admin stays on bike.tools. Existing links and your embed keep working. DNS changes can take up to an hour, and on Cloudflare the CNAME should be "DNS only" (grey cloud). Without Custom branding the card says Your own address comes with Custom branding., and an address you added stops serving your pages until it's back.

Where it runs

bike.tools runs on Cloudflare: the application, the database, photo storage and email are all there, close to Lightspeed's own servers. Pages are served over HTTPS only, and the design keeps the browser side small: every page works without JavaScript, and the little that runs is served from bike.tools itself.