Built, awaiting client goHome-care e-commerce, ~1,500 orders/month

An edge storefront replacing WooCommerce

Issue detected
WooCommerce at ~1,500 orders a month: plugin conflicts, a slow checkout, hosting bills — and e-invoicing that must not stop for a day.
Verification
The catalogue and the order flow rebuilt on staging and measured there: 579 URLs, accessibility 100, LCP under 2.5 s, 509 products in the edge database.
Root cause
A general-purpose plugin stack carrying an order volume it was never designed for — speed, stability and hosting cost all paid for it.
Fix
A custom storefront with the catalogue in an edge database, a back-office designed for the order volume, historic order import planned for 50–100k orders, invoicing and payment providers kept, tracking and consent built in.
Measured Delivered
579 URLs · accessibility 100 · LCP under 2.5 s
Window: stagingCaveat: Production untouched until the client's go; no order or revenue effect is claimed.

Before / after

What changed, in numbers.

BeforeWooCommerceplugin conflicts, slow checkout, hosting bills

System changeCatalogue moved to an edge database; a custom storefront and back-office; invoicing and payment providers kept.

After Delivered579 URLs · LCP < 2.5 son staging, accessibility 100

Measurement window: stagingConfidence / caveat: Production untouched until the client's go.

What was built

The system, in buyer words.

A custom storefront with the catalogue in an edge database, a back-office designed for the order volume, historic order import planned for 50–100k orders, invoicing and payment providers kept, tracking and consent built in.

Built on

AstroCloudflare WorkersD1Playwright

No dead ends

Related proof, same problem.

See the systems behind this proof →Start Universal · Your Opportunity Map within 48 hours.