Custom online stores
A store with its own code: catalogue, cart, payments and an admin panel, without depending on a platform or a chain of plugins.
Why a platform is not always enough
Shopify or WooCommerce are fine to start, but once the store needs something specific you end up stacking plugins, fees and patches. That's when building it custom makes sense: the logic is yours and you can change it without fighting anyone.
How I'd approach it
I haven't built a full store in production yet, so I'm not going to pretend I have. What I do know is how to approach it, because the pieces are the ones I've already worked with: well-modelled data, an admin panel like the one I built with Filament at Entreredes, and integrated payments.
- -A well-modelled catalogueProducts, variants and stock designed from the start, so nothing has to be rebuilt when it grows.
- -Payments with StripeA processor like Stripe handles the charge; the store just has to integrate it properly and not lose orders.
- -An admin panelOrders, stock and discounts in a simple panel, like the ones I have built with Filament.
- -Fast on mobileMost people buy from their phone, so loading and checkout have to be quick.
How I'd do it
Understand the store
What's sold, how it ships and how it's paid for. That decides what the first version really needs.
- ›Catalogue and variants
- ›Payments and shipping
- ›First version scope
Build it in parts
Catalogue and cart first, then payment, then the admin panel. Each part can be tested before moving on.
- ›Catalogue and product pages
- ›Cart and payment
- ›Admin panel
Take it to production
Test real purchases end to end before opening it, and leave it deployed and documented.
- ›Real purchase tests
- ›Deployment
- ›Documentation
What it should include
- ✓Catalogue with variants and stock
- ✓Cart and Stripe payments
- ✓Orders and stock panel
- ✓Mobile-first design
- ✓Search data on product pages
- ✓Documented code