Confirm ownership of the website source code; do not rely solely on the words “source code delivery” in a quotation. When choosing a website development provider for a trading or export business, first confirm whether the website will use custom development, an open-source system, or a SaaS platform. Then specify the scope of the code, intellectual property ownership or licensing arrangements, delivery format, and migration terms in the contract, and verify them through deployment and acceptance testing.
A common procurement problem is discovering only after the website goes live that it can run only on the provider’s platform, or that the files received are just page files, without the backend application or database structure. Even if the company owns the domain, it may then be unable to maintain the website independently and may have to bear the costs of redevelopment, data preparation, and switching services when migrating.
Source code ownership concerns rights to the code; delivery concerns whether the files can be obtained; and usage authorization determines how the company may use and modify the website. These are not the same thing. A provider’s giving the company a backend account usually means only that the company can manage the website within the agreed scope. It does not automatically mean that the company owns the platform source code or has the right to deploy it independently.
For custom development projects, the company can negotiate with the provider to specify which specially developed code and related rights belong to the company, and which pre-existing frameworks and components remain the property of their respective rights holders. If an open-source system is used, check its license requirements for activities such as modification and distribution. Do not simply stipulate that all third-party open-source code belongs to the company.
SaaS website development typically focuses on access to the platform, and the underlying source code may not be sold or delivered. This does not necessarily mean the solution is unsuitable, but before procurement, confirm whether data can be exported, whether the export format is usable, and what happens to the website and data when the subscription ends. If the source code cannot be migrated, assess the cost of rebuilding the website rather than equating “data can be exported” with “the website can be migrated in full.”

Request a written list and distinguish between custom-developed components for the company, the provider’s existing systems, and third-party components. At a minimum, check the following:
The delivery list should also specify versions and file formats. For example, receiving only HTML files visible in a browser does not mean the backend logic has been delivered; receiving a compressed code package does not mean it includes all dependencies. For anything not being delivered, ask the provider to identify it clearly and explain its impact on the website’s operation.
It is best to put verbal promises in the contract itself or in an attachment approved by both parties. Avoid ambiguous wording such as “all source code provided free of charge” or “the website belongs to the customer forever.” Pay particular attention to the following:
The contract should also list license restrictions on third-party software and assets. A provider should not promise the company full ownership of content it has no right to transfer. The company should assess whether the existing licenses cover its future operational, modification, and migration needs. For complex rights arrangements, consider having a legal professional familiar with software contracts review them.
The key to acceptance is verifying that the deliverables meet the contract requirements. For projects that can be independently deployed, ask the provider to demonstrate the process in an environment approved by both parties: install dependencies according to the delivery documentation, import the database, start the frontend and backend, and then test multilingual pages, inquiry forms, and key management functions. If any part requires an account held internally by the provider to run, document it and agree on an alternative or ongoing authorization terms.
If independent deployment cannot be completed immediately, technical personnel should still inspect the code directories, versions, configuration templates, and database backups, and document acceptance conditions for items that have not yet been verified. A website displaying correctly only proves that it works in its current environment. It does not prove that the delivery package is complete, much less that the site can be reproduced in a new environment.
Separately verify control of the domain registration account, server or cloud resource accounts, website backend, and data backups. The company should preferably control key accounts, with the provider granted access as needed for its work. During handover, check administrator accounts, recovery methods, and associated email addresses to avoid being unable to renew services or recover access after the cooperation ends.
Break each quotation down into website development, source code or licensing, deployment, maintenance, third-party services, and exit and migration costs, then compare them over the same period of use. A higher price for a source code buyout may not cover future server costs, security updates, and technical maintenance. A platform solution may avoid deployment work initially, but renewal, data export, and rebuilding costs should still be included in the budget.
If the company has an in-house technical team and plans to make ongoing updates independently, focus on source code completeness, modification rights, and deployment feasibility. If a fast launch and platform hosting are more important, focus on renewal terms, data portability, and exit costs. For a quotation that offers neither source code nor a clear explanation of data export, request written terms before deciding whether to proceed with the purchase.
Related Articles
Related Products


