Four releases a year.One per quarter.
fabular is developed continuously – not in big leaps every three years, but on a fixed rhythm. One release each quarter, with ongoing fixes in between. What goes into each one comes out of concrete customer needs.
fabular. process chain
Real timeOpen orders
128
Batches today
24
fabAI flagged batch L-2481: three days from best-before – FEFO suggestion created.
- Quarterly
- Covered by the maintenance contract
- Tested in your environment first
What was added most recently
Existing customers receive the complete notes through the helpdesk. The main points are below.
Version 4.1.0 – August 2026
- 1.fabAI becomes an agent: it creates records and builds reporting pages.
- 2.Its own MCP server – for the first time, fabular can be addressed from outside by AI agents.
- 3.Locally hosted language models can be addressed.
- 4.Custom pages via low-code, generated on request.
- 5.Contract management with multi-level condition calculation.
- 6.Improvements in payment processing and contract items.
Plus new features in PIM, partner management, production, questionnaires, interfaces, the weighing screen, the online shop and the portal.
Version 4.0.0 – May 2026
- 1.The technical basis for the agent functions.
- 2.Extensions in production planning and yard management.
- 3.Business intelligence and reporting expanded.
- 4.Portal and online shop extended.
- 5.Skill builder for your own AI assistants.
How an update runs
Updates are routine, not a project. The path is the same for every release.
- Step 01
Announcement
in advance
You learn what is coming and what it means for your configuration.
- Step 02
Test in your copy
before the date
The release first runs in a copy of your environment, not in the production system.
- Step 03
Installation
an agreed date
Scheduled together, usually outside your operating hours.
- Step 04
Follow-up
if needed
Anything unexpected is handled through the helpdesk with priority.
About releases and updates
Do we have to install every release?
Not immediately, but do not wait indefinitely either. We recommend staying in rhythm: the bigger the version gap, the more effort the jump takes. Support covers the current and the preceding version.
What does a release cost?
Nothing extra. The four releases a year and the ongoing fixes are covered by the maintenance contract, as is our support during installation. Only customisation projects you commission beyond that are calculated separately.
What happens to our customisations?
Because customisations in fabular are mostly configuration – fields, screens, reports, workflows, permissions – they survive across releases. That is exactly why we prefer configuration to bespoke development: it keeps an update routine.
Where do the topics for a release come from?
Mostly from customer needs. What comes out of a project and is generally useful moves into the standard product, instead of staying as a special solution at one customer. That is why everyone benefits from the requirements of individual customers.
Want to see the release live?
We show the new functions on a case from your own business, not on a demo dataset.