POS for a Consignment or Thrift Store: Payouts and Markdowns

A POS for a consignment or thrift store has to do three things most retail systems do badly: tag one-of-a-kind items quickly, track who owns each item and what share they earn, and mark prices down on a schedule. If your POS cannot show you, on any day, how much you owe each consignor, you will end up reconciling by hand. This guide covers what to look for in any POS, and says plainly what Retailer OS does and does not cover today.

What makes a consignment store different from other retail?

In a normal shop you buy stock, own it, and sell it again and again. In a consignment shop you hold other people’s goods and share the sale price with them. Every item is a one-off. There is no reorder, no vendor catalog and often no manufacturer barcode.

A consignment sale is a sale of an item you hold on behalf of someone else, where the shop keeps an agreed percentage and owes the rest to the consignor.

That one definition creates the whole list of POS requirements. The system must know who owns each item. It must calculate the split at the moment of sale. It must keep a running balance per consignor. And it must handle the fact that an item that sits for 60 days is worth less than the same item on day one.

• One-off items: each piece has its own record, price, photo or description, and tag.
• Consignor ownership: every item is linked to the person who brought it in.
• Split percentages: the shop and consignor shares, which often change by price band or by consignor tier.
• Markdown schedules: automatic price drops at set ages, such as 30, 60 and 90 days.
• Payouts: a way to pay each consignor what they are owed, by cash, check or store credit.
• Unsold items: a rule for returns to the consignor, donation or disposal at the end of the term.

How do split percentages and consignor payouts work?

Splits are usually a flat percentage, such as 50/50 or 60/40 in the consignor’s favor, or a sliding scale where the consignor earns more as the item price rises. The math is simple, but the volume is not.

A worked example

A consignor brings in a jacket. You price it at $80.00 on a 50/50 split. It sells on day 35 after a first markdown to $64.00.

• Sale price: $64.00.
• Shop share at 50%: $32.00.
• Consignor share at 50%: $32.00, added to what you owe them.
• Sales tax is collected on the $64.00 and is not part of either share.

Now multiply by 400 items a month and 120 active consignors. The risk is not the formula. It is that the balance owed is wrong, a payout is made twice, or an item sells with no link to its owner. Each of those is a cash loss or a dispute.

When you evaluate any POS, ask these questions:

• Can each item carry a consignor and a split percentage?
• Does the system compute the consignor share on every sale, including discounted and returned items?
• Can you print a statement showing what each consignor sold, what they earned and what you paid?
• Does a payout reduce the balance owed, and can you pay by cash, check or store credit?
• Are consignor balances kept separate from your own revenue in reports?

How should a thrift store handle one-off items and tags?

Thrift and consignment shops live or die on intake speed. If it takes four minutes to enter one blouse, a shelf of 200 pieces takes a full day. The goal is a tag in your hand in under thirty seconds.

The workflow most shops land on has four steps.

• Intake: record the consignor, category, price and condition.
• Label: print a barcode tag and attach it. The tag number, not the product name, is the identity.
• Shelve: put the piece in its category and note the date. The date drives markdowns.
• Sell: scan the tag at the register. The sale closes the record.

Because every item is unique, quantity is always one. A good system makes that fast: a short entry form, a few defaults by category, and a label printer that is ready when you are. Be wary of any POS that forces you to create a product, a variant and a vendor before you can print one tag.

Retailer OS supports SKUs, barcodes and label printing, and CSV import for items, customers and vendors. That lets a shop bring in a batch of items from a spreadsheet and print tags for them. What it does not do is link an item to a consignor or compute a split.

How do markdown schedules and price changes work?

A markdown schedule is a set of price drops tied to how long an item has been on the floor. Most consignment contracts spell it out, for example 25% off at 30 days and 50% off at 60 days.

The schedule matters for two reasons. It moves aging inventory, and it must be applied consistently, because the consignor’s share is calculated on the marked-down price. If one clerk discounts an item at 28 days and another waits until 40, consignors will notice.

• Sort the floor by intake date, and mark down by section on a fixed day each week.
• Use a color-dot system on tags so staff can see an item’s age at a glance.
• Keep a record of the old price and the new one, so you can explain every change to a consignor.
• Decide in your contract who bears the markdown. Usually the consignor’s share falls with the price.

In Retailer OS, discounts and price overrides are available at the register, and an item’s price can be changed in the catalog. A markdown on a given date is a manual action, not an automatic one. For the rules on overriding prices at the counter, see price overrides at the register.

How do you pay consignors?

There are three common payout methods, and most shops offer more than one.

• Cash or check: simple, but needs a drawer count and a record of who was paid.
• Store credit: the shop keeps the money and the consignor spends it. Many shops pay a bonus, such as 10 to 20 percent more, if the consignor takes credit.
• Bank transfer: a periodic batch payment, often monthly.

Store credit is where the math pays off for the shop. If a consignor is owed $100.00 and takes $115.00 in store credit, you hand over merchandise that costs you less than that. The shop keeps its margin, and the consignor spends it with you.

Retailer OS handles store credit and gift cards as tenders, and customers can pay with a mix of cash, card, gift card, store credit and a customer account in one sale. It also records cash drawer opens and closes, with the expected amount shown and any variance noted. It does not calculate a consignor’s balance for you. See split-tender payments for how mixed payments work.

What can Retailer OS do for a consignment or thrift store?

Retailer OS is an all-in-one retail system. It was not built around consignment, so the fit depends on how much of your process you can run with the pieces it has. The parts that help a resale shop are real:

• Fast checkout with barcode scanning, discounts, price overrides, returns and exchanges.
• Tags and labels through SKUs, barcodes and label printing.
• Bulk entry through CSV import of items, customers and vendors, plus a full data export.
• Store credit and gift cards as tenders, with split payments.
• Customer profiles with purchase history, loyalty programs and referrals. Texts and email campaigns need a Messaging & AI plan (Starter $39.99, Growth $69.99, Pro $99.99 a month).
• Reports and dashboards with saved views and scheduled email digests.
• Card payments on your own Stripe account, with Stripe Terminal readers. Stripe charges its fees directly, and Retailer OS takes no cut of sales.
• Offline selling in the desktop app only. The iOS app has no offline mode.
• An online store as a separate paid add-on at $99.99 a month, on the same catalog and inventory.

If you track consignor ownership in a spreadsheet next to your POS, that works at small scale, but it is a manual step on every sale. Many owners start there and move to a dedicated consignment system as the number of consignors grows. Be clear with yourself about which category you are in before you pick a tool.

On cost: a store is $99.99 a month and each user seat is $9.99 a month, so one store with the owner as the only seat is $109.98 a month. Add-ons are separate. See the pricing page for the full list, and note that the first 14 days are free with no card required.

How do you choose a POS for a resale shop?

Rank your needs by how much a failure would cost.

• Highest cost: wrong consignor balances. This is trust, and trust is your business.
• High cost: slow intake. It limits how much you can put on the floor.
• Medium cost: inconsistent markdowns. It leaves money on the shelf and annoys consignors.
• Lower cost: reporting polish. Helpful, but you can live without it for a month.

Then run a trial with your own data. Enter twenty real items from three consignors, sell half, mark some down, return one, and pay out a balance. Count how many steps happened outside the system. If the answer is more than a few, keep looking, or plan the manual step honestly.

For a broader checklist that applies to any shop, read what a small retail store needs from a POS, and browse our other store type guides.