Last.app

• Restaurants requiring deep, highly customized POS workflows (complex modifiers, advanced portioning, intricate menu hierarchies) where this platform’s simplified workflows may be limiting.
• Organizations that require published SOC2/ISO and enterprise IAM controls up front and cannot accept validation under NDA.

• The product does not integrate with other POS systems, per vendor positioning, which complicates phased migrations.
• Reservations reliability concerns have been reported in consumer review channels, including date, hour, and capacity errors.
• Some feature requests reported by customers (portioning, ad-hoc items, deeper menu structuring) appear not to be implemented or were reported as outstanding by reviewers.

• The vendor maintains a changelog and posts frequent product updates on its site, indicating ongoing iteration; a consolidated, publicly visible roadmap with firm dates was not found in the reviewed materials.

• Modular suite combining POS, delivery aggregation, QR ordering, online shop, and reservations under one vendor platform.
• Hardware flexibility across Windows, Android, and iOS devices, reducing dependence on a single vendor terminal ecosystem.
• Public API and integration tooling oriented toward aggregation of third-party delivery platforms and services.

• Vendor-published improvement metrics (reported percentage reductions in errors, increases in profitability, and reductions in lost orders) are presented on product pages; methodology and independent validation were not found in the reviewed materials and should be requested and validated by buyers.

• Independent review coverage and referenceability.
• Published enterprise security documentation and compliance attestations.
• Mature reservation and table management feature sets in some incumbent vendors.

• Desire for a unified toolset covering POS, delivery, reservations, online shop, and QR ordering.
• Hardware flexibility (Windows/Android/iOS) rather than a single-vendor terminal requirement.
• Integration capabilities as a differentiator (vendor reports numerous integrations).

Vendor-provided customer quotes emphasize channel consolidation and reduced manual errors, for example a customer testimonial on the Last.app homepage referring to time savings and fewer transcription errors.

App Store (Spain) reviews include positive comments about the tool being feature-complete and intuitive, and praise for technical support in some cases.

Trustpilot positives include reports of helpful installation assistance and individual technicians mentioned.

Based on negative Trustpilot reviews:

• Perceived instability in reservations and operational correctness.
• Concerns about pricing transparency and unexpected increases.
• Feature gaps in menu/catalog handling for certain service models.

A Spanish industry interview references PadThaiWok (reported as a multi-location chain) migrating to Last.app to unify POS, delivery aggregator, and online shop functionality to manage multi-location operations.

Critical view:

• The interview is not an independently audited case study; it provides directional evidence that Last.app can support multi-site chains but lacks quantified ROI (labor savings, error reduction, revenue lift) with documented methodology.

The vendor-published metrics on some product pages state substantial improvements (examples reported in local language). These vendor-published figures do not include methodology, sample size, baseline definitions, or independent validation.

Critical view:

• Buyers should request the measurement methodology, sample size, time period, and whether observed improvements are attributable to the product versus complementary process changes.

• Full-service restaurants, fast casual, bars, cafes.
• Delivery-first brands and virtual brands.
• Dark kitchens.

• Owners/operators seeking operational simplicity and consolidated billing.
• Operations managers responsible for multi-site visibility.
• IT/ops integrators focused on API and integration needs.

• Multiple tablets and isolated delivery marketplace integrations.
• Staff training burden due to turnover.
• Disconnected systems for reservations, ordering, POS, and reporting.

• Primary target: Restaurants and multi-location groups in Spain (and adjacent markets), including delivery-heavy concepts, dark kitchens, and chains.
• Positioning: A cloud-native, hardware-agnostic POS targeted at contemporary restaurant operations with an emphasis on integration density (vendor reports a few hundred integrations). It is positioned in contrast to traditional, Windows-local POS ecosystems.