Rolling out Odoo in the Canary Islands means combining core ERP decisions with the archipelago's specific tax and operational rules. Installing the Spanish localisation is not enough: you need to check the Canary localisation available for the chosen version, configure IGIC (the Canary Islands' local indirect tax, similar to VAT), review the SII (the immediate information supply system for VAT/IGIC) where it applies, test invoicing and accounting, migrate data with reconciliation, and set up support capable of handling period closes and tax-related incidents.
What the project needs to solve
Before choosing modules, it helps to describe the expected outcomes:
- A reliable single source for customers, products and price lists.
- Integrated sales, purchasing and inventory.
- Consistent invoicing and accounting.
- IGIC configured according to the operations involved.
- Traceability of orders and collections.
- Margin and cash-flow reporting.
- Integrations with ecommerce, banking or POS systems.
- Readiness for the applicable invoicing obligations.
Scope should be prioritised. A first phase usually covers master data, sales, purchasing, inventory, invoicing and accounting; CRM, projects, manufacturing or ecommerce can be added later.
Spanish and Canary localisation
Odoo's documentation includes the Spanish localisation, with chart of accounts, taxes, fiscal positions and reports. Odoo has also announced a Canary tax localisation available in Enterprise from version 18.
The company must verify, in the contracted version:
- The correct chart of accounts.
- The IGIC taxes.
- Fiscal positions for mainland Spain, the Canary Islands, the EU and third countries.
- The tax forms and reports actually available.
- The SII for IGIC where applicable.
- Compatibility with SIF/VERI*FACTU (Spain's anti-fraud invoicing software requirements) and electronic invoicing.
- Updates and support.
Tax obligations should never be based on marketing material. The tax advisor and the implementation partner must validate the configuration against real cases.
IGIC and fiscal positions
The configuration must reflect the day-to-day operations:
| Operation | Decision to test |
|---|---|
| Local sale | IGIC rate and account |
| Local purchase | Deductibility and posting |
| Transaction with mainland Spain | Treatment and documentation |
| Import | DUA (customs document), AIEM (Canary import duty) or other items as applicable |
| EU/non-EU customer | Fiscal position and test |
| Exempt or special rate | Legal basis and code |
Fiscal positions must be triggered by controlled conditions, not by manual corrections on each invoice.
SII for IGIC
The Agencia Tributaria Canaria (the Canary Islands' tax agency) states that the SII for IGIC is mandatory for taxpayers with a monthly filing period, such as those registered under REDEME (the monthly VAT/IGIC refund register), large companies and corporate groups, under the current rules. The project must confirm whether it applies and test registration, amendment, cancellation, response and reconciliation.
A connector should not be accepted simply because it "sends". It must show status, errors, retries and correspondence with the invoice.
Choosing the edition and hosting
| Option | Advantage | Risk to review |
|---|---|---|
| Odoo Online | Managed operation | Customisation limits |
| Odoo.sh | Controlled deployment and development | Code and environment governance |
| On-premise | Infrastructure control | Security, updates and continuity |
The decision depends on the modules, customisations, integration, data and technical capacity. The contract must clarify who is responsible for backups, updates, incidents and recovery.
Total cost
The budget includes:
- Licences.
- Analysis and configuration.
- Development.
- Data migration.
- Integrations.
- Training.
- Change management.
- Support.
- Infrastructure.
- Version upgrades.
- Contingency and exit costs.
It should be calculated over three to five years. The price per user does not reflect the real cost of the project.
Migration
The following should be separated:
- Active master data.
- Open documents.
- Balances and due dates.
- Stock by location and batch.
- Necessary historical data.
- Attachments.
- A searchable archive.
Odoo allows importing and exporting data; the documentation recommends splitting large volumes into batches. Each load is tested in a staging environment and reconciled.
Controls:
- Customers and tax IDs.
- Products, units and taxes.
- Accounts and balances.
- Outstanding invoices.
- Stock and valuation.
- Due dates.
- Counts and totals.
Integrations
For each integration, define the master system, identifier, frequency, validation, retry logic and owner. Ecommerce, POS, banking, payroll, logistics and BI must not create duplicates.
An available API is not the same as a maintainable integration. You need to test outages, credential changes and version upgrades.
Avoiding excessive customisation
Before developing anything, compare:
- Standard functionality.
- Configuration.
- A reasonable process change.
- A maintained module.
- Custom development.
Every customisation adds testing, maintenance and upgrade risk. There must be an owner and documentation for it.
Implementation partner and support
Consider:
- Demonstrable experience in the Canary Islands.
- Knowledge of IGIC and the SII.
- The assigned team.
- Methodology and deliverables.
- Support during period closes.
- Change management.
- Documentation.
- Continuity and backup coverage.
Support must have an SLA, an escalation path and controlled access. Relying on a single person is not advisable.
Acceptance testing
- Quote, order, delivery and invoice.
- Purchase, receipt and payment.
- Taxes by territory.
- Correction and returns.
- Accounting close.
- SII for IGIC where applicable.
- Stock, batches and valuation.
- Banking and ecommerce integration.
- Permissions and audit trails.
- Backup and restore.
Business users should run the test cases, not just the implementation partner.
90-day plan
Days 1-30
Processes, scope, localisation, data and architecture.
Days 31-60
Configuration, pilot migration, integrations and testing.
Days 61-90
Training, dry run, cut-over and stabilisation.
The timeline depends on scope; it is not a guarantee.
Common mistakes
- Confusing the Spanish and Canary localisations.
- Configuring IGIC manually on each invoice.
- Ignoring the applicable SII.
- Migrating historical data without criteria.
- Customising before testing the standard functionality.
- Not reconciling stock and balances.
- Choosing support based on proximity alone.
- Not budgeting for upgrades.
- Lacking a rollback plan.
- Going live without acceptance sign-off.
Checklist
- Scope and phases.
- Version and edition.
- Canary localisation verified.
- IGIC and fiscal positions tested.
- SII assessed.
- Migration reconciled.
- Integrations with idempotency.
- TCO and contingency.
- Support and SLA.
- Cut-over and rollback.
Frequently asked questions
Does Odoo support Canary Islands taxation?
Odoo announced the Canary localisation in Enterprise from version 18 onward. The exact coverage must be verified for the specific version and modules contracted.
Do I need an additional module?
It depends on your obligations and on standard coverage. This should be decided after testing processes and reports, not by default.
Should all historical data be migrated?
Not necessarily. A secure archive can be kept, migrating only what is needed for operations and compliance obligations.
Sources consulted
- Odoo: localización española
- Odoo: localización de Canarias
- Odoo: importar y exportar datos
- Agencia Tributaria Canaria: SII del IGIC
Summum Sistemas can support the assessment, implementation, migration and acceptance process in the Canary Islands.