Services

Portals that replace the inbox queue

Every question a client can answer themselves is an email your team never handles.

A web portal is where your organisation stops answering the same questions by email. Clients log in and see their orders, invoices, contracts and tickets; partners check stock, place orders and download price lists; employees submit requests and find documents — all against live data from your existing back-office systems, all with proper access control deciding who sees what. We build portals for European companies as the self-service layer over ERPs, CRMs and line-of-business databases, and the craft is mostly invisible: identity and permissions done rigorously, integration that shows real-time truth rather than yesterday’s export, and an interface plain enough that customers use it instead of calling anyway. The result reads directly in support volume, in the questions your team stops answering twice.

Let’s talk about your project

Message us on WhatsApp or send an email — you talk directly to a developer.

Message us on WhatsApp Send an email

office@northdan.com · +40 752 070 247

What you get

Live data, not nightly exports

The portal reads your ERP and databases through APIs in real time — what the customer sees is what your operations team sees.

Access control to the field level

Roles, organisations and per-document permissions ensure each login sees exactly its own world — auditable, GDPR-conscious, tested.

Fewer tickets, faster clients

Status checks, document downloads and standard requests move to self-service around the clock — your team keeps the cases needing judgment.

The kinds of portal we build

Customer portals showing orders, invoices, contracts, deliveries and support history against live back-office data. Partner and dealer portals with stock visibility, ordering, price lists and margin rules that differ per account. Supplier portals for purchase orders, confirmations and document exchange. Employee portals for requests, approvals, documents and internal knowledge.

What they share is identity done rigorously — single sign-on where you already have it, permissions decided per field rather than per page, and an audit trail of who saw and changed what. The second shared requirement is that the data is live: a portal showing yesterday’s export teaches users to phone anyway, and once that habit forms the project has failed regardless of how it looks.

Frequently asked questions

Can the portal connect to our existing ERP?

Almost always — through its API where one exists, or a secure integration layer we build where it does not. The portal is designed as a window onto systems you keep, not a parallel database to maintain.

How do users log in — do we manage more passwords?

Options range from classic email accounts with two-factor to single sign-on with Microsoft or Google for B2B users — chosen to match your clients’ reality, with self-service password recovery throughout.

What does a portal project typically look like?

A first release in two to four months covering the highest-volume use cases — usually order status, invoices and documents — then expansion guided by what usage analytics show clients actually need next.