A store built around how you sell, not around what a platform will let you do

Custom e-commerce builds run $2,800–$5,000. A standard store with a defined product catalog, Stripe checkout, customer accounts, an order management dashboard, and email receipts sits in that range. The main factors that push the number up are catalog size, variant complexity per product (size, color, material all tracked separately), whether you need live carrier shipping rates calculated at checkout, coupon and discount code systems, or a more detailed admin dashboard.

The comparison that matters isn't the build cost vs. a Shopify setup fee — it's the build cost vs. total platform spend over three years. A store on Shopify's main plan at $105/month, with a 1% transaction fee on outside processor sales, and a paid app stack commonly running $150–$300/month for a full feature set (as of mid-2026), runs roughly $3,000–$5,000 per year in platform overhead before touching your processor fees. Over three years that's roughly $9,000–$15,000 — and the bill never stops. A custom build in that range pays for itself in fee avoidance well before year three. See the detailed cost breakdown →

For any store that wants to rank in search, yes. A general shop page listing all your products is not what Google shows someone searching for "handmade soy candles" or "custom leather wallets." That searcher needs to land on a page specifically built around that query — its own title, its own meta description, its own product grid, its own structured data. Category pages rank independently for the product types they cover and bring in shoppers with specific purchase intent rather than browsers with general curiosity.

Category pages also improve the shopping experience for people who already know what they want. A customer looking for earrings shouldn't scroll through your full jewelry catalog. For stores with fewer than 20 products, a well-organized single-page view with clear sections and anchor links can work fine. For anything larger, category pages pay off in search traffic, in conversion rate (because the visitor landed on exactly what they searched for), and in paid search campaigns if you ever run them — because each category page becomes a proper landing destination for the matching ad group.

Stripe is the default and fits most stores well. It covers every major card type, Apple Pay, Google Pay, and subscription billing through one integration, with strong fraud detection built in. PayPal Checkout, Square, and Authorize.net are also available. The processor you use is your call — the integration works the same way regardless.

All payment processing uses the processor's hosted payment fields, so card data is never stored on your server. This means you have minimal legal liability for handling payment data and you're not required to undergo an annual security audit. Automatic systems handle the operational events: order confirmation emails send when payment succeeds, refund records update when a refund processes, and payment retry notices go out for subscription billing. Stores that sell internationally may benefit from Stripe's built-in support for international payment methods like SEPA, iDEAL, and Klarna — those integrations are set up based on which markets you're selling into.

For a store doing under $50k per year with a straightforward catalog and no unusual checkout requirements, Shopify works as a starting point. The hosted infrastructure is convenient and the fees at low volume are manageable. If you're trying to validate demand before investing in a custom build, starting on Shopify makes sense.

Past that point, two things shift. First, the fee math starts working against you — transaction fees, the monthly plan, and app stack costs accumulate into a recurring spend that a custom build eliminates. Second, checkout limitations start mattering. Shopify's checkout is locked to their template unless you're on Shopify Plus at $2,300/month. Custom cart logic, tiered pricing by customer group, unconventional fulfillment flows, or checkout steps that don't fit their standard pattern mean either accepting the constraint or paying for Plus. A custom store has none of those ceilings. See what plugin sprawl means for security if you're weighing WooCommerce, and the full Shopify vs. custom comparison →

Registered customers can store shipping addresses, view their full order history, and manage returns or exchanges without contacting support. Guest checkout runs alongside the account system — first-time buyers can complete a purchase without creating an account, and account creation is offered after the purchase completes, when it feels helpful rather than like a requirement. Forcing registration before payment is one of the most-studied abandonment triggers in e-commerce; this build eliminates it by design.

All customer data lives in your database on your hosting environment. Your customer list, order history, and purchase records are yours to export, query, or migrate at any time without restriction. Security on the account system follows current PHP best practices: CSRF protection on all form submissions, rate limiting on login attempts to block brute-force access, and secure session handling. If you ever switch hosting providers or bring on a different developer, the full customer and order database exports cleanly — no platform permission required, no data held hostage on a subscription you're leaving.

Every product page gets behind-the-scenes labels that tell Google to display your price, stock status, and review count directly in search results, before someone clicks through. This increases click-through rate against competitors showing as plain blue links. Category pages get their own search headline, search summary, and labeling so Google understands how your site is organized. When you offer filtered views or pagination of products, a special signal prevents Google from treating each variation as a duplicate page. The sitemap file telling Google what's on your site updates automatically whenever a product is added, archived, or changed — it requires no manual maintenance.

Special preview tags on product and category pages control how your links appear when customers share them on social media, in text messages, or in email — product name, photo, and price showing up correctly instead of a broken preview. Google Search Console is set up and the sitemap submitted at launch. For stores running content marketing alongside the catalog — buying guides, product comparison posts, care instructions — the internal linking structure between content and product pages is built in so search authority flows correctly through the site. What's included in SEO setup →

The admin is built for the person running the store, not for a developer. Everything is labeled in plain English. Product management lets you create, edit, and archive products with images, descriptions, prices, SKU numbers, inventory quantities, category assignment, and variant configuration for things like size and color. Order management shows the full fulfillment queue: filter by status or date, mark orders as shipped with tracking numbers, and process refunds — all from one screen. Customer management lets you browse accounts and pull up purchase history. Basic reporting shows revenue by date range and top-selling products.

Additional admin features can be scoped based on what your operation needs: bulk price editing for large catalogs, coupon and discount code management, shipping rate configuration by zone and weight, low-stock email alerts, and CSV product import/export for stores importing from a supplier catalog. For stores with a team, staff accounts with role-based permissions let a fulfillment employee update order status without having access to pricing or financial data. The goal is an admin that handles your actual daily workflow without navigating a feature-heavy platform designed for a different business than yours.

Yes, through Stripe's subscription billing. Subscription products can sit in the same catalog alongside one-time purchases. A customer picks a billing interval at checkout — weekly, monthly, quarterly, annually — and Stripe handles the recurring charge automatically. When each renewal succeeds, the renewal order is created in your system automatically and a confirmation email is sent to the customer. This works whether you're shipping a physical product on auto-replenishment, granting access to a digital service, or running a membership program.

Failed payment handling is built in: if a card declines, Stripe automatically attempts the charge again on a schedule, and emails prompt the customer to update their payment method. If the card problem is never resolved, subscription pausing or cancellation can be triggered automatically. Customers can manage their own subscriptions through the account dashboard — updating payment methods, pausing, or canceling without needing to contact you. Subscription billing is priced separately from a standard catalog build and is quoted after a discovery call covering your billing model, what customers can self-manage, and what the fulfillment workflow looks like for each renewal. See payment integration options →

Your store collects customer names, shipping addresses, email addresses, and purchase history. None of that is shared with third-party ad platforms or analytics services by default — no Shopify pixel, no Facebook Conversion API, no Google tag built into the store. If you choose to add ad tracking for attribution or analytics for conversion data, those are implemented as your explicit decision, not platform defaults you have to opt out of. A privacy policy and terms of service covering your data collection practices are included at launch.

Customer data lives in your database on your hosting server. You control retention periods, data deletion requests, and exports at any time. If your customer base includes EU residents, legal compliance — cookie consent management, the ability for customers to request their data be deleted, and data export in a format they can read — can be built into the store from the start. California customers also have rights around their data privacy; the store supports those requirements through the same infrastructure. Security and data protection basics →

Live shipping rate integrations with USPS, UPS, and FedEx are available. When a customer reaches the shipping step, their address and the cart's total weight are sent to the carrier and live shipping quotes come back for the customer to choose from. This is more accurate than a flat fee for stores with varied product weights and dimensions, and it removes the "is this shipping charge fair?" hesitation that flat rates sometimes trigger for customers close to or far from your location.

ShipStation integration for bulk label printing and automatic tracking number updates is available for higher-volume stores where the manual per-order workflow stops making sense. For stores using a third-party fulfillment center, the order management system can notify the fulfillment center automatically whenever a purchase completes. The specific setup depends on which fulfillment partner you use; that gets discussed during the initial discovery call. For stores that also sell at retail and need inventory to sync in real time between online orders and an in-store point-of-sale system, that integration is set up based on which point-of-sale system you're running.

A standard store with up to 50 products, Stripe checkout, customer accounts, and an order management dashboard generally runs four to six weeks from a signed scope to launch. Timeline is most affected by catalog complexity — the number of products, the number of variants per product, and whether any products have downloadable assets or custom configuration options. I send a data template spreadsheet at kickoff so you can fill in product names, descriptions, prices, inventory counts, and image file names in bulk rather than entering them one at a time in the final week.

Builds with subscription billing, live shipping carrier integrations, fulfillment software connections, or a more complex admin dashboard add two to four weeks depending on what's involved. The staging environment is live throughout development — you can test the checkout with Stripe's test cards, browse the admin, and flag anything that needs adjustment before going live. Rush timelines are available for stores with a specific launch date: a product campaign window, a seasonal opening, or a business partnership already generating traffic. Ask about rush availability →

Yes, and mobile is the primary experience — not a desktop layout squeezed to fit a smaller screen. More than half of online shopping happens on phones, and a checkout that requires zooming, horizontal scrolling, or tapping on links that are too small loses sales at the exact moment the customer was ready to pay. A custom build doesn't have this problem because mobile is tested throughout development, not as a QA step at the end.

Every part of the store is tested on actual iOS and Android devices: product browsing, the cart, checkout forms, and payment processing. Tap targets are sized for thumbs, not fingers. Form fields trigger the correct keyboard automatically — number pad for card numbers, standard keyboard for names, email keyboard for email, phone keyboard for phone numbers. Product images load at the optimal resolution for each screen size so pages don't slow down on mobile data connections. The cart and checkout flow requires no horizontal scrolling on any common device size. These are the defaults, not things to optimize after launch.