How to choose a POS for your boutique & apparel.
Last reviewed 2026-05-26 · by the RetailPOS team
Apparel retail is its own beast because one style is rarely one SKU. A linen sundress in six sizes and three colours is eighteen physically distinct items, each with its own on-hand count, each capable of selling out independently. The buyer's most important question — “what sold first, in which dimension, and what should I reorder?” — only makes sense if the POS thinks in dimensions, not flat lists. Most cheap retail POS doesn't.
This guide is for independent boutique owners — single-store curated apparel, small-chain designer-buyer shops, family-owned children's wear, vintage / consignment stores. It focuses on the workflows that decide buyer effectiveness (sell-through by size and colour, wishlist + back-in-stock comms, consignment ledger) and the operational realities of apparel retail (returns, season changes, wholesale price tiers).
What this industry actually needs from a POS
Size × colour grid is the headline win
A linen dress in 6 sizes × 3 colours = 18 stockable items. The till should show them as a single grid (size on one axis, colour on the other); the back office should show sell-through by dimension. Without this, your buyer cannot tell that cream sold out in size L before navy.
Sell-through by dimension drives the next buy
“Cream sold 80%, navy 40%, sage 20%.” That breakdown tells the buyer to deepen the cream order and trim the sage. A POS that only reports “Linen dress: 60% sell-through total” hides this signal.
Wishlist + back-in-stock SMS lifts conversion
Customer at the till asks for a size 8 you're out of. Staff wishlist for them. When that size lands at receive time, an SMS goes out. Captures revenue that would otherwise walk out. Conversion lift is real (5-10% in shops we've seen).
Consignment is a parallel ledger
Vendor consigns 10 pieces; sells 7. At month-end, vendor gets their share. The POS should track consignment pieces separately from owned stock + settle per-vendor with one report.
Return windows + store credit policy matter
Most boutiques: 30 days refund-to-tender, then store credit only, then no returns. The POS should enforce the policy at the till (with manager override) so staff aren't making judgment calls.
Seasonal stock turn is a planning constraint
SS26 collection arrives March; markdown October. Items have a brand + season tag; reports show velocity by tag. Bulk discount actions (everything tagged “SS25” → 40% off) are a regular workflow.
Gift wrap + receipt customisation
Gift purchases are common (birthdays, anniversaries). Gift receipt hides the price, prints a return-by date. Gift wrap as a $5 service line on the ticket; some boutiques include it free.
Tag printing is a weekly job
Brother QL-810W or similar prints price tags + size labels. Boutiques print tags as new stock arrives; the POS should make this a 1-click action per item.
Must-have features
- ✓Size × colour grid at the till
One style with 18 size/colour variants shows as a 6×3 grid. The cashier taps a cell to add to cart. On-hand per cell visible.
- ✓Sell-through by dimension
Reports break down by size, by colour, by brand, by season. Buyer sees which dimension is the bottleneck.
- ✓Wishlist + back-in-stock notifications
Customer wishlist tied to a customer record. When stock arrives at receive time, the system sends an SMS or email. Bring-your-own Twilio for the SMS.
- ✓Consignment ledger
Per-vendor tracking of consigned pieces in / sold / settled. One-tap settlement at month-end. Vendor's share computed automatically.
- ✓Configurable return policy
30-day refund-to-tender, then store credit, then no returns. The POS enforces at the till; manager can override with reason logged.
- ✓Brand + season tags
Multi-tag per item. Reports + bulk actions filter by tag. End-of-season markdown by tag in one bulk action.
- ✓Gift receipt + gift wrap as a service
Gift receipt hides prices, prints return-by date. Gift wrap as a $5 SKU added to the ticket; receipt notes “Gift wrapped by [staff].”
- ✓Tag printing integration
Brother QL-810W or equivalent label printer. One click per item to print a price + size tag. Bulk print on receive.
- ✓Customer record with purchase history
Regulars are a meaningful slice of revenue. Past purchases + preferences + sizes on the customer record. Staff greets the regular with context.
Nice-to-haves
- +Pop-up sale events
Temporary 24-48 hour discount on a brand or season. Auto-on / auto-off scheduling. Most boutiques do this manually; native scheduling is a small luxury.
- +Lookbook / outfit builder
Group items into a recommended outfit; surface at the till. Niche; useful for sites with strong styling identity.
- +In-store pickup of online orders
Customer orders online (boutique e-commerce), picks up in-store. Requires e-commerce integration; lift depends on online traffic.
- +Per-staff commission on sale
The salesperson who closed the dress earns commission. Borrowed from salon-pack patterns. Few boutiques run this, but the high-end ones do.
- +Bridal / formal appointment workflow
Booking-style appointments for bridal try-ons. Multi-hour, multi-staff. Niche but high-margin where it fits.
Buying traps to avoid
- ⚠Variants as a flat list, not a grid
Some retail POS systems support “variants” but show them as a flat 18-row list at the till instead of a 6×3 grid. At lunch rush, the staff hates this. Demo the till view; if it's a list, walk away.
- ⚠Consignment as “a special supplier”
Some POS systems try to model consignment as a supplier with weird payment terms. The math gets close but never quite right. Real consignment is its own ledger.
- ⚠Wishlist + SMS as a $30/month add-on
Several POS systems gate the wishlist + back-in-stock feature behind an upgrade. For a single-store boutique, $360/year for a feature that lifts conversion by 5-10% is fine; for a 4-shop chain at $30/store/month, it adds up. Confirm whether it's included.
- ⚠Tag printing through a third-party app
If the POS exports a CSV that you import into a separate tag-printing app, you'll skip the workflow on busy days and the floor will have untagged items. Native integration is worth paying for.
- ⚠Return-policy logic that's “configurable” but lives in cashier memory
Some POS systems claim configurable return policy but the enforcement is “tell your staff.” That means refunds happen outside policy when nobody's looking. Real enforcement is the till blocking the refund with a manager override required.
How to choose your boutique & apparel POS
- 1Count your real SKU depth
How many styles do you carry? How many variants per style on average? 50 styles × 12 variants = 600 SKUs. That number drives the catalogue management workflow and stress-tests the till search.
- 2Demo the grid view
Pick your most complex style (most sizes × most colours). Ask the POS to show it on the till. If it's a flat list, the workflow fails on a busy Saturday. The grid has to be the default till view, not a back-office report.
- 3Test sell-through by dimension
On the demo: ring 5-6 sales across different sizes + colours. Pull the sell-through report. Confirm it breaks down by size, by colour, by brand. If the report is “everything sold equally well,” you cannot make buying decisions.
- 4Walk the wishlist + SMS workflow
Demo: customer asks for size 8 in cream, out of stock. Wishlist via the customer record. Receive 4 size-8-cream pieces. Confirm the SMS or email fires to the customer. Confirm cost (per SMS via Twilio is ~$0.01 — small; some POS bundle this as a $20/month add-on).
- 5Check the consignment flow
If you take consignment: demo a vendor with 10 pieces brought in. Sell 7 over a month. End-of-month settlement should compute the vendor share automatically and produce a per-vendor statement. If it's a manual spreadsheet, skip it.
- 6Validate the return policy enforcement
Demo: try to refund a 60-day-old purchase against the original card. The system should block + require manager override (per your policy). Then try store credit — should succeed. The till is the policy enforcer.
- 7Test the tag-printing flow
Receive 20 new pieces. Confirm you can bulk-print tags via Brother QL or equivalent in one workflow, not item-by-item. If tag printing is annoying, the staff will skip it.
- 8Run a real Saturday
Boutique traffic peaks Saturday afternoon. Get a 14-day trial; run a real Saturday. New customer + wishlist + try-on + multi-piece sale + a return + an end-of-day buy decision based on the day's data. The system that fits the rhythm is the one to buy.
Glossary
- Variant
- A specific size + colour + brand combination of a style. One “Linen sundress” style with 6 sizes and 3 colours = 18 variants. Each is independently stocked.
- Grid view
- The till display showing all variants of a style in a 2D matrix (size × colour). Each cell shows on-hand; tap to add to cart.
- Sell-through by dimension
- Reports that break down sales by one axis of the grid (which sizes sold first; which colours sold first). Drives the buyer's next purchase decision.
- Wishlist
- A customer-attached list of out-of-stock items they want. When stock arrives, the system notifies them.
- Back-in-stock SMS
- The text message sent to a wishlisted customer when their item arrives. Typically via a bring-your-own Twilio account.
- Consignment
- A model where a vendor lends pieces to the shop; the shop sells them and remits the vendor's share (typically 50-60%) at month-end.
- Return-policy tiers
- The progression from refund-to-tender → store credit → no returns based on time since purchase + condition.
- Season tag
- A label on items (SS26, AW25, Resort26) used for reports + bulk markdown actions at end-of-season.
- Gift receipt
- A printed receipt that hides prices, shows return-by date, lets the recipient return without knowing what was paid.
- Tag printer
- A label printer (Brother QL series, Dymo) that prints price + size tags. Boutiques print tags as new stock arrives.
Frequently asked
- How does the size × colour grid actually work at the till?
- Scan the barcode, the till loads the specific size × colour cell — no menu drill-down. The buyer's back-office grid shows on-hand per cell with red zeros for sold-out; sell-through % per dimension drives the next buy.
- Wishlist + back-in-stock — how do customers get notified?
- Customer at the till asks for a size 8 you're out of; staff adds the wishlist. When that size lands at receive time, a templated SMS goes out — bring your own Twilio account (one-time setup), or use email at no extra cost.
- Can it handle consignment vendors?
- Yes. Each consigned piece is its own item flagged with a vendor; the ledger tracks pieces in, pieces sold, vendor's share. One-tap settlement at month-end.
- What about returns past 30 days?
- Per-department return policy: 30 days fresh, then store credit only. Configurable. The customer gets store credit on their loyalty record (or a printable code) instead of original-tender refund.
- Do you do e-commerce too?
- Not directly — we're a point-of-sale system. The roadmap shows a Shopify connector landing post-V1 so you can keep one inventory across in-store and online. Today, treat us as your in-store source-of-truth and sync to Shopify nightly via CSV export.
Ready to look at the product side of this? See the boutique & apparel pack →
Open your boutique & apparel in 30 seconds.
No card. Free until your first 100 sales. Bring your own Stripe; keep your hardware.