Quick answer
An online store needs to work after the order is placed. Start with the product catalogue: variants, stock, bundles, discounts and who updates listings. Then map checkout, payment confirmation, delivery choices, order changes, returns and customer service.
Practical scope
Check whether the store must connect with a point-of-sale system, inventory tool, accounting software, couriers or a CRM. Identify the source of truth for stock so two systems do not sell the last item twice. If products are made to order or configured by customers, document how options affect price and fulfilment.
An established ecommerce platform may cover standard needs. Custom features should be justified by a real operational requirement. Ask for a demonstration of both the customer purchase and staff fulfilment journey, including an out-of-stock item and a refund.
What to define before requesting proposals
- Products, variants, bundles and stock ownership
- Checkout, payments, tax, delivery and collection
- Order changes, returns, refunds and customer service
- POS, accounting, courier and CRM integrations
Questions to ask service providers
- Which standard platform features will be configured?
- How are overselling and failed payments prevented?
- What can staff manage without a developer?
How to assess the answers
Demonstrate the complete order lifecycle, including out-of-stock and refund cases. A polished shopfront is incomplete without dependable fulfilment operations.
Related planning guides
Next step: Put these decisions into one project brief, then ask providers to respond to the same scope.