In short
Anyone evaluating an add-on for SAP Business One almost always looks at the initial license price first, because it is the most visible line in the quote. It is also, almost always, the smallest line over time. Maintenance fees, certification at every SAP B1 upgrade, the number of vendors involved when something breaks, and the cost of customisations outside the standard model: these four items are what drive the real TCO of an add-on over the 3-5 years after signing. This article offers a simple framework for reading any quote on comparable terms, beyond the sticker price.
Why the initial license is the small part of the bill
The typical pricing model for a third-party add-on has two separate components: an initial license (one-off, per user or per module) and an annual maintenance fee paid for as long as the add-on stays in use. The fee usually covers support and minor updates; it almost never covers certification for a major SAP B1 upgrade, which is typically billed as a separate project.
Looked at over a single year, the license looks like the dominant cost. Looked at over 3-5 years — the realistic lifespan of a SAP B1 installation before the next major version jump — the cumulative maintenance fee almost always overtakes the initial license. And the fee is only one of four line items that matter.
The 4 items that weigh in after year one
Recurring maintenance
The annual fee is recurring by definition: it adds up year after year, and unlike the license it never fully amortises. Before signing, it is worth asking explicitly what is included (support, minor patches) and what is excluded (new features, major-release certification, customisations): the answer changes the 3-5 year bill considerably.
SAP Business One upgrades
A third-party add-on does not live in isolation: it has to stay compatible with the version of SAP Business One it runs on. Every time SAP HANA or the underlying SQL engine moves to a major release, the add-on has to be re-certified by its vendor. Who pays for the wait — and who decides when your SAP B1 can move up a version — is not you: it is a third-party vendor’s certification timeline you do not control.
Vendor dependency
When an integration breaks after a patch, how many different parties need to get involved to figure out whose problem it is? The add-on vendor, the SAP partner who manages the installation, internal IT: more parties mean more diagnosis time before anyone even gets to the fix, and none of the three necessarily has full visibility into the other two.
Customisations outside the standard
Every add-on has its own data model and its own set of expected behaviours. When your process diverges from that model — one extra field, a business rule specific to your industry — the customisation has to be commissioned from the add-on vendor, on a timeline and at a cost that are rarely in the initial quote.
Side-by-side comparison
| Dimension | Third-party add-on | Integrated development and maintenance |
|---|---|---|
| Initial license | Separate line, often per user/module | Part of the implementation project |
| Maintenance fee | Recurring, distinct from the SAP fee | Included in the direct support relationship |
| Certification at SAP B1 upgrades | Depends on the third-party vendor’s timeline | Handled by the same team that built the integration |
| Vendors involved when something breaks | add-on vendor + SAP partner + internal IT | One team is accountable for the integration |
| Customisations outside the standard | Commissioned from the vendor, variable timelines | Part of the same development cycle |
How to read a quote in 10 minutes
Before signing, it is worth asking the vendor four direct questions:
- Who certifies the add-on for the next SAP B1 major upgrade, and on what typical timeline?
- What is included in the maintenance fee, and what gets billed separately on top?
- How many different parties need to be involved if the integration breaks after a patch?
- How is a customisation handled when the product’s standard model does not cover it?
The answers to these four questions, compared across quotes, say more about the real 3-5 year cost than the license price alone.
FAQ
Does integrated development always cost less than a third-party add-on over time?
Not necessarily in every case, but the cost structure is different: a third-party add-on adds, by definition, a recurring maintenance fee and a certification cycle you do not control. A solution maintained by the same team that built it removes that layer — not necessarily the underlying cost itself.
What does “certification” for a SAP B1 upgrade actually mean?
It is the work an add-on vendor has to do to verify that its product keeps working correctly after a major release of SAP Business One (for example a version change of the underlying SAP HANA engine). Until certification is complete, the SAP B1 upgrade stays blocked or risky.
How do you estimate TCO over 3-5 years before signing?
Add up the initial license, the maintenance fee for each year of the horizon you are considering, and a conservative estimate of the customisations you already know you will need. Ask the vendor to put it in writing: a quote that refuses to project the fee across several years is a signal worth not ignoring.
Do you always need custom development, or is there a ready-made product?
It depends on the process. For standard scenarios (van sales, warehouse management, transport) ready-made suites exist, natively integrated with SAP Business One: the question to ask is not “custom or product”, but “who maintains the integration over time, and on what cost model”.
Where MTF fits
MTF is a Silver Partner SAP and develops and maintains MTF.Sales.Suite, MTF.Warehouse and MTF.TMS in-house: all three natively integrated with SAP Business One via Service Layer, with no reselling of third-party products. That means one team is accountable for the software and its integration, from the quote to post-go-live support — no separate maintenance fee to manage with a second vendor, no waiting on a third-party certification timeline you do not control.
Explore MTF.Sales.Suite · Explore MTF.Warehouse · Explore MTF.TMS