// includes/store-count.php add_filter('stack_stores', fn() => 86 );
Stack Innovations
Start a project
WooCommerce is the most-shipped commerce platform on the web because it rides WordPress — the editor your team already knows, the plugin ecosystem you already trust. We build the engine room: product schema, variable products, taxes, shipping zones, payments, subscriptions, headless storefronts when you need to outrun the theme layer.
Each stat is a PHP add_filter() hook from real production code. Hover any to see the snippet. Counters scrub with scroll.
// includes/store-count.php add_filter('stack_stores', fn() => 86 );
// includes/gmv-meter.php add_filter('stack_gmv', fn() => 180_000_000 );
// includes/curated.php add_filter('stack_curated', fn() => 42 );
// includes/budget.php add_filter('stack_bloat', fn() => 0 );
Click an item in the WP-admin sidebar — the active capability opens in the editor. Each pane is a working pattern we've shipped.
Product types modelled around how the editor actually thinks: simple, variable (S/M/L × colour), grouped, subscription, downloadable, bundle. Attribute taxonomies auto-generate filters. wc_get_product() + custom meta-boxes for the bespoke fields. WP-CLI imports for bulk migrations.
wp wc product createHigh-Performance Order Storage on every new build — orders live in dedicated tables, not wp_posts. Checkout uses the React-based checkout block, with custom StoreApi extensions for fields beyond billing/shipping. Cart fragments wired so AJAX add-to-cart actually feels instant.
Stripe (cards + Apple/Google Pay), PayPal, Klarna, Afterpay, Mollie. Tax via WooCommerce Tax / TaxJar / Avalara depending on jurisdiction. SCA-ready, 3-D Secure where required, refund & partial-refund flows wired into admin without third-party tools.
WooCommerce Subscriptions for recurring billing, Memberships for content gating, Bookings for time-slot / appointment products. Dunning flows for failed payments, prorated upgrades / downgrades, customer self-service portal. We integrate with the gateway's native subscription primitives where possible.
Block themes (Full-Site Editing) by default — editors compose headers, footers, and product templates without touching code. Custom blocks for the bespoke patterns. Where FSE doesn't fit, a clean Storefront child theme. Theme.json drives tokens; CSS is bounded by design tokens, not freestyled.
When the theme layer is the bottleneck, we go headless: Astro or Next.js reads from /wc/v3 + StoreApi (or WooGraphQL), prerenders the catalogue, hydrates the cart on the client. Editors keep WP-admin; shoppers get a sub-second TTFB. Migration path is incremental — one route at a time.
/wc/v3 REST · StoreApi for cartEvery WooCommerce store is a curated stack of extensions. Click any plugin in the shelf — the build dashboard updates: capabilities unlock, monthly cost adjusts, complexity rises, the active add_action() hooks list grows, and the store's "profile" sentence rewrites itself. This is what we'd actually scope.
add_action() hooks
Same platform, two very different ways it ends up shipping. Eight criteria your team will actually feel — in plain English, with the receipts.
30 plugins, no object cache, theme renders every product page from scratch. Shoppers feel every byte.
Curated plugins, Redis object cache, full-page edge cache, optional headless. CI fails on regression.
Order queries scan wp_postmeta. Fine at 1k orders, slow at 100k, painful at a million.
High-Performance Order Storage on every new build. Order admin scrolls fast at any volume.
Every feature is another plugin. Admin slows, security surface grows, conflicts compound on each update.
Each plugin justifies its weight. We write the bespoke functionality as a child plugin we own and ship.
Bolted on as a follow-up engagement. The "we'll get to it" version of SEO.
Sitemaps, product structured data, hreflang for locales, OG images — live on day one.
Single-tenant cheap host, no Redis, single region. Black-Friday traffic finds the limits.
Managed WordPress host with Redis, full-page CDN, automated backups, staging environments out of the box.
You move the products yourself. URLs break, customer accounts orphan, search rankings drop.
Product + customer + order export, WP-CLI import, redirect map, dry-run, cutover. SEO continuity holds.
"Good luck with wp-admin." Editors learn by trial and error in production.
Editors leave training feeling fluent. First product launch happens without a Slack ping.
Hand-off, then silence. Six months later WordPress is two majors behind, plugins are unpatched.
Monthly version bumps, security audits, perf monitoring, real Slack channel. Features, not tickets.
WooCommerce is the engine; the storefront is a choice. Pick a project shape on the left — the exact stack we'd reach for shows on the right, with deep links into the framework pages where relevant. Same WooCommerce admin underneath, four different ways to render the front.
Inventory products, attributes, variants, customer states. Plugin shortlist. Hosting + HPOS plan. Lighthouse baseline.
Managed WP host, WooCommerce + curated plugins, theme.json tokens, ACF Pro fields, dev/staging/prod with WP-CLI deploys.
Block theme + custom blocks, product templates, checkout block + Store API extensions, payment gateways, tax + shipping zones.
Object cache, full-page CDN, image pipeline, JSON-LD products, sitemap, OG images. Lighthouse pass at 95+ on every PDP.
Product + customer + order migration, redirect map, dry-run, atomic deploy, DNS cutover. Editor handover with Loom kit.
WP + Woo + plugin upgrades, security audits, conversion-rate review, monthly performance budget.