Skip to content
Store Types

Clothing Boutique POS: Size Matrix and Consignment Payouts

Retailer OSNovember 21, 20268 min read
Clothing Boutique POS: Size Matrix and Consignment Payouts

A clothing boutique needs a POS that can build a size-and-color grid for every style, give each cell its own barcode and stock count, and keep consigned pieces separate from the stock you bought. Get the grid right and you can answer "do you have this in a medium?" in seconds. Get consignment right and you can pay each consignor the correct amount without a shoebox of tags. Most boutique problems come from doing one of these two things on paper.

This post covers both: how to set up matrix inventory so counts stay true, and how to run consignment so payouts are fair and easy to check. Where it describes Retailer OS, it says so. Consignment-specific tools are not something Retailer OS lists as a feature, so that part is general advice for any system you consider.

What is matrix inventory for a boutique?

Matrix inventory is a way to create one style once and have the system build every size and color combination as its own item, each with its own barcode and stock count. A dress in four sizes and three colors becomes twelve sellable items under one style. You manage the style as one thing and count the twelve as twelve things.

Without a matrix, boutiques usually do one of two things. They create one item called "Wrap Dress" with a quantity of 9, which says nothing about whether those nine are all size XL. Or they create twelve separate items by hand, with slightly different names, and spend a weekend fixing typos. Both approaches break the moment a customer asks for a size.

How do you set up sizes and colors so counts stay accurate?

Decide your naming rules before you enter the first style, because renaming 800 variants later is slow work. These rules keep the catalog clean:

  • One size scale per category. Use XS, S, M, L, XL for tops and numeric sizes for pants. Do not mix "Med" and "M" and "Medium".
  • One color list. Pick a short set of color names, such as Black, Ivory, Sage, and add to it deliberately. "Off-white" and "Cream" for the same shade split your stock.
  • A style code you can read. For example WRAP-DRS-01, with the variant suffix added by the system.
  • Cost and price on the style, then override on a variant only when it truly differs, such as extended sizes that cost more.
  • A barcode on every cell. The register cannot tell an M from an L without one.

Then count by cell, not by style. If your system says you have 9 wrap dresses, ask what the grid looks like. Four in black M, three in sage S and two in ivory XL is not nine sellable dresses for the customer who wants a black L. A boutique’s real stock position is the grid.

What should a boutique know about size-run math?

Boutiques that buy in size runs often discover that the middle sizes sell first. A simple way to see it is to track sell-through by size for a season. Suppose you bought 12 units of a style in this split: 1 XS, 2 S, 4 M, 3 L, 2 XL. After six weeks, you sold 0 XS, 2 S, 4 M, 2 L and 0 XL. That is 8 of 12 sold, a 67 percent sell-through. But the useful part is that M is gone, S is gone, and the XS and XL are sitting.

  • Sell-through = units sold ÷ units received. Here: 8 ÷ 12 = 66.7 percent.
  • Weeks of supply = units on hand ÷ units sold per week. Here: 4 ÷ (8 ÷ 6) = 3 weeks.
  • Reorder or not: if the style still has weeks of supply but the right sizes are out, reorder the missing sizes, not the whole run.

Reorder points and par levels, set per variant, are how that decision becomes routine. Reading sizes by cell is the only way to know the gap in the first place. Our post on markdown cadence, fitting-room returns and seasonal turns covers what to do with the sizes that do not sell.

How does consignment work in a boutique?

Consignment is an arrangement where a seller places goods in your store, you sell them, and you pay the seller an agreed share of the price after the sale. You never own the goods until they sell, so they do not belong in your cost of goods, and an unsold piece is not your loss. It is the consignor’s, until you return it or the agreement says otherwise.

A typical split is 50/50 or 60/40 in the consignor’s favor, but the terms are yours to set. Here is the math for a piece that sells at $120 on a 60/40 split:

  • Consignor share: 60 percent × $120 = $72.
  • Store share: 40 percent × $120 = $48.
  • Tax: collect sales tax on the full $120. The tax is not part of either share.
  • Card fees: decide in the agreement whether fees come out of the store share or are split. Write it down.

What are the traps with consignment?

Consignment is a record-keeping job, and most failures are record-keeping failures. Watch for these:

  • Mixing consigned and owned stock. If both live in one count, your inventory value, margin and reorder reports will all be wrong.
  • Lost tags. If the consignor ID is only on a paper tag, a missing tag is a missing payout.
  • No expiry. Set a window, such as 90 days, after which unsold pieces are marked down or returned, so the rack does not fill with dead stock.
  • Unclear markdown rights. Say whether you may mark a piece down, and by how much, without asking.
  • Payouts by memory. Pay on a fixed day each month from a printed list of sold items, not from whatever you remember.
  • Damaged or stolen goods. State who bears the loss before anything goes missing.

When you evaluate any POS for consignment, ask whether it can tag an item to a consignor, report what sold per consignor over a date range and keep consigned stock out of owned inventory value. If it cannot, plan on a separate spreadsheet, and keep it up to date every day, not once a month.

What does Retailer OS do for clothing boutiques?

Retailer OS has a dedicated apparel and boutique flow built around matrix inventory, so size-and-color grids are first-class and not a workaround. These parts ship today:

  • Variants and matrix (size-color). Create a style once and manage each size and color as its own item with its own stock.
  • SKUs, barcodes and label printing. Print a label for each variant so every item at the register scans to the right cell.
  • Per-item, per-location stock with a movement ledger. Every sale, transfer, receipt and adjustment leaves a row, which makes a count variance traceable.
  • Reorder points and par levels. Set them by variant so a missing size shows up before the customer asks for it.
  • Purchase orders and receiving. Receive against the order and keep cost with the item.
  • Returns and exchanges. An exchange from a medium to a large moves stock both ways in one transaction.
  • CSV import. Bring in items, customers and vendors from a spreadsheet to build the catalog.

Retailer OS does not list a dedicated consignment module, so do not buy it expecting one. If consignment is a large part of your store, ask in a demo how you would keep consigned items separate, for example by vendor, and decide whether that is enough for your payouts. We would rather you know that now than after you have set up your catalog.

Retailer OS is priced per store and per user seat: $99.99 a month per store and $9.99 a month per user. One store with the owner as the only seat is $109.98 a month. If you want to text customers when a new drop arrives, texts run on pay-as-you-go Credits at 9 cents per segment, and every new store starts with $5 in Credits. AI help with product details, such as filling in a product from a photo, also runs on Credits, billed at usage. See the pricing page for the full list.

How should a boutique price and sell online from the same grid?

If you sell online, the online store needs to read from the same size grid as the register, so a size sold in the shop disappears online right away. Retailer OS’s online store is a paid add-on at $99.99 a month, once per account, and it runs on the same catalog and inventory as the point of sale. The Amazon and eBay channels are separate paid add-ons at $99.99 a month each. The online store can also publish a product feed to Google Shopping, which you can set up through Google Merchant Center. Our post on loyalty, text campaigns and online sales from one inventory goes deeper on that side.

How do you test a boutique POS before you commit?

  • Create a style with four sizes and three colors. Time how long it takes. It should be a few minutes, not a half hour.
  • Print a label for one variant and scan it at the register. Does it ring the right cell?
  • Sell one unit, then check that only that cell’s count changed.
  • Do an exchange from one size to another and check both counts.
  • Ask for a report of stock by size for one style. If you cannot see the grid, you cannot reorder from it.
  • Ask how consigned items would be tracked, and what report you would use for payouts.

To see how this sits within the wider platform, read the Retailer OS platform overview or the page on retail inventory visibility.

Next step: bring your messiest style, the one with the most sizes and colors, to a demo and see how it looks as a grid. Request a demo and we will build it with you at the counter.

#clothing boutique POS#size and color matrix#consignment#boutique inventory#barcode labels

Last updated November 21, 2026

Run every store from one system.

Point of sale, inventory, and your team in one place. Start a 14-day free trial with no card required, or book a walkthrough with our team.