Estate Sale Management Software

Estate sale software for the whole house, tagged once.

Your crew prices a house on paper tags and a spreadsheet, then rebuilds the family settlement from receipts after the sale. We turn that week into one system: every item tagged once, every sale recorded as it happens, and a settlement the family can read line by line.

See our work

Bring one recent sale. 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

The tag on the item and the price on the sheet disagree, and the buyer is already at the table.

02

Discount day starts and nobody is sure which items were meant to stay at full price.

03

The settlement takes days to rebuild from receipts, and the family still asks what sold.

Plain answer

Estate sale management software helps a liquidation company tag and price every item in a house, run sale day sales, track what did not sell, and produce an itemised settlement for the family. RaftLabs builds it around your sale week, your crew roles, and your commission and cleanout rules.

What to remember

  • Use this when the same sale week repeats and the paperwork after it keeps costing days.
  • One record per item should carry the tag, the price, the sale, and the settlement line.
  • The first release should cover one full sale, from first walkthrough to family settlement.
  • Discount rules, held back items, and price changes need a written record, not crew 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 tagging, sale day checkout, and the family settlement in the way your crew 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 crew trusts it and the gaps are narrow. Start with evidence: where the records live, how prices change, what the settlement leaves out, and who can see and change what.

  • 03

    Build

    Own the system when your sale week has rules the maintained products will not follow: your discount schedule, your hold back list, your commission and cleanout terms, and a settlement in your format. Start with one complete sale.

  • 04

    Wait

    Do not turn unsettled sale rules into permanent software. Fix the contract terms, the discount policy, and who may change a price first, then measure what the paperwork costs you across a few sales.

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.

Running more sales is not enough on its own. The case is real when the same paperwork problems show up after every sale.

A fit

You run in-home sales most weeks, and each one ends with days of settlement work.

Price changes, discount days, and held back items depend on crew memory today.

Families or executors ask item level questions your current records cannot answer fast.

Not a fit

A maintained estate sale product already covers your week with reasonable setup.

You run one small sale now and then, and a price list is all the record you need.

Your commission, discount, and cleanout terms change from sale to sale 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 sale week, not the software.

An estate sale problem usually starts as a paper problem. The crew walks the house and writes tags by hand. Prices live in a notebook or a spreadsheet. On discount day, the reductions live in one person's memory. After the doors close, someone rebuilds the whole sale from receipts to work out what the family is owed.

The visible complaint may be "we need better tags." The real cost sits later in the week. A tag and a price sheet disagree in front of a buyer. A held back item gets discounted because nobody wrote the exception down. The settlement goes out as one total, and the executor asks about three specific items the family cared about. Answering takes days, because the record was never built to answer it.

One record per item fixes the shape of the week. The item is entered once, with its room, photo, and price. The tag prints from that record. Checkout reads the same record, applies the discount for that day, and marks the item sold. What does not sell gets a closing state. The settlement is then a print of records that already exist, not a rebuild.

Custom software makes sense when one owned system can carry that week better than a product, a connector, or a process change. The first release should run one complete sale, from the first walkthrough to the settlement and the cleanout list. It should not try to run your marketing, your listings, and your accounts in the same step.

We start where it hurts.

The screens are only one part of the job. The real scope includes the tag record, the discount rules, the sale day till, who can change a price, and the settlement the family reads.

Tagging and pricing the whole house

Walk room by room, add each item once with a photo, a category, and a price, and print or write the tag from that record. Tag numbers are issued so two crew members cannot clash. A lost tag reprints with the original price attached.

Discount days without retagging

Set the schedule once per sale, with the items and categories that stay at full price named in advance. Checkout shows today's price next to the original, and every reduction follows the rule instead of a decision at the table.

Sale day checkout that keeps the line moving

Run more than one checkout point from the same item list, take cash, card, and split payments, and keep holds and deposits attached to the item. The same item cannot sell twice, and the running total matches the records as the day goes.

Unsold items and the cleanout

Close each unsold item with a state the family agreed to: return, donation, buyout, or removal. The cleanout list and the settlement come from the same records, so the house ends empty and the paperwork agrees with what left in the truck.

A settlement the family can check

Every sold item listed with its tag, asking price, and final price. Commission and agreed costs come off line by line. Sales tax stays apart from the family money. The net owed is the last line, and any single line can be traced back to a sale day record.

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 week

One sale, four jobs, one record.

An estate sale is four jobs that pass work to each other. Software earns its place when the price set on Monday is the price on the tag, the price at the till, and the price on the settlement.

Set up and stage

The house record holds the family or executor contact, the contract terms, the sale dates, and the rooms. Items the family keeps are marked held from the start, so they never reach a tag or a table.

Price and tag

Everyday goods go in fast, in batches by room or table. Pieces that may be worth more get flagged for a closer look before a price is set. Nothing is retyped later, because the tag, the listing photo, and the settlement line all read the same entry.

Sell

Checkout reads the tag, applies the day's discount, and records how the buyer paid. A pile deal at the table still marks each tagged item sold, so group prices never leave gaps in the record.

Settle and clear

The settlement builds itself from the sale records. Then the unsold list drives the last days of work: donation pickup, buyout, or cleanout, 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 sale 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 sale week

    Where does the time and the argument actually come from?

    Follow one house from the first walkthrough to the day the family gets paid. Include the handwritten tags, the price changes nobody logged, the discount decisions at the table, and the night spent rebuilding the settlement.

    Decision produced

    A map of one full sale: walkthrough, pricing, sale days, settlement, and cleanout, with the points where records break named.

    Risk closed

    Paying to fix the visible tag problem while the settlement problem stays.
  2. 02
    Shape

    Choose the first useful release

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

    Choose the shape from the way the sale runs, not from a preferred technology. Name the rooms, the devices, the discount rules, who can change a price, the exceptions, and the settlement format the first release must produce.

    Decision produced

    The first release boundary: item entry, tags, checkout, settlement, and the crew roles and rules each one needs, with a clear definition of done.

    Risk closed

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

    Review working software

    Will it hold up in a real house on a real sale day?

    Review the product against the agreed sale week, not a tour of finished screens. Tag a room, lose a tag, change a price, sell at a discount, close an unsold item, and check that the settlement still reads clean.

    Decision produced

    Working checkpoints tested with a real house worth of items, real crew roles, a discount day, and a settlement read by someone outside the build.

    Risk closed

    Discovering the gaps on the Friday morning a line is already at the door.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new system shorten the week, and can another capable team operate it?

    Run one sale on the new system while the old way stays as backup. Compare the hours spent on settlement and the questions the family asked before the next sale moves over.

    Decision produced

    A controlled release on one sale first, a comparison of settlement time and disputes 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 sale

The house, the crew roles, the tag record, the discount 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 tagging, checkout, and settlement the way your crew already worksYour discount, commission, and settlement rules are the way you win and keep referrals
Manual workSetup and process changes can remove the paperworkThe settlement rebuild repeats after every sale and costs days
ConnectionsExisting connections work with reasonable setupA critical connection to your other systems cannot be done cleanly any other way
Neighbouring workUse auction software when the sale is bidding on consigned lotsOwn custom software when the work is fixed price, in the home, and ends with a family settlement

Work with us

Bring one recent sale. 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 one in-home liquidation sale. One record per item carries the room, the tag number, the price, and the category. Sale day sales, holds, and discounts update that same record. After the sale, the unsold items, the cleanout record, and the family settlement all come from those records, not from a second spreadsheet.

A focused first release covers the house record, room by room item entry with photos, tag numbers that cannot clash between crew members, a price history for every change, a discount schedule set once per sale, sale day checkout on more than one device, holds and deposits, an unsold item record for donation, buyout, or cleanout, and the itemised settlement. Your contract terms decide the commission and expense rules; the software applies them the same way every time.

Tag numbers are issued by room or by crew member, so two people working at opposite ends of the house cannot hand out the same number. Each tag points back to one item record with its photo and price. If a tag falls off or gets damaged, a reprint brings back the original price, so the item never gets priced twice by mistake.

You set the schedule once for the sale: full price on the first day, then the reductions you use on later days. Items or categories you hold back, such as jewellery or pieces under a separate agreement, stay at full price by name. At checkout the screen shows the price for today next to the original price, so the crew never has to guess or retag the house.

Yes. Two or three checkout points can work from the same item list, so the front room table and the garage table cannot sell the same item twice. Cash, card, and split payments sit on the same sale record. Sales tax is recorded apart from the family money, because it belongs to neither side of the settlement.

Houses, basements, and barns often have weak signal. The sale day screens should keep working without a connection: item lookup, checkout, and the running total stay on the device, then sync when a connection returns. The scope should state plainly what works offline and what waits for signal, and the crew should test it in a real house before a live sale depends on it.

Every sold item appears with its tag number, category, asking price, and final price. Below that, your commission and the agreed costs, such as advertising or cleanout, come off line by line, and the last line is the net owed to the estate. The executor sees the working, not just a total. That one change turns most settlement disputes into a short check of a single line.

Each unsold item gets a closing state in the same record: held for family, donated with a receipt noted, sold in a buyout, or removed in the cleanout. The settlement and the cleanout list then agree with each other. What your company promises the family is a contract decision. The software makes sure the record matches the promise.

An auction house sells consigned lots by bidding, often from its own rooms. An estate sale is a fixed price sale inside the family home, over a few days, with discount days and a cleanout at the end. If your work is saleroom bidding and consignor lots, our auction house page is the closer fit. This page covers in-home liquidation and the family settlement only.

A retail till assumes the same shop, the same stock, and repeat customers. An estate sale is one house, one weekend, and stock that will never repeat. Pawn shop software adds loans and regulated retail records, which an estate sale does not have. Estate sale software starts at the walkthrough, not the till, and ends at the settlement and the empty house.

A spreadsheet holds a price list well. It breaks when the same item also needs a tag, a discount state, a sale record, a payment note, and a settlement line, and three people update it during one weekend. The warning signs are simple: two prices for one item, a settlement rebuilt from receipts, and questions from the family that take days to answer.

The first paid phase may cover a bounded audit of your current sale process, a small proof, or a first release that runs one complete sale. The final price depends on how many crew roles use it, whether checkout and payments are included, what it needs to connect to, and how your commission and expense rules work. The agreed phase is priced in writing before it starts.

That is a rule you set before the build. A common split is simple: the person tagging can set the first price, only the sale lead can change a price after setup, and the person at checkout cannot change a price at all. Every change keeps the old price, the new price, who made it, and when. When the family asks about one item, you answer from the record.

You judge what you can see, not the code. Run one real sale week through each checkpoint yourself: tag a room, change a price, sell at a discount, and read the settlement 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 sale days get replaced.