Multi-store POS operations

Running POS across stores needs clear ownership of product data, traceable stock transfers, defined staff access and a device update plan. Check these controls against the subscriptions, devices and accounts your branches actually use.

Give shared product records an owner

Agree who may create an item or variant, change its SKU or description, and retire it. Branches need a way to request corrections. Keep a product's identity separate from its stock quantity and availability at each location: a correctly defined item may be stocked at only one branch.

Square supports multiple locations and can match items from an existing item library. Shopify describes SKUs as internal codes for tracking inventory and sales, and advises unique SKUs for product variants. Before a large catalogue change, inspect items sold at several branches, including a variant stocked at only one.

Govern location records and lifecycle

Set a controlled naming convention for branch records. In Square, the location business name appears on customers' card statements and digital receipts; the location nickname is for internal use. Create locations in Square Dashboard.

Treat location creation as a controlled change: Square locations cannot be deleted but can be deactivated, and a master account has a limit of 300 locations. Check whether an existing location should be deactivated before creating another.

Key System Limits and Requirements

Make transfers traceable

Record the source, destination, item, quantity and transfer reference. Decide when stock leaves the sending branch's available count, when the destination can sell it, and who checks the physical delivery. Record shortages against the movement, not as unexplained adjustments.

Provider workflows differ. Square's Australian instructions describe a Dashboard action that completes a stock transfer and records its number in a history log. The feature has subscription or retail-mode conditions, and items need location availability. Arrange a physical receiving check.

Shopify transfers are created in admin; staff can fulfil and receive them in POS at Pro locations with an active internet connection. A transfer does not automatically activate a product for sale at its destination.

Define the transfer hand-off

For Shopify transfers, origin staff pick and pack the transfer in POS; creating a shipment updates inventory counts and notifies the destination that items are on their way. At the destination, staff receive the incoming transfer, creating a defined hand-off between the two locations.

Shopify supports multiple shipments when inventory moves incrementally. Set out how staff identify each shipment and compare what arrives with what was sent, so a partial delivery is handled as part of the transfer rather than as an unrelated stock change.

Separate branch duties from central access

List what sales staff, branch managers, stock coordinators and head office must do: checkout, returns, discounts, stock adjustments, transfers, catalogue edits, reports, staff access and device settings. For each role, check both permitted actions and information visible outside its assigned stores.

Square says a team member's assigned locations determine access to associated location data and features, alongside their permission set. Shopify says location assignment restricts where a staff PIN works, but POS staff can still view inventory at other locations.

Shopify POS merchants on the POS Pro plan can create custom POS roles with unique permissions for POS app activities. Test the access boundaries that matter to your business rather than relying on a role's name.

Make staff actions attributable

Where staff actions need to be attributable, Square personal passcodes let the business track sales, time and actions by individual team members rather than relying on a shared team passcode. Team members must accept their invitation by email or phone within 30 days to complete sign-up.

Shopify distinguishes staff with POS and admin access from POS-app-only staff. POS-app-only staff are available to merchants using Shopify POS Pro, can log in only at Pro locations, and do not have Shopify admin or Point of Sale channel access. Use that distinction when deciding which staff need administrative access as well as branch checkout access.

Plan updates for the actual device fleet

Keep a register of each branch's device, POS app, operating system, payment hardware and support contact. Update a representative group first, check its trading workflows, then schedule remaining devices outside trading hours.

Where your business uses MDM to manage Shopify POS devices, Shopify documents staged app deployment so updates can be tested before being rolled out across the fleet. Check each device and update path before setting a fleet-wide schedule.

Validate updates across the device fleet

Shopify POS releases a new version every two weeks, and changes may affect daily workflows or require additional staff training. Shopify recommends testing updates on a controlled device group for 2–3 business days before rollout, extending testing to a full week before peak sales periods.

Check operating system updates separately from POS app updates: most MDMs manage them independently, and Shopify advises confirming that both are covered so an operating system update does not arrive before the POS version has been tested. Shopify POS cannot be rolled back to a previous version after updating.

Compare providers using the same branch scenario

Square is a candidate where location-specific reporting, a shared item library and its Dashboard transfer action fit the business. Confirm transfer eligibility, staff permissions and how a receiving branch will count deliveries.

Shopify POS is a candidate where its location-based POS transfer workflow fits the business. Confirm POS Pro at branches that need POS transfers, staff permissions, connectivity and destination product availability.

Ask each candidate to show a shared item change, a transfer with a shortage, branch and head-office sign-ins, and an update on one device. Record manual handoffs and plan restrictions.