SAP Business One · Add-ons & Custom Apps
SAP Business One add-ons and custom apps, built where they belong.
When a requirement cannot be met with configuration, we build the missing piece as an add-on or a connected application, using the SAP Business One® SDK, the Service Layer and modern web and mobile technology.
- Inside
- A client add-on: shortest reach, highest upgrade cost
- Beside
- A service on supported interfaces, updated in one place
- Outside
- Its own application, for people who should not be in the ERP
- Alongside
- Read-only queries and reports. Never writes
Four checks first
We would rather not build it
A development project is the most expensive answer to any requirement and the one that leaves you with the most to own afterwards. These four questions come before a quote.
- 01
Is it already in the product?
Approval procedures, alerts, user-defined objects, recurring transactions. A surprising amount of what people ask us to build ships with SAP Business One and has never been switched on.
- 02
Is there an add-on for it?
The ecosystem is large. Where a published add-on fits, we recommend it and say so plainly, even though it earns us less than building.
- 03
Would it need customizing anyway?
An add-on that covers 60 percent and needs work to reach the rest is often worse than a clean build, because you now own two things.
- 04
Is it one of ours already?
Four of our solutions began as custom builds for a single client. If the requirement matches one, configuring a product beats a project.
Placement
Four places the work can live
Once building is the right answer, this is the choice that determines who can use it, how it is deployed, and what happens on the weekend the environment is upgraded.
Inside SAP Business One
Inside the client
A UI API add-on, loaded by SAP Business One on each desktop
- Who reaches it
- Only people working in the SAP Business One client
- Deployment
- Installed per machine, and every machine has to be on the same version
- Upgrade exposure
- Highest exposure. It runs inside the product, so the product moving underneath it matters
When the work belongs in a screen the user is already on, and interrupting their flow to open something else would be worse.
The product boundary
Outside it, at increasing distance
- 02
Beside it, as a service
A background service talking to the Service Layer or the DI API
- Who reaches it
- Nobody directly. It works while people are elsewhere
- Deployment
- One place, updated once
- Upgrade exposure
- Low, on supported interfaces. Tested against the new version before the environment moves
For anything scheduled or triggered: document creation, notifications, feeds, reconciliation, integration.
- 03
Outside, as its own application
A web or mobile application reading and writing through the Service Layer
- Who reaches it
- Anyone you give an account to, including people with no SAP Business One licence
- Deployment
- Once, centrally. No desktop installation at all
- Upgrade exposure
- Low. It is a client of the interface, not a resident of the product
When the users are customers, reps, warehouse staff or anyone who should not be inside the ERP.
- 04
Alongside, in the database
Queries, views and reports over the SAP Business One schema, read-only
- Who reaches it
- Reporting tools and whoever consumes them
- Deployment
- Nothing to install
- Upgrade exposure
- Moderate. The schema can change, so anything reading it needs checking
For reporting and extracts. Never for writes, which have to go through the application.
We put as little as possible on the left of that line. Code inside the product has the shortest reach and the highest upgrade cost, which is a poor trade unless the work genuinely belongs on a screen the user is already looking at.
Scope
What we build on SAP Business One
- 01Purpose-built add-onsScreens and logic inside SAP Business One for processes the standard menus do not cover.
- 02Mobile applicationsWarehouse, counting, sales and delivery apps that read and write SAP data, online and offline.
- 03Web applications and portalsCustomer, vendor and rep portals with SAP data behind them.
- 04Workflow automationScheduled jobs and triggers that create documents, send notifications and move data without a person clicking.
- 05Reporting applicationsDashboards and reporting tools for the cases where Crystal Reports and queries are not enough.
- 06SAP Customer CheckoutPoint-of-sale connected to SAP Business One for companies that also sell over the counter.
Already built
Four that started as one client's problem
Each of these was a custom build before it was a product. If your requirement matches one, configuring it is faster and cheaper than repeating the project.
- 01B2B eCommerceCustomer ordering portal with live pricing, stock and account history.See it
- 02Sales Rep AppMobile order entry, customer data and pricing for reps in the field.See it
- 03Inventory CountingBarcode-driven physical and cycle counts, synchronized to SAP Business One.See it
- 04Price Label PrintingPrice and barcode labels generated from SAP Business One item and price data.See it
Afterwards
Upgrades and ownership
Anything built against supported SAP Business One interfaces carries across an upgrade with minor changes. Anything built against undocumented behaviour does not, and it fails on the weekend the environment moves, which is the weekend nobody is watching.
- Built on the Service Layer, the DI API or the SDK, never on direct writes to SAP Business One tables.
- Tested against the new version in a test company before your environment is upgraded.
- Ownership and licensing terms set in the agreement before development starts, not afterwards.
- Delivered with documentation and a support path, so it is maintainable by somebody who did not write it.
Questions
About building on SAP Business One
Next step
Talk through your SAP Business One project with someone who will actually work on it.
A short conversation about where you are today, what is not working and whether SAP Business One and our team are the right fit. No slide deck.