Select hosting around the exact Bitrix release, installed modules and business workflow. A procurement brief should state what the application needs, who operates it and what evidence will confirm that it works.
Inventory the installation
Record the product edition, CMS release, PHP, database and extensions. Compare them with the vendor's documentation for the selected release. Ask the developer to identify custom modules and integration dependencies. A supported base installation does not establish compatibility for a customized project.
Describe background work
List inventory exchanges, indexing, backups and other scheduled jobs. Record startup, duration, expected results and ownership. Confirm whether the service supports the required execution model and how an interrupted job becomes visible.
Compare offers against one brief
Ask for compatible runtime versions, permissions, process limits and database placement. Confirm updates, copies and recovery separately. A project that needs system services must budget for server operations. A prepared image or panel can help with setup, and the actual application still needs acceptance testing.
A store with inventory exchange
Suppose stock updates run on a schedule while customers place orders. The team confirms the exchange module and startup method before buying. In a separate test copy, it verifies inventory updates, order storage and a retry after failure. If the exchange runs only during a manual login, the scheduled workflow has not passed acceptance.
Write acceptance criteria
Record the version, test conditions and required behavior during ordinary and peak activity. Verify saved results and separately test recovery from a copy. Agree how to restore a previous release and who reconciles records received after switching.
Prepare your selection brief
See Hosting requirements for an online store for the purchase workflow and VPS slices, resources and server management for VPS responsibilities.
Discuss the requirements through hosting selection.