ERP Left Untouched
No changes to core tables and no direct posting into them.
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.
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.
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.
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 changes to core tables and no direct posting into them.
B1 Service Layer, DI API, Business Central REST and OData, or read-only SQL views.
Users see current stock, prices and documents, not an overnight copy.
Customers, dealers and agents log in to the portal, not the ERP.
We hand over the source code and database. Nothing is rented.
No core table changes, so your ERP stays supportable and upgrades stay clean.
Standard add-ons cover standard processes. These are the ones that never fit the template.
Orders, invoices, delivery status and documents, so customers answer their own questions instead of emailing your team.
Live pricing and stock, order placement, returns and warranty checks, replacing the email-and-spreadsheet loop.
Real availability calculated from on-hand, committed and on-order stock, so nothing gets sold twice.
Multi-step sign-off with a full audit trail, then the approved document written back into the ERP.
iOS and Android apps for field staff, agents and warehouse teams, on the same live data.
Reporting your team will actually open, in Power BI, Looker Studio or built into the portal.
Each group gets screens built for what it needs to do, connected to the same ERP.
Self-service orders, invoices, statements and delivery tracking.
Price lists, stock, ordering, returns and warranty claims.
Mobile apps for visits, deliveries, picking and stock counts.
Portal products are rented and built for the average business. A custom layer is owned by you and built for yours.
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
A clear four-step process that starts with how your ERP is set up.
Confirm the ERP version, hosting, API access and test environment.
Agree users, screens and which data is read-only or written back.
Build the portal or app and connect it through the supported API.
Onboard users, go live and keep it working through ERP upgrades.
We connect through the interfaces SAP and Microsoft support, using a proven .NET and React stack.
Your client wants a portal or a mobile app. Your team does ERP. We build only what sits on top.
Partner With UsNo AL development, no B1 add-ons and no licence revenue.
Deliver under your name, or work openly alongside you.
Scoped and priced up front for your own proposal.
See how we have built portals and platforms that connect customers, vendors and teams to the data they need.
We ask these first. A number given before the answers is a guess, and guesses get corrected later at your expense.
Tell us which ERP you run.
Book a Free ConsultationSAP Business One on HANA or SQL Server, cloud or on-premise; Business Central online or on-premise. This decides how we connect.
You, or your implementation partner. Access delays are the most common reason these projects slip, so we sort this out first.
Showing live data is straightforward. Creating documents inside the ERP is a different piece of work and the largest single cost driver.
Customers, dealers, agents or staff. This shapes the access rules and screens, not just the licence maths.
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.
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.