Question 1

What is Lispa?

Accepted Answer

Lispa is a European cloud point-of-sale and backoffice platform built for independent retailers, repair shops and service businesses. You start with modular pricing — a POS register from €59 per workstation or invoicing from €39 — and add webshop, appointments, wholesale or a service website only when you need them. Stock, customers, receipts and optional online channels share one tenant, so your team works from a single source of truth instead of juggling separate tools. Data is hosted in the EU with GDPR-aware defaults, export and audit trails. Lispa targets shops that want counter speed without ERP complexity.

Question 2

Who is Lispa designed for?

Accepted Answer

Lispa suits phone and electronics repair counters, fashion and specialty retail, freelancers who invoice services, and appointment-led businesses such as salons or clinics. The platform supports repair workflows with basket lines, variants and model pages, while general retail gets fast search, barcode scanning and label printing. You can run a single register or several workstations with role-based permissions. Optional modules add a branded website, online booking, B2B wholesale pricing and payment links. If you outgrew spreadsheets but do not want a multi-year ERP rollout, Lispa is sized for your scale.

Question 3

Is Lispa cloud-based or on-premise?

Accepted Answer

Lispa is cloud-first: you sign in from any modern browser on counter PCs, tablets or laptops without maintaining a local server. Updates, backups and security patches are handled on the platform side, so your shop stays current without weekend maintenance windows. A stable internet connection is required for live sales, stock sync and tenant payment webhooks from Stripe or Mollie. Registers can use locally connected receipt and label printers via the hardware settings screen. Offline sales mode is on the roadmap; today we recommend a reliable connection with a mobile backup hotspot for continuity.

Question 4

Where is Lispa data hosted?

Accepted Answer

Lispa stores tenant data in European Economic Area infrastructure with GDPR-by-design practices: purpose limitation, data minimisation and documented subprocessors. Customer records, invoices, stock movements and website content remain inside your organisation tenant with role-based access. You can export customer and transaction data for portability requests or accountant handoffs. Backups and encryption at rest protect against hardware failure without exposing data to non-EU regions by default. For shops subject to Dutch or broader EU retail regulation, hosting location and auditability are first-class concerns, not afterthoughts.

Question 5

What modules can I add to Lispa?

Accepted Answer

Every tenant picks a base: POS workstations at €59 each or invoicing at €39. Up to fifty products or manually typed sale lines are included; larger catalogues add the product module. Optional website modules include webshop (€50), appointment booking (€40), wholesale portal (€80) and a simple service site for freelancers (€20). WhatsApp chat button, label printing and FIFO stock valuation are toggled per tenant. Compose only what you use — no opaque bundle like legacy kassa packages. Your monthly preview in the backoffice shows line items before you commit.

Question 6

Can I try Lispa before subscribing?

Accepted Answer

Yes. Lispa provides demo tenants that mirror real shop configurations — including repair list pages, POS counters and sample stock — so you can click through workflows without entering card details. Book a walkthrough via the contact form if you want a guided tour of repair baskets, FIFO lots or wholesale price lists. Demo data resets periodically; do not treat it as production storage. When you are ready, provisioning creates an isolated organisation with your chosen modules and Stripe or Mollie payment keys under your control.

Question 7

How do I get help with Lispa?

Accepted Answer

Documentation lives on lispa.io under Help, covering POS, invoicing, website CMS, appointments and hardware setup. In-product guidance points to settings paths such as Hardware for printers or Website for SEO pages. For billing, module changes or migration from MplusKassa, Lightspeed or spreadsheets, use the contact form and include your current product count and channels. Critical counter issues during opening hours are prioritised. Community tips and release notes highlight new features like feed exports or appointment inbox improvements each sprint. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 8

Does Lispa support multiple shop locations?

Accepted Answer

Each Lispa organisation represents one trading entity with one or more POS workstations counted per register. Stock, customers and website channels are shared inside that tenant, which suits a single storefront with multiple counters or a back office plus front desk. If you operate legally separate branches with isolated stock, you typically provision separate organisations and link them operationally through exports or accountant tools. Workstation seats scale linearly at €59 per active register. Central reporting rolls up sales, stock valuation and appointment volume for the tenant without per-location surprise fees.

Question 9

Which languages does Lispa support?

Accepted Answer

The marketing site and backoffice support Dutch and English locales today, with public shop pages able to follow your chosen customer-facing language. Product titles, repair model descriptions and CMS pages are authored by you, so bilingual shops can maintain parallel content where needed. Receipts and invoices respect your organisation language settings and EU number formatting. Additional locale packs are planned based on customer demand in Belgium, Germany and France. Interface labels update without redeploying your shop theme, keeping operational training consistent across staff who prefer Dutch or English.

Question 10

How does Lispa secure my shop data?

Accepted Answer

Authentication uses industry-standard sessions with role-based permissions separating owners, managers and counter staff. Payment credentials for Stripe or Mollie are stored per tenant and never shared across organisations. API access for storefront checkout and appointment forms is scoped to public shop slugs without exposing backoffice keys. Activity around invoices, stock adjustments and GDPR exports is traceable for internal audit. Infrastructure providers are vetted for SOC-aligned practices. You control which staff see customer phone numbers, wholesale rates and cost prices through capability flags tied to each user seat.

Question 11

How are Lispa updates rolled out?

Accepted Answer

Lispa ships continuous cloud updates without manual installer runs on counter machines. Features such as FIFO stock, new marketing blocks or appointment inbox filters appear tenant-wide once deployed, usually with prior notice in release notes. Breaking changes are avoided for live trading hours; maintenance windows are rare and communicated. Your bookmarks and hardware printer mappings persist across updates. Demo tenants receive the same build as production so evaluations match reality. If a module you do not use changes, your enabled capabilities remain stable because pricing is tied to explicit flags, not hidden bundle versions.

Question 12

What integrations does Lispa offer?

Accepted Answer

Tenant checkout connects to Stripe and Mollie for cards, iDEAL and common EU methods, with webhooks updating invoice and order status automatically. Website modules can emit product feeds for Google Merchant Center and Meta catalog ads. Google Analytics and Search Console verification fields are built into website settings. Hardware integrates ESC/POS receipt printers and ZPL label printers from the backoffice. Accounting exports support CSV handoff to your bookkeeper. Marketplace connectors such as Bol or Channable are on the omnichannel roadmap alongside deeper repair-model import from legacy WordPress catalogues.

Question 13

How long does Lispa onboarding take?

Accepted Answer

A lean retail shop with under fifty products can run same-week: create the tenant, add products, connect a printer and sell at the counter. Repair shops importing model lists from spreadsheets or WordPress may take one to two weeks to clean titles, map variants and publish SEO pages. Website plus appointments adds DNS pointing and opening-hours configuration — often a single afternoon once content is ready. Wholesale portals need customer approvals and tiered price lists prepared upfront. Lispa onboarding is lighter than ERP projects because you enable modules incrementally instead of configuring unused departments.

Question 14

How transparent is the Lispa product roadmap?

Accepted Answer

Public roadmap sections on lispa.io summarise omnichannel feeds, offline-tolerant POS and deeper marketplace adapters without promising fixed dates. Features ship when API, backoffice and storefront surfaces are coherent — repair workflows and FIFO stock landed before broad ERP connectors by design. Customers influence priority through contact themes: migration pain, appointment no-shows, wholesale login flows. Deprecated paths are avoided; Stripe Checkout Sessions and modern Mollie APIs are preferred over legacy integrations. Your modular subscription only expands when you toggle new capabilities, so roadmap experiments do not inflate your bill silently.

Question 15

How does Lispa modular pricing work?

Accepted Answer

You compose a monthly stack instead of buying a monolithic package. Base choices are €59 per POS workstation or €39 for invoicing-only freelancers. Catalogues beyond fifty SKUs add €20. Website modules are priced separately: webshop €50, appointments €40, wholesale €80, service site €20, WhatsApp button €10. The backoffice pricing preview totals each line before checkout. Annual billing may include a discount percentage shown at signup. There are no hidden seat caps inside a module — you pay for registers and features you explicitly enable, unlike opaque legacy kassa bundles.

Question 16

What does a POS workstation cost?

Accepted Answer

Each active register is €59 per month, covering counter sales, returns, customer lookup, receipt printing and stock movements for that workstation. Additional registers add another €59 line — transparent and linear. The price includes backoffice access for configured staff roles; you do not pay per manager separately. Invoicing, webshop and wholesale modules are additive if enabled. Compared with competitors that bundle website or appointments as expensive add-ons, Lispa keeps register pricing focused on counter operations so small shops can start with one seat and scale seasonally.

Question 17

What is included in the €39 invoicing base?

Accepted Answer

The invoicing base targets freelancers and service businesses that need professional invoices, payment links and customer records without a full POS counter. Create line items from services or manual descriptions, send Stripe or Mollie payment links, and track paid status from webhooks. Up to fifty products or typed lines are included; larger catalogues add the product module. You can later enable POS registers or a service website without migrating to a different product. EU VAT-friendly fields and PDF exports support accountant workflows without ERP overhead.

Question 18

How much do website modules cost?

Accepted Answer

Webshop capability is €50 monthly, synchronising visible products and checkout with tenant payments. Appointment websites are €40, including public booking and a backoffice inbox tied to opening hours. Wholesale portal access is €80, covering login-gated B2B price lists and approval flows. A lightweight service website for freelancers is €20 with services, contact and quote sections. Combining modules follows additive pricing — for example POS plus webshop plus appointments — with conflicts surfaced in the preview if incompatible toggles are selected. Domain and email hosting remain your choice and are billed outside Lispa.

Question 19

Is annual billing cheaper than monthly?

Accepted Answer

Lispa offers annual intervals with a published discount percentage applied to the modular total shown in your pricing preview. Annual checkout charges once per year while monthly bills each calendar month. Module changes prorate according to platform billing rules displayed at confirmation time. Shops with stable register counts often choose annual for predictable operations budgeting. You can switch intervals during renewal conversations with support; mid-cycle changes show clearly in the ops billing view before you confirm. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 20

Are there hidden fees in Lispa pricing?

Accepted Answer

Lispa does not use surprise seat limits inside enabled modules or charge extra for basic receipt printing configuration. Payment processing fees come from Stripe or Mollie under your own merchant agreements, not Lispa markups. Domain registration, email hosting and DNS assistance are excluded and optional. SMS reminders or third-party shipping labels, when used, bill through those providers. Your subscription line items match the module catalog keys in the backoffice — if a feature is not listed on your invoice, you are not paying for it.

Question 21

How does Lispa pricing compare to Lightspeed?

Accepted Answer

Lightspeed often layers e-commerce, appointments and marketing feeds as separate subscriptions with higher entry tiers. Lispa charges €59 per register with website modules priced explicitly — webshop, appointments and wholesale — so you see the total before signup. Repair-centric workflows and EU hosting are included in the platform scope rather than partner marketplaces. Independent shops frequently pay for Lightspeed modules they never open; Lispa modular pricing lets you defer webshop until you publish online. Total cost depends on registers and modules enabled, not opaque package names.

Question 22

How does Lispa compare to MplusKassa pricing?

Accepted Answer

MplusKassa historically bundles modules and hardware leases in ways that are hard to compare month to month. Lispa lists €59 registers and optional digital modules with euro amounts on the marketing site and in your tenant preview. Cloud delivery removes local server maintenance contracts. Website, SEO pages and appointment booking are native rather than third-party plugins with separate licences. Migration customers often start with POS only, prove counter speed, then add webshop when feed exports matter — controlling spend at each step.

Question 23

When do I need the product catalog module?

Accepted Answer

Up to fifty products or manually entered sale lines are included in base POS or invoicing. Crossing that threshold with structured SKUs, variants, barcodes and stock tracking typically requires enabling the product catalog module at €20 monthly. Repair shops with long model lists often enable it early for FIFO lots and label printing. Seasonal pop-ups under fifty items may never need it. The backoffice warns as you approach limits so you can archive discontinued models or upgrade before counter search degrades.

Question 24

Why is the wholesale module priced higher?

Accepted Answer

Wholesale at €80 reflects B2B complexity: authenticated accounts, tiered price lists, approval queues and separated visibility from consumer webshop prices. Consumer checkout stays simple while trade buyers see net rates after login. Support and testing surface area is larger than a brochure website. The module pairs with stock and invoicing so pick lists and tax lines remain consistent across channels. Retailers migrating from email-based trade orders gain self-service reordering without building a custom portal. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 25

Who pays Stripe and Mollie transaction fees?

Accepted Answer

You connect your own Stripe or Mollie account to your Lispa tenant. Card, iDEAL and wallet fees follow those providers' European pricing tables and settle to your merchant balance. Lispa subscription fees are separate from payment processing. Webhooks update paid invoices and webshop orders inside your backoffice for reconciliation. This model keeps you in control of payout timing and dispute handling while Lispa focuses on POS, stock and website workflows rather than acting as a payment intermediary. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 26

Does Lispa POS support barcode scanning?

Accepted Answer

Yes. Counter staff scan EAN and custom barcodes into the sale search field to add line items instantly. Products store barcode values in the catalogue so label printing and scanning stay aligned. USB and Bluetooth scanners that emulate keyboard input work without proprietary drivers on supported browsers. Repair SKUs and variant barcodes resolve to the correct model and price tier. If a code is unknown, staff can fall back to text search by name or repair model identifier without leaving the sale screen, keeping queues moving during busy Saturday trade.

Question 27

How do repair baskets work in Lispa POS?

Accepted Answer

Repair shops add devices or jobs to a basket with variant attributes such as model, colour and repair type. Line items can mix parts, labour and deposits in one receipt. Staff park baskets while waiting for customer approval or parts delivery, then recall them for payment on pickup. Linked appointment records show when the customer expects collection. Model metadata feeds website repair list pages when published. The workflow avoids generic retail carts that lack service context, so technicians see the exact phone and fault description at the counter every time.

Question 28

How are returns and refunds handled?

Accepted Answer

Staff locate the original sale or invoice, select lines to return, and choose refund method matching how the customer paid — cash, card or store credit policies you define operationally. Stock increments return quantities into the appropriate warehouse bucket when items are resellable. Partial returns keep audit linkage to the parent receipt for accounting. Stripe and Mollie refunds initiate from the payment record where supported, with status reflected after webhook confirmation. Manager roles can restrict void windows to reduce end-of-day discrepancies while still protecting legitimate warranty cases.

Question 29

Can I park sales and finish them later?

Accepted Answer

Held receipts let you suspend a basket while the customer fetches cash, approves a repair quote or steps out briefly. The sale retains line items, discounts and customer attachment under a visible hold queue per workstation. Recalling a hold restores context without re-scanning barcodes. Holds expire based on shop policy you communicate to staff. This pattern is essential for repair counters where diagnosis finishes before pricing. Night closing reports separate completed sales from open holds so cash reconciliation stays honest.

Question 30

How fast is customer lookup at the counter?

Accepted Answer

Search matches name, phone, email and customer numbers with keyboard-first navigation for busy queues. Recent customers surface for repeat repair visitors. Attaching a customer to a sale pre-fills invoice delivery and warranty notes. GDPR consent flags display where you track marketing opt-in. Creating a minimal record takes seconds when a walk-in buys accessories only. Deep history — prior receipts, open invoices and appointment bookings — opens in a side panel without abandoning the active sale, reducing average handle time versus legacy kassa scroll screens.

Question 31

What are quick service buttons?

Accepted Answer

Quick service buttons pin high-frequency labour lines or flat-rate repairs to the POS home grid. Phone shops might expose screen replacement, battery swap and diagnostic fees as one-tap rows that still map to revenue accounts. Limits scale with tenant capabilities so starter configs stay uncluttered. Managers arrange buttons per workstation role. Combined with repair model search, technicians spend less time drilling categories. Buttons respect tax settings and can prompt for mandatory notes when insurance documentation requires IMEI capture. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 32

How do staff roles work on POS?

Accepted Answer

Owners configure users with roles that gate refunds, cost price visibility, stock adjustments and settings access. Counter staff sell and print; managers approve discounts and edit catalogue rows. Permissions apply across browsers — not per device licence files. Session timeout policies reduce risk on shared tablets. Audit views show who changed prices or voided receipts when disputes arise. Adding a colleague does not require a separate backoffice SKU beyond your operational decision to share credentials responsibly. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 33

How do I print receipts from Lispa POS?

Accepted Answer

Connect an ESC/POS compatible USB or network receipt printer in Settings → Hardware, then test print from the same screen. Completed sales offer automatic print with shop logo and footer text you configure once. Reprints require appropriate role rights to prevent duplicate fiscal confusion where local rules apply. Email receipt delivery complements paper where customers prefer digital. Printer mappings persist per organisation so replacing hardware reuses the same logical device name across workstations after a quick remap. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 34

What end-of-day reports does POS provide?

Accepted Answer

Daily summaries aggregate gross sales, returns, payment method breakdowns and tax lines per register. Stock movement reports highlight shrink-sensitive categories when FIFO is enabled. Export CSV for your bookkeeper or import into accounting tools on your schedule. Appointment conversion metrics appear when the module is active, linking booked slots to collected deposits. Reports respect organisation timezone boundaries so late Sunday sales do not spill into Monday incorrectly. Managers can compare workstation totals to identify training gaps or tender mistakes before banking cash.

Question 35

Does Lispa support pay-on-pickup for repairs?

Accepted Answer

Yes. Technicians complete repair lines, park the basket or mark awaiting payment, and notify the customer when ready. At pickup, staff recall the job, verify identity, and settle by card, cash or pre-authorised link sent via invoice module. Stock parts consumed during repair decrement at the right FIFO layer when enabled. Website appointment customers see consistent status messaging if you publish pickup instructions online. Pay-on-pickup reduces premature charges before quality checks, a common expectation in phone repair where post-test failures would otherwise trigger refunds.

Question 36

How do discounts work at the counter?

Accepted Answer

Line and basket discounts support percentage or fixed amounts with optional manager approval thresholds. Campaign pricing can stem from wholesale tiers when a logged-in B2B buyer purchases at the register using their account. Repair bundles combine part and labour components without losing margin visibility on cost fields restricted to managers. Receipts show discount reasons for audit. Unlike coupon plugins bolted onto web-only platforms, Lispa keeps promotion logic inside the same sale object used for stock and revenue recognition. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 37

How does Lispa handle product variants?

Accepted Answer

Variants capture size, colour, storage capacity or repair grade under a parent model with distinct SKUs, barcodes and prices. Search resolves either parent or child codes. Stock tracks per variant with optional FIFO lots for parts with expiry or batch traceability. Website list pages can expose variant selectors when published online. Repair catalogues benefit when the same screen glass fits multiple chassis listings — staff pick the precise variant without maintaining duplicate flat SKUs that confuse reporting. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 38

Can Lispa open a cash drawer?

Accepted Answer

When your receipt printer exposes a cash drawer kick pulse via ESC/POS, completing a cash tender can trigger the drawer open command configured in hardware settings. Mixed tenders record cash and card components separately on the receipt. End-of-day cash counts compare expected cash sales plus opening float against physical drawer totals. If you are card-only, disable cash methods to simplify reporting. Drawer wiring varies by manufacturer; test after setup to confirm pin mapping matches your printer documentation. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 39

Are there keyboard shortcuts for POS speed?

Accepted Answer

Power users navigate sales with keyboard shortcuts for search focus, quantity edits, payment screen and receipt print confirmation. Fewer mouse trips mean faster queues at lunch peaks. Shortcuts are documented in Help for Dutch and English layouts. Touchscreen counters still expose large tap targets for hybrid use. Training new staff starts with mouse flows, then introduces shortcuts once muscle memory develops — a pattern repair shops prefer when gloves or tools make mouse use awkward. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 40

How do I create an invoice in Lispa?

Accepted Answer

From the invoicing backoffice, start a new invoice, add customer details, and insert service lines from your catalogue or free-text descriptions. Taxes and currency default to EUR with EU-friendly VAT fields. Save drafts, send PDF links, or generate Stripe and Mollie payment URLs that mark paid status automatically via webhooks. Recurring service businesses duplicate prior month templates to save time. Invoices link to customers for history and GDPR export. Freelancers without a POS register use this base at €39 monthly before adding optional websites.

Question 41

How do Lispa payment links work?

Accepted Answer

Each invoice can expose a secure payment link backed by your tenant Stripe or Mollie configuration. Customers pay by card, iDEAL or supported wallets without staff present. Webhooks update invoice status to paid and store provider references for reconciliation. Partial payments can be policy-restricted depending on your settings. Links expire or remain active based on operational rules you communicate externally. Repair shops use links for deposits before ordering parts, reducing no-shows while keeping card data off your own servers through provider-hosted checkout pages.

Question 42

Should I use invoicing or POS?

Accepted Answer

Choose invoicing at €39 when you bill projects or services without a physical till — consultants, mobile technicians or appointment-only studios. Choose POS registers at €59 when you need fast counter sales, cash/card tenders, receipt printers and live stock decrement. Many shops enable both: POS for walk-in accessories and invoicing for B2B net terms. Modules stack in one tenant with shared customers. Migration from spreadsheet invoicing is fastest on the invoice base; add POS when you open a retail front.

Question 43

How does Lispa handle VAT on invoices?

Accepted Answer

Line items store VAT rates appropriate to EU services and goods with totals calculated per line and summarised on PDF exports. Customer VAT IDs can be captured for B2B reverse-charge scenarios you validate with your accountant. Reports aggregate tax buckets for filing periods. POS and invoicing share tax configuration to avoid mismatches between counter and monthly billing. Lispa does not file taxes on your behalf; exports give your bookkeeper structured CSV aligned with Dutch and broader European conventions. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 44

Can I issue credit notes?

Accepted Answer

Credit notes reference original invoices, reversing all or partial amounts with audit linkage. Stock-return flows may companion a credit when goods come back sellable. PDFs and payment provider refunds align where card settlements apply. Managers control who can issue credits to prevent misuse. Accountants receive traceable numbering sequences separate from new sales invoices. This complements POS returns for cases where the buyer is an invoiced business customer rather than a walk-in receipt. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 45

How do I remind customers about unpaid invoices?

Accepted Answer

Filter open invoices by age and send reminder emails with the existing payment link attached. Staff add notes when a customer promises payment Friday. Dunning intensity stays under your commercial judgment — Lispa provides visibility, not aggressive collections automation. Pair reminders with WhatsApp module buttons on your service site for informal nudges where appropriate. Webhook-paid invoices drop off open lists automatically so staff do not embarrass customers who paid overnight via iDEAL. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 46

Does Lispa support recurring service billing?

Accepted Answer

Service businesses duplicate prior invoices or maintain template line sets for monthly retainers. Automatic subscription engines are roadmap items; today workflow efficiency comes from copy-forward and stable customer records. Appointment-led studios bill after sessions using appointment inbox references in invoice notes. Integrate external subscription tools via exported customer lists if you need provider-grade dunning before native recurrence ships. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales. Contact Lispa support through lispa.io if your scenario mixes modules and you want a pricing preview before migration weekend.

Question 47

Can I brand invoice PDFs?

Accepted Answer

Organisation settings store trading name, address, logo and footer payment instructions reflected on PDFs and customer emails. Consistent branding matches your website module when enabled. Multi-language footers follow your locale choice. Test PDFs before sending large batches to wholesale clients. Brand fields also appear on receipts when shared logo assets are configured, giving a coherent identity from counter to accounts receivable without separate design tools. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 48

Can I invoice on net payment terms?

Accepted Answer

Create invoices with future due dates and net-thirty language in notes while status remains open until webhook or manual settlement. Wholesale buyers accustomed to monthly statements appreciate stable numbering and PDF archives. Pair with wholesale portal visibility so buyers reconcile against their order history. Credit risk policies remain yours; Lispa tracks exposure via open balances per customer without acting as a credit agency. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 49

What website CMS features does Lispa include?

Accepted Answer

Manage pages, navigation menus, hero sections and SEO metadata inside the backoffice without WordPress plugins. Publish repair model lists, product grids or service descriptions with clean URLs for search indexing. Connect Google Analytics and Search Console verification tags in settings. Product feeds export to Google Merchant Center and Meta when webshop modules are active. Content changes deploy to your public shop slug without redeploying separate hosting stacks, keeping brand and stock aligned from one tenant. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 50

How does webshop checkout work?

Accepted Answer

Customers browse published products filtered by channel visibility flags set in POS. Cart checkout uses your tenant Stripe or Mollie keys with methods you enable — cards, iDEAL and common EU wallets. Paid orders create backoffice records staff fulfil from the same stock pool counters use. Appointment-only shops can disable payment checkout while still listing services. Shipping and pickup rules are communicated on pages you edit; carrier API depth expands on the omnichannel roadmap alongside label integrations. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 51

How does Lispa help with SEO?

Accepted Answer

Each page exposes title, meta description, canonical slug and structured content blocks tuned for repair and retail keywords you choose. Automatic sitemaps and sensible heading hierarchy support crawling without manual developer tickets. Comparison landing pages on lispa.io demonstrate positioning; your shop pages focus on local intent like model repairs or boutique collections. Feed exports reinforce product discovery on Google Shopping when SKUs sync from POS. Avoid duplicate slugs and keep titles unique per variant page for best results. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 52

What are repair list pages?

Accepted Answer

Repair list pages present mobile-friendly model directories — battery, screen or data recovery services — sourced from POS catalogue metadata. Customers tap a model, see indicative pricing or book appointments depending on modules enabled. The layout references modern phone shop UX rather than dense ecommerce grids ill-suited to small screens. Publishing toggles per model prevent advertising repairs you temporarily cannot source parts for. Lists update when stock or pricing changes in backoffice without nightly batch jobs. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 53

How do I connect my own domain?

Accepted Answer

Point DNS A or CNAME records to Lispa storefront hosting as documented in website settings. TLS certificates provision automatically once DNS propagates. Email hosting is not included; keep mail at your existing provider. Optional paid assistance helps migrate DNS without downtime scares. Subdomain defaults let you preview before cutover. Wholesale and consumer sites can share one domain with path-based slugs when branding should stay unified under your apex hostname. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 54

Does Lispa export Google Merchant feeds?

Accepted Answer

Webshop-enabled tenants generate product feeds compatible with Google Merchant Center from visible SKUs, prices and stock status. Updates reflect catalogue changes without manual CSV wrangling each Monday. Pair with Search Console to monitor indexing issues. Meta catalog feeds follow similar rules for retargeting ads. Feed fields respect channel visibility so wholesale-only SKUs stay excluded from consumer surfaces. Image URLs come from product media you attach in POS for consistent presentation. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 55

Can I customise website navigation?

Accepted Answer

Build header and footer menus linking to CMS pages, repair categories, contact and external social profiles. Drag sort order matches how you merchandise services — appointments prominent for studios, shop grid for boutiques. Multi-language labels appear when you maintain translated page titles. Menu changes publish instantly without developer deploys. Keep depth shallow on mobile so repair customers reach booking in two taps, mirroring best-performing reference layouts from migrated WordPress shops. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 56

What does the WhatsApp module add?

Accepted Answer

For €10 monthly, display a floating WhatsApp chat button on public pages with your business number. Customers ask stock or appointment questions informally while you still track structured bookings through the appointments module when needed. Button styling respects theme colours configured in website settings. It complements payment links for quick human conversations about repair quotes without exposing personal staff numbers if you use a shop line. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 57

What is the freelancer service website?

Accepted Answer

At €20 monthly, publish a lightweight site describing services, coverage area, testimonials and contact forms without full webshop complexity. Ideal for invoicing-base customers who need credibility beyond PDF quotes. Upgrade path adds appointments or POS later in the same tenant. SEO fields mirror larger website modules so local service searches find your business. Content blocks stay manageable so solo operators update season offers without agency retainers. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 58

Can I customise my shop theme?

Accepted Answer

Adjust colours, typography accents, list versus grid catalogue layout and border radius to match brand guidelines within supported theme tokens. Repair shops often choose list layout for readability on phones; fashion boutiques may prefer visual grids. Preview changes before publishing. Heavy custom CSS is intentionally limited to preserve performance and accessibility. Logo upload and hero imagery communicate professionalism equivalent to bespoke WordPress themes without separate hosting bills. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 59

What marketing blocks can I add to pages?

Accepted Answer

Compose landing pages with hero banners, feature grids, stats bars, testimonial rows, comparison tables, logo clouds and CTA sections exported from Lispa marketing patterns. Blocks speed seasonal campaigns — back-to-school repairs or holiday boutique collections — without writing HTML. Each block exposes titles, items and links editable in backoffice forms. Structured data for FAQs can render when you maintain published FAQ entries tagged for website surfaces. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 60

How do I migrate from MplusKassa?

Accepted Answer

Export products, customers and open stock figures from MplusKassa via CSV or vendor reports your partner provides. Map columns to Lispa import templates focusing on barcodes, VAT rates and variant titles. Run a parallel counter week where staff verify prices on a Lispa demo register before cutover weekend. Recreate receipt printers in Hardware settings. Website content may rebuild in CMS using repair list blocks faster than cloning legacy theme PHP. Lispa support documents common field mappings for Dutch retail. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 61

How do I migrate from Lightspeed?

Accepted Answer

Lightspeed exports vary by plan; extract product catalogues, customer emails and gift card balances you still honour. Disable redundant Lightspeed modules you paid for but never used — Lispa modular pricing lets you enable only POS first. Map ecommerce URLs to new Lispa slugs with 301 redirects your DNS host manages. Appointment histories may be snapshot archived if full import is impractical; forward bookings recreate in inbox manually. Stripe accounts often transfer with reconnection in tenant payment settings. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 62

Can I import a WordPress repair catalogue?

Accepted Answer

Selective WordPress SQL or CSV exports of custom post types and meta fields feed mapping scripts documented in omnichannel phase guides. Focus on model titles, repair categories and hero images actually used on list pages — skip entire media libraries. Lispa repair list components mirror mobile-friendly layouts from reference imports. Plan one to two weeks cleaning duplicates and aligning SKU barcodes before publishing. POS remains source of truth post-migration; WordPress becomes read-only archive you retire after DNS cutover. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 63

Can I start from a spreadsheet catalogue?

Accepted Answer

Yes for smaller catalogues under a few hundred rows. Prepare columns for name, SKU, barcode, price, VAT and stock quantity. Import via backoffice tools, then enable FIFO later if you track lots. Validate random samples at the counter before deleting spreadsheets staff might relapse to using. Add product module when crossing fifty structured SKUs. Repair shops often maintain model lists in sheets during evaluation, then graduate to Lispa without ERP middleware. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Question 64

How do I import customer records?

Accepted Answer

CSV import maps name, email, phone, address and marketing consent flags into customer tables with duplicate detection on phone numbers. GDPR requires lawful basis documentation for marketing contacts you import — attach notes where needed. Avoid importing stale emails that bounce and hurt domain reputation. Post-import, staff verify lookup at counter with a few regulars before marketing campaigns. Wholesale tiers assign after customer rows exist. Staff training materials and Help articles reinforce the same workflow language across Dutch and English backoffice locales.

Answers for every stage of your Lispa stack

FAQ library by topic

Browse by category

General & getting started

POS, stock and counter hardware

Invoicing, VAT and payment links

Website modules and omnichannel

Migration and switching POS

GDPR, data export and EU hosting

Popular starting questions

How FAQ tags work on marketing pages

Still need help?

Related resources

Frequently asked questions

Did not find your answer?