The complete online buying journey
An ecommerce project joins customer-facing pages to the operational work behind an order. A shopper needs to find the correct item, understand its suitability, see the applicable price and delivery information, and complete payment with confidence. Staff then need an accurate order that can be fulfilled and supported.
For search visibility, product and category URLs should be stable and consistent. Filters, variants and tracking parameters need deliberate handling so the same stock is not exposed through endless alternative addresses. Google documents ecommerce URL design.
Example: selling a product with variations
Consider a supplier selling workwear in different sizes and colours. A photograph of the general product is not enough: the selected variant must match stock availability, price and the item passed to the order system. If one size sells out, the page should explain that state without implying that every variant is unavailable.
The build specification should identify which system owns the stock quantity, when updates occur and what happens if an update fails. Customer service also needs to recognise the purchased variant when dealing with an exchange or an order query. These decisions affect the interface as much as the integration.
What to test before opening the store
Walk through the purchase on a phone, including a failed payment, an unavailable item and an address outside the delivery area. Check that confirmations refer to the right order and that staff receive enough information to fulfil it. Use the payment provider’s supported testing facilities.
A checkout that works once is not evidence that the entire store is ready. Test changes to quantities, discounts and shipping choices, then reconcile the order record with the payment record. Include product editing and stock management in the handover so routine updates do not require a developer.
Common questions about ecommerce
Is an online catalogue ecommerce?
A catalogue can support sales without taking online payment. Decide whether customers should buy immediately, request a quote or contact the business; the required order workflow differs.
Should every product variant have its own page?
Not automatically. The best structure depends on meaningful product differences, customer needs and the platform. Keep variant selection clear and make the relationship between equivalent URLs explicit.
Related definitions
- Faceted navigation — Filters that let users narrow a large collection, such as products by size and colour. The resulting URL combinations need a deliberate crawling and indexing strategy.
- Conversion — A valuable action defined for measurement, such as a qualified enquiry, booked appointment or completed purchase. A page view is not automatically a business outcome.
- API integration — A connection that uses software interfaces to exchange information or coordinate actions between systems, with authentication, validation and error handling.
- Canonical URL — The preferred URL for a page when identical or substantially similar content is accessible through multiple addresses. A canonical link communicates a preference rather than forcing a redirect.
Related SEO guides
An online catalogue needs useful commercial pages and deliberate handling of the many URLs generated by product filters.
For help connecting these decisions with your website, explore our SEO services or start with an SEO audit.
Put it into practice
Explore our ecommerce web design service or talk with Refined IT about applying this to your website or business systems.