Portals & Apps for SAP Business One
and Business Central

Your ERP runs the business, but it was never built to face your customers. We build the layer on top: customer portals, dealer portals, mobile apps and dashboards, connected to your ERP through its API. Nothing inside the ERP changes.

The Problem

Everyone Who Needs the Data Needs a Licence

SAP Business One and Business Central are licensed per seat. The sales agent who checks stock twice a day, the dealer placing an order and the customer chasing an invoice each become a paid user of a system they will barely use, and one they were never designed to log into.

An API-connected portal serves the same people without additional ERP seats, because the portal holds the user accounts and the ERP holds the data. For a business with hundreds of customers or dealers logging in, that difference can add up quickly.

You may be dealing with

When the only way into your data is an ERP licence, people outside the finance team end up asking someone else for it.

Paying for ERP seats for people who only need to check stock, prices or invoices.

Customers emailing for updates on orders, deliveries and invoices your team has to look up.

Dealer orders by email and spreadsheet re-typed into the ERP by hand.

Add-ons that don't fit your pricing rules, approvals or booking process.

How It Works

Three Layers. We Only Work in the Top Two.

Your ERP stays exactly as it is. We build a separate application on top and connect it through the ERP's own supported API.

No core table changes, so your ERP stays supportable and upgrades stay clean.

What We Build

The Work Your ERP Partner Hands Back

Standard add-ons cover standard processes. These are the ones that never fit the template.

  1. 01

    Customer Portal

    Orders, invoices, delivery status and documents, so customers answer their own questions instead of emailing your team.

  2. 02

    Dealer & B2B Portal

    Live pricing and stock, order placement, returns and warranty checks, replacing the email-and-spreadsheet loop.

  3. 03

    Inventory & Booking

    Real availability calculated from on-hand, committed and on-order stock, so nothing gets sold twice.

  4. 04

    Approval Workflow

    Multi-step sign-off with a full audit trail, then the approved document written back into the ERP.

  5. 05

    Mobile Apps

    iOS and Android apps for field staff, agents and warehouse teams, on the same live data.

  6. 06

    Dashboards & KPIs

    Reporting your team will actually open, in Power BI, Looker Studio or built into the portal.

Who It Serves

Your ERP Data, for the People Outside It

Each group gets screens built for what it needs to do, connected to the same ERP.

Customers

Self-service orders, invoices, statements and delivery tracking.

Dealers & Distributors

Price lists, stock, ordering, returns and warranty claims.

Field & Warehouse Teams

Mobile apps for visits, deliveries, picking and stock counts.

Why Custom, Not an Add-On

Products Stop Where Your Process Starts

Portal products are rented and built for the average business. A custom layer is owned by you and built for yours.

Standard

ERP Seats & Rented Add-Ons

  • A paid ERP seat for every occasional user
  • Screens designed for accountants
  • Customers and dealers can't log in
  • Subscriptions that never end
  • Workarounds for rules the product doesn't support
Recommended

API-Connected Custom Layer

  • Portal accounts, not ERP seats
  • Screens designed for each type of user
  • Customers and dealers serve themselves
  • Source code and database handed to you
  • Your approval levels and pricing rules built in

When Does This Make Sense?

When people outside your finance team need ERP data every day, or a process keeps landing in someone's inbox because the ERP can't handle it, a custom layer usually pays for itself.
Book A Call
Our Process

From ERP Access to a Live Portal

A clear four-step process that starts with how your ERP is set up.

Technology

Built on Supported Interfaces

We connect through the interfaces SAP and Microsoft support, using a proven .NET and React stack.

B1 Service Layer & DI API
Business Central REST & OData
ASP.NET Core & SQL Server
React & TypeScript
React Native
Azure & AWS
B1 Service Layer & DI API
Business Central REST & OData
ASP.NET Core & SQL Server
React & TypeScript
React Native
Azure & AWS
For SAP & Microsoft Partners

We Take the Custom Layer, You Keep the Client

Your client wants a portal or a mobile app. Your team does ERP. We build only what sits on top.

Partner With Us

We Stay Out of the ERP

No AL development, no B1 add-ons and no licence revenue.

White Label If You Want

Deliver under your name, or work openly alongside you.

A Number You Can Quote On

Scoped and priced up front for your own proposal.

Before We Quote

Four Questions Decide the Whole Project

We ask these first. A number given before the answers is a guess, and guesses get corrected later at your expense.

Still have a question?

Tell us which ERP you run.

Book a Free Consultation
01 Which ERP, and which version?

SAP Business One on HANA or SQL Server, cloud or on-premise; Business Central online or on-premise. This decides how we connect.

02 Who controls the API and the test environment?

You, or your implementation partner. Access delays are the most common reason these projects slip, so we sort this out first.

03 Read-only, or does the portal write back?

Showing live data is straightforward. Creating documents inside the ERP is a different piece of work and the largest single cost driver.

04 Who uses it, and how many?

Customers, dealers, agents or staff. This shapes the access rules and screens, not just the licence maths.

Good to Know

Many projects start read-only: customers and dealers see live orders, stock and invoices first, and writing documents back into the ERP is added once the portal is in use.

Let's Build What's Next

Tell Us What Your ERP Won't Do

Send us the version you run and the process that keeps landing in someone's inbox. We'll tell you honestly whether it's a portal job, an ERP job, or not worth building.