Servizio · E-Commerce
E-Commerce
A physical store works when the shutter is up. Online, competitors sell while you're closing the till.
The problem isn't "build a site with a cart": it's avoiding the chain of providers that puts in a heavy theme, three random plugins, shared hosting and a fragile checkout.
Here we build an e-commerce with clear structure: catalog, variants, inventory, payments, shipping, transactional emails and cart recovery. WooCommerce when it makes sense, headless when the case demands it.
In a 180-SKU catalog, one wrong shipping rule is enough to burn orders every week. Fewer hand-offs, more control on the points that block sales. Period.
01 — Awareness
The marketplace takes customers who could be yours
If you don't have a direct channel, somebody else intercepts demand in your place.
- 01
Shutter vs 24/7
The physical store sells when it's open. Online, competitors take in money in the evening, on holidays, and while you're doing inventory.
- 02
Customers handed to marketplaces
Amazon and generic platforms don't wait. If your catalog isn't directly purchasable, they take traffic, customer data and the commercial relationship.
- 03
Plugins without control
Heavy theme, shared hosting, plugins picked at random, slow checkout. The classic six-handed chain where nobody really owns the problem.
02 — What you get
6 features- 01
Catalog under control
Products, categories, variants, attributes and inventory get set up with commercial logic, not loaded in blocks without criteria. Sizes, colors, availability and SKUs have to be readable for buyers and manageable for sellers.
- 02
Frictionless checkout
Checkout stays clean: necessary data, clear payment methods, understandable errors, no useless steps. If 9 fields are needed to buy a simple product, the cart is already losing people.
- 03
Multi-courier shipping
Zones, thresholds, shipping classes, couriers and operational rules get put in order before launch. If shipping is confused, the cart dies right there. End of story.
- 04
Emails that arrive
Order confirmations, payments, shipping, password resets and cart recovery can't depend on luck. We set up a serious email flow, with correct senders, readable templates and tracking on critical events.
- 05
Schema for Shopping
Product, Offer, price, availability, brand and identifiers get prepared for Google Shopping and organic search. The catalog has to be understood by platforms, not just seen in the browser.
- 06
Stack without mess
No bloated theme, plugins installed because "maybe useful", and cheap hosting. The platform is chosen on the case: WooCommerce for fast editorial management, headless when performance and integrations matter more.
03 — How I work
5 phases- 01
Discovery call
30 free minutes to understand the real need. I listen, ask questions, take notes. No cold quotes: I need to know what you're actually building first.
- 02
Quote
Flat fee with clear scope, timeline and costs. No surprises: if something falls out of scope I tell you upfront, not when the invoice lands.
- 03
Design / Strategy
Wireframes, moodboard or audit with action plan — depends on the service. You see the direction before any code or content gets touched.
- 04
Build
Development, technical work or operational execution. Agreed check-ins along the way, none of that "let's sync end of month".
- 05
Launch & follow-up
Go-live + 30 days of assistance included. Documentation, training if needed, and an open door for the small things later.
04 — AFTER LAUNCH
The online store has to stay under pressure
Launch isn't the finish line. It's the first moment when the store meets real orders, declined cards, undecided customers, out-of-zone shipments, emails ending up in spam and products Google misinterprets. Here we look at the dirty part of e-commerce: Shopping feed, Product and Offer schema, abandoned carts, checkout performance, error logs, WooCommerce updates, plugin compatibility, inventory and email flows. The chain of providers is the poison: one handles the theme, one the server, one the tracking, one the payments, and when something breaks the blame-passing starts. Better to have clear technical direction and targeted interventions on the points that block orders and management. You decide.
05 - What you get
Deliverables
| No. | Deliverable | Format | Timing |
|---|---|---|---|
| 01 | Catalog and variants map | .xlsx + .md | week 1 |
| 02 | Base store setup | CMS config | week 1-2 |
| 03 | Payment gateways configured | Stripe/PayPal | week 2 |
| 04 | Shipping rules and taxes | Config + .md | week 2 |
| 05 | Structured product cards | CMS + CSV | week 2-3 |
| 06 | Product and Offer schema | JSON-LD | week 3 |
| 07 | Google Shopping feed | XML/CSV feed | week 3 |
| 08 | Transactional emails | MJML/HTML | week 3 |
| 09 | Orders dashboard | Admin panel | pre-launch |
| 10 | 12-scenario checkout test | Checklist | pre-launch |
| 11 | Catalog management training | Meet + .md | post-launch |
07 - Related services
08 - Free audit · 15 minutes
How many orders are you losing at checkout?
I check cart, payments, emails and product feed. 15 minutes on Meet, no detour and no quote before problems.
No obligation - reply within 24h
09 — Frequently asked questions
6 answersThe questions I hear all the time.
Better WooCommerce or headless e-commerce?
Depends on catalog, internal management and integrations. WooCommerce works when you need editorial autonomy, fast product management and a familiar panel. Headless makes sense when performance, dedicated frontend and connections with external systems matter more. The choice is made on real work, not on current fashion.
Can I sell online if I already have a physical store?
Yes, and it's often the most sensible case. The physical store stays the strong point, but online covers people who don't pass through your area, who buy outside hours, and who look for you after seeing you on social or Google. Selling only to those who come through the door is a technical limit, not a law.
Can products already in a management system be imported?
Yes, if the management system exposes clean data or reliable exports. First we check fields, codes, variants, stock, images and categories. Importing a catalog badly creates chaos: duplicate products, wrong availability, useless filters. Better to fix the structure first, then automate.
How are payments and security handled?
Stripe, PayPal, bank transfer and cash on delivery get configured according to the company flow. Payment data can't pass through improvised paths: we use serious gateways, HTTPS, correct roles, controlled updates and limited access. Checkout is where amateurism costs lost orders.
Does cart recovery really work?
It works when set up properly. It's not enough to send a generic email to whoever abandons. You have to distinguish registered customer, real cart, consent, sending times and useful content. Cart recovery doesn't save a terrible checkout, but it recovers sales that would otherwise disappear.
What happens after launch?
After launch we look at what really happens: orders, payment errors, undelivered emails, most-viewed products, abandoned carts, Shopping feeds and slow pages. An e-commerce doesn't end when it goes online. It begins when traffic, questions and real orders arrive.
10 - Start here?
Ready to start?
A 30-minute call to figure out what's actually needed. No PowerPoint.