Square for Retail: Where It Shines and Where Stores Outgrow It

Square for Retail's main limitations show up in three places: inventory depth (purchase orders, cost tracking, transfers), accounting (it syncs to a bookkeeping tool rather than including one), and sales channels (no native marketplace selling to Amazon). For a single counter with a simple catalog, none of this matters. For a growing store, a second location, or a wholesale side of the business, all three become daily friction.

What is Square for Retail actually good at?

Square built its reputation on fast, clean setup. You can get a register running in an afternoon, the hardware is simple, and the payments experience is genuinely good — tap, insert, or swipe, with a checkout flow that doesn't need training. For a single-location shop with a straightforward product catalog and no wholesale or multi-channel ambitions, that's a real strength. It's also why so many stores start there.

The honest review has to start with that: Square isn't a bad product. It's a well-built single-purpose tool. The limitations aren't bugs — they're the natural edge of what a payments-first POS was designed to do.

What are the main Square for Retail limitations?

Square for Retail limitations cluster around one theme: it was built as a point-of-sale with inventory features attached, not as an operating system for the whole business. That shows up in a few specific ways as a store grows past one register and one location.

• Inventory depth — stock counts and basic reordering work fine, but purchase order receiving, landed cost tracking, and in-transit inter-location transfers require workarounds or a separate inventory tool.
• Accounting — sales and payouts need to be synced to a separate bookkeeping product to produce a general ledger, journal entries, and financial statements. There's no built-in books.
• Marketplace selling — there's no native way to list and fulfill from Amazon out of the same inventory; that means a separate marketplace tool and a manual reconciliation step to avoid overselling.
• Multi-location roll-up — reporting across several stores tends to require exporting and stitching data together rather than one live, shared view.
• Wholesale/B2B — contract pricing, credit terms, and a vendor or rep portal aren't part of the core product.

Is Square's inventory deep enough for a growing retailer?

This is the question that comes up most from stores adding a second location or picking up wholesale accounts. A useful definition here: deep inventory means every unit is tracked through its full lifecycle — purchase order, receiving, cost, sale, transfer, and adjustment — with an audit trail behind each movement, not just a stock count that updates after a sale.

Square's inventory tools handle the basic count-and-sell loop well. Where retailers hit a wall is the layer around that loop: receiving a purchase order against expected cost, tracking a transfer while it's in transit between two stores, setting reorder points that trigger real recommendations, and tracking serial numbers on higher-value items. Those are exactly the workflows that matter once you have more than one stockroom or a supplier relationship worth managing carefully. Our guide to running multi-location inventory without spreadsheets covers what that operational gap actually looks like day to day.

Does Square for Retail include accounting?

No — and this is the limitation that costs the most time without anyone noticing. Square records the sale and the payout. Turning that into a general ledger, categorized journal entries, accounts payable, and financial statements requires syncing to a separate bookkeeping product such as QuickBooks. That sync has to be mapped correctly, monitored, and reconciled — every discount, refund, gift card redemption, and fee needs to land in the right account, or your books drift from what the register actually did.

For a lot of independent retailers, that reconciliation work is quietly outsourced to a bookkeeper every month, which is a real, recurring cost that doesn't show up on the software's price tag. We've written more broadly about this pattern in the real cost of disconnected retail systems — the sync itself is a hidden line item.

Can you sell on marketplaces from Square for Retail?

Not natively, out of the same inventory. Selling on Amazon means adding a separate app or service, then manually — or semi-manually — keeping stock levels in sync so you don't sell the same unit twice across channels. For a store that only sells in person, this never comes up. For a store trying to add an online storefront or list on a marketplace to reach new customers, it's an extra subscription and an extra reconciliation job, on top of the accounting sync you're already running. We cover the mechanics of unifying that in selling on marketplaces from one catalog.

When do stores actually outgrow Square for Retail?

There's no single revenue number where this happens — it's tied to specific operational triggers. Watch for these signals:

• You open a second location and need one real-time stock count instead of two separate ones.
• You start placing formal purchase orders with vendors and need to track cost and receiving against them.
• Your bookkeeper is spending real hours each month untangling the sync between your POS and your accounting software.
• You want to sell online, on a marketplace, or both, without keeping a manual spreadsheet of who has what stock.
• You pick up a wholesale account and need contract pricing, credit terms, or a rep-facing ordering process.
• You're comparing store performance across locations and the reporting requires exporting and combining data by hand.

If none of those apply yet, Square for Retail is probably still the right tool. If two or three do, it's worth pricing out what you're actually paying once you add up the POS subscription, the accounting sync, and any marketplace or ecommerce add-on — because that's the real comparison, not sticker price against sticker price.

What buying criteria actually matter when comparing retail POS systems?

Independent retailers evaluating a switch should score any POS — Square included — against the same short list, because these are the areas where single-purpose tools quietly force you into extra subscriptions:

• Inventory ledger depth: does every sale, transfer, receipt, and adjustment leave an audit row, or just a running count?
• Purchase order and receiving workflow: can you place a PO, receive against it, and track landed cost natively?
• Accounting hand-off: do sales reach your bookkeeping product automatically every day, or does someone export and re-key them?
• Marketplace and online reach: can you sell online and on marketplaces from the same inventory record, with no separate stock file to maintain?
• Multi-location reporting: is there one shared, real-time count and roll-up, or does reporting require manual consolidation?
• Payment ownership: do you control your own payment processing account, or are you locked into the vendor's payments stack? (Systems built on Stripe and Stripe Terminal let you bring your own account.)

For a fuller checklist of what a POS should cover for an independent store, see what a modern POS should do for an independent retailer, the pillar guide behind this comparison.

How does Retailer OS handle these gaps?

Retailer OS is an all-in-one retail operating system: one platform that runs the counter, the stockroom, the website, the marketplaces, the payments, and the team, instead of a POS plus three bolt-on subscriptions from other vendors. The online store and the Amazon and eBay channels are paid add-ons, but they run inside the same system. It's built specifically to close the gaps described above:

• Deep inventory, not just a stock count: per-item, per-location stock with a full movement ledger — every sale, transfer, receipt, and adjustment leaves an audit row. Purchase orders, receiving, cost tracking, and inter-location transfers with in-transit tracking are native, along with reorder points and, on an AI plan, AI-assisted reorder suggestions.
• An accounting sync you don't have to build: a QuickBooks Online connection posts a daily sales journal per channel and received purchase orders as bills, with a nightly check against the source, alongside vendor bills and customer receivables in Retailer OS.
• Marketplaces from one inventory record: sell on Amazon and eBay (paid add-ons) from the same catalog and stock the POS uses, so online, in-store, and marketplace inventory never double-counts.
• A hosted online store on the same catalog (a paid add-on): no second system to keep in sync, with buy-online/pickup-in-store supported out of the box.
• Bring-your-own-Stripe payments: card payments run on your own Stripe account — in-store via Stripe Terminal and online through Stripe Checkout — reconciled on one surface instead of two.
• Multi-location by default: one shared, real-time stock count across every store, warehouse, and stockroom, with reports you can filter by location and a corporate roll-up that compares revenue, orders, average ticket, and margin across the store accounts you own — see multi-location retail management.
• Wholesale support when you need it: customer accounts with credit terms, contract pricing, sales reps, and a vendor/PO portal for stores adding a B2B side.

None of this requires ripping out a working checkout to get. Retailer OS supports CSV import and data export, and for Shopify stores the Retailer OS team moves the catalog, customers, and order history over once you connect your account — the goal is a single system, not a bigger stack. You can see the full platform breakdown on the platform overview page or check current pricing.