Frequently Asked Questions

Yes, for invitation-based procedures: e-Request supports compliant, transparent tendering under “Einladungsverfahren” (VöB / VOL/A UVgO), with an activity log and role-based access. It is not designed for WTO-scale public tenders.

That depends on the deployment model. For Cloud SaaS we set up your instance with a Swiss provider on request; our demo and test environments currently run in Germany. Encryption at rest is not part of the standard setup — where you need it, we agree it in your quote. With On-Premise and Managed Service the data sits in your own infrastructure and you decide the location.

Regardless of the model: transport is TLS-encrypted and the product is GDPR and DSG compliant. Backup concept, SLA and the data processing agreement are settled contractually rather than claimed wholesale on a website.

Most organizations are productive within weeks, not months. e-Request is web-based and self-explanatory — a single training day is typically enough.

Today through signed webhooks (offer.submitted, contract.signed, supplier.approved), CSV/XLS export of lists and the REST API /api/v1. The API is switched on and paid for: it reads tenders, suppliers, offers and categories, and writes tenders, suppliers and categories — offers stay read-only, they are authored in the supplier portal. One API key sees everything in the tenant. Direct ERP connectivity is on the roadmap. For sign-in: OIDC SSO for the buying side against your existing identity provider, as a paid add-on; an IdP that only speaks SAML needs a broker in front.

Yes. e-Request is designed to be self-explanatory; onboarding includes training, and one training day is the stated maximum for a purchasing team.

Support is included in every plan, with priority and dedicated support options for larger organizations. On-Premise and Managed Service customers receive deployment support as well.