Storefronts and catalogues
Estimate product records, images, search traffic and the resources used by your commerce platform. Include room for catalogue growth.
Choose server resources for online stores, product catalogues and wholesale ordering applications around the workflows that bring orders into your business.
Estimate product records, images, search traffic and the resources used by your commerce platform. Include room for catalogue growth.
List the payment-service, email and account integrations involved in an order. Check which services your server operates and which are provided separately.
Document imports, stock updates, customer pricing and partner connections. Include scheduled processing in database and CPU estimates.
Plan for your expected concurrent shoppers and order activity during promotions. Test the complete application rather than relying on homepage loading alone.
Use the commerce platform’s requirements to compare CPU, RAM and database storage. Large image catalogues also need a storage and delivery plan. Choose a dedicated configuration when your brief calls for a physical server, or assess cloud plans against their listed resources and the workload you tested.
Use the server comparison to review the two server types, or explore country and city guides for location options.
Use your payment provider’s test mode to check the basket, checkout, confirmation and order record.
Verify stock changes, imports and cancelled test orders so integrations leave the catalogue in the expected state.
Restore files and the database together, then document how you will reconcile orders with external payment and inventory systems.
The standard dedicated and cloud plans are presented as unmanaged. Assign responsibility for the operating system, applications, updates, monitoring and backups. Review server management responsibilities and use the deployment checklist to plan the move.
Compare the current configurations and prices, then review your product, location, options and final total in the cart.