Review whether source-code access, modification rights and delivery conditions fit your project, with the scope defined by agreement.
Not just getting a copy of code. You gain ultimate control of the system. No limits from here on
Consider whether source-code access is suitable for your product model, technical team and business plans
Discuss the level of access and modification rights available for the specific cooperation arrangement
Review how the intended operating environment may affect source-code use and project implementation
Separate the responsibilities for development, testing, updates and technical decisions within the project
Identify the materials, access arrangements and handover items to be discussed for the project
Confirm permitted use, modification, support and delivery conditions through project discussion and contract terms
Source-code cooperation may be relevant for POS providers with an established technical team, a product roadmap, or a need to review and adapt selected parts of a system. The suitable scope depends on the project
Before any source-code arrangement is confirmed, both sides should discuss access methods, modification work, testing, documentation, ongoing support and the conditions for delivery
Review what your team needs to access, modify, test or maintain before defining the cooperation scope
Keep technical work, handover items and contractual delivery conditions clear during project discussions
Source-code access, modification rights, support and future arrangements are discussed according to the specific project and agreement
Share your technical plans and intended use case to discuss a suitable source-code arrangement