Custom software connected to SAP Business One
SAP Business One is SAP’s ERP for small and mid-sized companies, and it usually arrives through a partner who implements it. When a process is left outside, we build the missing app and connect it through the routes SAP documents.
1A solid ERP with edges
SAP Business One covers purchasing, sales, stock and finance rigorously. The problems appear at the edges: sales reps who need to check stock on the road, customers asking about their order, documents arriving as PDFs that someone retypes, or an industry process the ERP does not cover.
That does not require touching the core of the ERP. It requires an app that talks to it and respects its business rules.
2How it connects
SAP documents two main routes on its help portal. Service Layer is a web API based on OData, exposing SAP Business One business objects as resources. DI API is the classic interface of the development kit and shares its object definitions with Service Layer. According to SAP’s documentation, logic that must run as one complex transaction can only be wrapped that way through DI API.
- Service Layer, when your version and database allow it: our preferred route for web and mobile apps.
- DI API, when the case requires it and your installation supports it.
- Integration tools your partner already has, if they cover the case.
- Import files for one-off loads.
3What we solve
Some typical projects around SAP Business One:
- An app for sales reps with customers, prices, stock and orders, which writes the order to the ERP.
- A customer portal to check orders, deliveries and invoices without calling the office.
- Reading supplier invoices and delivery notes in PDF, matched against purchase orders before posting.
- Alerts when something does not add up: a price other than agreed, or fewer units delivered.
4What to check first
The SAP Business One version, the database (SAP HANA or Microsoft SQL Server), whether it runs on your server or is hosted by your partner, and which add-ons are installed. Whether Service Layer is available, and how access is configured, depends on that.
With SAP Business One there is almost always a partner. We work with them: they know the installation, manage the licences and must approve the technical user the integration will use.
5What we do not promise
We are not an SAP partner and we do not implement SAP Business One, and we have no published case with it. We build outside the ERP, with minimal permissions, a log of every operation and changes switched off until verified on real data.
6What we have already built

Farmacta
A pharmacy’s back office, built on its paperwork
Farmacta reads supplier delivery notes and invoices and reconciles them with what was ordered. It is the same check that would be needed against SAP Business One purchase orders, although it is not an SAP case.
In use at its first pharmacy

Certero
Tender intelligence for public works
Certero reads public tender documents and award records, turns them into structured data and is live in production. It shows the rigour with which we handle data that feeds decisions; it is not an SAP case.
Live at certero.es. Accepted into NVIDIA Inception.
7Frequently asked questions
Service Layer or DI API?
It depends on your version, your database and what the integration does. For web apps we usually prefer Service Layer; we decide during the diagnosis.
Do we need additional SAP licences?
Possibly, depending on how the app connects. It is a question for your SAP partner and we raise it at the start.
Will you touch our SAP Business One?
We do not touch the core or the configuration. The app lives outside and uses the interfaces SAP documents.
Are you an SAP partner?
No. We are not an SAP partner or implementer.
Tell us which process is left outside SAP
With your version and one example of work done by hand today, we can tell you whether it can be connected and how.
Tell us your problem