The admin experience is part of the product
If adding a product, correcting stock or changing a collection is slow, the customer experience will eventually become stale or inaccurate. Catalogue operations deserve the same design attention as the storefront.
Payments are a state machine, not a button
Orders can be initiated, authorised, failed, captured, refunded or disputed. The interface, database and operational communication need to agree on those states without exposing credentials or trusting the browser.
Returns reveal the real architecture
A return touches eligibility rules, customer identity, order history, inventory, payment refunds, status communication and internal review. Treating it as a contact form creates manual work and weak customer trust.
Launch is the first operational day
Production domains, observability, email authentication, storage policies, backups and recovery routes are not finishing touches. They are part of what makes the store safe to operate.