Lispa Retail is the counter-first module stack for independent shops: barcode POS, FIFO stock lots, repair intake, customer CRM, held receipts, reporting and optional omnichannel webshop or wholesale — one catalog, transparent per-seat pricing, GDPR-aware EU hosting.
Sixteen capabilities owner-operators ask about before they switch POS — each grounded in the current Lispa backoffice, with honest notes where multi-store chain features are still evolving.
Search products by name, SKU or barcode scan. Complete sales, returns and exchanges with fewer clicks than legacy kassa bundles. Held receipts support pay-on-pickup and busy repair queues without losing the basket.
Book incoming purchase lots with cost price and received date; sales consume FIFO layers automatically with fallback handling if lot data is incomplete. Valuation reports show what is on hand and what it cost.
Record supplier deliveries against products and variants. Import supplier PDF invoices where supported to reduce manual line entry — especially valuable for phone and accessory distributors with high SKU churn.
Repair groups combine model landing pages, variant pricing and repair basket flows on the storefront. Service counters link online intake to in-store completion without a separate ticketing subscription.
Park open sales while customers fetch accessories or approve repair quotes. Held receipt lists give managers visibility into open counter work — the practical service-queue pattern repair shops use daily.
Generate barcodes for products and print shelf labels from ZPL-capable devices. Pair with USB scanners at the register for scan-to-add basket lines without touching the search field.
Each Lispa organization is one shop tenant today with storefront location blocks for public display (addresses, hours, maps). Running two legal entities or registers under one backoffice works; centralized multi-branch chain dashboards are roadmap — we document that clearly instead of overselling.
Customer records store contact details, invoice history, notes and repair context. Search from POS to recognize returning buyers; export lists for campaigns you run outside Lispa if needed.
Issue quotes and invoices from the same customer record as counter sales. Send payment links via Stripe, Mollie or Pay.nl connections configured per tenant — retail and service on one ledger.
Financial sales views, held receipt counts and stock movement history help owners answer daily performance questions without exporting to a BI tool. Reports respect staff permissions.
Export sales and invoice data for your accountant or external package. Lispa focuses on shop operations, not replacing localized general ledger rules — clean handoff is the goal.
Per-seat licensing with role-based permissions limits who can change prices, issue refunds or edit stock. Each active seat includes one signed-in device to reduce casual credential sharing at the counter.
Enable webshop module so public product pages and cart checkout share real-time stock with POS. Toggle per-product website visibility and feed export without duplicating the catalog.
Tenant APIs back the UI you see — suitable for scripted imports, internal integrations and connector projects. Start from CSV exports if you are not ready for custom code.
Settings → Hardware supports QZ Tray for USB receipt printers on workstations, direct network ESC/POS paths and ZPL label output. Test prints and QZ event logs speed up counter deployment.
Process customer and order data under GDPR with export tooling and EEA-oriented hosting. Security logs and subprocessors are documented for privacy reviews your lawyer actually asks for.
Early annual subscribers can qualify for assisted product, customer and opening-stock import. Typical sub-2,000 SKU catalogs go live in days when source files are clean.
A practical cutover path used by phone shops, accessory stores and general merchandise independents.
Request CSV or vendor export from your current POS. Include barcodes, variant labels, tax classes and category columns. Export customer emails and addresses if you use CRM at the register.
Sign up with the POS module (€59/register) and add the product module if you exceed fifty SKUs. Configure company, tax and receipt headers before importing data.
Migration service customers send files to our team for mapping. Self-serve tenants upload CSV and book opening stock lots with cost and quantity per SKU.
Run parallel test sales in Lispa while legacy POS still takes live card payments if needed. Train staff on held receipts for repairs and barcode scan add-to-basket.
Install QZ Tray where USB printers attach to workstations; configure network printers otherwise. Connect Stripe, Mollie or Pay.nl before accepting payment links or webshop orders.
Turn on webshop or appointment modules from Settings → Website after the counter is stable. Products already in the catalog appear on public channels with the same stock figures.
A candid side-by-side for owner-operators — not an enterprise feature matrix.
| Feature | Capability | Lispa Retail | Legacy kassa bundle | Spreadsheets + invoicing |
|---|---|---|---|---|
| Barcode counter speed | Fast search & scan | Varies by vendor | Manual lookup | |
| FIFO stock valuation | Built-in lots | Often add-on module | Not native | |
| Repair model pages | Service website module | Rare or third-party | Separate CMS | |
| Webshop stock sync | Same catalog | Extra license common | Double entry | |
| Per-seat pricing clarity | Published modular | Opaque bundles | N/A | |
| GDPR export tooling | Backoffice exports | Varies | Manual files | |
| QZ / label printing | Settings → Hardware | Vendor-specific | Not integrated | |
| Migration support | Documented service | Partner-dependent | Manual only |
Lispa Retail is the operational backbone for independent European shops that sell physical products and services at a counter: phone and device repair, fashion boutiques, tool merchants, food specialty counters, beauty retail with product walls, and wholesale distributors that still serve walk-in buyers. The stack begins at €59 per register per month on the POS base, with transparent per-seat fees as staff join. You are not buying an ERP implementation — you are buying daily workflows that respect how fast a Saturday queue moves.
This page documents retail capabilities honestly: what ships in the backoffice today, how FIFO stock and repair intake connect to optional webshop channels, and where multi-branch chain management is still evolving. For phone-specific repair examples, see our phone shop retail page. For module pricing, use the modular calculator. For assisted cutover, read the migration service offer.
The register is where Lispa earns trust. Counter staff search products by typing a few letters of a name, pasting a SKU, or scanning a barcode with a USB scanner. Basket lines adjust quantities, apply line discounts where permitted, and switch between customers when a held receipt parks an open sale. Returns and exchanges follow the same search patterns so trainees are productive on day one.
Held receipts are not a niche feature — they are how repair shops survive lunch-hour rushes. A customer approves a screen replacement quote but needs to fetch their wallet from the car; the sale waits in held state without losing line items or tax breakdown. Managers open the held receipt list to see open counter work and coach staff on queue discipline. Pay-on-pickup patterns for online orders map to the same held mechanism when you enable omnichannel flows.
Payment completion routes through providers you configure per tenant: Stripe, Mollie and Pay.nl patterns for card and local methods. Receipt headers and footers pull from Settings so legal entity names, return policies and thank-you lines print consistently. Receipt layout hints reference QZ Tray, direct network printing or browser print depending on hardware — there is no single proprietary terminal lock-in.
Role-based permissions restrict sensitive actions. Not every seasonal employee should issue refunds, edit cost prices or delete stock lots. Seat licensing bills per active user; each seat includes one signed-in device, which discourages shared passwords on a busy counter tablet. When a user signs in elsewhere, older sessions revoke — a practical control for shops worried about casual logout discipline.
Retail margin lives in stock accuracy. Lispa defaults to FIFO inventory method at the organization level (LIFO and average exist for tenants that need them, but FIFO is the retail standard we document first). Incoming stock is booked as lots with purchase price, supplier reference and received date. Sales consume oldest lots first; valuation reports show remaining quantity and carrying value per product.
Purchase booking screens tie deliveries to products and variants. For distributors receiving weekly supplier invoices, PDF import support reduces retyping when line items match catalog SKUs. When PDF parsing cannot match a line, staff map products manually once and future imports improve — the goal is fewer Sunday-night admin sessions, not magic OCR marketing.
Stock movements log adjustments, shrinkage corrections and transfers you record. Reorder settings on products can flag low quantities for buyers who still phone suppliers the old-fashioned way. Valuation views help owners answer “how much cash is sitting on shelves” before placing another accessory order — a question spreadsheets answer slowly and legacy POS systems often bury under accounting modules you never licensed.
FIFO honesty also means training: a sale without available lot quantity triggers fallback decrement logic with logged notes so stock does not silently invent negative layers. Shops migrating from average-cost systems should reconcile opening lots during migration week so first-month margin reports do not surprise the owner.
Phone repair and service retail is a first-class scenario, not a vertical afterthought. Repair groups combine public model pages, repair type variants (screen, battery, charging port) and repair basket behavior on the storefront. Customers select device model and repair type online; staff complete or adjust the sale at the counter with the same variant SKUs. Explore the phone shop page for sector-specific positioning.
We describe “work orders” the way independents actually work them: held receipts for in-progress jobs, appointment records for scheduled intake, and repair basket lines that survive from web to counter. There is no separate enterprise work-order license — the operational queue is held sales plus calendar visibility plus customer notes. If you need heavy factory routing with bill-of-materials explosion, ERP tools still win; if you need Saturday screen replacements done with barcode speed, Lispa wins.
Service websites (€20 module) publish repair SEO pages with FAQ blocks and model lookup paths. Appointment module (€40) adds slot booking constrained by opening hours. Combined, a repair shop can run intake online and settlement offline without Zapier chains between five SaaS logos.
Barcode workflows start at product creation: assign or generate barcodes, print shelf labels, scan at POS. Label printing targets ZPL-capable devices from Settings → Hardware; receipt printing supports ESC/POS via QZ Tray on workstations with USB printers or network paths where configured. Test print actions and recent QZ event logs help diagnose “printer worked yesterday” mysteries without waiting for Monday support queues.
QZ Tray is required only for local USB printer workflows on the workstation running it — cloud POS does not mean cloud printers magically discover themselves. Shops with networked receipt printers can use direct network printing when supported. We document this plainly because hardware frustration causes more POS churn than missing dashboard widgets.
Scanner hardware is standard USB keyboard-wedge scanners for most counters. No proprietary Lispa scanner purchase is required. Train staff to scan before typing — latency drops and queues calm down.
Retailers with more than one address ask about multi-location inventory and consolidated reporting. Today, each Lispa organization is one tenant with one stock pool and one backoffice. Storefront settings include a locations JSON block for public addresses, hours and map links — ideal for a repair chain showing Utrecht and Oosterhout on the website while operating one catalog.
If you operate legally separate stores that must not share stock quantities, you create separate Lispa organizations today. If you need centralized chain dashboards, buyer-level analytics across branches, and inter-store transfers in one UI, that is roadmap territory — we would rather document the gap than sell a checkbox that does not exist. Many phone shops with two counters in one legal entity run happily on one tenant with two registers (two POS seats).
Every sale can attach to a customer record with email, phone, address and notes. Invoice and quote documents share numbering rules you configure once. Payment links let staff collect remote deposits for special orders without a separate invoicing SaaS. Repair shops store device identifiers in notes; fashion boutiques store sizing preferences; distributors store VAT IDs for B2B walk-ins.
CRM depth is operational, not a marketing automation suite. You export customer lists when you run email campaigns elsewhere. Inside Lispa, search-at-counter is the killer feature — recognizing a returning buyer before they explain their last visit.
Owners open reporting for daily sales, held receipt counts and stock valuation — not board packs. Financial sales pages summarize performance managers compare week over week. Export paths hand data to accountants who still live in localized accounting packages; Lispa does not claim to replace your fiscal advisor’s chosen ledger for every EU country’s rule changes.
VAT display on receipts and invoices respects settings you maintain with professional advice. When governments change e-invoicing rules, we adapt export and document fields — retail POS stays aligned with compliance workflows without becoming compliance software itself.
Growing from owner-only to a five-person Saturday roster means adding seats, not renegotiating enterprise tiers. Permissions gate refunds, cost price visibility, stock adjustments and settings access. Seasonal workers get narrow roles; buyers get stock screens; managers get reporting. The per-seat model is predictable on an annual budget — unlike opaque “terminal counts” some legacy vendors use.
Retail does not end at the door. The webshop module (€50) exposes catalog products with cart checkout on your domain. Stock sync is real-time because it is the same table the counter decrements. Toggle Show on website per SKU when you want channel-specific assortments — repairs might be counter-only while accessories sell online.
Product feeds export items flagged for Google Merchant Center or Meta when marketing enables them. Wholesale portal (€80) serves trade buyers with login, customer-specific price lists and reorder carts — valuable for distributors who still run a public counter for walk-ins. See wholesale module and the TechSupply demo tenant for a live B2B combination.
Checkout modes include appointment-led flows (common in repair demos) and payment checkout with shipping rules, pickup toggles and MyParcel integration for parcel labels on webshop tenants. Abandoned-cart capture can be enabled to build recovery lists even before email automation ships.
Tenant APIs power the backoffice UI — scripted importers and internal tools can create products, book stock and read orders without clicking through wizards. If you are not ready for API projects, CSV import and scheduled exports still beat retyping. Payment integrations, feed exporters and DNS for custom domains sit alongside API access as part of a headless posture: your data remains operable outside any single screen.
Accounting integrations are intentionally export-first rather than pretending every EU accounting package shares one API standard. Sales exports and invoice CSVs feed your advisor’s workflow. Platform billing for Lispa subscriptions uses operator Pay.nl configuration separate from shop POS credentials — two payment contexts, clearly separated.
Switching POS is scary because catalog mistakes become visible customer-facing errors. Our migration service for early annual subscribers includes product and variant import, customer mapping, opening stock quantities and DNS cutover guidance. Typical catalogs under two thousand SKUs complete in three to five business days once clean source files arrive — not a quarter of downtime.
Self-serve migrations follow the same data discipline: barcodes, variant names, categories and tax codes in CSV columns. Repair shops should map model compatibility columns so public repair pages align with counter SKUs. Train held receipts and FIFO booking in the trial tenant before cutover Friday, not after Monday’s live queue.
Domain and email hosting are not bundled — you keep registrar relationships. We provide checklists for pointing shop domains at Lispa storefront settings. Email mailboxes stay where they are; only DNS records change for public URLs.
Before go-live weekend: install QZ Tray on workstations with USB receipt printers; configure network printers in Settings → Hardware; run test receipt and test label prints; pair USB barcode scanners; verify payment provider credentials in test mode; print a barcode sheet for top twenty SKUs so Saturday scans succeed. Recent QZ events should show successful prints — if not, fix hardware before inviting customers.
Support requests start at info@lispa.io with one-business-day response targets on weekdays. Help docs cover POS basics, FIFO booking and website channel toggles. Privacy and terms pages document processor roles, subprocessors and data subject rights — GDPR is operational reality for EU repair shops holding device identifiers and salons storing appointment history.
Data export tooling in the backoffice supports portability requests. Security logs back incident review. We host with EEA orientation where possible and document when subprocessors process outside the EEA with appropriate safeguards.
Choose Lispa Retail if you are an independent or small-chain EU shop that values counter speed, FIFO stock discipline, repair or service intake, and modular omnichannel growth. Choose something else if you need full manufacturing BOM routing, complex intercompany accounting, or centralized franchise analytics today — we will not oversell roadmap items as shipping features.
Ready to model cost? Open pricing, add POS seats and modules you actually need, and start a trial. Moving from MplusKassa, Lightspeed, spreadsheets or a legacy Dutch kassa? Mention migration on contact and attach a sample export so we confirm column mapping before you commit to cutover weekend.
Opening: staff sign in on two POS seats, review held receipts from Friday evening pickups, and scan opening cash totals against yesterday’s report. A courier delivers supplier cartons; the buyer books FIFO lots from the delivery note, attaching cost prices before shelves fill. Online appointment slots show three screen repairs at eleven — customers checked in from the appointment module overnight.
Mid-morning queue: walk-ins outnumber appointments. Barcode scans add tempered glass SKUs to baskets in seconds. A complex mail-in repair gets parked on held receipt while parts are reserved. A returning customer is recognized by phone number search; their prior battery replacement note prevents selling an incompatible pack.
Afternoon omnichannel: a webshop order for a case ships from the same stock figure the counter sees — no “e-commerce buffer” spreadsheet. A wholesale buyer logs into the trade portal for a reorder at their contracted price list while a floor associate sells the same SKU at retail walk-in price. Both transactions decrement the shared lot.
Closing: manager exports daily sales for the bookkeeper, reviews valuation on high-shrink accessories, and schedules Monday training on label reprints after a ZPL template tweak. That rhythm — fast counter, honest stock, optional channels — is what Lispa Retail optimizes for.
Phone and device repair combines repair model SEO, appointment intake, held receipts for in-progress jobs, and accessory upsell at checkout. See telefoonwinkel positioning for sector copy.
Fashion and footwear uses variant sizes and colours with barcode labels, seasonal staff seats, and returns handling at the register without waiting for a buyer to answer “did we still have a 42 in navy?”
Food specialty and deli counters mix weighed items typed as manual lines with barcoded packaged goods; FIFO matters when shelf life drives markdown decisions.
Tool and hardware merchants need supplier PDF import velocity and clear purchase history per SKU when negotiating next season’s assortment.
Beauty retail with services pairs appointment module bookings for treatments with POS product walls — one customer record whether they bought shampoo or booked colour.
Distributors with a public counter run wholesale portal for trade accounts and POS for walk-ins, sharing stock rather than maintaining parallel spreadsheets.
Cloud POS means backups and multi-device access are inherent — you sign in from the back office laptop after the counter tablet dies, not from a single PC under the till. That requires reliable internet; we document the cloud-first posture plainly rather than promising offline mode before it ships. Session revocation on new logins reduces casual credential sharing risk when seasonal staff rotate.
Tenant isolation keeps demo catalogs and production shops separate at the data layer. New signups do not inherit another tenant’s payment credentials, hardware profiles or GSM demo settings — a common failure mode in immature multi-tenant POS products we avoid by scoping organization settings per shop.
vs Lightspeed — Lispa prioritizes EU independents with repair workflows and included website modules rather than enterprise chain depth. vs MplusKassa — Lispa is cloud-first with SEO CMS and modular pricing without legacy server maintenance. vs Odoo POS — Lispa avoids ERP breadth you will never configure. vs spreadsheets — FIFO, barcodes and held receipts end the Sunday-night inventory arguments.
Detailed comparison pages live under Products → Compare in the marketing site; this retail page focuses on operational fit for your counter team.
Documentation under Help covers POS search, held receipts, FIFO booking and enabling website channels. Email info@lispa.io for onboarding, migration file format questions and hardware setup reviews. We respond within one business day on weekdays — enough for independents who cannot afford enterprise SLA contracts but still deserve a human answer before a busy weekend.
Retailers rarely sell one flat list. Lispa products support variants — size, colour, storage tier, repair type — each with its own SKU and barcode where needed. Categories organize reporting and public navigation when webshop modules are enabled. Channel toggles decide where a variant appears: counter-only repair labour, web-visible accessories, feed-exported hero SKUs for Google Shopping campaigns.
Import templates expect consistent variant columns during migration; messy legacy exports get cleaned once so Saturday barcode scans do not map to the wrong colour. Product images attach for webshop and feed presentation; repair groups can expose model imagery on service pages without maintaining a separate media library.
Reorder hints and low-stock signals help buyers who still phone suppliers on Monday mornings. They are not AI forecasts — they are practical thresholds you set per SKU based on lead time experience. Combined with FIFO valuation, you see both how many and what they cost before placing another carton order.
Returns at the register should be as fast as sales. Lispa ties return lines to original sale context where available, restores stock to appropriate lots when configured, and prints credit receipts with the same header discipline as sales. Exchange flows let staff swap sizes without forcing a manual return-plus-sale choreography that confuses trainees during January sales.
Customer trust improves when notes follow the buyer: a fashion client’s exchange history visible at search prevents arguing about prior purchases. Repair shops document device condition notes so repeat visits do not relitigate scratched frames. These CRM touches are small features with large queue-impact — they are part of why independents switch from anonymous receipt-only systems.
Seasonal peaks — Black Friday, back-to-school, holiday repair rushes — are when held receipts and barcode speed matter most. Lispa Retail is written for those Saturdays, not for demo-day screenshots alone.
When you are ready to compare vendors, read our Lightspeed, Shopify POS and EasyPOS alternative pages — honest matrices without inflated claims — then model your monthly stack on pricing.
Retail teams that outgrow a single location still operate one organization per shop in Lispa today — multi-location rollouts within one tenant are on the roadmap and documented plainly rather than oversold.
Start with POS from €59 per register, add website modules when omnichannel is ready, and use migration service if you are moving from legacy kassa exports.