Orders and requests
An agreed list of records, statuses and actions. We decide who creates and updates each record, and show success only after the operation has been confirmed.
ERITKOM / Customer portal development
Give customers and partners a place to follow orders, exchange documents and manage requests. We define who can do what before building the interface.
Every feature should serve an agreed business task. We discuss the requirements and boundaries before implementation.
An agreed list of records, statuses and actions. We decide who creates and updates each record, and show success only after the operation has been confirmed.
File exchange with agreed formats, limits and retention rules. Server-side checks protect each record and operation, including requests made through direct links.
Customer, partner and staff access are defined separately. CRM and accounting connections depend on available interfaces, data ownership and repeat-delivery rules.
We test mobile workflows, invalid input and cross-account access. The proposal defines the test environment, launch steps and ongoing support boundaries.
These ERITKOM products demonstrate different application scenarios. They are not client case studies or a promise of identical results: your project scope and integrations are agreed separately.
A register, deal approval and acknowledgement tracking. An example of connecting documents, roles and workflow in a web application.
Explore Insider ↗Scheduling audio and video content across retail locations, controlling playback and monitoring locations. Russian software registry entry No. 21757 dated 7 March 2024.
Explore Zvukovod ↗We agree what is included before development begins, test the key scenarios and prepare the handover.
There is no fixed price list for custom development. We estimate the scope, number of pages, integrations, content and testing effort, then agree the stages and price before starting. Third-party licences, equipment and additional services are quoted separately when required.
We assess its architecture and authentication first. Depending on the constraints, the account can be part of the website or a separate connected service.
A customer account focuses on one customer or partner and their records. A broader portal may bring together multiple audiences and workflows; that requires its own architecture.
We estimate the roles, workflows, documents and integrations before agreeing stages and price. There is no fixed price list; external licences and services are identified separately.
Tell us what you want to launch or improve. We will discuss the next step and the scope. Please do not send passwords or confidential customer data through this form.