Service · Websites and web applications

Customer portal

In many companies, customer service spends half the day re-sending information that already sits in a system. “Where is our order?” “Could you send last month's invoice again?” “We need the dispatch note as a PDF.” Imagine a logistics firm in Gebze handling storage and distribution for several dozen business clients. Those clients want to see live stock, pending shipments, e-İrsaliye documents and monthly service invoices. All of that is already in the firm's WMS and accounting software, yet every request still needs a staff member to fetch and forward it. A customer portal removes the middle step: clients see their own data, when they want, behind a secure login.

Self-service
order status, documents and requests together
Two-step sign-in
required for every user
Roles on the client side
separate admin and standard users
Live data
pulled straight from ERP, WMS or CRM

What the work covers in practice

The questions your team answers most often decide what the portal contains. A typical first version includes the following.

Agree the scope with the engineer who will do the work

Secure login and user management

Email and password with two-step verification by app or SMS, and single sign-on through Microsoft Entra ID or Google for corporate clients who want it. The client's own admin adds and removes colleagues.

Order and job tracking

Open orders, production or shipping stage, planned delivery date and carrier or vehicle tracking. Clients are notified automatically when the status changes.

Documents

Invoices, e-İrsaliye documents, contracts, technical sheets and certificates listed per client and ready to download. Files arrive from your systems automatically, so no one uploads them by hand.

Requests and support

New orders, samples, returns or complaints are raised through forms, routed to the right team, and tracked by the client inside the portal. Email threads are attached to the request.

Account summary

Open invoices, overdue items and recent payments. For reconciliation, the client's accountant downloads the period statement unaided.

Logging and KVKK

Every document access is logged with user and time. Portal users get their own privacy notice, and no personal data is collected beyond what the portal needs.

How we approach the job, from first call to handover

We begin with the requests your staff handle most often. They define what version one must do.

01

Request analysis

We sort the last few months of client emails and requests into categories. The five most frequent questions form the scope of the first release.

02

Data sources

We decide which system supplies each item: ERP, WMS, accounting or CRM. API or database connections are set up with narrowly scoped permissions.

03

Pilot clients

The portal opens first for two or three willing clients. Screens and notifications are refined based on their feedback.

04

Roll-out

Invitations go to every client along with a short guide and video. In the first months we track together how far incoming questions have dropped.

A portal is only as good as the freshness of its data. If order status lags by a day, a client checks the portal, then emails or rings anyway, and the portal is soon abandoned. We therefore avoid overnight file exports and read data from the source in real time or at intervals of a few minutes wherever possible. Where the source system cannot support that, the portal clearly states when the data was last updated.

Frequently asked questions

Usually yes. Logo, Mikro, Netsis and similar systems can be connected through an API, database views or scheduled exports. We avoid writing directly into the database and work with read-only access wherever we can.

Adoption depends on how useful the portal is from the first login. Put the information clients ask for most into version one, and reply to email requests with a portal link, and the habit usually settles within a few months.

No, it is a web application that works comfortably on phones, so there is no app store process or extra update burden. If helpful, it can be offered as a web app that users pin to their home screen.

The portal runs on a server opened in your company's name in a data centre in Turkey or the EU. If client data would be transferred abroad, we suggest reviewing that with your KVKK adviser.

Plan your customer portal

Tell us what your clients ask most often and which systems hold that information. Within one working day we suggest a time for a first conversation.

Availability
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Calls
By video, over Microsoft Teams or Google Meet

The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.