Point of sale: Shopify, Square, Lightspeed, Ascend, Hike and Loyverse

If you run a point of sale, completed jobs, hire bookings and fittings flow into it so payment and reporting stay in one place, and your stock levels feed Velobook's Inventory. Seven connectors, one pattern.

Last updated 14 September 2026


Velobook pushes completed jobs into your point of sale so the sale lands where your reporting and payments live. Hire bookings and fittings travel the same road. Supported: Shopify, Square POS, Lightspeed (R-Series and X-Series), Ascend RMS, Hike and Loyverse. Money always settles directly to you.

Shopify

  • A completed job is pushed to Shopify as an Order, marked paid if the customer paid online, or pending so you collect at the counter.
  • Each new booking can also create a draft order the moment it lands, with the service and add-ons as line items, to charge at the till at pickup. Separate from the completed-job push: use either or both.
  • Add received stock to Shopify puts booked-in deliveries back on your Shopify counts, matched on SKU. Off until you turn it on, it only ever adds units, and a store with more than one location picks a receiving location first. Leave it off if your team already books deliveries in to Shopify by hand.
  • Shopify still owns the sale: its products, tax and reporting.
  • Payment taken at booking runs through your connected payment provider; Shopify receives the resulting order.
  • Install the Velobook app from the Shopify App Store, then manage the connection under Integrations → Payments & POS.
  • Hire bikes too? The same connection can build your hire catalogue from your Shopify products and put a booking widget on each product page. See hire from your Shopify product pages.

Lightspeed

On Lightspeed X-Series and Lightspeed R-Series alike, a completed job lands as a parked sale on the till, ready to open and ring up when the customer collects.

  1. 1In Integrations → Payments & POS, open the Lightspeed row for your series. X-Series asks for your store's domain (the bit before .retail.lightspeed.app); R-Series connects straight away. Approve on Lightspeed and you land back in Velobook.
  2. 2Pick where sales land: the outlet on X-Series, or the Shop, Register, Employee and Tax Category on R-Series. Pushes stay paused until this is done. R-Series also offers a Payment Type, only needed if you close sales paid in Velobook.
  3. 3Leave Dry-run mode on while you watch a few jobs go through, then turn it off.

Ascend RMS

A completed job is submitted as a websale to your Ascend location, and your Ascend stock feeds Velobook's Inventory. Connect from Integrations → Payments & POS.

Square

Marking a booking complete sends an open order to Square with the customer and service items filled in, and your till takes payment against it. Your Square item library and stock counts flow into Velobook.

  1. 1In Integrations → Payments & POS, open Square and choose Connect Square POS. Approve the permissions on Square and land back here.
  2. 2Pick a location. Every Square order is booked against one, so pushes stay paused until you choose. Any register at that location can pick the order up.
  3. 3Leave Dry-run mode on while you watch a few jobs go through, then turn it off.
Square POS is not Square card payments

Taking card payments through Square is a separate connection under Online payments. Connecting Square POS here does not switch card payments on, and disconnecting does not switch them off. See taking payments at booking.

Hike

  • The job pushes an unpaid invoice to your Hike register with the customer and service items pre-filled. Your till operator opens it when the customer arrives, adds anything extra, takes payment and finalises the sale
  • Choose when that happens, on the POS panel: when you mark the job complete (the default), or when the job reaches a stage such as *Ready for pickup*. Take payment on your own register and the second one is what you want, so the sale is waiting at the till before you finish the job rather than after
  • Your Hike catalogue and stock flow into Velobook
  • Choose Connect Hike; Hike's own screen picks the store. Then choose an outlet and a register. If an outlet has one register, Velobook pins it. Pushes stay paused until both are set
  • If you buy parts at a trade or member rate, point the connection at the Hike customer group that carries it, under Parts pricing on the Hike panel. Parts added from Hike then carry that group's price. Unset, a quote shows retail

Loyverse

Loyverse is the odd one out, and in a way that matters to your books: it has no held sale to ring up later. A finished job arrives as a completed, paid receipt under a payment type you choose, and your Loyverse stock feeds Velobook's Inventory.

  1. 1In Loyverse: Settings, then Access tokens, and add one. Copy it.
  2. 2In Integrations → Payments & POS, open Loyverse and paste the token. Velobook checks it with Loyverse before saving anything.
  3. 3Pick the store the receipts belong to, and the payment type they are recorded under. Pushes stay paused until both are set. If your account has one of each, Velobook pins them for you.
  4. 4Optional, and worth it if you ever finish a job before the customer pays: pick a second payment type for jobs not yet paid for. Most shops add one in Loyverse called On account. Leave it empty and those jobs go under the main type with a line on the receipt saying payment was not recorded.
  5. 5Leave Dry-run mode on while you watch a few jobs go through, then turn it off.
A Loyverse receipt counts as money already taken

Because the receipt arrives finished, the amount is on your Loyverse day the moment it lands. Do not ring the job up again when the customer collects. A job Velobook does not have as paid goes under your second payment type if you set one, so your takings stay honest. Many shops add a payment type in Loyverse called Velobook so these receipts sit apart from what the till took by card or cash.

A Loyverse access token has no permission settings

Loyverse issue one token per account and it carries full access, so the one you paste can read and write everything in that account. Velobook writes receipts, customers and the odd catalogue item, and reads your stock. Delete the token in Loyverse at any time and the connection stops.

The panel tells you if sales cannot push yet

Stock levels flow from Hike the moment you connect. If sales cannot be sent yet, the Hike panel says so and completed jobs are logged rather than sent until it clears.

Every connector starts in Dry-run mode

All seven connectors open in Dry-run mode: completed work is logged, nothing reaches your till. It never turns itself off; switch it off on the connector's panel when you are happy. Stock levels flow either way. Dry-run also holds back Shopify's received-stock sends.

Your stock feeds Inventory

Whichever POS you connect, its stock levels flow into Inventory. Velobook reads your stock and writes nothing back unless you ask; the one exception is Shopify's received-stock setting. Ascend shares stock levels only, not names or prices, so Ascend-sourced rows show their SKU rather than a product name.

No POS? You do not need one. Take card payments at booking through Stripe or Square, and keep your own stock counts in Inventory. See taking payments at booking and parts, stock and ordering.

Was this helpful?

Still stuck?

Email alex@velobook.app. A real person reads every message, usually within a few hours during Sydney business hours.

Cookies & storage

Velobook uses essential browser storage to keep you signed in, remember which shop you are working in, and route custom domains. With your permission, we also use Google Analytics to understand how people use Velobook. Advertising trackers are always off. Choose what is okay with you.

Read our privacy policy.