Last updated: August 8, 2026
ERPLORA CLOUD S.L., with Tax ID (CIF) B27593136 and registered address at Avda Lisboa 17, Pta. C, 28822 Coslada (Madrid) (hereinafter, "ERPlora"), provides cloud-based business management services (SaaS) through https://erplora.com and the *.erplora.com hubs or the customer's own domains.
Use of the service implies full acceptance of these terms.
1. Service
ERPlora offers a modular, multi-tenant ERP/POS SaaS platform, deployed on European cloud infrastructure, with features such as sales, inventory, and customer management, invoicing, tax integrations (VeriFactu), and modules available for purchase from a marketplace.
The service is provided "as is" without warranties of fitness for a specific purpose beyond what is described in the official documentation.
2. Registration and account
To use the service, the customer must create an account providing accurate information. The customer is responsible for maintaining the confidentiality of their credentials and for all activity carried out under their account. Any unauthorized use must be reported immediately to soporte@erplora.com.
3. Subscriptions and payments
- Plans and prices are published at /pricing/ and may be updated; changes affect future renewals, not the current period.
- Payment is made through a recurring subscription (monthly or annual) via Stripe. ERPlora does NOT store card data — it is managed by Stripe.
- The invoice is issued using the billing details provided by the customer.
- Non-payment at maturity will result in suspension of the service after a 7-day grace period with prior notice. A suspended Hub keeps its data intact and can be brought back by resuming the subscription.
- A Hub that remains suspended for 180 days is deleted, together with its data. The account holder is notified beforehand, by email and with a specific date, and receives the copy described in section 5.1.
4. Trial period and cancellation
- A free trial period is offered whose duration depends on the plan contracted and is shown on the pricing page at the time of signup (currently, 6 months on the Starter plan). If not cancelled before the end of the trial, the first period is billed automatically.
- The customer may cancel the subscription at any time from the dashboard; the service will remain active until the end of the already-paid period, with no prorated refund except as provided by mandatory consumer protection regulations where applicable.
5. Ownership of customer data
The data that the customer enters into their Hub (end customers, sales, inventory, etc.) is the property of the customer. ERPlora acts as data PROCESSOR under Art. 28 GDPR; the processing terms are detailed in the Privacy Policy and, where applicable, in the Data Processing Addendum (DPA) signed between the parties.
While the Hub is active, the customer may export their data from it at any time. If the subscription lapses, the Hub is paused and its data is kept intact; the customer is notified in writing, with a specific date, before anything is deleted.
5.1 What the customer receives when their Hub is deleted
Before deleting a Hub, ERPlora prepares a complete copy of it for the customer: the full database of the Hub and all the files it had stored, in a single archive that is NOT encrypted, so that it can be opened and kept without any ERPlora software or key.
A download link is sent to the account holder by email and remains available for 90 days from the date of that email. After that date the copy is deleted and cannot be recovered, by the customer or by ERPlora.
Keeping the accounting and tax documentation for the legally required period is the customer's responsibility as the party subject to those obligations (6 years, article 30 of the Spanish Commercial Code; 4 years of tax limitation, article 66 of the General Tax Act). ERPlora is the software producer and, in respect of the data, the processor: its obligation on termination is to return or delete the data, which is what the copy described above does.
6. Availability and SLA
ERPlora makes reasonable efforts to maintain 99.5% monthly availability. Scheduled interruptions are notified at least 48 hours in advance. Unscheduled interruptions are handled according to internal incident processes.
Compensation for SLA breaches, if any, is set out in the specific contract signed with the customer.
Updates to the service are not scheduled interruptions: they are applied without stopping the service and are governed by section 7.
7. Updates and versions
7.1 ERPlora applies the updates
ERPlora keeps the service up to date and applies updates to the customer's Hub itself, without the customer having to request them. The customer does not choose the version they run and cannot postpone an update: the whole fleet runs the current version, and that is what allows ERPlora to fix faults, close security holes, and keep pace with tax regulations for every customer at the same time.
The customer may bring an update forward at any time from the Hub, both for the service and for each module. What they cannot do is postpone it.
7.2 Valid reasons for updating
ERPlora modifies the service only for the following valid reasons, which are stated here because a power to modify the contract unilaterally requires them:
- to correct faults and keep the service in conformity with the contract and its documentation;
- to close security vulnerabilities;
- to adapt the service to changes in the applicable law, in particular tax and electronic invoicing rules;
- to keep the service working with the third-party systems it depends on: the tax authority, the payment provider, browsers, operating systems, and devices;
- to improve the service and add features, and to retire technically obsolete components, always within the limits of section 7.3.
7.3 What ERPlora undertakes with every update
- Continuity. The new version is started and checked before the previous one is withdrawn. An update is not, in itself, an interruption of the service and is therefore not a scheduled interruption for the purposes of section 6.
- Backward compatibility. An update does not destroy the customer's data and does not leave the Hub with fewer functions than it had before.
- Automatic reversion. If the new version does not start correctly, the previous one is restored automatically and the customer carries on working with it.
- Notice of visible changes. Changes that alter the way the day-to-day sale is operated — from signing in to charging — are announced before they take effect, under section 7.5.
- Traceability. The Hub shows the version in use and a history of the updates applied, stating which version each one came from and went to.
Modules installed from the marketplace are updated under these same rules.
7.4 An update never costs the customer anything
An update does not change the price of the contracted plan, does not put behind an extra charge a feature the customer already had, and does not oblige the customer to buy hardware or software in order to carry on using what they contracted.
7.5 Notice, and the right to terminate
Updates needed to keep the service in conformity — correcting faults, security, and adapting to changes in the law — are applied without prior notice: holding them back would leave the customer worse off, not better.
Where a modification goes beyond that and negatively affects the customer's access to the service or their use of it, other than to a minor extent, ERPlora will inform the customer with reasonable advance notice, on a durable medium, of the features and the timing of the modification and of the right set out in the following paragraph.
That notice is given by email to the address on the account. Announcing it inside the product as well does not replace the email: a message the customer only sees by logging in is not, on its own, a durable medium.
In that case the customer may terminate the contract at no charge within thirty calendar days from receiving that information or from the moment ERPlora makes the modification, whichever is later. On terminating, ERPlora refunds the proportional part of the price paid for the period not yet used, and the customer keeps the right to export their data under section 5.
For customers who are consumers, this section gives effect to articles 126 and 126 bis of the consolidated text of the General Law for the Defence of Consumers and Users. ERPlora applies it to every customer, consumer or not, because it cannot reliably tell them apart and does not intend to.
7.6 ERPlora answers for its own updates
If an update leaves the service not in conformity with the contract or its documentation, that is ERPlora's responsibility, and the general wording of section 1 does not exclude it. ERPlora will restore conformity without undue delay and at no cost to the customer.
If it does not, the customer may claim a reduction of the price proportional to the time during which the service was affected and, where the lack of conformity is not minor, terminate the contract. The customer does not have to prove that ERPlora was at fault: showing the lack of conformity is enough.
7.7 Desktop and mobile application
The installable application is the exception: it is never updated on its own. ERPlora announces that a new version is available and informs the customer of the consequences of not installing it; the customer decides when to install it.
Where the customer does not install, within a reasonable time, an update that ERPlora has supplied and announced in that way, ERPlora does not answer for a lack of conformity that is due solely to that uninstalled update.
7.8 Invoicing software
When an update affects the components subject to the regulation on the requirements of invoicing computer systems, the responsible declaration for the new version is published, and the previous ones remain available, in the public archive of responsible declarations.
7.9 Relationship with the rest of these terms
The undertakings in this section are specific obligations of ERPlora and prevail over the general wording of section 1. Except for what section 7.6 provides, they do not create an availability commitment beyond section 6.
This policy is explained in plain language, without legal wording, on the Updates page.
8. Acceptable use
It is prohibited to:
- Use the service for unlawful or fraudulent activities, or activities that infringe the rights of third parties.
- Reverse engineer, decompile, or attempt to access the source code beyond the components published as open source.
- Attempt to compromise security, overload the infrastructure, or access other customers' data.
- Resell the service without ERPlora's express authorization.
Breach may result in immediate suspension without refund, without prejudice to any applicable legal action.
9. Intellectual property
All software, design, documentation, and trademarks of the platform are the property of ERPLORA CLOUD S.L. or its licensors. The customer receives a non-exclusive, non-transferable, and revocable license to use the service during the subscription period.
10. Limitation of liability
To the maximum extent permitted by law, ERPlora's aggregate liability to the customer for any claim arising from the service will be limited to the amount actually paid by the customer in the 12 months prior to the event giving rise to the claim.
ERPlora is not liable for indirect damages, loss of profit, or data loss when the customer has reasonable backup mechanisms of their own and when the breach is not attributable to willful misconduct or gross negligence by ERPlora.
When the customer is a consumer under the terms of the General Law for the Defense of Consumers and Users, the above limitations will be interpreted in accordance with that regulation, with consumer legal protection prevailing.
11. Changes to these terms
ERPlora may modify these terms. Substantial changes will be notified at least 30 days in advance. Continued use of the service after they take effect implies acceptance.
Changes to the software itself are governed by section 7.
12. Termination
Either party may terminate the contract:
- At any time (customer), in accordance with section 4.
- For serious breach, following notice with a 15-calendar-day cure period.
- Due to insolvency, bankruptcy, or cessation of activity of the other party.
13. Applicable law and jurisdiction
These terms are governed by Spanish law. For any dispute, the parties submit to the Courts of the city of Madrid, waiving any other jurisdiction that might otherwise apply, without prejudice to consumer jurisdiction where applicable.