What comes across
Your catalogue and your takings
Loyverse's REST API gives BasilBook everything it needs from one personal access token.
Items and categories
Your Loyverse catalogue becomes BasilBook sale items under matching categories. Names are matched case-insensitively, so re-syncing updates the item rather than creating a second one.
Receipts
Each receipt becomes a sale with its lines, discounts and totals, keyed on the receipt number Loyverse issued — which is what makes a repeat sync harmless.
Employees
The person who rang the sale becomes a staff record, so you can see takings by cashier without maintaining a second list of names.
One store, on purpose
A Loyverse token can reach every store on your account. BasilBook asks you to pick one and syncs only that — because one workspace is one location, and mixing two stores' takings into one set of books is not something you can unpick later.
Setup
A token and a store
You need an owner or manager role in BasilBook, and admin access in Loyverse to mint a token.
- 1
Create a personal access token in Loyverse
Loyverse back office, under Integrations. Copy it once — Loyverse will not show it again.
- 2
Paste it into BasilBook
Settings, Integrations, Loyverse. The token is encrypted before it is stored and is never shown back to you in full.
- 3
Pick your store
BasilBook lists the stores the token can see. Choose the one this workspace is the books for. This is the step to get right.
- 4
Sync items, then receipts
Items first so receipts have something to attach to. Then choose a date range and import.
Then leave it alone
Pick a cadence and receipts arrive on their own. Each run re-reads the last three days rather than resuming from a bookmark, so a receipt amended after the fact is corrected instead of missed — and re-reading costs nothing, because a receipt already imported is skipped on its number. If the token is revoked, the schedule pauses itself after five failures and says so, rather than retrying every hour into a wall.
What it does to your books
Receipts become journal entries
Posted automatically as the receipts import, and balanced before they post.
Revenue and tax, separated
Sales revenue and tax payable go to their own accounts rather than a single lump, so your tax position is a number you can read instead of one you have to calculate.
The right cash account
Card takings debit the bank; cash and QR debit Cash on Hand and wait there until a deposit clears them. That waiting is deliberate — it is what makes the money you have and the money you banked two different, checkable numbers.
Stock and cost of sales
If you track stock, a sale moves it. Cost of sales posts against the sale under recipe costing, at your stock count under count costing, or on purchase under direct costing.
Questions
The things people ask first
I run three stores on one Loyverse account. What happens?
You create a BasilBook workspace per store and point each at its own Loyverse store. One access token can serve all three; the store you pick is what scopes the sync. Each location then has its own books, stock and reports, which is what you need for a per-location P&L.
Does BasilBook write anything back to Loyverse?
No. The integration reads only. Your catalogue, receipts and stock in Loyverse are untouched.
Will re-syncing duplicate my sales?
No. Receipts are matched on the number Loyverse gave them, so anything already imported is skipped. This is what lets automatic sync re-read the last three days on every run.
What if my items are already in BasilBook?
They are matched by name, case-insensitively, and updated rather than duplicated. Your menu prices stay yours — a delivery channel's marked-up price is stored per channel and never overwrites the counter price.
Is it included in the free plan?
No. Loyverse sync is Pro, at $39.99 a month or $399 a year per location, along with imports, payroll, invoicing and bank reconciliation.