Skip to main content

Recreatex documentation

Integrations

Storecove
E‑invoicing for Germany, Austria and Switzerland

Storecove is a global e-invoicing and e-delivery platform that helps businesses, governments, and software providers send, receive, and process electronic invoices (e-invoices) in compliance with international standards and networks.

We already offer Storecove e‑invoicing in several countries (such as the Netherlands, Belgium and France). With this release, the Storecove integration has been extended and is now available for Germany (DE), Austria (AT), and Switzerland (CH), with support across all invoicing components in Recreatex.

What was already possible
  • Storecove e‑invoicing for selected countries (NL, BE, FR).

  • Electronic invoices sent via Storecove to companies and public administrations where e‑invoicing was already supported or required.

What is new in this release
  • Storecove e‑invoicing support has been extended to Germany (DE), Austria (AT), and Switzerland (CH).

  • The integration has been updated to follow the country‑specific e‑invoicing rules for these markets.

  • The Storecove integration is designed to make e-invoicing possible for all Recreatex components that can generate invoices (cash desk, event, booking, etc.).

Background
  • Germany is introducing a legal obligation for domestic B2B e‑invoicing from 2025 onwards.

  • Austria and Switzerland already require e‑invoicing in the B2G segment and are aligning further with European standards.

  • The goal is to ensure that customers in DE/AT/CH can send compliant e‑invoices via Storecove in line with local rules.

Impact for customers
  • Customers in Germany, Austria and Switzerland can now use Storecove to send e‑invoices, similar to customers in our already supported countries.

  • Existing Storecove countries (NL, BE, FR) remain supported.

  • It is still possible to combine e‑invoices and traditional invoices (such as paper), depending on legal requirements and your own processes.

Oracle Opera 5
Limit POS item sales per booking based on guest count

Oracle Opera is a hotel property management system used to handle bookings, room charges, and guest profiles. We have already integrated Opera with POS for guest lookup and “Charge on room” payments, and have now extended this integration to limit sales of selected POS items per day, based on the number of guests in the linked Opera booking.

What was already possible
  • Look up and visualise guest information from Opera via an extra function button on the POS screen.

  • Pay for a purchase using the Charge on room payment method, and send the sale to Opera.

What is new in this release

The plugin can now control how many of the configured membership articles can be sold at the POS:

  • The maximum number of sold articles is limited to the number of guests linked to the Opera booking

  • The limit applies per booking per day

  • The limit is enforced across multiple sales on the same day for the same booking

Configuration
  • OracleOpera counter plugin: In the plugin configuration, you can now add the membership articles that will trigger the Opera flow at the POS when selected.

Visualisation
  • When a configured membership article is selected at the POS, the Oracle Opera popup opens automatically, showing the following additional elements:

    • Table overview: Displays the items already purchased for the current booking, including received date, quantity and item (article type).

    • Today / All filter (default: Today): Allows you to filter the information displayed in the grid.

    • Quantity selector (X/Y) including :

      • Plus and minus buttons +/- to adjust the quantity.

      • X : Quantity selected in the current sale.

      • Y: Remaining number of items allowed for the current booking on that day.

How it works
  • The plugin tracks previously sold membership articles for the same booking and day, calculates how many items are still allowed, and blocks any sale that would exceed the daily limit.

  • Limitation: The limit is applied only to the total number of guests on the booking. Since Opera does not provide age information, the system cannot verify whether the correct ticket type was sold and can enforce only the overall quantity.

  • If the cashier changes the quantity in the current sale, the Opera flow is re-triggered, ensuring the limit check and X/Y indicator always reflect the latest quantity and already sold items.