Federico Rao
TRAFFIC IS NOISE. REVENUE IS ARCHITECTURE.
E-commerce architecture, product discovery, conversion measurement, operational automation, and maintainable integrations for online stores.
Where online stores actually lose revenue
Most underperforming stores do not have a traffic problem. They have a catalogue that cannot be navigated, product pages that omit the information required to decide, a checkout that adds friction at the moment of commitment, and measurement that cannot attribute any of it. Diagnosis starts by separating the funnel into discovery, evaluation, and purchase, then locating which stage loses the most qualified sessions. Spending on acquisition before that is identified reliably increases cost per order without increasing orders.
Catalogue structure and discovery
Category architecture should reflect how customers describe what they want, not how the business organises its inventory or how a supplier structures a feed. Faceted navigation needs deliberate rules about which combinations are crawlable, which are canonicalised, and which are blocked, because uncontrolled filters generate thousands of near-identical URLs that consume crawl budget and compete with the pages that matter. Search on site deserves the same attention as navigation: for large catalogues internal search is the highest-intent surface in the entire store.
Product pages and the evidence to decide
A product page has to answer sizing, materials, compatibility, delivery time, total landed cost, and return conditions without requiring a support message. Images need consistent framing and scale references; variants must be selectable without breaking the URL; stock status has to be accurate rather than optimistic. Structured product data allows search systems to present price and availability correctly, and it should describe what is actually on the page rather than inventing ratings or reviews. Reviews, where used, must be genuine and their collection method disclosed.
Checkout, payment, and post-purchase
Checkout should ask for the minimum required to fulfil and charge, present total cost including shipping and tax as early as possible, support the payment methods the target market actually uses, and never require account creation before purchase. Post-purchase is part of the same system: order confirmation, dispatch notification, tracking, returns initiation, and the reorder path all affect repeat rate more than any acquisition campaign. Abandoned-cart automation belongs here too, subject to consent and a frequency that does not train customers to ignore the sender.
Operations, integrations, and data ownership
Commerce systems fail operationally more often than they fail visually. Inventory synchronisation, pricing rules, product feeds to shopping and marketplace channels, order export to fulfilment, and returns handling all need defined owners and failure behaviour. Where several systems hold product data, one has to be authoritative and the direction of synchronisation must be explicit. Customer and order data should remain exportable and owned by the business rather than locked inside a platform that controls both the storefront and the relationship.
What to measure in a store
The metrics that matter are conversion rate by traffic source, average order value, contribution margin after acquisition and fulfilment cost, return rate by product, and repeat purchase rate. Sessions and impressions describe activity, not health. Consent-aware analytics will under-report, and modelling that gap honestly is better than configuring tracking that ignores consent. No technical improvement compensates for a product that is not competitive on price, availability, or delivery in its market, and that constraint is named rather than engineered around.
Page focus
Map catalog discovery, product content, checkout, conversion measurement, inventory operations, and commerce integrations.
Operational context
Adapt the system to the organisation’s actual services, location, regulation, team ownership, user questions, and conversion journey.
Measurement and limits
Evaluate Ecommerce with observable checks relevant to this route. Record material changes when the underlying offer, system, evidence, or dependency changes. Technical eligibility or deployment alone does not guarantee rankings, traffic, enquiries, revenue, accessibility compliance, or operational improvement.