Marcus Biel.

Custom B2B and self-service portals

Customer portals for orders, documents and service requests

Customers often call to ask three things: where their order stands, where to find a document, and whether anyone has answered their question. A portal can put all three on the order itself.

I design the portal around the tasks your customers want to handle themselves. I build it around the records you already keep and the permissions each person needs.

What customers can do in a portal

Start with the things customers already call or email about.

An order’s status, a missing invoice, or a question about delivery can be much easier to handle when both sides are looking at the same record.

View orders and their status

Customers can open an order to check its status, look up a delivery date, or see what’s happening with a related service request.

Together we decide what to display, which system supplies it and how current it needs to be.

Download documents

Customers see the quotes, order confirmations, invoices, and technical documents they’re authorized to access for each order.

Customers can find and download the documents they need in one place.

Place or repeat an order

Customers can prepare and submit recurring orders, repeat orders or requests for quotes in the portal.

The portal can show the items and terms that apply to each customer, request any required approvals, and send the order into your existing workflow.

Ask a service question about a specific order

Customers can ask about a specific order, product, or contract and attach the documents your team needs.

The link to the original record gives your team the context it needs to answer through the normal service workflow.

From signing in to answering an order question

Connect your portal to ERP, CRM and business applications

A portal draws information from the systems your business already uses, including order management, ERP, CRM, document management or custom applications.

For each type of record, I work through a few questions.

  • Source of record. Which system owns customer details, orders, documents and status updates?
  • Integration. Which interfaces or import options are available?
  • Update frequency. When will changes appear, and how will customers know when their order was last updated?
  • Changes made in the portal. What can a customer submit or edit? Which changes need approval?
  • Failed updates. What will customers and staff see if a change is rejected or never reaches the other system?

Those decisions determine how the portal connects to the software you already run.

More about APIs and system integration

Who can see and change what?

Who can see order A-1042?

Purchasing at Werkstatt Nord
Lea can see the company’s orders, download its approved PDF and reply to S-73. Staff notes are private.
Werkstatt Nord’s reseller
The partner can see the status of assigned customers’ orders and raise a separate question. The purchase document, S-73 and internal notes stay private.
Your customer service team
Staff can see the full order, release a document to the customer, answer questions and write internal notes.
A different customer
A-1042 is outside that account’s permissions, including in search results and via a direct link.

Several people at a B2B customer may need different permissions. One might read documents, another place orders, and another manage users.

I build roles around those tasks, link users to the correct company and cases, and check what each person can read or do.

I also cover the account lifecycle, including invitations, activation, changes in permissions and disabling access for people who leave.

If you already use central identity management, I assess how to integrate it.

What to include in a first release

Together we choose a common customer workflow and define the tasks the first release should support from start to finish.

For example, your first release could include

  • a personal login for each customer employee, linked to their company
  • a searchable list of orders or requests
  • an order page with the details and documents the customer can access
  • a way to ask a question about that order
  • a connection to the system that owns the records

Before I start building, you can try the main screens and workflows. I account for customers’ devices and the work your team will do to administer the portal.

I test with realistic accounts, orders, and requests. Before launch, I work with your team to make sure customers know how to get access and where to go for help.

Once customers start using the portal, their questions and feedback help you choose the next features.

Plan your first portal release

Who will build your customer portal?

I’m Marcus Biel. I’ve worked on Java applications since 2001.

I’ll work with the people who handle customer orders and service requests, design the portal, and help write the code. I can join your developers or bring in specialists as needed.

You can try the first screens yourself and tell me what to change before I build the rest.

More about working with Marcus
Marcus Biel
Marcus BielSoftware developer and architect

What affects the time and cost?

For an estimate, I look at the first customer workflow, which roles need access, and the systems the portal needs to connect to.

Other factors include data quality, approvals, existing customer accounts, and how you plan to design and run the service.

I quote for a first release your customers can use and outline what could come next, so you can decide which additions are worth the cost.

I include hosting, support, and future releases in that conversation.

What would you like customers to do for themselves?

Tell me who the portal is for, what they need to do, and which system holds the information today.

Together we’ll define a first portal release that fits your business.

Other project inquiries: Connect an ERP or CRM.

Prefer to talk first? Call +49 171 1151013 or message me on LinkedIn.

Discuss a customer portal