360Portal — self-service portals for ERP customers.
Self-service customer and vendor portals on top of Microsoft Business Central. Order tracking, document access, real-time inventory — without exposing the back-office system.
360Portal turns your Business Central data into a polished customer and vendor portal. Order status, document access, real-time inventory, multi-tenant from day one. Built for mid-market companies that have outgrown email and spreadsheets but don't want to rebuild from scratch.
Currently in beta with the first cohort. Launches publicly on 360portal.io in Summer 2026.
Live BC data, no plumbing
Connects via the BC API; deploys in days, not months.
Multi-tenant from day one
One platform, many customers, complete data isolation.
Configurable, not custom
Your branding, your workflows, no code changes per tenant.
Who it's for
Not a CMS, not a CRM. A focused self-service surface bolted to your ERP for the people who already work with you.
Customers who reorder weekly
Order status, lead times, invoice history, real-time inventory by SKU, document downloads. Cuts inbound "where's my order" calls roughly in half from the day you turn it on.
Vendors confirming POs
Suppliers see open POs, confirm shipment dates, upload packing lists. Replaces the email thread that purchasing manually copies into BC every Tuesday.
Field crews + customers
Daily intervention reports, equipment status, safety check-ins from a phone. Customers see job history + invoices for their site without calling the office.
Architecture, in one paragraph
360Portal reads BC via the official API in real-time for hot data (order status, inventory) and via a scheduled snapshot for cooler data (document indexes, customer master). Writes from the portal — vendor PO confirmations, intervention reports, document uploads — go through a one-step approval queue before they post into BC, so the back-office stays the system of record. Identity is handled by Entra B2B for corporate customers, or per-tenant email + magic link for everyone else. Multi-tenant from line one of code: one platform handles many customers with complete data isolation, configurable per-tenant branding, and a shared ops/monitoring footprint.
Beta cohort — frequently asked
What's the catch with "first cohort, €0"?
No catch. We're shipping our first paying-tier launch and want a small group of real customers running on it before we open the price list. You get hands-on setup at no charge in exchange for honest feedback during the beta — and if you're willing, a quote we can put on the page when the public site goes live.
Can the portal write back to BC?
Yes, scoped per workflow. Common write paths: vendor PO confirmation, intervention report posting, document attachment to a sales/purchase header. Every write goes through a one-step approval queue so the BC user (not the portal) is the journal author of record.
What about custom fields and dimensions?
Configurable per tenant via a JSON map. Add a custom field on the BC sales header and surface it as a column in the customer's order list — no code change, no redeploy. Dimensions follow the BC global + project dimension structure as-is.
What's the public pricing model going to look like?
Per-tenant flat with a portal-user tier. We'll publish on 360portal.io when the public site goes live. The beta cohort gets locked-in pricing for the first 12 months once we publish.
Beta cohort — €0
The first companies onboarding before public launch get hands-on setup at no charge in exchange for honest feedback. Limited slots; cohort closes when 360portal.io goes live.
Related: Mijnuren for time tracking · all SaaS solutions.