Thrift Store Management Software

Thrift store software for stock you will never see twice.

Your stock arrives in bags and boxes, not from a supplier, and almost every item is the only one of its kind. We turn intake, tagging, markdowns, and payouts into one system: every item recorded once, every colour-tag discount applied on schedule, and every donor and consignor able to see their own record.

See our work

Bring one busy intake day. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

Donations pile up at the back door while the floor stays thin, because tagging takes too long.

02

Colour-tag markdown week arrives and the till still depends on cashier memory.

03

Consignors ring to ask what sold, and nobody can answer without digging through paper.

Plain answer

Thrift store management software handles stock that arrives by donation or consignment, one item at a time, with no catalogue and no reorder. It covers donation intake, colour-tag markdowns, donor receipts, consignor payouts, and a simple till volunteers can learn fast. RaftLabs builds it around your store model and rotation rules.

What to remember

  • Use this when donated or consigned stock, not bought stock, is how your store fills its floor.
  • One record per item should carry the intake, the tag, the markdown state, the sale, and the payout or receipt.
  • The first release should cover one complete path, from donation door or consignor drop-off to sale and settlement.
  • Colour-tag rotation, donor receipts, and consignor splits need written rules, not staff memory.
  • The code, cloud accounts, data, and operating notes should stay usable by another capable team.

The first decision is not what to build.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it already covers your intake, your rotation, and your receipts or payouts in the way your store works. Paying for software you do not have to maintain is often the better trade.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep a tool you already use when the floor trusts it and the gaps are narrow. Start with evidence: where the item records live, how markdowns are applied, what the payout report leaves out, and who can see and change what.

  • 03

    Build

    Own the system when your store model has rules the maintained products will not follow: your rotation length, your split terms, your receipt wording, and a till your volunteers can run without training notes. Start with one complete path from intake to settlement.

  • 04

    Wait

    Do not turn unsettled store rules into permanent software. Fix the rotation policy, the split terms, and who may override a price first, then measure what the back room paperwork costs you across a few weeks.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Custom software should earn its maintenance burden.

Selling more is not enough on its own. The case is real when the same intake and settlement problems show up every week.

A fit

Donated or consigned stock is your main supply, and intake speed decides how full the floor stays.

Colour-tag markdowns, donor receipts, or consignor payouts depend on staff memory today.

Consignors or donors ask questions your current records cannot answer without a dig through paper.

Not a fit

A maintained thrift or consignment product already covers your model with reasonable setup.

Most of your stock is bought new, catalogued, and reordered like a standard shop.

Your rotation, split, and receipt rules change week to week with no pattern.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the donation door, not the software.

A thrift store problem usually starts at the back door. Bags and boxes arrive in bursts no one can plan for. Almost every item inside is the only one of its kind. There is no supplier to ring, no catalogue to pick it from, and no second one coming when it sells.

The visible complaint may be "we need a better till." The real cost usually sits earlier and later than the till. Earlier, donations wait days to be sorted and tagged, so the floor stays thin while the back room stays full. Later, markdown week runs on one person's memory, a consignor rings for the third time to ask what sold, and a donor's receipt cannot be found when they ask for a copy.

One record per item fixes the shape of the week. The item is entered once, at intake, with its source, category, price, and tag colour. The tag prints from that record. The till reads the same record, applies the discount for that colour on that date, and marks the item sold. What does not sell gets a closing state. Receipts and payouts are then prints of records that already exist, not rebuilds.

Custom software makes sense when one owned system can carry that path better than a product, a connector, or a process change. The first release should run one complete path, from the donation door or the consignor drop-off to the sale and the settlement. It should not try to run your fundraising, your accounts, and your online shop in the same step.

We start where it hurts.

The till is only one part of the job. The real scope includes the intake record, the tag, the rotation rules, who can override a price, and the receipt or payout at the end.

Donation intake that clears the back room

Log each drop-off against its donor as it arrives, then move goods through clear states: received, sorted, priced, and on the floor. Pickup requests sit in one list with address and access notes, so collections run as one planned route.

One-of-one stock, entered once

Enter items by category, condition, and price, with a tag printed on the spot. No product codes, no supplier list, no reorder step. A lost tag reprints with the original price attached, so an item never gets priced twice by mistake.

Colour-tag rotation without retagging

Set the rotation once: weeks at full price, the discount week, and the pull that follows. The till applies the right discount for the tag colour and the date on its own. The floor keeps moving and no cashier does markdown maths.

Donor receipts that can be found again

Print the same receipt every time, naming the donor, the date, and what was given, with no value placed on non-cash goods. A copy stays on the donor record, alongside thank-you notes and round-up gifts at the till where you use them.

Consignor splits and payouts without the phone calls

Every consigned item sits on one consignor account at its agreed split. A sale credits the account at once. The payout report shows what sold, when, and what is owed, and consignors who can check their own balance stop ringing the counter.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

The floor

One item, four jobs, one record.

A thrift store is four jobs that pass work to each other. Software earns its place when the price set at intake is the price on the tag, the price at the till, and the price on the payout.

Take in

Donations and consignor drop-offs are logged at the door, with the donor or consignor named on the batch. Goods not fit to sell are recorded at this point too, so the count from door to floor still adds up at the end of the week.

Price and tag

Everyday goods go in fast, in batches by category, at the standard price for that category. Pieces that may be worth more are held back for a closer look before a price is set. The tag, the floor record, and any online listing all read the same entry.

Sell

The till scans the tag, applies the rotation discount for today, and records how the buyer paid. A volunteer-friendly screen keeps the actions plain, and refunds or price overrides wait for a manager code, with each use written to the record.

Settle and clear

Receipts and consignor payouts build themselves from the sale records. Then the unsold list drives the last job: pull, salvage, return to the consignor, or hold, each closed out against the item it belongs to.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which part of your store week costs you the most?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace one real store week

    Where does the time and the argument actually come from?

    Follow one bag of donations from the back door to the floor, and one consigned item from drop-off to payout. Include the tags written by hand, the markdowns held in memory, and the evening spent rebuilding consignor balances.

    Decision produced

    A map of one full week: intake, sorting, tagging, floor days, markdown week, receipts, and payouts, with the points where records break named.

    Risk closed

    Paying to fix the visible till problem while the intake problem stays.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one complete path to run?

    Choose the shape from the way the store runs, not from a preferred technology. Name the intake point, the devices, the rotation rules, who can override a price, the exceptions, and the receipt and payout formats the first release must produce.

    Decision produced

    The first release boundary: intake, item entry, tags, till, receipts or payouts, and the staff and volunteer roles each one needs, with a clear definition of done.

    Risk closed

    A small-looking feature list that quietly depends on printers, payments, and three different user roles.
  3. 03
    Prove

    Review working software

    Will it hold up on a busy Saturday with a new volunteer?

    Review the product against the agreed store week, not a tour of finished screens. Log a donation, reprint a lost tag, sell at a markdown, refund with a manager code, close an unsold item, and check that the payout still reads clean.

    Decision produced

    Working checkpoints tested with a real day of intake, real staff and volunteer roles, a markdown day, and a payout read by someone outside the build.

    Risk closed

    Discovering the gaps on the morning the donation queue is already at the door.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new system clear the back room faster, and can another capable team operate it?

    Run one intake path on the new system while the old way stays as backup. Compare the hours from door to floor and the calls from consignors before the rest of the store moves over.

    Decision produced

    A controlled release on one intake path first, a comparison of tagging time and payout questions with the old way, operating notes, and an account ownership map.

    Risk closed

    Measuring screens delivered instead of days saved, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names one complete path

The intake point, the store roles, the item record, the rotation rules, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

The work is checkable without being technical

Checkpoints are working software you use yourself, reported in plain language.

Custom software by industry.

Start from your domain. Each area below is a working practice with shipped products behind it.

What it costs

Every project starts at $10K.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10K

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Build or buy

Buy an existing productBuild custom software
Best fitCovers intake, rotation, and receipts or payouts the way your store already worksYour rotation, split terms, and receipt rules are the way your store runs and keeps its donors and consignors
Manual workSetup and process changes can remove the back room paperworkIntake backlogs and hand-built payouts repeat every week and cost days
ConnectionsExisting connections work with reasonable setupA critical connection to your other systems cannot be done cleanly any other way
Stock modelUse a general retail till when most stock is bought, catalogued, and reorderedOwn custom software when stock is donated or consigned, one item at a time, with no catalogue behind it

Work with us

Bring one busy intake day. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

It is software built around stock that arrives one item at a time, by donation or on consignment. One record per item carries where it came from, its category and price, its tag colour, and its state: on the floor, sold, pulled, or settled. Donor receipts, consignor payouts, and reports all read from those same records.

A focused first release covers donation intake with donor records and receipts, fast item entry by category with a tag printed on the spot, a colour-tag rotation with markdowns that apply by date, a simple till volunteers can learn in minutes, consignor accounts with splits and payouts where you consign, and a closing state for every unsold item. Your store rules decide the rotation length, the split, and what gets pulled.

It never asks for one. Items are entered by category, condition, and price, not by product code, because there is no supplier list behind them. Common goods move in fast batches with a standard price for the category. A piece that may be worth more gets flagged for a closer look before it is priced. When the item sells, its record closes. Nothing reorders.

Everything processed in a given week gets that week's tag colour. You set the rotation once: how many weeks a colour stays at full price, when its discount week starts, and what happens to what is left after that. The till applies the discount for today's date on its own, so no cashier does markdown maths at the counter and no one retags the floor.

Each drop-off is logged against the donor as it arrives, then moves through clear states: received, sorted, priced, and on the floor. For stores that collect, pickup requests sit in one list with address, access notes, and a time window, so a day of collections can be planned as one route instead of a pile of phone notes. Donations that are not fit to sell are recorded too, so the count still adds up.

The receipt names the donor, the date, and a description of what was given. For non-cash gifts it describes the goods without putting a value on them, because the donor works out the value. Your accountant and your local rules decide the exact wording and thresholds. The software prints the same receipt every time and keeps a copy against the donor record, so a lost receipt can be reissued without a search.

Every consigned item is tied to one consignor account with the split agreed for that consignor or that category. When the item sells, the account is credited at that split, less any fees your terms name. The payout report then shows each consignor what sold, when, at what price, and what they are owed. Consignors who can check their own balance online stop ringing the counter to ask.

Yes, if the till is built for it. A volunteer till has large, plain actions: scan the tag, take the payment, print the receipt. Discounts come from the tag colour and the date, not from judgement. Actions that need care, such as refunds, price overrides, and opening the drawer without a sale, sit behind a manager code, with each use recorded. Test it the honest way: ask your newest volunteer to ring up a sale with no help and watch where they get stuck.

There is only one record for the item, so there is only one state it can be in. When it sells at the till, it leaves any online listing at the same moment. When it sells online, the floor record shows it sold before a cashier can ring it. Double selling usually starts when the shop and the website keep separate lists. One list ends it.

Each unsold item gets a closing state in the same record: pulled for salvage, returned to the consignor, held for a later sale, or disposed of under your policy. The rotation report then shows how much of each week's intake sold at full price, how much the discount week cleared, and how much was pulled. That pattern tells you whether your rotation runs too long or your full prices sit too high.

A general retail till is built around products you buy, catalogue, and reorder. Its strongest tools, purchase orders and supplier lists, do nothing when stock comes through the donation door. It also has no native home for donor receipts, colour-tag rotations, or consignor splits, so stores end up bolting those on with spreadsheets. Thrift software starts at intake, not at the till, and treats every item as one of one.

They need different centres. A donation store lives on intake speed, pickup routing, donor receipts, and rotation. A consignment store lives on consignor accounts, splits, payouts, and item status that consignors can check themselves. A hybrid store needs both, with each item marked clearly as donated or consigned from the moment it arrives, so no donated item ever creates a payout and no consigned item is ever given away by mistake.

It stops working when the same item needs an intake note, a tag, a markdown state, a sale record, and a payout or receipt line, and different people hold different parts of that list. The warning signs are simple: bags waiting days to reach the floor, markdown week run from memory, consignor balances rebuilt by hand, and donor receipts that cannot be found again.

The first paid phase may cover a bounded audit of your current intake and till setup, a small proof, or a first release that runs one complete path from intake to settlement. The final price depends on whether you donate, consign, or do both, how many tills and locations it serves, what it needs to connect to, and how your rotation and payout rules work. The agreed phase is priced in writing before it starts.

You judge what you can see, not the code. Run one real intake day through each checkpoint yourself: log a donation, print a receipt, tag a batch, sell at a markdown, and read the consignor payout it produces. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Yes. Takeover starts with an audit: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Code that is sound stays. Only the parts blocking reliable intake days and sale days get replaced.