Prices that are settled before the project
Fixed setup prices per connection, a project day with a transparent rationale and an hourly rate for small tasks. This page shows how the price of your interface is composed and what changes it.
Setup fixed price · net plus VAT
- A binding fixed price only after the free system analysis
- One price per connection instead of a lump sum for the whole project
- Third-party licences for connectors, middleware and accounting tools shown separately
- Changes during the project only after written approval
The entry price applies to a clearly delimited connection, for example a document export into financial accounting or a payment interface. Inventory systems such as JTL-Wawi or Lexware start at 4,900 €, Microsoft Dynamics 365 Business Central at 6,900 €, SAP Business One at 9,900 €, and each additional marketplace channel at 2,480 €. Custom development is billed via the project day at 990 € net or the hourly rate at 119 € net. All prices net plus VAT.
Most integration quotes leave open exactly the question that matters before you commit: what will this cost in the end? We therefore work with two separate pricing logics. For connections whose scope can be described precisely in advance, we state a fixed setup price. For everything that cannot be delimited beforehand, there is a project day and an hourly rate. This page discloses both logics — including the question of why the project day is deliberately not a multiple of the hourly rate.
The pricing structure at a glance
Fixed setup prices per connection
An integration project rarely consists of a single connection. Two to four connections are typical: the leading inventory or ERP system, financial accounting, a payment interface and possibly a marketplace channel. We calculate each of these connections individually, because they involve different amounts of work and because this lets you decide what belongs in the first stage and what can follow later. A project with a DATEV integration and a payment integration therefore sits in a different order of magnitude than a SAP integration with condition technique and availability checks — and the price should reflect exactly that.
The fixed setup price covers concept work, field mapping, development, testing on a test environment, commissioning and handover with documentation. It does not cover what we do not know beforehand: custom logic that only surfaces during the project, migrations of historical data or adjustments to systems we have no access to. We name such points during the analysis, estimate them separately and only implement them after your approval. The full description of services per module is in the service overview.
Entry prices per connection type
All prices net plus VAT. The amounts shown are entry prices; the binding fixed price is confirmed after the free system analysis.
Document and payment connection
A clearly delimited connection to exactly one target system.
- Invoices, credit notes and cancellations transferred in a structured format
- Rule-based account assignment with revenue account and tax key
- Payment connection including reconciliation of open items
- Testing on a test environment of the target system included
- Third-party export licence shown separately
Inventory system and ERP
The standard scope between the leading system and your shop.
- Products, prices, stock and orders in both directions
- JTL-Wawi and Lexware from 4,900 €, Dynamics 365 from 6,900 €
- SAP Business One from 9,900 € due to condition technique and document flow
- Queue with automatic retry and error log
- Field mapping and transformation rules documented
Custom development
For everything that cannot be scoped cleanly in advance.
- Hourly rate 119 € net for delimited individual adjustments
- Project day as a package price including coordination and handover
- Custom API development and middleware
- Effort estimate before we start, billing based on actual effort
- No minimum call-off, no prepaid hour packages
Project day and hourly rate: the rationale
Anyone doing the maths on our rates runs into an apparent inconsistency: eight hours at 119 € add up to 952 €, yet the project day costs 990 €. That is not an arithmetic error but the difference between two billing models. The hourly rate applies to delimited individual tasks that we slot into a running week: an additional field in the mapping, a corrected tax key rule, a new webhook. What is billed is the time actually spent on that task.
The project day, by contrast, is a package price for an exclusively reserved working day. It includes up to eight hours of implementation plus everything that makes such a day productive in the first place: preparation and getting into your system, coordination calls with you or your ERP partner, documentation of the changes and the handover at the end of the day. In the hourly model, exactly these items are counted individually. That is why the project day is deliberately not a multiple of the hourly rate: it bundles more than eight hours of pure implementation time.
This leads to a simple rule of thumb that we apply ourselves before every engagement: if you need less than half a day of implementation, the hourly rate is cheaper for you. If a full day is occupied with coordination, testing and handover, the project day is cheaper. We tell you on our own initiative which of the two billing models results in the smaller invoice for your specific task, and we put that in writing in the quote. Both rates are net plus VAT.
| Criterion | Hourly rate 119 € net | Project day 990 € net |
|---|---|---|
| Billing unit | Each quarter hour started | One reserved working day as a package |
| Included service | Pure implementation time on the task | Implementation plus preparation, coordination, documentation, handover |
| Typical occasion | A single field, rule or webhook | Expansion stage, migration, larger extension |
| Predictability | Effort estimate with a range | Fixed amount per day, number of days estimated upfront |
| Cheaper for | Less than half a day of work | A full day with coordination and testing |
| Less suitable for | Multi-day expansion stages | Small 30-minute corrections |
What this means in practice
What determines the price of your interface
Two projects with the same ERP and the same shop can differ considerably in effort. The reason almost never lies in the interface technology but in the rules that have to apply before data is handed over. In our project practice, these six factors explain most of the price differences (project experience).
Number of data flows
Products, prices, stock, orders, documents and returns are six independent flows with their own rules. Every additional flow increases the effort for mapping, testing and error handling.
Complexity of pricing
A list price is quickly transferred. Customer groups, contract prices, volume tiers and promotion logic, by contrast, require a runtime price query against the leading system.
Variants and master data depth
A size and colour matrix, bills of materials or configurable products create a multiple of records and require dedicated reconciliation logic in the shop.
Tax and document rules
Reverse charge, the One-Stop-Shop procedure, third-country deliveries and credit notes each bring their own assignment and validation rules that must be modelled in the mapping.
Interface quality of the legacy system
A system with a documented REST API is connected far faster than one that only offers file exports or direct database access.
Data volume and cadence
A few hundred products in a nightly run are something different from six-digit product counts with real-time stock changes and peak loads during campaigns.
Want to know where your project sits in this range?
We review your system landscape, name the required data flows and state a binding fixed price per connection before development starts.
What the fixed price includes and what is itemised separately
A price is only transparent if it is also clear what it does not include. We therefore draw a consistent line between our service share and third-party costs. Licences for connectors, middleware components, accounting export modules or payment providers appear in the quote as their own line item with provider and term. That way you can see at a glance which part of your budget stays with us and which part goes to third parties on an ongoing basis.
- Included in the fixed setup price: concept work and field mapping, development of the connection, transformation rules, error handling with retry logic, testing on a test environment, commissioning and handover with written documentation.
- Itemised separately: licences for connectors and middleware, third-party accounting export modules, payment provider fees, marketplace fees as well as hosting or cloud costs for broker components.
- Billed by effort: custom logic that only becomes visible after the analysis, migration of historical data, adjustments to third-party systems and training beyond the handover.
- Optional and separate: ongoing interface monitoring with alerting, agreed response times and regular reviews after go-live.
- Not charged: the system analysis before the quote, the initial consultation and the preparation of the quote itself.
From enquiry to a binding fixed price
Initial consultation, around 30 minutes
We clarify which systems are involved, which processes are still manual today and where the biggest pain lies. Afterwards both sides know whether a project makes sense. This conversation is free and non-binding.
System analysis with a look at the interfaces
We examine the interfaces that are actually available: which fields does the ERP deliver, which endpoints does the shop offer, how are prices and stock modelled there? Without this step there is no binding price, only an estimate.
Data flow concept and scope definition
For each data flow we record which system leads, which fields are transferred and what happens in case of conflicts. What is not in the scope is not in the fixed price — and is listed as a clearly named option.
Binding quote with a fixed price per connection
You receive a price per connection, an effort estimate for the parts billed by effort and a separate list of third-party licences. Payment plan and milestones are part of the same document.
Implementation with approval for changes
If a requirement comes up during implementation that was not in the scope, you receive a short written estimate. Work only starts after your approval. Surprises on the final invoice are ruled out this way.
Handover and your decision about operations
After commissioning we hand over documentation and access credentials. Whether you then book a monitoring package, order maintenance by the hour or continue on your own is entirely your decision, with no follow-up contract required.
Three ways to calculate an integration project
Open hourly budget, lump sum or fixed price after analysis
All three models are common in the market. They mainly differ in who carries the risk of a wrong estimate.
Open hourly budget
- Project start possible without lengthy preparation
- Changes can be slotted in at any time
- The budget risk lies entirely with you
- The final price is only known at the end of the project
- Retrospective discussions about effort are frequent
Lump sum without analysis
- A single figure that is easy to compare
- No upfront work required before the engagement
- The risk premium is inside the price but not visible
- Edge cases end up in change requests instead of the quote
- What exactly is included often remains vague
Fixed price after a system analysis
- A price per connection instead of one sum for everything
- Scope, fields and conflict rules are documented in writing
- Third-party licences shown separately from the service share
- Setup fixed price from 1,490 € net after a free analysis
- The analysis takes time before the first line of code is written
Worked examples from project practice
The following scenarios show how fixed price, project day and hourly rate combine in typical starting situations. These are illustrative sequences from project practice (project experience), not quotes for a specific case.
How the pricing logics mix in practice
Illustrative scenarios from typical project sequences (project experience), anonymised and without customer details. All prices net plus VAT.
Ongoing costs after go-live
An interface is not a piece of furniture that you set up once. ERP updates change field contents, shop releases change endpoints, and legislation changes document rules — the e-invoicing mandate is the most recent example. For ongoing operations there are therefore three building blocks you can book individually or in combination. None of them is mandatory, and none requires a commitment beyond the agreed term.
Maintenance by effort
Small adjustments, new fields or corrected rules are billed at the hourly rate of 119 € net. No base fee, no minimum call-off, no prepaid quota.
Interface monitoring
Automated checks on throughput, latency and error rate with alerting when a data flow stalls. Scope and response times are defined together with you.
Learn morePlanned expansion stages
Larger extensions such as an additional channel or a new target system are booked as project days at 990 € net or again as a fixed setup price.
Learn moreThe essentials about our pricing
- Fixed setup prices apply per connection, not as a lump sum for the entire project: from 1,490 € net for document and payment connections, from 4,900 € net for inventory systems, from 6,900 € net for Dynamics 365 Business Central and from 9,900 € net for SAP Business One.
- The project day costs 990 € net and is a package price for a reserved working day including coordination, documentation and handover.
- The hourly rate is 119 € net and suits delimited individual tasks. Eight hours of pure implementation add up to 952 € — which is why the project day is deliberately not a multiple of the hourly rate.
- Every price only becomes binding after the free system analysis; without a look into the interfaces we only quote ranges.
- Third-party licences for connectors, middleware and export modules are always shown separately from the service share.
- All prices are net plus statutory VAT.