PL EN
Let's talk
Odoo Partner in Poland

Odoo as your operational backbone. Not another system alongside Excel.

We design the process, configure Odoo, organise the data and integrate the systems around it. We specialise in B2B companies where sales, pricing, purchasing and inventory need to operate as one process.

Book an Odoo consultation See how we implement
Implementation, migration and integrations by Derave
Status
Odoo Partner
Expertise
Odoo 19 Certified
Specialism
B2B distribution
Approach
Standard, pilot, scale
Why Derave

We make difficult implementation decisions explicit.

We connect process decisions, data and technical ownership, and say plainly what is not worth building.

Status

Odoo Partner

We help choose the right model and lead the implementation from process review through launch and ongoing improvement.

Expertise

Odoo 19-certified functional consultant

Connects process analysis with Odoo configuration and turns business decisions into implementation-ready work.

Domain

B2B sales and operations

We understand product catalogues, customer-specific pricing, CRM, orders, inventory and cross-system data flows.

Ownership

Business and engineering in one team

We do not stop at a process map or pass decisions between the consultant, analyst and developer.

The way of working comes first

The most expensive implementation is one that recreates today's chaos 1:1.

When a project starts with a module list, important questions remain unanswered: who owns the data, which exceptions need to remain and how success will be measured.

At Derave, we map the process, ownership and baseline first. Only then do we decide what to simplify, configure in standard Odoo, integrate or build. If Odoo does not fit a critical process, we say so before creating an expensive workaround.

Implementation scope

The areas we connect into one operating system

We choose the modules and integrations required for a first verifiable result. Further scope follows the process.

CRM, sales and customer service

Leads, activities, quotes, sales orders and handover to fulfilment in one clear flow.

Catalogue, variants and pricing

Product data, customer price lists, discounts, margins and approvals organised as rules instead of knowledge held by a few people.

Purchasing, inventory and WMS

Demand, purchase orders, receipts, reservations, stock and delivery connected to sales.

Accounting, Polish localisation and KSeF

Polish localisation and the technical KSeF flow, configured and tested with the client's accounting team.

Manufacturing, projects and service

MRP, project delivery, timesheets or service workflows, used where they complete the operational flow.

Migration and integrations

Connections to ERP, PIM, e-commerce, banks, carriers, BI and industry systems, with data-quality controls.

Standard before custom

We use custom code only after testing the standard options.

Every departure from standard Odoo increases maintenance and upgrade costs. We review each requirement in the same order.

Handover scope, access to code and documentation, and maintenance ownership are written down before development begins.

  1. Standard 01

    First we test how Odoo handles the process without code changes.

    If the standard is sufficient, we simplify the way of working instead of recreating old habits in a new ERP.

  2. Configuration 02

    We adapt roles, rules, views, documents and automations.

    Changes stay close to standard, are easier to explain to users and safer during upgrades.

  3. Integration 03

    We connect systems that remain responsible for their data.

    We do not move everything into Odoo. We define how data flows, how errors are handled, what is monitored and who owns each interface.

  4. Custom code 04

    We add custom code when the business case is clear.

    Before the decision, we show the value, maintenance cost, upgrade impact and the simpler alternative.

What you receive after the first phase

  • Process and ownership map

    Steps, roles, exceptions, decisions and responsibility for data.

  • Fit-gap decision log

    The chosen approach (standard, configuration, integration or code) and its rationale.

  • Data and integration plan

    Systems responsible for each dataset, migration scope, validation and error handling.

  • Pilot scope and acceptance criteria

    Real users, scenarios and a result that can be checked.

Odoo at the operational core

From enquiry to invoice, every team works with the same data.

Information moves between teams without retyping, guesswork or another control spreadsheet.

Operational flow in Odoo

  1. Enquiry 01

    CRM and qualification

    Customer, need, activities and the salesperson responsible.

  2. Quote 02

    Product, price and approval

    Current data, customer terms, margin and commercial decisions.

  3. Order 03

    Sales and commitment

    A confirmed order triggers the next steps without retyping data.

  4. Delivery 04

    Purchase, inventory or project

    Availability, reservation, delivery, manufacturing or team work.

  5. Settlement 05

    Invoicing, KSeF and reporting

    Invoices, payments and management data stay connected in one view.

Systems we can connect

  • PIM
  • e-commerce
  • banks
  • carriers
  • BI
  • industry systems
How we implement Odoo

First, a measurable result in a small scope. Then we scale.

  1. 01 DISCOVERY

    Process diagnosis and baseline

    We speak with process owners and inspect real cases and data. We select the problem and a measure that can be compared after implementation.

  2. 02 FIT-GAP

    Target process and decision log

    We show the target flow, standard and configuration scope, integrations, migration, roles and agreed exceptions.

  3. 03 PILOT

    Pilot on real data

    We configure a bounded scope, rehearse migration and run scenarios with future users. We correct the flow before the wider launch.

  4. 04 GO-LIVE

    Launch, handover and development

    We train users on the company's processes, document decisions and stabilise work after launch. The next stages follow data and an agreed development plan.

Are we a fit

We check the fit before the contract is signed.

Odoo projects work best when both sides can assign people to make process decisions and test real cases.

We are probably a strong fit when:

  • you run specialist B2B sales or distribution and the process connects CRM, pricing, purchasing and inventory
  • you have a complex catalogue, customer-specific terms or data scattered across ERP, Excel and email
  • you are selecting Odoo, organising an existing setup or need to take over an implementation that has stalled
  • you want one team for process, configuration, data, integrations and go-live
  • you can appoint a process owner and users who will test the pilot on real cases

We are probably not the right fit when:

  • you need developers by the hour without one team accountable for the result
  • the goal is to copy the current process 1:1, with no willingness to simplify exceptions and roles
  • the project must cover everything at once, but no one owns decisions and users have no time to test
  • you do not want to agree a baseline, acceptance criteria or maintenance rules before work begins

If discovery shows that Odoo is not the best choice, or that a simpler solution would work, we will tell you before implementation begins.

Odoo implementation questions

Key questions before implementation.

We explain scope, responsibilities and technical decisions before work starts.

How much does an Odoo implementation cost?

We do not quote one standard price without understanding the process. After a diagnostic conversation, we set out the phases, assumptions, responsibilities and exclusions. This lets you compare the full scope of configuration, migration, integrations, testing and go-live, rather than just a day rate.

How long does implementation take?

It depends on the number of processes, data quality, integrations and the availability of your team. We define a first production-ready scope that users can work with, then launch the remaining areas in stages.

We already have Odoo, but the project has stalled. Can you take it over?

Yes. We begin with an audit of the configuration, custom modules, data, integrations and unresolved decisions. Then we show what to keep, simplify or repair, and whether an upgrade makes sense now or after the process has stabilised.

Will we need custom code?

We check standard Odoo and configuration first. We propose custom code only when it adds clear business value or an integration requires it. The proposal spells out the maintenance and upgrade impact, along with access to code and documentation.

How do you approach data migration?

We agree which data is operationally necessary, who owns its quality and how it will be validated. We rehearse migration before production, document mapping rules and validate the result with the relevant process owners.

Does Odoo support Polish accounting and KSeF?

Odoo 19 provides Polish localisation and a KSeF integration module. We configure and test the technical flow, permissions and document scenarios. Your accounting team or tax adviser validates tax decisions and accounting correctness.

Community or Enterprise?

We start with the process, then compare the required features, hosting model, upgrade path and total maintenance cost to recommend the right edition.

What happens after go-live?

We agree a stabilisation period, support channel, ownership and the next improvement plan. Ongoing support and SLA scope are described separately, so maintenance cost is clear before work starts.

LET'S TALK

Let's start with the process that is blocking the business today.

In 30–45 minutes we'll check where time is operationally leaking, what's still manual today and whether there's room for real improvement.

Let's talk