Storefront and catalog scope
Count distinct product types, options and content patterns before counting products alone. A catalog with complex variants needs different validation from a small set of simple items. Decide whether search, filters, size guides, bundles and subscriptions are essential at launch. Product photography, copy, data cleanup and upload responsibility should be visible in the estimate.
Checkout and operational connections
Confirm the merchant’s chosen platform and eligibility for payment and delivery providers. Include testing for taxes, address entry, discounts, inventory and order status where those features are in scope. Payment processing fees, platform subscriptions and third-party apps are operating costs. An integration quote should say who owns credentials, monitors failures and maintains compatibility.
Migration and search visibility
A replacement store needs a product and collection URL map, redirects where appropriate and validation of canonical metadata. Reconcile product records and preserve original approved media. Importing customer or order history requires permission and a defined purpose. Test representative products and edge cases before switching the live domain.
Compare delivery and ownership
Ask whether a theme or headless frontend is proposed and why. Include ongoing editing, deployment, account recovery and support in the comparison. Define launch acceptance around actual cart and approved checkout flows; a beautiful preview does not prove orders can be placed. Bring a sample catalog, critical apps, target markets and provider details to receive an estimate tied to the operation.