SAP Business One is licensed and designed around internal named or concurrent users — people in your company who need the full application. That model works well for staff, and poorly for anyone outside the company (or outside a desk) who just needs a narrow slice of the data.
The signal to watch for
If you find yourself asking "should this customer/vendor/driver just get a SAP login," it's usually a sign you actually need a web portal, not another SAP seat. A few concrete patterns:
- Customer self-service. Customers want to check inventory, order status, or invoices without calling. They don't need SAP's interface — they need a narrow, purpose-built view of a few tables.
- Vendor collaboration. Vendors need to confirm purchase orders, submit shipping notices, or update pricing. Giving them a SAP login exposes far more than they need (and costs a license).
- Field or warehouse access. Staff need a simple, mobile-friendly screen for one task — receiving, picking, or a quick lookup — not the full SAP client on a handheld device.
- Public or semi-public information. Anything that needs to be reachable without a VPN or a SAP client installed at all.
Why a portal instead of "just give them access"
A purpose-built web portal, integrated through the SAP Business One Service Layer or DI API, gives you control over exactly what's exposed, how it's authenticated, and how it's presented — without licensing external users as if they were employees, and without exposing SAP's full interface (and everything reachable from it) to people outside your organization.
What to check before building one
- Which specific data and actions does the outside party actually need? Scope creep here quickly turns a small portal into an unofficial second ERP client.
- Does the integration need to be read-only, or does it need to write back to SAP (orders, shipping confirmations)? Write-back changes the integration approach and the testing required.
- Who owns keeping the portal in sync if your SAP Business One version or add-ons change later?
If you're weighing this against a direct database connection instead of going through SAP's supported integration layer, see our companion piece on choosing between direct database access and API integration.
TODO: Add any client-approved examples of SAP Business One portals you've built, and note which SAP Business One versions and integration methods (Service Layer, DI API, B1if) you have direct experience with.