Tech Stack

A tech stack is the combined set of technologies an application is built on — programming languages, frameworks, databases, infrastructure, and the third-party services that connect them. The term originated in software engineering ("MEAN stack," "LAMP stack") and has expanded to describe the entire technology footprint of a business or product. For ecommerce brands, the tech stack is everything from the storefront platform to the email tool to the data warehouse.

Common ecommerce stack layers

• Storefront platform: Shopify, BigCommerce, custom commerce. The foundational layer.
• Front-end framework: Liquid (Shopify default), Hydrogen, Next.js, Vue, or custom React for headless setups.
• Payments: Shopify Payments, Stripe, PayPal, BNPL providers.
• Email and SMS: Klaviyo, Attentive, Iterable, Braze.
• Reviews and UGC: Yotpo, Okendo, Bazaarvoice, Pixlee.
• Customer support: Gorgias, Zendesk, Intercom, Front.
• Subscriptions: Recharge, Skio, Loop.
• Loyalty: Smile, LoyaltyLion, Yotpo Loyalty.
• Fulfillment: ShipBob, ShipStation, internal warehouse, 3PL ERP.
• Analytics and BI: GA4, Triple Whale, Northbeam, Looker, Mode.
• Data infrastructure: Fivetran, Airbyte, Snowflake/BigQuery, dbt for warehouse-based teams.
• Customer data platform: Klaviyo CDP, Segment, RudderStack, custom warehouse-driven CDP.
• Ad platforms: Meta, Google, TikTok, Pinterest, Klaviyo Ads.

Why tech stack composition matters

The tech stack isn't just a list of tools — the choices compound. Tools that integrate well multiply each other's value; tools that don't integrate create operational friction, data fragmentation, and the eternal "we have the data, we just can't connect it" problem.

Two mid-market Shopify brands with similar revenue can have wildly different operational efficiency depending on tech stack design. Brands with thoughtful, well-integrated stacks ship faster, make better decisions, and waste less time on data reconciliation.

Common tech stack mistakes

• Tool sprawl. Every team adds the tool they want. Two years in, the brand has 40 SaaS subscriptions, 60% of them underutilized, and no clear inventory of what does what.
• Pursuing best-of-breed without integration. The "best" email tool plus the "best" SMS tool plus the "best" reviews tool can produce worse results than three integrated good-enough tools because the data doesn't flow.
• Locked-in to platforms that won't scale. Tools that work at $1M ARR may not work at $10M. Sometimes worth choosing the slightly-overbuilt tool now to avoid a migration later.
• No data layer. Brands without a CDP or data warehouse end up reconciling spreadsheets weekly because no system has the full picture.

Stack-thinking principles

• Start simple. Add tools when their value is provable, not speculative.
• Prioritize integration over features. A tool that integrates well with existing stack often beats a feature-richer alternative that doesn't.
• Audit annually. Tools that were essential a year ago may be redundant or replaceable now.
• Centralize customer data. Whether through a CDP or a data warehouse, having one place where customer data lives is the foundation that makes the rest of the stack work.