LISPA.io

LISPA.io

Retail POS for every shop

Shop loginTake a lookStart free trial
Home

Run your phone repair counter without spreadsheet chaos

Model-aware POS, parts stock, repair tickets and online booking — one EU-hosted platform for independent telefoonwinkels and GSM repair chains.

Calculate your priceStart free trial

Built for phone repair workflows

From screen replacements to battery swaps — Lispa connects the counter, parts shelf and public repair pages.

📱

Repair model database

Publish SEO repair pages per device model. Customers find pricing before they walk in; staff pick the same model at the counter.

🔧

Repair tickets & baskets

Combine labour, parts and accessories on one receipt. Hold jobs for pay-on-pickup without losing track of the device.

📦

Parts stock tracking

Track screens, batteries and flex cables by SKU. FIFO lots help you value consumables and spot shrinkage early.

📅

Walk-in & online appointments

Opening hours drive public booking slots. Reduce queue chaos on Saturday mornings with scheduled drop-offs.

🧾

Invoices & warranty notes

Customer records store IMEI notes, warranty terms and repair history — ready for B2C disputes or supplier RMA.

🌐

Service website channel

Branded repair lookup, contact forms and analytics without a separate WordPress project.

💶

Modular per-seat pricing

Start with POS (€59/register). Add appointments (+€40) and service website (+€20) when you are ready.

Start with a repair-ready demo counter

Spin up Lispa with model pages, parts catalog and appointment booking. See how a telefoonwinkel runs counter, stock and website on one stack.

Start free trialCalculate your price

Why phone repair shops outgrow generic retail POS

Independent telefoonwinkels and GSM repair counters sell more than accessories. Every day you intake devices with unique faults, quote labour plus parts, wait for supplier deliveries and hand back phones with warranty obligations. Generic retail software treats each sale like a barcode scan. That works for cable packs, not for a queue of iPhone 13 screens waiting on back-ordered digitizers.

The operational pain shows up in small failures: a technician grabs the wrong screen because SKUs look identical in a spreadsheet; a customer calls about a repair you cannot find because the ticket lived on paper; Saturday walk-ins stack up while your website still says "call for appointment". Lightspeed and legacy Dutch kassa packages can be configured for repairs, but you pay in clicks, add-on modules and consultant hours. Odoo offers depth you will never use at a single storefront.

LISPA.io is counter-first retail SaaS with repair workflows included — model pages, basket composition, parts stock and optional online appointments on the same catalog your team already searches at the register. Data stays in the EU with GDPR-aware tooling, which matters when you store customer contact details and device identifiers.

Typical telefoonwinkel pain points

Model complexity and quoting speed

Apple, Samsung and budget brands each ship dozens of variants. A customer asks for a glass replacement; your counter staff must confirm the exact model, check parts availability, quote labour and possibly offer a tempered glass upsell — all while three people wait behind them. When pricing lives in memory or scattered PDFs, quotes become inconsistent and margins leak.

Parts inventory that is never quite accurate

Repair shops carry high-mix, low-quantity parts: screens, batteries, charging ports, flex cables. A single wrong pick wastes margin and delays the job. Without FIFO visibility you may ship older stock first or fail supplier RMA deadlines. Spreadsheets break the moment two staff book the same part for different jobs.

Appointment chaos and walk-in peaks

Many telefoonwinkels mix walk-ins with booked drop-offs. If online booking is a Calendly bolt-on, opening hours drift out of sync with the counter calendar. Double bookings and no-shows frustrate technicians who could have scheduled bench time for wholesale orders instead.

Website disconnected from the bench

Customers research repair prices online before visiting. If your public site is static WordPress while prices live in the backoffice, you update twice or publish stale numbers. SEO landing pages per city and model are tedious to maintain without a structured model database tied to sellable SKUs.

Warranty disputes and missing repair history

When a customer returns claiming a fault was pre-existing, your team needs intake notes, quoted lines and completion timestamps in one place. Paper tickets get lost; WhatsApp threads are not auditable. Structured customer records with device identifiers reduce chargebacks and speed up supplier warranty claims.

Supplier lead times and partial shipments

Parts vendors ship incomplete orders during busy seasons. Without purchase tracking tied to open jobs, you cannot tell which customers to call first when a screen arrives. Lispa purchase workflows book partial receipts into FIFO lots so costing and availability stay aligned with reality.

How Lispa fits the telefoonwinkel workflow

Morning: stock check and bench planning

Open the backoffice and review low-stock alerts on high-turnover parts — iPhone 11 displays, Samsung A-series batteries, USB-C ports. Purchase orders from yesterday are booked into FIFO lots so costing stays honest. The appointment calendar shows drop-offs for the next two hours; bench time is reserved before walk-ins arrive.

Midday: intake at the counter

A walk-in needs a battery replacement. Search the repair model database by name or browse the published tree that matches your website. Add the labour line and matching battery SKU; attach customer contact and IMEI notes. Issue a held receipt if they pay on pickup. Stock decrements immediately — no end-of-day sync job.

Afternoon: parts receiving and RMA

Supplier delivery arrives. Scan or select inbound lines against the purchase invoice; quantities flow into the correct lots. Defective parts flagged for RMA stay traceable to the original job and customer where needed.

Evening: online funnel

While the shop is closed, customers book slots via the appointment website module or browse model pages from the service website module. Tomorrow's calendar already reflects their choices because opening hours and services share one configuration.

Weekend peaks without counter meltdown

Saturday queues are predictable for phone shops. Publish repair turnaround times on model pages, cap appointment slots per hour and let walk-ins see honest wait expectations. Counter staff spend less time repeating prices and more time finishing jobs.

Modules that matter for phone repair

  • Lispa POS (€59/register/month) — counter sales, repair baskets, customer records, receipts and stock.
  • Product catalog module — when you exceed included manual lines; essential for parts-heavy shops.
  • Appointments (+€40/month) — public booking tied to store hours and team availability.
  • Service website (+€20/month) — repair model lookup pages, menus, FAQ blocks and contact flows.
  • Webshop (+€50/month) — optional if you sell accessories online with shared stock.

Compose your stack on the modular pricing calculator. Example: POS + products + appointments + service website fits many single-location telefoonwinkels without paying for wholesale or ERP modules you do not need.

Compared to legacy kassa and ERP sprawl

MplusKassa-style bundles often hide website and appointment features behind opaque module packs. Lightspeed excels at multi-location retail but treats repair model SEO as an integration project. Odoo can model anything, yet a GSM winkel rarely needs manufacturing or full accounting inside the POS. Lispa keeps the surface area small: run the counter, track parts, publish model pages, add channels when revenue justifies them.

Customer records that survive disputes

Repair is trust-heavy. Store structured notes — device condition at intake, quoted price, warranty window, photos referenced externally if you prefer. When a customer returns claiming "it worked yesterday", your team sees the original lines and timestamps without digging through messaging apps.

Multi-user counters and permissions

Each active seat covers one signed-in device. Technicians can sell and intake; managers approve discounts or view purchasing. Transparent per-seat billing beats surprise seat caps when you hire a part-time Saturday helper.

Reporting that owners actually open

Daily sales by category, parts margin snapshots and appointment conversion are available without exporting to Excel first. See which repair models drive revenue and which accessories attach best at checkout — useful when negotiating supplier terms.

Getting started

  1. Sign up and choose POS as your base on the trial page.
  2. Import your top fifty SKUs and repair labour lines — or start manual and expand.
  3. Enable the service website channel and publish your highest-traffic model pages.
  4. Turn on appointments when walk-in peaks justify scheduled drop-offs.

Pricing callout

Transparent modular pricing — no package-on-package. Lispa POS from €59 per register per month, invoicing from €39, service website from €20, appointments from €40, webshop from €50, and wholesale portal from €80. Domain and email hosting are excluded; DNS migration help is optional. Annual billing discounts apply for teams that want predictable costs. A typical telefoonwinkel stack — POS + products + appointments + service website — stays predictable month to month.

Build your exact monthly stack on the modular pricing calculator before you commit. Compare modules on the retail overview and add website channels only when revenue justifies them.

Explore Lispa for your shop

Independent retailers across the EU choose Lispa because the platform stays focused: counter speed, honest stock, optional website channels and GDPR-aware hosting without ERP bloat. Pair the service website with online appointments when your repair queue justifies scheduled drop-offs.

Questions about switching from legacy kassa software? Read the migration service offer for annual subscribers or contact us for a guided demo.

Bench operations and technician throughput

Repair throughput is the hidden KPI of a profitable telefoonwinkel. When intake staff quote accurately and parts are on the shelf, technicians spend more minutes fixing and fewer minutes hunting. Lispa repair tickets link the quoted model, parts lines and customer contact so the bench sees the same story the counter promised. Managers review open tickets by age to spot bottlenecks — waiting on parts, waiting on customer approval, or waiting on bench capacity.

Accessory attach rate matters as much as labour revenue. Tempered glass, cases and chargers should be one search away at pickup. Because accessories share the parts catalog, stock decrements stay honest when a tech grabs a screen protector during handoff. Promotions on high-margin attach SKUs can be tested per season without rebuilding your entire price list.

Public repair pages that convert research into visits

Most GSM customers compare three shops online before walking in. Structured model pages with clear service descriptions, turnaround expectations and links to appointment booking reduce phone calls asking the same questions. When prices change, update once in the backoffice — the public page and counter quote stay aligned. That alignment is harder when WordPress and kassa are separate projects maintained by different people.

Local SEO benefits from consistent page titles and meta descriptions per model family. Lispa service website pages expose those fields so you can target "screen replacement" queries without hiring an agency for every new iPhone launch. Combine with FAQ blocks tagged for retail and telefoonwinkel to surface sector-specific answers on industry landing pages.

Hardware, payments and counter reliability

Lispa runs in the browser on standard tablets, laptops or all-in-one touch screens — you are not locked to proprietary terminals with opaque lease contracts. Pair with your preferred payment terminal via supported providers in Settings → Payments. If the internet blips, your team should follow your documented offline policy; we recommend resilient connectivity for repair shops that promise same-day turnaround.

Migration from legacy GSM software

Moving from MplusKassa, Lightspeed or spreadsheet hybrids is easier when you import top SKUs and parts first, then model pages, then appointments. Our migration service helps early annual subscribers map products, customers and opening stock. Train staff on search and repair tickets before cutover weekend to avoid Monday chaos.

Why modular beats package-on-package

Traditional vendors bundle website, appointments and B2B into tiers you may not need yet. Lispa modular pricing lets you pay for POS first, then add the service website (€20), appointments (€40), webshop (€50) or wholesale portal (€80) when revenue justifies each fee. Review the modular pricing calculator with conservative assumptions — expand modules when customers actually use new channels.

EU hosting and GDPR-aware operations

Customer emails, order history and business contact data stay in EU-hosted infrastructure designed for GDPR responsibilities. Export tooling supports access requests; retention policies remain your responsibility as shop owner. For specialised or high-trust retail, that hosting story matters as much as feature checklists.

Counter speed as a competitive advantage

Independent shops compete with chains on service and speed, not ad budget. Lispa optimizes for fewer clicks at the register: search, basket, pay, next customer. Heavy ERP layers slow staff during Saturday peaks — the opposite of what a single-location owner needs when the queue reaches the door.

Product catalog growth path

Start with included manual lines for lean catalogs; enable the product module when SKU count grows. Import CSVs from legacy exports during migration. Barcode labels printed from the same records staff search at POS reduce mismatch between shelf and system.

Website channels are optional, not day-one requirements

Many successful shops run weeks on POS alone before publishing service pages or webshop categories. That sequencing keeps onboarding manageable. When you enable a website module, opening hours and product data reuse the same backoffice configuration — no duplicate admin across WordPress and kassa.

Payments and terminal flexibility

Connect payment providers from Settings → Payments per tenant policy. Lispa does not lock you to a single acquirer brand — choose what your accountant and bank already understand.

Migration and annual subscriber support

Switching systems is disruptive. The migration service supports early annual subscribers with catalog and customer import guidance. Plan cutover on a quiet weekday, not the busiest Saturday of the year.

Retail overview and sector pages

Compare how Lispa serves other verticals on the retail overview. Sector-specific FAQ tags on this page surface answers tuned to your industry alongside general retail documentation.

Talk to us before you over-buy modules

If you are unsure whether wholesale or webshop should come first, contact us with your revenue mix. We will recommend a minimal stack that matches how you actually sell today — you can enable more modules later without replatforming.

Frequently asked questions

Boutiques use variants for size and colour, label printing for seasonal collections, and fast counter search during Saturday peaks. Website modules publish lookbooks or grid layouts with Instagram-linked hero blocks. Stock thresholds flag replenishment before bestsellers vanish. Returns at register restock sellable pieces with audit linkage. FIFO optional for stores tracking consignment lots. Pricing stays modular — add webshop when ready without replacing POS core. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

© 2026 LISPA.io. All rights reserved.

info@lispa.io

Built for EU retail · GDPR-aware