Back to blog

How a consignment shop works, from intake to payout

Consignment is not regular retail. Here is the daily loop from drop-off to payout, and what software has to keep attached.

Hang tags, a barcode ticket, a clipboard checklist, a ruler, and a kraft envelope arranged on a charcoal counter with a rust-colored panel.

Consignment looks simple from the sidewalk. People drop things off. Other people buy them. The store keeps a cut.

The hard part starts after the first drop-off. Every item still belongs to someone who is not the store. That person will ask, later, whether it sold, what they are owed, and why the number is what it is. The shop that can answer without hunting through notebooks is the shop that keeps getting inventory.

This is the daily loop that actually runs a consignment store, whether you are opening one or looking at consignment software for a shop you already have.

The item has an owner who is not the store

In regular retail you buy stock, you own it, you sell it, and you keep the money.

In consignment the consignor still owns the item until it sells. The store is holding it, pricing it, putting it on the floor, and splitting the sale according to an agreement. Until that sale happens, the store is a caretaker, not the owner.

That one difference is why a regular point of sale is a poor fit. Checkout is the easy part. Ownership, terms, and payouts are the work.

The loop: intake, label, sell, close, pay

A working shop repeats the same five handoffs. If any one of them loses the item, the rest of the day is reconstruction.

1. Intake

Create or find the consignor. Capture what they brought: category, condition, price, brand, size, colour, notes, and how long it stays. Apply the store's commission rules to that drop-off, not to a guess later.

Keep the agreement with the intake. A signed page in a drawer is not the same as a record that still matches the item on the floor.

Messy intake is how you get two records for the same lamp, the wrong split on a jacket, and a consignor who is sure they never agreed to those terms.

2. Label

Print a barcode from the same item record. The label should already know the price, the control number, and enough detail for the floor. Re-typing that at the printer is how mistakes get baked onto the rack.

Batch printing helps on a busy drop-off day. Starting the sheet in the right label position helps more than it sounds like it should.

3. Sell

Scan the item. Record how the customer paid. Keep the sale tied to the consignor so the split is not a later reconstruction.

Discounts need a rule before anyone is standing at the register. If the store marks a slow item down to move it, does that cut the consignor's share, or does the store fund the discount? Either policy can be fair. What is not fair is a silent change to a split the consignor thought was settled.

Returns need a rule too. A return is not the same as a manager correcting a wrong price. Mixing those two makes the till and the consignor statement lie in different directions.

4. Close the day

At close, cash in the till, recorded tenders, returns, store earnings, and consignor earnings should already agree. The point of closing is to confirm the day, not to rebuild it.

If closing means a second set of books in a spreadsheet, the first system did not hold the work.

5. Pay consignors

See what each person is owed. Prepare the payout. Keep the supporting history so a question in March still has an answer.

This is the moment consignors remember. A shop can look great on the floor and still lose drop-offs if payouts are late, unexplained, or disputed. Statements built from the same item and sale records are how you stay out of that argument.

Follow one item, on paper

Before you change software, or before you open, pick one imaginary sweater and walk it through:

  1. Jane drops it off on a Tuesday. Split is 60/40, Jane's favour. It expires in 90 days.
  2. It gets a control number and a barcode. It sits on the floor.
  3. Two weeks later it sells for $50, paid half cash and half card. Jane should be owed $30. The store keeps $20.
  4. The next week Jane asks what sold. You should be able to show the sweater, the date, the price, and the $30 without reconstructing anything.
  5. You pay her. The statement still shows that sweater, that sale, and that payout.

If your current tools cannot do that for one item, they will not do it for three thousand.

That walkthrough is also the fairest way to judge consignment software. Ask the vendor to follow the sweater. Not a feature list. The sweater.

Where shops get stuck

Most pain is not "we need more reports." It is a broken handoff.

A regular retail register can take money. It does not know Jane still owns the sweater, so it cannot tell you what she is owed.

A spreadsheet can hold a list. It cannot survive intake day, a line at the register, and a payout Saturday in the same file without someone being the glue.

Disconnected tools (one place for inventory, another for checkout, a third for "what we owe") recreate the same gap the homepage of a good system is trying to close: the item disappears between the intake table, the sales floor, the register, and the payout desk.

Aging inventory is the slow version of the same problem. Items that should have gone back to Jane, been marked down, or been donated are still on the floor because nobody had a list that was trustworthy.

If you are starting a shop

Get the loop right before you add extras.

Write down, in plain language:

  • The default split, and whether some categories or consignors differ
  • How long items stay, and what happens at expiry (return, donate, markdown, extend)
  • Who is allowed to discount, and whether a store-funded discount protects the consignor's share
  • How you take payment, and how you close the till
  • How often you pay consignors, the minimum you will cut a cheque or e-transfer for, and what a statement includes
  • Who on staff can change prices, void sales, or issue payouts

Independent shops in Canada and the U.S. both run this model. Currency, tax labels, and payout habits change. The loop does not.

You do not need a custom-coded system on day one. You need practical consignment store software where those rules stick to the item as it moves.

If you are looking at consignment software

Use the sweater test, then check that the software can hold the boring parts that make a real store work:

  • Consignor and item created together, with the terms that applied that day
  • Labels printed from that same record, individually or in a batch
  • Scan-to-sell checkout that keeps the consignor on the sale
  • Discounts and returns that follow store rules instead of silently rewriting a split
  • A till you can open, trust, and close
  • Consignor balances, statements, and payout history in one account
  • Aging and expiry views so floor time has a limit
  • Staff access that matches the job (the person on the register should not have the same reach as the owner)
  • Store-set commission, markdown, tax, and payout rules, without turning the product into a custom project
  • A way to bring existing inventory in, and a way to export your data later

Ask what is in the software price and what is separate. Card terminals, scanners, label stock, and counter computers are usually the store's. That is normal. A percentage fee on your sales is a different kind of cost; know whether it is there.

Optional settings are useful when they mean "turn this on when the shop is ready," not "pay more to finish the loop."

The system behind this article

ConsignEngine is built around this same order: intake, labels, register, consignors, closing, and payouts. It grew out of Country Consignment, a working store, so the product follows the counter instead of a feature grid.

The complete feature guide documents the current store plan. Pricing is one plan, with no software setup fee and no percentage of store sales.

If you want to try the loop in a workspace, the trial is 14 days and does not need a card.

Your privacy choice

Google Analytics and Meta Pixel are active by default. Choose Necessary only to opt out. Privacy Policy.