{"id":63854,"date":"2026-02-22T10:18:03","date_gmt":"2026-02-22T09:18:03","guid":{"rendered":"https:\/\/www.sushiya.de\/?p=63854"},"modified":"2026-05-15T16:01:03","modified_gmt":"2026-05-15T14:01:03","slug":"lightspeed-kassensystem-erfahrungen","status":"publish","type":"post","link":"https:\/\/www.sushiya.de\/en\/blog\/lightspeed-kassensystem-erfahrungen\/","title":{"rendered":"Our experience with the Lightspeed K series"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A well-functioning POS system is essential for us in the food service industry. The customer doesn't see it, but they feel the effects when something doesn't work, such as the numerous problems and negative experiences we've had since switching to the Lightspeed K series. Many of these problems unfortunately end up with the customer, for example due to long waiting times when cashing up, back and forth when creating invoices, etc. We are currently experiencing considerable problems in our sansaro restaurant, which are noticeable for customers in service due to delays, even when simply taking orders.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Our experience with the Lightspeed K series<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Since Lightspeed is an international company whose hotline sometimes leads to nirvana, we are writing down our experiences here in the blog. This is because we are dealing with sometimes dramatic faults that need to be rectified immediately - and the fact that the hotline keeps referring to a feedback form is another problem: apparently there are no contact persons in Germany who can or want to take proper care of things.<\/p>

Maybe colleagues will use it or someone at Lightspeed who can change something will listen. Because for us as a well-functioning restaurant, changing the POS system (again?) is not easy. A lot of programming and training time goes into every POS system and, ideally, different operational systems should work together.\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Why we opted for Lightspeed K<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

We deliberately opted for Lightspeed K because it can connect to OpenTable, our preferred reservation system for many years, and - theoretically - also to other systems for merchandise management, accounting and so on.<\/span>\u00a0From our point of view, it is an essential aspect that a POS system today is not a closed ecosystem (like Gastronovi, for example, which we used for years), but on the contrary is very open and can make contact with all kinds of other systems.<\/p>

Lightspeed also offers very fast and efficient payment processing, the system looks very modern overall in the back office and also has some setting options that we appreciate. For example, the accounting assignment of product groups can be carried out independently of menu structures. For freaks: this means that we can address mixed items such as sake and wine within a menu, but address different accounting account assignments for both. Theoretically at least... more on this later.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Problems with Lightspeed K in Germany<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This article is still under development. After weeks of trying to clarify the problems with Lightspeed with the support, the account manager and even an external IT support for Lightspeed, we are writing down our experiences here and will post them with screenshots and more detailed information for other colleagues.<\/strong><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Basic problems with DATEV export<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Unfortunately, we haven't noticed much of this yet - because the automatic connection with DATEV Kassenarchiv online (the only accounting connection Lightspeed offers!) seems to be seriously flawed. And Lightspeed has not responded to requests for Lightspeed Inventory or Rest API in recent weeks.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Heutzutage ist die gr\u00f6\u00dfte Herausforderung f\u00fcr eine funktionierende Buchhaltung, die verschiedenen Datenstr\u00f6me sauber und effizient zusammenzufassen.<\/span><\/p>

The Lightspeed K series does not have its own cash book. This in itself is somewhat of a problem, as other providers such as Gastronovi have an integrated cash book, which can then be neatly managed by the employees on site.\u00a0<\/span><\/p>

In theory, it should be easy to connect other cashbook solutions to the Lightspeed K series. But this is where the problems start. This is because Lightspeed offers the transfer to the DATEV cash archive as the only interface for external accounting.\u00a0<\/span><\/p>

That in itself is not a bad thing - DATEV is, after all, a widely used standard for accounting processes in Germany.<\/span><\/p>

But:<\/span><\/p>