How to Choose a POS for a Clothing Store

01 / Size and color matrix

Track the variant, not just the style.

A fashion boutique, apparel shop or clothing retailer needs to answer “Do we have this size in this color?” A style total cannot answer that. Start with the workflows your staff repeat, then use the general POS selection guide for the wider checkout, reporting and cost questions.

For example, an Oxford Shirt in four sizes (Small, Medium, Large, Extra Large) and three colors (Navy, Black, White) has 4 × 3 = 12 sellable variants. Medium/Navy and Large/Navy need separate quantities even though they belong to the same parent style.

A matrix is a size-by-color view of those records. Lightspeed’s R-Series documentation describes matrices with separate variant SKUs and inventory. That is a documented product example, not proof of another system’s capability.

Demo test: open the full matrix, find a missing size, and inspect its stock and sales separately. Ask about variant limits, bulk creation, discontinued combinations and whether importing an existing range preserves each identifier.

02 / Variant-level barcode and SKU

Make every scan identify the actual garment.

A SKU identifies the stock record; a scannable barcode must retrieve the actual sellable variant, not only the parent style. For example, your internal SKU OXF-NV-M should retrieve Oxford Shirt / Navy / Medium, with its own quantity. Do not reuse that barcode for Large/Navy.

Demo test: print labels for two sizes of the same color, scan each at checkout and receiving, and check which record changes. Check existing supplier barcodes, duplicate detection, label reprints and readable size/color text. Lightspeed’s barcode documentation illustrates item identifiers; verify your own printer, scanner and label format with the provider.

03 / Exchanges and returns

An exchange changes two variant records.

When a customer brings back Medium/Navy for Large/Navy, the receipt and stock movements should preserve both variants. A net style quantity of zero hides whether the right size is available.

Demo test: find the original sale, process the size exchange, inspect the receipt and inventory history, and check any price difference or refund. Only restock the returned unit as sellable if its condition allows it. Ask how damaged returns, permissions and returns at another branch are recorded.

04 / Purchasing and receiving

Keep the size/color distribution through the order.

Ordering “24 shirts” is insufficient if you need specific sizes and colors. The purchase order and receiving record should preserve quantities for each variant, supplier references and destination location.

Demo test: order a mixed size run, receive only part of it, and record a short shipment or wrong color. Check that received quantities become stock in the right place while outstanding quantities remain distinguishable. Ask how costs, supplier replenishment, corrections and the person making each change appear in the audit history.

05 / Seasonal and dead stock

Review slow colors and broken size runs.

A style can sell well overall while White/Extra Large sits unsold and Navy/Medium repeatedly runs out. Review sales, last-sale dates, receipts and stock at style, size and color level, with location and selling season in view. Low sales during a stockout are not evidence of low demand.

Demo test: filter a slow color, inspect its remaining sizes, and apply a markdown only to the intended variants. Check start/end dates, staff permissions, online price effects and margin reporting before confirming it. Review whether to reorder the fast sizes, transfer a slow variant or stop replenishing a color.

Use the dead stock guide to distinguish slow, seasonal and dead inventory. The Reorder Point Calculator supports replenishment timing for a variant you intend to keep. The Profit & Stock Calculator helps assess margin, inventory turnover and GMROI using verified inputs; it does not identify a slow size automatically.

06 / Multi-location inventory

Know where each size is available.

Demo test: create, dispatch and receive a transfer; then inspect the source, destination, timestamps and staff audit trail. Test a partial receipt and discrepancy. Ask how counts, reservations, warehouse stock and branch permissions affect the availability shown to staff.

07 / Ecommerce synchronization

Test what happens when the last variant sells.

If the last Medium/Navy sells in store while online stock still shows one, another customer may order a unit you cannot fulfill. Matching style names is insufficient: both channels must refer to the same variant and the relevant location’s available stock.

Shopify’s POS help documentation describes synchronization across its retail locations and online channels. Treat that as vendor research. It does not establish timing, failure recovery or compatibility for a different POS or connector.

Demo test: sell the last unit, inspect online availability, then try an online order and a cancellation. Ask which system owns stock, how reservations and returns update it, what happens during a connection failure, and how staff detect and reconcile sync errors. Confirm whether a connector or extra plan is required; do not assume a synchronization or offline guarantee.

08 / Market and payment fit

Verify the whole setup in your market.

Software access does not establish payment, hardware or support availability. Verify each part for your country, business and proposed plan before committing:

• Software: account eligibility, variant and location limits, integrations, exports and current plan terms.
• Payments: supported processors and local payment methods, onboarding eligibility, settlement, refunds and current fees.
• Hardware: compatible tills, scanners, label printers, terminals and local replacements.
• Support: coverage hours, language, onboarding, escalation and help during trading hours.
• Local and tax fit: receipt, invoice, tax reporting and any fiscal requirements; confirm these with the provider and a local adviser.

Demo test: get written confirmation for the exact configuration and test it with your intended devices. Ask which checkout and payment actions work during an outage and how records reconcile afterward. This guide does not verify country availability, prices, payment support or offline operation for any product.

09 / Original ShopsInto evaluation method

Run the same Linen Shirt workflow in every demo.

This fictional scenario is a repeatable evaluation method, not a vendor score or a report of hands-on testing. Create a Linen Shirt in 3 colors (Navy, Black, White) × 4 sizes (Small, Medium, Large, Extra Large) = 12 variants. Start with empty stock at Store A and Store B.

1. Receive 24 units across 12 variants. Receive 2 of each into Store A. Confirm every size/color balance is 2 and the style total is 24.
2. Print variant barcodes. Label all 12 variants and scan samples to confirm the correct size, color and SKU appear.
3. Sell Medium/Navy. Sell 1 at Store A. Confirm Medium/Navy falls from 2 to 1 and total stock becomes 23.
4. Exchange for Large/Navy. Return the sellable Medium/Navy (+1) and sell Large/Navy (−1). Confirm balances of 2 and 1 respectively, with total stock still 23.
5. Transfer two Small/Black units to another store. Dispatch from Store A and receive at Store B. Confirm balances of 0 and 2, an audit trail and no change to total stock.
6. Receive supplier replenishment. Order 3 Medium/Navy and 1 Large/Navy; receive those exact variants at Store A. Confirm balances of 5 and 2 and total stock of 27. Inspect the linked purchase order and receipt.
7. Mark down one slow color. Treat White as the fictional slow color. Change its selling price across all four sizes, leaving Navy and Black unchanged. Confirm quantities remain 27 and check the effect on margin and online prices.
8. Export inventory by variant. Export style, size, color, SKU, barcode and quantity by location. Reconcile the 12 variant records and 27 units against the movements above.

For each step, record what you observed, any workaround, required plan or integration, and any question still awaiting confirmation. Keep vendor statements separate from your own demo observations. For workflows you do not use yet, note whether they will matter as the shop grows. A missing essential workflow is a reason to investigate another setup, not to average it away with a score.

10 / Choose by workflow fit

Turn the results into a shortlist.

For a small boutique, start with accurate variants, scanning, exchanges and location stock. Add purchasing, transfers, seasonal markdowns and ecommerce tests when those jobs are part of your operation. Write down essential workflows, acceptable workarounds and unresolved market checks before comparing cost.

Use POS Finder to explore options with your shop context, then bring this checklist to provider demos. Visit Comparisons for available product research and its evidence status. Vendor research alone cannot establish a universal best POS for clothing stores.