Square Online isn't overcharging you. It's deciding for you.

No, which is the single most important thing to get right about Square Online. Unlike Shopify, which adds 0.5% to 2% on outside gateways, Square layers no platform fee on top of processing, just Square's card rate. As of mid-2026 that's 2.9% plus 30 cents online on free and Plus, 2.6% plus 30 cents on Premium (verify current rates, processors reprice). The usual "percentage skimmed off the top" argument against hosted platforms doesn't apply here; instead, Square removes the choice, selling exclusively through its own processing at the rate it publishes. On a custom store, processing and storefront are separate decisions, where the difference shows up at volume.

Not as your checkout processor. Square Online runs on Square Payments, which is largely why the platform exists. You can add PayPal or Afterpay as a buyer-facing option on some plans, but can't replace Square as the underlying processor or route volume to a different merchant account. That matters at real money: $500,000/year in card volume costs roughly $16,000 at 2.9% plus 30 cents, versus about $13,000 at a negotiated 2.4% interchange-plus rate. Square does offer custom pricing at higher volume, but you're negotiating with the only supplier allowed. A custom store connects to Stripe, Braintree, Authorize.net, a bank account, or whoever quotes best, and switches without touching the storefront.

For many businesses, you shouldn't. The free plan: working catalog, cart, checkout, no monthly fee, just Square branding and a square.site address until upgrade. Selling a handful of products, testing demand, or running a secondary channel to a physical location is the right spend, not custom. Custom isn't about Square being expensive, usually isn't, it's the ceiling: a checkout you can't restructure, URLs you don't control, a locked processor, a feature set that stops where the builder stops. Worth it when the ceiling costs more than the build: organic search, a checkout Square won't build, or a long-term asset you intend to own.

No, and any page telling you otherwise is doing the math wrong. Square Online Plus at $29/month billed annually is about $1,740 over five years; Premium at $79 is about $4,740; a $45/month loyalty or marketing add-on pushes a loaded stack to roughly $7,440. A custom store (site build plus store build, $6,300–$15,000) plus $60/mo to $180/mo hosting lands between $9,900–$25,800 over five years, more than even a fully loaded Premium-plus-add-ons stack. You're not buying a cheaper store; you're buying processor freedom, checkout control, an uncapped feature set, and an asset you own. If cost per month is the deciding factor, Square wins outright.

Square Online's checkout is Square's checkout: you set which fields appear, tipping, pickup/delivery options, and confirmation copy, all within Square's options. You can't restructure the flow: no conditional steps per product, no cart-driven upsell logic, no custom quote or approval step, no B2B purchase-order path, no field validation Square didn't anticipate. Fine for most retail and food ordering; a constraint when selling is unusual, made-to-order goods needing spec capture, rentals needing date ranges, wholesale needing tiered pricing, or services needing intake before payment. On a custom store checkout is code, so the flow follows the sale.

Square Online is rendered by a visual builder (its engine traces to Weebly, acquired by Square in 2018), carrying a layout framework, editor runtime, and generalized scripts covering every possible section any merchant might use. A product page tends to become usable on mobile in roughly two and a half to four seconds depending on images and sections. A hand-coded store sends finished HTML directly to the browser with no builder runtime, generally under a second. The gap matters most on mobile, where each extra second measurably increases visitors leaving before buying, and Google's page checks read the same numbers. If traffic comes from ads or Square POS receipts, that gap matters less than to a store competing in organic search.

Partially. Square Online lets you edit titles and meta descriptions, generates a sitemap, and connects to Search Console, enough to rank in low-to-moderate competition categories. What it doesn't give is structural control: the builder decides the URL pattern for product and category pages, so you can't design a hierarchy like /leather/wallets/bifold/ that groups your catalog the way people search, and you don't control server headers or the structured data Google reads, which is whatever the platform emits rather than markup you author per product. On a custom store, URL architecture, product schema with price/availability/reviews, and canonical/redirect handling are all yours. In a competitive category that's measurable; as one of three local sellers, usually not.

Significantly, yes, and it's the strongest case for staying. A physical-location Square register shares one item library with Square Online: sell the last unit at the counter and the online listing updates with no integration, sync job, or nightly reconciliation. Orders, customers, and payouts land in one dashboard and deposit. Rebuilding that on a custom store means integrating against Square's APIs (possible, and something we do), converting something free and automatic into something built and maintained. If in-person is the majority of revenue, that trade rarely pays. It starts to pay once online becomes the primary channel and needs what the builder won't do, at which point a custom store with a Square inventory integration keeps the sync and removes the ceiling.

You can export item and customer lists plus order and transaction histories as spreadsheets, and keep an externally purchased domain. Pages, layout, checkout settings, and the store itself are not portable files; leaving requires rebuilding and repointing the domain. Like every hosted builder, migration costs make later price or policy changes easier to absorb than negotiate. A custom store delivers PHP files, database, and images at launch on your server. Changing hosts or developers requires a file transfer, not a rebuild.

Custom builds are quoted per project, catalog size, checkout complexity, and integrations vary too much for a flat price. Standard stores (defined catalog, card checkout, customer accounts, discount codes, order admin) land in the $6,300–$15,000 range: the site build ($2,800–$5,000) plus the store build ($3,500–$10,000). Hosting is the only recurring cost after launch, billed monthly from launch: $60/mo for SSL, backups, uptime monitoring, and patching; $100/mo adds up to an hour of content edits a month and quarterly performance reviews; $180/mo adds up to three hours, same-day response, and a staging environment. No long-term contract; cancel with 30 days' notice, no fee, take the source files. Against Square Online Plus at roughly $1,740 over five years, a custom store on Core hosting at about $9,900 costs more, buying your choice of processor, a checkout built for your sale, a designed URL structure, and a store that's an asset, not a subscription.