Questions before a bilingual website or software project

Does a bilingual project require two separate systems?

Usually the important question is which facts should be shared and which explanations need their own editing and review. A common content model may support both languages, but the right architecture depends on the existing tools and required behaviour. We examine that before proposing a rebuild.

Can you provide Arabic translation and approval?

Arabic translation and qualified language review are separately arranged. Technical project communication is normally in English, and development is delivered remotely from the United States. Publishing Arabic material does not establish local staffing or certified translation services.

Can you repair a site built by another developer?

That can be possible when authorised access to the relevant code, accounts and dependencies is available. The first scope may be an investigation to reproduce the issue and establish what can safely change. Missing access or unsupported components can affect the options.

Which language should an enquiry use?

Technical communication is normally in English. You can describe the Arabic content or interface problem and identify the intended reviewer. Do not send confidential documents to explain a translation issue; an anonymised excerpt or public link is enough to start discussing the work.

Does a document upload mean the file is accepted?

No. Receiving a file, checking its format, reviewing its contents and making a business decision are different steps. A portal should make the relevant distinctions visible. The organisation decides the actual review policy and the meaning of acceptance.

Can a language approval also approve commercial terms?

Only the organisation's authorised process can define that authority. We recommend identifying the question and edition covered by each decision. A linguistic correction should not silently grant authority over an amount, contractual exclusion or professional judgement.

Can you connect our payment provider?

We first verify the provider's supported interface, the actual merchant account and the required operation. Currency display does not establish account eligibility or settlement capability. Applicable commercial, invoice and tax requirements need the responsible reviewers.

What if payment looks successful but the order is uncertain?

The workflow needs a reconciliation route that uses provider evidence tied to the intended order. A browser return or repeated notification alone should not trigger duplicate fulfilment. The precise checks depend on the provider and agreed scope.

Must we build a customer portal?

Not necessarily. A better explanation, controlled use of an existing platform or a simpler document routine may solve the problem. A portal becomes more persuasive when customers need repeatable, permissioned actions that the current arrangement cannot reasonably support.

What happens to personal or confidential information?

Project-specific purposes, access, locations, suppliers, retention and recovery are reviewed before production data is shared. Qualified advisers determine applicable requirements. The initial form is for an enquiry, not a channel for customer datasets, identity documents or credentials.

How are schedules and costs agreed?

They follow the actual scope, available access, content readiness, provider dependencies and review responsibilities. An investigation can clarify uncertainty before a larger estimate. Changes that affect the outcome or assumptions are discussed before expanding the work.

Who maintains the result?

The handover identifies the agreed accounts, editing responsibilities, routine checks and recovery owners. Ongoing support has its own coverage and response arrangements. The handover checklist helps prepare for that discussion.

Read scope and budget, or send the question that affects your project.