Service · Websites and web apps

Client portal

Good portals grow out of your service inbox. Look at what people ask most: has my delivery left, please resend the invoice, same again as in March. Each answer a customer finds unaided gives your team minutes back. And the customer gets it at ten on a Sunday evening instead of waiting for Monday morning.

Orders
status and reordering in one place
ERP
data from your own systems
2FA
or company sign-in
Documents
invoices, delivery notes, contracts

Included in this service

We judge every candidate feature by one yardstick: how many support messages will it absorb?

Talk the scope through with an engineer

Sign-in

One-time email codes, two-step verification, or Microsoft Entra ID single sign-on for corporate clients tired of juggling passwords.

Orders

Items, agreed prices, fulfilment stage, parcel tracking and a “Buy again” shortcut.

Documents

Invoices, WZ dispatch notes, certificates and contracts fetched from Comarch ERP XL, enova365, Symfonia or Business Central, available as PDF or the original KSeF XML.

Trading terms

Personal price lists, discounts, credit ceiling, current account balance and the assigned sales contact.

Users and permissions

Client administrators add colleagues and control visibility: finance staff see invoices but not the basket, warehouse staff place orders but never see balances.

Notifications

Email or text alerts about status changes, approaching payment deadlines and new documents, removing the need to chase.

How we work together

Whether your ERP already offers an API, or data must first be extracted, largely sets the pace.

01

Enquiry analysis

Three months of support emails and tickets are sorted to reveal recurring questions. Solving those is the portal's purpose.

02

Design

Roles, access rights, sections and data exchange with your back-office software.

03

Build

Screens, authentication, integrations and alerts, trialled on data from several genuine customers.

04

Roll-out

A pilot group is invited, given a short guide, and we count how far support traffic drops.

Customer portals hold personal data, which brings GDPR fully into play. Expect data minimisation, audit trails of access, EU hosting, processor agreements and a routine for access and erasure requests. Baking that in at the design stage is far cheaper than retrofitting it once a client or the Polish supervisory authority (UODO) starts making enquiries.

Questions and answers

They will if it fixes something real: tracking a delivery, grabbing a document, repeating a purchase. A portal offering only a profile page and blank history attracts no one and is not worth commissioning. Small nudges help, such as emailing a link to the invoice in the portal rather than attaching the file.

Not for everything. Balances and stock should be live, while invoice archives can refresh a few times daily. That mix lightens the load on the ERP and keeps the portal online even during accounting-system maintenance.

Seldom. A portal that behaves well in a mobile browser covers the same ground with no download and no app store approval. Native apps earn their keep when push alerts or offline use matter, say for field sales reps.

Strong authentication is mandatory, repeated failed logins lock the account, document downloads are logged with user and timestamp, and idle sessions time out. A security test precedes launch, and you receive its findings in writing.

Plan a portal your customers will use

List the questions your support team hears most. We will design the portal to answer precisely those.

Hours
Mon-Fri 8:00-18:00 CET, reply within one working day
Meetings
Online via Teams or Google Meet

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.