Standard first, then code
We start by reviewing Odoo’s existing functions and modules. We develop custom code only for requirements they cannot cover. At Prantl, standard functionality meets 13 of the 18 requirements in the ordering process.
This makes ongoing operation easier: your team can configure standard functions itself, while customisations need additional checks with each upgrade.
What we build
Customisations and custom modules
Rauschenberger records agency and venue commissions by partner and product category. Odoo includes them in quotes and recalculates them when the partner changes. We also worked with accounting on the DATEV export, adding a posting-type column and removing an unused one.
Interfaces
Our published projects include online shop and Microsoft 365 mailbox integrations, as well as DATEV exports. At Prantl, shop orders are created as drafts for review before confirmation. We use Odoo’s APIs to connect other systems.
Automation
At Rauschenberger, Odoo calculates deadlines in business days, from initial customer contact to the last call before an event. Deposit and final-invoice tasks are assigned to finance.
Interfaces at a glance
Before quoting, we establish how each integration will be delivered. Standard means functionality included with Odoo Enterprise. A connector uses an existing add-on or an external service provider. Custom interfaces are developed using Odoo’s APIs.
| System | Standard | Connector | Custom |
|---|---|---|---|
| DATEV (posting batches, master data, documents) | yes | – | for a different format |
| E-invoicing (XRechnung, ZUGFeRD) | yes | – | – |
| Microsoft 365 (Outlook, mailbox) | yes | – | – |
| Online shop (Shopware, WooCommerce, Magento) | – | yes | for a custom data model |
| EDI with retail customers (EDIFACT) | – | through an EDI provider | yes |
| Bank (statements, SEPA payments) | yes | EBICS | – |
| PIM (product data) | – | depending on the system | yes |
| DMS and archive | Odoo Documents | depending on the system | yes |
| MES and machine data | IoT box | – | yes |
| CAD and PDM | – | – | yes |
| Payroll (DATEV Lohn, payroll bureau) | – | – | hand-over of pre-payroll data |
| SAP as the leading system of the group | – | – | yes |
We document the data flow, triggers and error handling for each interface. These records form part of the customisation documentation and are reviewed during upgrades. Any third-party connector licence fees are listed separately in the quote.
How we work
- Requirement: You describe the process; we check the standard and existing modules.
- Concept: We describe the planned customisation and record the requirements for future version upgrades.
- Development: We develop in a test instance and show you interim results.
- Test and sign-off: Your team tests with its own data and signs off the customisation.
- Delivery: We deploy the customisation and hand over the documentation.
Who develops
Our development team builds customisations for Odoo Community and Enterprise, whether hosted in the cloud or on your own servers. Odoo uses Python and PostgreSQL. You have a named project manager and deputy, with direct access to management for escalations.
Costs
Smaller customisations are billed at €120 per hour or deducted from your support plan’s hours. For larger pieces of work, we provide a fixed-price quote. Available plans are on the pricing page.