Describe the problem in your own words. AI picks the services, solutions and articles on our site that fit it.

    Web Apps & B2B Portals

    A portal where clients order, download invoices and check status themselves

    Clients log in, see their prices and stock, place orders and download documents. Orders go into the ERP and your team takes fewer calls.

    From the first workshop to a client portal

    Shown with an ordering portal for a wholesaler.

    1. 1ScopeWe agree what clients should handle themselves: orders, invoices, complaints, status. The rest waits for later versions.
    2. 2ERP connectionClient prices, discounts, stock and documents come from the ERP. Orders go back to the ERP as documents.
    3. 3Company accountsEach company gets several accounts with roles: who orders, who approves, who sees invoices.
    4. 4Launch with selected clientsA few regular clients get the portal first. Their feedback goes in before it opens to everyone.

    Signs your clients need a portal

    Orders come by email and phone

    Someone in the office types them into the system and chases missing items.

    Status questions eat the day

    Clients call to ask if goods have shipped, and the team checks three places to answer.

    Invoices are sent by hand

    A client asks for an invoice copy or a statement, and someone finds it and emails it.

    Every client has their own prices

    Price lists and discounts are individual, so an ordinary online store won't do.

    The portal uses the systems you already have

    Clients see ERP data, not a copy someone typed in.

    ERP

    Comarch, Subiekt, enova365, Symfonia, SAP Business One: prices, stock, orders, invoices.

    Accounting

    Invoices, credit notes and statements to download as PDF.

    Warehouse and shipping

    Picking status and the courier's tracking number.

    CRM

    The account manager sees orders and requests from the portal.

    Login

    Company accounts with roles, and Microsoft or Google sign-in if the client wants it.

    Technology

    Angular or React on the front end, an API in Node.js, Java or .NET, PostgreSQL.

    How we check the results

    Before launch we count orders by email and phone and status calls. After launch we compare the same numbers.

    1. 1Orders placed in the portal
    2. 2Orders retyped by hand
    3. 3Calls about order status
    4. 4Clients active in the portal

    Portal analytics show where clients give up or still pick up the phone.

    Common questions

    How is a portal different from an online store?

    A portal shows each client their own prices, credit limits and documents, and several people on the client's side can approve orders.

    Will clients actually use it?

    We start with the clients who order most often and shape the portal around their feedback before everyone gets it.

    What if our ERP has no API?

    We connect through the database or file exchange. In the workshop we check which route is safe.

    Can the portal run in English and German?

    Yes. We plan languages and currencies from the start if you have clients abroad.

    Tell us how clients order today

    Let us know how many B2B clients you have, how they place orders and which ERP you use. We reply within one business day.

    Other parts of this service

    Internal systems

    Order flow, warehouse, planning, settlements – software shaped to your process, with real access control.
    I want to know more

    Out of Excel and email

    We move processes from spreadsheets and mail threads into one system. Data is entered once, and everyone sees the same thing.
    I want to know more

    Operational apps and dashboards

    Screens that show the state of the business right now: jobs, deadlines, workload. Instead of a report assembled once a month.
    I want to know more

    Backend, APIs and integrations

    The application connects to the systems you already run – ERP, accounting, warehouse. Designed for the load you have and the load you’re planning for.
    I want to know more

    Takeover of existing apps

    We audit, stabilize and keep developing applications other teams built. Missing tests and docs are our starting point, not a blocker.
    I want to know more