Regulations for Paid Configuration Services in 4logist
These Regulations define the procedure for submitting requests and the conditions for assessing, performing, and accepting paid configuration services in 4logist.
Paid configuration services are individual changes to a client’s database configuration that are performed manually by a specialist and do not constitute standard system support or the correction of a technical error.
Request Submission Procedure
Requests for paid configuration services are accepted only in writing:
– by email at help@4logist.com;
– through official messengers agreed upon as communication channels with the company.
Verbal agreements, voice messages, comments without a clearly defined task, and separate requests scattered throughout a conversation are not considered a valid task description.
A request can be accepted for assessment only if a properly prepared technical specification has been provided.
Before estimating the cost, a specialist will first check whether the requested change can be technically implemented in the system.
What Is Considered a Paid Configuration Service
Paid configuration services include changes that require a specialist to manually modify the client’s database configuration.
Such services may include:
– modifying forms;
– adding, editing, or hiding fields;
– making fields required or optional;
– renaming fields;
– changing the position of elements in forms;
– adding or modifying custom fields;
– modifying tables;
– adding, hiding, or changing the order of columns;
– changing the structure of Excel exports;
– changing the data displayed in exports;
– making individual adjustments to settings that the client cannot change independently through the system interface.
If you are unsure whether your request qualifies as a paid configuration service, please contact Technical Support. A specialist will review the request and advise whether you can make the change yourself or whether a separate paid configuration service is required.
System Configuration Limitations
System configuration options are subject to certain technical and logical limitations.
Not every client request can be implemented through an individual database configuration. The possibility of implementation depends on the current system architecture, available configuration parameters, data structure, access rights, section logic, and interface limitations.
Before estimating the cost, a specialist will check:
– whether the requested change is technically possible;
– whether the request conflicts with the system’s standard logic;
– whether the change may affect other sections of the system;
– whether the change may cause data to be displayed incorrectly;
– whether the configuration can be completed without individual software development.
If the requested change cannot be implemented using the available system settings, Technical Support will inform the client accordingly.
A paid configuration service does not guarantee that any requested change can be implemented. Technical feasibility is checked first, and the cost is estimated only after this check.
Technical Specification Requirements
To request a paid configuration service, the client must provide a technical specification containing a complete description of the required changes.
The technical specification must state:
– which section of the system needs to be changed;
– which fields, columns, forms, or exports need to be added, hidden, or modified;
– what the expected result should look like;
– whether a field should be required;
– which users, groups, or scenarios the configuration should apply to;
– which data should be displayed;
– whether any conditions apply to displaying the data;
– whether an example of the expected result is available.
The following descriptions are not sufficient:
– “Add a field”;
– “Change the table”;
– “Make it more convenient”;
– “Add the required data”;
– “Let’s try it this way and see how it works.”
The following information must be specified:
– the section of the system where the change should be made;
– the exact field or column that should be added;
– its required name;
– where it should be displayed;
– which data it should contain;
– the expected result after the configuration is completed.
If the request does not contain sufficient details, it will be returned to the client for clarification.
Assessment of Feasibility and Cost
After receiving the technical specification, a specialist will conduct a preliminary assessment of the request.
The assessment includes:
– reviewing the client’s current database settings;
– checking technical feasibility;
– determining the scope of work;
– assessing whether testing is required;
– checking the possible impact of the change on other system elements.
After the assessment, Technical Support will inform the client:
– whether the configuration is possible;
– which changes can be implemented;
– whether the technical specification needs clarification;
– how much the work will cost.
Paid configuration services are provided at the current service rates. Please contact Technical Support to confirm the applicable price.
The cost depends on the scope and complexity of the configuration, the number of changes, the required scenario testing, and the amount of manual work involved.
Cost and Payment Procedure
Individual system configurations are provided on a paid basis.
The terms of service and payment procedure are governed by the applicable agreement and terms of service.
After receiving a complete technical specification:
– a specialist checks whether the configuration is technically possible;
– the required effort is estimated;
– the cost is calculated;
– the cost is agreed upon with the client.
Work begins only after the cost has been approved and the applicable payment conditions have been met.
If the client changes the requirements or adds new items after the cost has been agreed upon, the task must be reassessed.
Completion Time
The completion time is determined after the technical specification has been assessed and depends on the scope of work, the complexity of the changes, and the specialists’ current workload.
The completion period begins after:
– a complete and approved technical specification has been received;
– the cost has been confirmed;
– the applicable payment conditions have been met.
The completion time may be extended if:
– the technical specification is incomplete or incorrect;
– the requirements change while the work is in progress;
– additional approval is required;
– technical limitations are identified;
– additional testing is required.
If the task is changed after work has started, a new assessment will be prepared.
Testing and Acceptance Procedure
After the configuration has been completed:
– the specialist performs an internal check of the result;
– the client is notified that the work is complete;
– the client checks the completed changes in their database.
The client has three business days from the date of notification to check the result and submit any comments.
If the comments relate to the originally approved technical specification, the required corrections will be made at no additional cost.
If no written feedback is received within three business days, the work is considered accepted.
Comments submitted after this period, as well as requirements that were not included in the original technical specification, are treated as a new task and processed under the standard procedure: a new technical specification, a new assessment, and a new payment.
Additional Changes After Completion
Each paid configuration service is performed strictly within the scope of the approved technical specification.
If the client requests additional changes, asks to modify the previously approved logic, or wants to try a different configuration after the work has been completed, the request will be treated as a new task.
Each new change requires the database configuration to be reassessed, updated, and tested.
Additional changes are not considered a continuation of the completed work unless they were included in the original technical specification.
What Is Not Considered a Paid Configuration Service
Issues related to technical errors in the system are not considered paid configuration services.
If a feature does not work correctly, an error occurs, or the result does not correspond to the system’s standard logic, Technical Support will handle the request under the standard support procedure.
Guidance on using standard system features is also not considered a paid configuration service if the client can perform the required action independently through the interface.
Limitation of Liability
The Service Provider performs the configuration strictly in accordance with the submitted and approved technical specification.
The Service Provider is not responsible for:
– incorrectly formulated requirements in the technical specification;
– an incomplete description of the expected result;
– missing information about the required section, field, table, or export;
– changes to the requirements after the work has been approved;
– issues reported after the specified acceptance period;
– changes to the client’s business processes after the work has been completed;
– the inability to implement requests that conflict with the system’s technical limitations.
If the assessment shows that the requested change cannot be implemented using the available system settings, the task will not proceed until further actions have been agreed upon with the client.
General Provisions
Each paid configuration request is treated as a separate task.
Any changes to the requirements after the work has been approved or completed must be submitted as a new technical specification.
These Regulations are intended to ensure:
– clear and unambiguous requirements;
– transparent cost and time estimates;
– a clear division of responsibilities between the parties;
– fewer repeated revisions;
– agreement on the expected result before work begins.
To confirm whether a configuration is possible and obtain the current service rates, please contact 4logist Technical Support.
Was this helpful?
0 / 0