Questions to resolve before a Serbia-connected development project

The useful answer depends on the actual task and the systems involved. These questions explain how we approach that investigation and where decisions remain with your organisation or an external provider.

Must an existing website be replaced?

No. A catalogue may need clearer relationships between products and drawings while its editing system remains suitable. An application may have one repairable failure. We inspect the symptom, available code, dependencies and receiving task before comparing a focused change with replacement. The repair service describes that assessment.

Can customers use Serbian Latin, Cyrillic and English?

The project can include the language editions the audience needs, subject to an agreed scope and suitable content review. Your nominated reviewer approves meaning, terminology and commercial promises. We implement the content structure and publication behaviour. A language switch or a technically valid text file does not establish translation quality.

Technical project communication is in English unless another arrangement is agreed. Also decide how language expectations are handled when a customer reaches a provider interface, a download or later support.

Do we need customer accounts for a catalogue?

Only when the intended task needs them. Public specifications and an enquiry may be sufficient. Restricted drawings, customer-specific records or recurring protected actions can justify an account area. We define the represented organisation, permitted records and action authority before building the screens. Removing a menu link alone is not an access-control rule.

Can you connect IPS payments or electronic invoicing?

We can investigate an agreed integration using the relevant current documentation and account facilities. The merchant, bank or provider must confirm the actual arrangement. Your finance and professional advisers resolve document treatment and applicable obligations. No general development service establishes eligibility or compliance.

Checks use provider-permitted test facilities and designated data. A later operational verification, if needed, must follow provider rules as well as the business's authorisation. Project approval alone is not permission to send live test transactions.

What happens when a transfer or payment result is uncertain?

The design should identify the record to inspect and the person responsible for resolving the uncertainty. A returned browser page, transport acknowledgement and completed business action can mean different things. We agree the state labels, receiving evidence and permitted next steps. Blindly repeating an operation is not an adequate recovery plan.

Can old customer records and attachments move to a new system?

A migration begins with the datasets, authority to retain them and relationships staff still need. We agree transformations, trial imports and reconciliation. Serbian text, leading-zero references and attachments deserve representative examples. The final update window, late changes and recovery decision also belong in the scope. Migration planning covers that work.

Does an accessibility review certify the website?

The service examines agreed tasks using suitable tools and human checks. It can identify and repair specific barriers, including keyboard interaction, labels, errors and layouts with approved Serbian text. The evidence records what was examined. It does not automatically establish universal accessibility or provide a legal opinion or professional certification.

Who controls the accounts after handover?

Your organisation retains its domain, hosting and provider accounts. We agree the access needed for the work, who maintains the delivered system and how unnecessary access is removed. Ownership, source deliverables, subscriptions and support must be explicit in the project agreement.

How are budget and release timing decided?

We need the intended result, current system condition, source material and important dependencies. A missing provider facility or unavailable content reviewer can change the practical plan. The proposal defines deliverables and exclusions; a substantial new finding is discussed before expanding the work. See scope and cost.

What is enough for an initial conversation?

Describe one customer or staff task, the result that is difficult to trust and who can explain the correct outcome. Public or sanitised examples are enough to begin. The contact page explains what to include, while the release planner helps identify the next reviewer or provider conversation.