Identify the configuration covered by the evidence
Record the operator, proposed games, system version and material integrations. Match the laboratory evidence and the authority's requirements to that configuration. A certificate associated with a supplier's product family may not answer every question about the deployment being purchased.
The project plan should distinguish preparation for testing, completion of testing and the applicable regulatory acceptance. They are related milestones, but they are not interchangeable.
Control changes between testing and launch
A release can differ from the configuration described in its evidence. Catalog additions, wallet changes or revised integrations should therefore trigger a review of whether further assessment is needed.
As a practical procurement check, ask the delivery team to identify the tested build and show how it corresponds to the proposed production build. Record any difference and the party responsible for resolving its approval implications.
Scope the work around the outstanding stage
Discuss your Portugal project with SuperBluOrange using the license status, available reports and planned configuration. We can define the implementation work relevant to the remaining steps. A general claim that software is suitable for Portugal should not replace evidence for the actual operator and deployment.
Last source review: October 17, 2026. Recheck applicable rules before committing.