Decide what the store must do at launch
Write down your product count, variants, stock process and target customers. A retailer serving Sri Lankan buyers may need LKR pricing and local delivery rules; an exporter may need a different currency, delivery process or enquiry-led catalogue. Confirm those requirements in the brief.
Separate essential launch features from later additions. Product pages, checkout and order notifications may come first; loyalty schemes, subscriptions or automated follow-ups should be included only when the platform and agreed scope support them.
Prepare a product catalogue customers can understand
- Use consistent product names, categories and descriptions.
- Supply clear images, prices, sizes or variants and availability.
- Explain dimensions, materials or compatibility where they affect the decision.
- Identify delivery charges and relevant return conditions before purchase.
- Decide who maintains stock and what happens when an item is unavailable.
Assign one owner for the catalogue. An attractive storefront cannot correct missing specifications or outdated stock information.
Confirm payments before committing to a platform
Ask your selected payment provider to confirm eligibility for your business, supported currencies, settlement arrangements, fees and platform compatibility. Requirements can change, so obtain current confirmation directly from the provider. A gateway name in a proposal is not an approval.
Agree who owns the payment account, who completes onboarding and who handles payment enquiries. During testing, cover successful, failed and cancelled payments, and verify that order status changes correctly. Liquid Flame Design confirms compatible payment integration during scoping; we do not assume every gateway works with every store.
Define delivery and the customer support handover
Document the areas you serve, delivery rates, estimated times and any collection option. Decide how your team receives orders, shares tracking details and handles failed deliveries or returns. If you use cash on delivery, define its availability and how the order is confirmed.
Write policies that reflect your actual operation and have the appropriate business review before launch. Tell the designer where those details belong in product pages and checkout.
Test the complete mobile buying journey
- Find a product, choose a variant and add it to the cart.
- Check totals, delivery charges and required address fields.
- Complete a test order using the provider’s approved test process.
- Verify customer and staff notifications and inventory behaviour.
- Try an unavailable item and a failed payment.
- Confirm the contact and support links work on a phone.
Also test checkout with a keyboard, readable text and clear error messages. Agree a named person who signs off the launch test and records unresolved issues.
Agree the build, migration and care scope
Our ecommerce service can cover storefront design, product organisation, mobile usability and payment integration within an agreed scope. Data migration, email automation and additional integrations are scoped separately when needed.
If you are replacing a store, list existing URLs, products and integrations before changing them. Prepare a redirect plan for important pages. Use the website budget guide for quote questions, but request a separate store quote: the one-page website starting price excludes ecommerce functionality.
Turn the brief into a clear scope
Tell us what your business needs, what is ready and where you need help. We will agree deliverables and costs before work begins.
