Skip to content

Solution

Customer portal with ERP integration

A customer portal gives your customers self-service access to orders, delivery status, documents and invoices, and takes reorders and enquiries in structured form. It is connected to ERP and CRM, so the information is correct. Your sales support team gains time for the cases that really need a conversation.

Who it is for: For manufacturers, service providers and fiduciaries with recurring customers and many status enquiries.

Starting point

How the process runs today

Customers phone and email to ask about delivery dates, invoice copies, certificates and the progress of their orders. Sales support looks it up in the ERP and replies. Documents are sent as attachments and then hunted for again at the customer's end. This ties up staff and looks dated next to digital competitors.

What it costs

  • A large share of calls are questions the ERP could have answered long ago.
  • Documents are sent several times because the customer cannot find them.
  • Reorders arrive informally and have to be interpreted.
  • Key accounts demand a portal as a condition of doing business.

Process

What the process looks like afterwards

  1. 01

    Sign-in

    Your customer signs in securely and sees only their own company's data.

  2. 02

    Overview

    Current orders, delivery dates and open invoices on one page.

  3. 03

    Documents

    Invoices, delivery notes and certificates are available to download.

  4. 04

    Action

    Reorder, report a complaint or upload documents.

  5. 05

    Synchronisation

    Everything ends up in the ERP or CRM and with the person responsible.

What customers can see and do in a customer portal: three stages

A customer portal does not have to be built in one go. We recommend starting with stage 1 and expanding once usage is right. Each stage builds on the previous one. Prices are guidelines excl. VAT, binding with the cost ceiling from the preliminary study.

Your customers look things up instead of calling. Guideline CHF 25,000 to 40,000.

  • Secure login, each company sees only its own data
  • Open orders with status and delivery date
  • Delivery notes, certificates and other documents to download
  • Open and paid invoices, every copy as a PDF
  • Connected to your ERP

Security and login in a customer portal

Each company sees only its own data. This separation is built into every data query and verified with automated tests. It does not depend on someone setting permissions correctly.

Within a customer's company, roles govern who may do what. We recommend a main user at the customer who invites colleagues and removes them again. If someone leaves the company, the customer blocks their access immediately, without involving your sales support team.

Login includes a second factor, such as a code from an app on a smartphone. From stage 3, your customers' staff sign in with their existing company account. The customer's IT then decides who has access, and leaving the company also blocks access to the portal.

The Swiss e-ID does not replace the login. It identifies people, not companies or signing authority. Once it launches, it can complement registration or account recovery. The launch has been postponed and has no date yet. So plan your login today with two-factor authentication or company accounts.

How to measure whether a customer portal pays off

Whether a portal pays off shows in a few figures you can already count today. Count for two weeks before the preliminary study and again three months after launch. Without a baseline, the benefit remains a guess.

  • Status enquiries: how many calls and emails ask about a delivery date or order progress? A tally sheet in sales support is enough.
  • Sending documents: how often do you send invoice copies, delivery notes or certificates on request? After launch, compare this with downloads in the portal.
  • Reorders: how many arrive informally by email or phone, and how often do you have to ask for details? After launch, what counts is the share that arrives complete through the portal.
  • Usage: how many of your customer companies sign in at least once a month? This figure shows early on whether the portal is being adopted.

An example with assumed figures: your sales support team counts 250 status enquiries in two weeks. Three months after launch, there are 150 in two weeks. That matches the target of 40 percent fewer status enquiries. At about eight minutes per enquiry, your team gains a good 13 hours every two weeks.

If the drop is much smaller, first check whether your customers know about the portal. Point to it on every invoice, for example.

Project timeline: a customer portal in 10 to 24 weeks

  1. Weeks 1 to 3

    Preliminary study with cost ceiling

    We define the stage, the features for launch and the connection to ERP and CRM. You receive a cost ceiling. Fixed price CHF 4,000 to 9,000.

  2. From week 3

    Clickable prototype with pilot customers

    A clickable prototype shows what your customers will see. Two or three pilot customers give feedback before any code is written.

  3. From week 5

    Delivery in stages

    Login and order overview first, then documents and invoices, then the features of your stage. Each step can be tested on its own.

  4. Before launch

    Pilot operation

    The pilot customers work with real data. Your sales support team checks that status and documents are correct and collects questions.

  5. Weeks 10 to 24

    Launch for all customers

    Your customers receive an invitation. A note on invoices and in your email signature makes the portal known.

  6. 3 months after launch

    Review and expand

    You compare the figures with the baseline and decide whether and when the next stage follows.

Integrations

Which systems are connected

The portal holds no truth of its own. Orders, documents and customer data stay in the system of record and are read and written there.

ERP and accounting
  • Abacus
  • bexio
Calendar and collaboration
  • Microsoft 365

Make or buy

Off-the-shelf or custom?

Off-the-shelf software is enough if

  • Your ERP's portal module shows what your customers need to see.
  • All that is needed is access to invoices.
  • Few of your customers need a portal.

Finished products for this case: Portal modules from the ERP vendors, helpdesk portals and the customer accounts of common shop systems.

Custom is worth it if

  • Data from several systems should come together in one view.
  • Your customers have their own roles, sites or cost centres.
  • The portal should carry your branding and fit your offering.
  • Orders, approvals or uploads need their own workflows.

Effort

Price range and duration

Price range
CHF 25'000 to 80'000
Duration
10 to 24 weeks

Non-binding estimate, excl. VAT.

What drives the effort

A portal with an order overview, documents and one ERP integration sits in the lower range. Additional customer groups, roles and systems increase the effort.

The price becomes binding after the fixed-price discovery phase.

Customer portal with ERP integration

Frequently asked questions

How secure is customer data in the portal?

Each customer sees only their own data, enforced at the level of the database queries and verified with automated tests. On top of that come two-factor sign-in, encrypted transmission, access logging and hosting in the EEA.

Will our customers actually use a portal?

If it saves them work, yes. Portals get used when they answer the most common requests faster than a phone call: order status, documents, reordering. That is why we start with two or three functions and measure usage before adding more.

Can users sign in with their existing company account?

Yes. Portals can be connected to Microsoft Entra ID, Google Workspace or other providers using OpenID Connect and SAML. For external customers we set up a sign-in with two-factor authentication.

Let us talk about your case.

20 minutes are enough to find out whether a custom solution is worth it for you.