Requirements
Prepare a dedicated domain or subdomain, active TLS, an empty document root, a PHP version supported by the selected PrestaShop release and an available database. Decide the shop country, currency, timezone and administrator email before installation. A production shop also needs working transactional email and a tested backup plan.
Install PrestaShop
Install PrestaShop on the intended domain and empty document root with the required language and a strong administrator password. A dedicated database avoids collisions with other applications. Reuse an existing database only when it is ready, its password is known and a unique prefix isolates the shop tables.
Resolve an installation failure
Do not retry blindly after a failed installation. Preserve the first error and inspect the destination for partial files and the database for partial tables. A non-empty root must be cleared only after a recoverable copy exists. A database connection error requires checking hostname, database name, username, password and readiness together; enabling TLS or changing shop settings cannot repair an unreachable database.
Secure the back office
Use the generated administration URL returned by the installation; PrestaShop normally randomises the folder, so do not assume /admin. Store that URL securely, create individual staff accounts with the minimum profile required and enable multifactor authentication where supported. Remove the installation directory if the installed version has not already done so.
Recover back-office access
Use the password-reset link for the exact employee account when transactional email works. If it does not, take a database dump before following the recovery procedure for the installed PrestaShop version; password storage changes between releases, so do not paste a generic hash from an unrelated version. After recovery, rotate the temporary password and verify employee profiles and permissions.
Configure the shop
Confirm the canonical shop domain, HTTPS, country, currency, taxes, language, timezone, shipping zones and payment configuration. Create a test product with stock, tax and shipping behaviour representative of the real catalogue. Do not open the store to customers until totals and customer emails have been checked.
Configure transactional email
Use authenticated SMTP with a dedicated mailbox and send a test from the PrestaShop email configuration. Then complete a test order and confirm customer confirmation, staff notification and password-reset messages. Check SPF, DKIM and DMARC when a message is accepted but reaches spam.
Run a complete test order
Test account creation, guest checkout when enabled, tax, shipping, discount, payment sandbox or approved low-risk payment path, stock reduction, order status and refund procedure. Verify the storefront and back office over HTTPS from a second device. Remove test customers and orders only according to accounting and audit requirements.
Updates, modules and performance
Install modules and themes only from maintained sources and remove unused ones. Back up files and database, enable maintenance mode, apply one change set and clear PrestaShop cache before testing. Large catalogues and search operations should be measured with representative data rather than an empty store.
Protect and recover transactional data
The database changes with every customer, order and stock event, while product images and modules change the file tree. Back up both frequently and retain an off-platform copy. Recover matching points, clear cache and test the back office, catalogue, cart and one controlled order before reopening the shop.
