For a business that sells online and in store, the first decision is which system masters the catalog and the orders: the ecommerce platform or the POS. Everything else, from pickup to refunds, follows from that answer. The three candidates answer it differently. The Lightspeed and WooCommerce documentation below was checked on October 7, 2026; the Shopify POS and Square descriptions rest on their published positioning.
- Shopify POS: the ecommerce platform is the master. The store sells from the same Shopify catalog and order history.
- Lightspeed: the POS is the master. Lightspeed's Retail (X-Series) documentation for its Shopify integration treats Retail POS as the system of record and warns that edits made in Shopify may be overwritten.
- Square: one vendor covers the POS and payments. For a business already running WooCommerce, WooCommerce documents a Square extension that syncs products and inventory, with a setting where the merchant picks WooCommerce or Square as the source of truth for product data, plus an order fulfillment sync that is disabled by default.
Decide who edits products
Ecommerce teams may own descriptions, images, launch timing, and online-only offers, while store teams handle receiving, counts, barcodes, and transfers. List each product field and the team that changes it, then check it against the master each candidate imposes. A mismatch is not a configuration detail: it decides which team works in which tool every day.
Apply the same test to orders and customers. Name where an online order lives, where a store sale lives, and which record customer service opens first. A shared customer view should not require store staff to hold administrator or payment privileges.
Scenario: a pickup order is only partly in stock
A customer orders three items online for pickup at a second store. When the associate prepares the order, one item cannot be found. The customer takes two items, the missing one is refunded to the original payment, and the store adjusts its stock.
Shopify POS is positioned on one commerce workflow, so confirm in the trial that the pickup order, the partial fulfillment, and the refund stay on one order record. With Lightspeed, online sales sync into Retail POS, so the buyer must confirm where partial fulfillment and the refund are performed and whether both systems then agree. With Square and WooCommerce, the extension's order fulfillment sync is disabled by default, so run the split pickup with that setting off and then on, and check each time where the partial fulfillment and the refund are recorded and whether WooCommerce and Square then agree.
Run a split-pickup test
Create a synthetic catalog with variants at two locations. Place an online pickup order for three items, fulfill two at the second store, refund the third to the original payment in approved test modes, and adjust stock. Then change one product description on the side that is not the declared master.
Check where each step happened, whether the refund reached the right payment, whether stock agrees in both systems, and which description survived. Ask ecommerce, store, and finance users to explain the order from their own screens. POS Platform Guide has not performed the test.
Edge case: one storefront still needs tax and payment answers
Shared commerce data does not establish correct sales-tax treatment. The business and qualified advisers must decide nexus, sourcing, taxability, and filing, then confirm that the configuration and exports support that policy. A shared payment provider does not prove PCI DSS compliance for every channel either; map each application, device, provider, and merchant duty through PCI SSC materials.
Conclusion
Choose Shopify POS when the online store is the center of the business and store staff can work inside its catalog. Choose Lightspeed when store operations should own products and the ecommerce team can accept Retail POS as the system of record. Choose Square when the web store runs on WooCommerce and will sync through the documented extension, and the merchant is ready to set the sync direction; for any other web platform, get Square's pairing in writing first. If the ecommerce platform has no documented route to any of the three, none of them is the right start: choose the POS that platform documents, or keep the store on its own system until one exists. In each case, keep the candidate only if the split-pickup test leaves one explainable order, refund, and stock history.
Traceable evidence
Sources for this decision
- vendorShopify POS official product siteShopify POS · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: Retailers evaluating one commerce workflow across Shopify ecommerce and in-person selling. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.Open source ↗
- vendorSquare official product siteSquare · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: Small merchants evaluating an integrated POS, payment, hardware, and business-software ecosystem. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.Open source ↗
- vendorLightspeed official product siteLightspeed · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: Retail and hospitality operators evaluating deeper inventory or location workflows. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.Open source ↗
- standardsPCI Data Security StandardPCI Security Standards Council · checked Aug 5, 2026 · supports: The published PCI Data Security Standard requirements for payment account data environments; it does not certify a merchant, processor, integration or POS product.Open source ↗
- officialRemote Seller FAQsStreamlined Sales Tax Governing Board · checked Aug 5, 2026 · supports: Multistate remote-seller registration and sales-tax FAQ context from the Streamlined Sales Tax Governing Board; it does not replace confirmation of individual state rules and effective dates.Open source ↗
- vendorSetting up the Shopify integration (Retail POS X-Series)Lightspeed · checked Oct 7, 2026 · supports: Lightspeed Retail (X-Series) help article on its Shopify integration, which treats Retail POS as the system of record and shares product, inventory, customer and sales data with stated sync limits: updates made in Shopify may be overwritten or cause syncing issues, images attached to Shopify products do not sync to Retail POS, products can no longer be sold exclusively on Shopify and a Shopify product missing from the catalog is created in Retail POS automatically, and barcodes sync once from Shopify to Retail POS at initial setup unless Support enables two-way syncing; it does not cover other Lightspeed product lines or prove sync behavior for a specific catalog.Open source ↗
- vendorWooCommerce Square extension documentationWooCommerce · checked Oct 7, 2026 · supports: WooCommerce documentation for its Square extension, which syncs products and inventory between WooCommerce and Square, with separate setup guides for the Square-to-WooCommerce and WooCommerce-to-Square directions, a bidirectional order fulfillment sync, and use as a payment gateway; it does not prove conflict handling for a specific catalog or hosting setup.Open source ↗
- vendorWooCommerce Square sync settingsWooCommerce · checked Oct 7, 2026 · supports: WooCommerce Square extension sync-settings page: the merchant chooses which platform is the source of truth (system of record) for product data, WooCommerce pushing product updates to Square or Square pulling product updates into WooCommerce, alongside inventory sync, a sync interval and an order fulfillment sync that is disabled by default; it does not prove conflict handling, recovery after a failed sync or behavior for a specific catalog.Open source ↗