Connection to your systems
Read and, where needed, write access to ERP, industry software or ticketing, for example Business Central, SAP Business One or a warehouse or transport management system. Where no API exists, we build a secure data sync.
A portal is only as good as the data behind it. Every project therefore starts at the interface, not at the layout.
Read and, where needed, write access to ERP, industry software or ticketing, for example Business Central, SAP Business One or a warehouse or transport management system. Where no API exists, we build a secure data sync.
Invoices, credit notes, delivery notes, certificates and inspection reports as searchable PDFs filtered by period, optionally also as ebInterface files for the customer accounts department.
Open orders, shipment status, delivery dates and service appointments at a glance, with email notifications whenever something changes.
Complaints, repeat orders or appointment requests through structured forms that land as tickets with the right team and show their progress in the portal.
One lead contact per customer company who invites colleagues and decides who sees invoices and who sees orders only. Two-factor sign-in is standard.
A least-privilege role model, access logging, encryption and an entry for your record of processing activities that slots into your GDPR documentation.
We begin with the questions your team answers most often today. They determine what the first version of the portal must handle.
For two weeks your team notes which customer queries come in by email and phone. The three most frequent topics form the core of release one.
Working remotely with your IT or the software vendor, we establish which data leaves the ERP, how, and how up to date it has to be.
We build the first version and test it with five to ten selected customers willing to give honest feedback. Their questions feed straight into the revision.
Invitations to all customer companies, a short guide and references on invoices and in email signatures so the portal actually gets found.
Portal adoption is won or lost at sign-up. Ask customers to email for access, sit tight until credentials arrive and then memorise one more password, and the majority will not bother. Uptake is far higher when one named contact per client receives a personal link that opens their account straight away, then brings in co-workers on their own. Where the customer runs Microsoft 365, they can sign in with the account they already have. We put as much care into that first step as into the rest of the portal.
No. The portal reads data from your existing system. What it needs is an interface or at least a regular export, and we clarify that in step two before any real effort is spent.
Each company sees only its own records. That separation is enforced on the server and deliberately attacked during testing. Access is logged, connections are encrypted and hosting is in Austria or the EU.
Yes. Reordering from past orders is a common extension. If you need a full range, tiered prices and approval workflows at scale, a B2B platform is the better tool.
The portal then shows the last synchronised data with a timestamp and keeps accepting requests. Once the connection is back, everything catches up.
Name your ERP or industry software and the questions customers ask you most often. We will get back to you within one working day.
Your enquiry has arrived
Our reply reaches you within one working day. Outages that leave your staff unable to work are dealt with first.
We could not find that town. Try another spelling, or choose whichever provincial capital lies closest; as everything is handled remotely, you get the same service in all nine Austrian states.