WooCommerce Square

WooCommerce Square connects a WooCommerce store with Square for online payments and, where supported, in-person selling. Its distinguishing feature is the link between ecommerce transactions and Square’s point-of-sale ecosystem rather than checkout processing alone.

Quick take

This integration is most useful for merchants already using Square in a physical location or planning to unify online and in-person inventory. The extension itself is free, while Square processing fees vary by country and transaction type.

What the integration actually does

WooCommerce Square can accept major cards, Apple Pay, Google Pay, Cash App Pay and supported Square methods online. It also synchronizes catalog, stock, orders and customer data between WooCommerce and Square, which is the reason it deserves separate consideration from gateways focused only on online checkout.

Merchants can use card-on-file functionality and authorize a charge before capture. WooCommerce also lists compatibility with WooCommerce Subscriptions and Pre-Orders, making Square viable for stores that need recurring or delayed-charge workflows within the supported feature set.

Where Square fits

The strongest use case is omnichannel retail. A merchant taking payments at a counter through Square and selling the same products through WooCommerce can avoid maintaining entirely separate payment and inventory systems. That can be more important operationally than comparing a fraction of a percentage point in gateway pricing.

Country and account constraints

WooCommerce Square is not globally available. Woo currently lists support for the United States, Canada, Australia, Japan, Ireland, France, Spain and the United Kingdom. A valid SSL certificate, supported WooCommerce version and Square account are required.

Because Square controls payment processing, deposits, account reviews and fee schedules remain outside WordPress. The extension does not make Square available in unsupported markets.

Costs

The extension is free. Payment processing uses Square’s country-specific rates, and optional instant deposits can carry separate fees. Merchants processing high annual volume may be eligible for custom processing rates.

When another gateway fits better

Online-only stores with no Square POS requirement may find Stripe, WooPayments, PayPal or Mollie a more natural fit depending on geography and payment-method coverage. Square’s inventory sync advantage matters most when Square is part of the broader retail operation.

PluginSuggest verdict

WooCommerce Square is primarily an omnichannel decision. Its value is strongest when WooCommerce and Square need to share payments and retail data, not when a merchant simply wants another online card gateway.

Setup and migration considerations

A Square migration should start with the catalog and inventory model, not only the payment form. The integration can sync data between Square and WooCommerce, so merchants should decide which system should be the primary source for products and stock before enabling synchronization. Conflicting edits from two systems can create avoidable catalog work.

Stores replacing another online gateway should also review saved cards, subscription renewals and refunds. Payment credentials stored by one processor are not automatically portable to Square. Test checkout, refunds and renewal behavior in a staging or controlled environment before routing all live orders through the new gateway.

Inventory and POS operations

The operational advantage of Square appears when staff sell the same inventory online and in person. Shared stock levels can reduce overselling and duplicate product maintenance. That advantage is much smaller for a purely digital business or an online-only catalog with no Square point-of-sale workflow.

Payouts and finance workflow

Orders live in WooCommerce while payment settlement is handled by Square. Finance teams should map how transaction fees, refunds, chargebacks and deposits will be reconciled. Standard deposits and optional instant transfers have different timing and fee considerations.

Decision guidance

Choose WooCommerce Square when Square already sits at the center of in-person retail and the business wants one connected online/offline payment stack. Keep a different gateway when the store is online-only, operates outside supported Square countries, or needs payment methods Square does not cover.

Testing before launch

Test an online payment, refund, inventory sync, and any card-on-file or subscription flow the store depends on. Also verify how product edits move between systems so staff do not accidentally overwrite WooCommerce or Square catalog data after launch.

Support and maintenance

Because the extension connects two active commerce systems, updates can affect both checkout and synchronization. Keep WooCommerce, the Square extension, and connected Square account settings under change control, and retest sync behavior after major updates.

Document ownership of catalog changes internally before staff begin daily synchronization.

FAQs

POS synchronization and migration checks

WooCommerce Square is more than a checkout gateway when the merchant also sells through Square POS. Inventory and catalog synchronization can connect the online store with in-person operations, but that creates an ownership question: decide whether WooCommerce or Square is the source of truth for product data, stock, and selected catalog fields before enabling synchronization broadly.

Test synchronization with a small product set first. Variations, SKUs, tax settings, images, and products that exist in only one system can expose mapping problems that are not obvious with a single simple product. Stores with multiple Square locations should also verify which location is connected for inventory and payment behavior.

If the store is moving from another gateway, separate new checkout traffic from existing recurring-payment obligations. WooCommerce Square can work with supported subscription workflows, but previously stored payment tokens from another processor do not automatically become Square credentials. Keep the old gateway available for active renewals until token migration, customer reauthorization, or a planned renewal transition has been completed.