Consignment and Thrift Store Software: Build or Buy at Your Channel Mix
The threshold is roughly 300 active consignors and one selling channel.
On this page
The threshold is roughly 300 active consignors and one selling channel. One or two stores under that, selling mostly on the floor, should buy: SimpleConsign, Ricochet or ConsignCloud understand consignors, splits and markdowns for a few hundred dollars per location per month, and building is vanity at that size because your constraint is foot traffic. The flip comes when online passes thirty percent of revenue across three or more channels, you pass 800 consignors, and you have oversold twice in a quarter. Then the packaged tool has stopped saving money and started capping revenue.
When is off the shelf genuinely the right call here?
Buy if you run one or two stores with under roughly 300 active consignors and sell mostly on the floor. SimpleConsign, Ricochet and ConsignCloud all understand consignors, splits and markdown schedules, they cost a few hundred dollars per location per month, and at that size your ceiling is how many people walk through the door rather than what your software can model. ConsignPro and Liberty from Resaleworld are established alternatives in the same territory and plenty of good shops run on both.
Buy if your online activity is a single channel and modest. One store plus a Shopify presence with a manual delist is entirely workable at low volume, and the oversell risk that justifies a build only becomes real when one unit is listed in five or six places and delisting lives in somebody's head at two hundred sales a week.
What you should not do is solve this by moving to a general retail platform. Shopify point of sale (POS), Square for Retail and Lightspeed handle multi location and payments properly and have no concept of a consignor. That is the route by which operators end up running consignor accounting in a spreadsheet with fourteen tabs beside a system that cost real money, and it is a worse position than the packaged consignment tool they left.
The signal that buying is still right is that your bins are not backing up and your payout day is an afternoon rather than a week. If a tagger can keep pace with intake and one person can run payouts without a shoebox, the tool is not the thing holding you back.
When does a custom build actually pay off?
Build when several signals arrive together. Online is past thirty percent of revenue across three or more channels. You have 800 or more active consignors, or a payout run that eats more than a day of someone's week. You run three or more locations and want inventory to move between them. Somebody maintains a spreadsheet the business would stop without. And you have oversold twice this quarter.
The structural reason packaged tools cannot fix the oversell is worth stating precisely, because it is a modelling limit rather than a defect. Their marketplace sync is built around a quantity field. You sell one garment once, so what you need is a reservation event: the register scan does not decrement a count, it reserves that single item everywhere, and channel workers race to delist within seconds with each failure surfaced to a human instead of discovered through a refund. There is no configuration of a quantity based sync that becomes that.
The second earner is the ledger. Ask a consignor with 300 items what she is owed and the truth sits in five places: the contract split, a promotion applied at the register, a marketplace fee, a return processed eleven days later and a store credit conversion done by hand. Packaged tools store a balance and overwrite it, so a correction in April silently rewrites February and your defence in a dispute is a manager's memory. An append only event log where the balance is derived rather than stored makes statements reproducible for any past date and turns a forty minute dispute into a forty second one.
The third is intake throughput, which is the real growth ceiling. A good tagger runs 25 to 40 items an hour, and no packaged tool addresses that because they all assume a human types the item in.
How do they compare on the things that matter in this industry?
- Inventory model. Every other retailer sells the same item code hundreds of times. You sell one item once and owe a stranger a share of it. Quantity of one with an owner who is not you, a markdown clock and an expiry decision is a different system from a point of sale.
- Channel coverage. Channels with a published interface, such as Shopify and eBay, are ordinary integration work either way. Poshmark and Whatnot have no clean public interface, so they need a maintained authenticated browser integration. Any vendor promising six clean interface integrations including those has not built this.
- Ledger integrity. Ask whether a correction rewrites history or appends to it. If a balance is stored rather than derived, past statements are not reproducible and disputes get settled by goodwill.
- Markdown and expiry rules. Packaged schedules work for one store with one rule. Different schedules per category, split bands above a price threshold, an expiry that pauses while an item is out on a marketplace, and notice before ownership transfers are where they run out.
- Payout and tax handling. Collecting tax forms digitally at onboarding and rolling year to date payouts per tax identity across locations is not a settings screen. Nor is ageing a dormant balance into a due diligence queue.
- Data portability. Your consignor history, item history and financial events are the record you would need in any dispute. Confirm you can export all of it with dates and reasons intact, not just current balances.
What does total cost of ownership look like at your scale?
A focused first release covering item level inventory with a reservation state machine, versioned consignor contracts, an append only financial ledger, assisted intake and two channels plus your own store runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding six channels, automated payouts with tax identity rollups and dormancy handling, multi location routing, buy outright with secondhand dealer reporting, forecasting and a staff mobile application runs $150,000 to $400,000 phased over 6 to 12 months.
A three store operator with roughly 1,200 consignors selling on the floor plus Shopify, eBay, Poshmark and Whatnot came in at $194,000 across twenty weeks. Two decisions put it there rather than in the first release band: two browser driven channels at $26,000, and assisted intake at $32,000 in scope from day one. Drop both and shorten the parallel period, and the same scope lands at $128,000. Migration with reconciliation and a signed off opening balance per consignor was $24,000 on its own, typically three to five weeks of work, and it is the line nobody budgets.
Running costs are 15 to 20 percent of build cost annually, roughly $29,000 to $39,000 against a $194,000 platform. Four lines are specific to resale. Browser driven marketplace integrations break when the site changes and repairing them is permanent rather than one off. Payment and payout rail fees are transactional and scale with volume. Assisted intake needs a human review step, which is staff time rather than a licence. And unclaimed property administration carries dormancy tracking, due diligence letters and annual filings.
Against that, the honest comparison is not a few hundred dollars a month against ninety thousand. It is ninety thousand against two salaries and the growth you are not getting because intake throughput and channel coverage are capped.
What does the hybrid look like, and when is it the honest answer?
Two hybrids are worth considering before anyone prices a full platform, and both keep your packaged tool as the consignor record and store point of sale.
The first attacks oversells only. Build the item level reservation layer and the channel workers that sit between your existing tool and the marketplaces, so a register scan reserves the unit everywhere and failed delists surface to a person. This is the sharpest single risk in a multi channel resale operation and it is the one that costs you consignors rather than just money, because a consignor who watched her item sell twice and get paid zero times does not stay.
The second attacks throughput only. Build the photo station and assisted intake, drafting brand, category, colour, material, measurements, condition notes and a channel appropriate title, with a proposed price band from your own sold history, then push the finished record into the tool you already run. That turns the tagger from a typist into a reviewer, and it is the right first spend for any operator whose bins are backing up.
The condition that decides whether either hybrid is feasible is the same: whether your existing tool exposes item level data and accepts status and record updates programmatically. Several products in this category offer a data export rather than a working interface, and a hybrid built on a nightly file is a reconciliation exercise rather than a reservation system. Test that specifically during evaluation, with your own tool and your own volumes, before committing to either route.
Which should you choose, by operator size and stage?
One or two stores, under 300 consignors, floor sales dominant: buy SimpleConsign, Ricochet or ConsignCloud and put the money into inventory and rent. Nothing about a build helps you yet.
Two stores with growing online volume on one or two channels: buy the packaged tool and build the reservation layer only if you have actually oversold. If you have not, a disciplined delist process and a single person owning it is cheaper and works.
Bins backing up, tagging capped at 25 to 40 items an hour, supply plentiful: buy the packaged tool and build assisted intake first. It is the highest return module for operators whose growth is limited by processing rather than by supply, and it does not require the rest of the platform to exist.
Three or more stores, 800 or more consignors, four or more channels, payout day eating a week: build the first release and go live in one store before touching the others. Start with the channels that have real interfaces, defer the browser driven ones and their permanent maintenance obligation, and do not launch in your busiest season.
In every case where you build, insist on reconciliation rather than a straight import, and on a signed off opening balance per consignor before go live. Launching with a ledger your consignors do not believe is what ends these projects in month one, and it is the one failure that cannot be repaired with a later release.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Item-level RFID tagging enabled 99.9% order accuracy in the retail supply chain, versus a baseline where 69% of orders shipped between brands and retailers contained data errors - showing how RFID-at-POS integration reduces inventory inaccuracy. Source: Auburn University RFID Lab & GS1 US (2018) →
- Vendor case material reports that tableside/handheld mobile POS transmits orders directly to the kitchen and improves table turnover, with a hotel client example citing a 30% increase in table turns from faster handheld payment and service - illustrating the transaction-speed-to-revenue link in restaurant POS (qualitative vendor claim, not independent research). Source: NCR Voyix (2024) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- McKinsey argues software developer productivity can be measured by combining system-level metrics (DORA and SPACE) with its own outcome-oriented approach, which it reports deploying across nearly 20 tech, finance, and pharmaceutical companies - a claim that sparked significant debate in the engineering community. Source: McKinsey & Company (2023) →
Frequently asked questions
What does it actually cost to migrate off ConsignPro or SimpleConsign?
Budget three to five weeks and roughly $24,000 at around 1,200 consignors, and treat it as a project rather than an import. Your export will carry duplicate consignor records, several spellings of the same person, items with no intake date and balances that do not reconcile.
The deliverable is a signed off opening balance per consignor, not a loaded database. Insist on it. Launching with a ledger your consignors do not believe is the single most common reason these projects fail in the first month, and no later release fixes the loss of trust.
What happens if our consignment software raises its per location price?
Per location pricing is the exposure that bites growing resale operators, because a fourth store adds cost before it adds profit and a seasonal pop up is charged like a permanent site.
Ask at renewal how additional locations and temporary sites are priced, and whether marketplace connectors carry their own fee. The broader point is that your bargaining power is low while your consignor ledger and item history live inside the product, so confirm you can export financial events with dates and reasons intact rather than only current balances.
How long before we can run a store on a custom system?
Twelve to sixteen weeks to a first release, and it should go live in one store before you touch the others. That release should include the reservation model, the consignor ledger, contracts and markdown schedules and a consignor portal.
Do not launch in your busiest season and do not launch before opening balances are signed off. Full platforms with six channels and automated payouts phase over 6 to 12 months, and anyone promising all of it in eight weeks is selling you a rewrite in month nine.
Is SimpleConsign enough once we are selling on Poshmark and Whatnot?
For consignors, splits, markdowns and the store itself, it does the job. The verifiable limit is that its marketplace sync is built around a quantity field, and neither Poshmark nor Whatnot is treated as a first class channel, because neither offers a clean public interface for anyone to build against.
That means delisting a single unit across five or six places within seconds of a register scan is not something configuration reaches. If you are overselling, that is the mechanism, and it is why the narrow reservation layer beside your existing tool is often the proportionate response rather than a full replacement.
Why do Poshmark and Whatnot cost more to connect than Shopify and eBay?
Because they have no clean published interface, so the integration is an authenticated browser session that has to be maintained indefinitely. The site changes, the integration breaks, and repairing it is a recurring obligation rather than a one off build cost.
In a representative build, Shopify and eBay together were $18,000 while Poshmark and Whatnot together were $26,000, and only the second pair carries an ongoing maintenance line. Deferring them defers both costs, which is usually the right call in a first release.
Can we build only the intake side and keep our current system?
Yes, and it is the right first spend for operators whose growth is capped by tagging throughput. A photo station drafts brand, category, colour, material, measurements, condition notes and a channel appropriate title, with a proposed price band from your own sold history, and pushes the finished record into the tool you already run.
The precondition is that your existing tool accepts records programmatically rather than only by file upload. Test that with your own product and your own volumes before committing, because a nightly file makes this a batch job rather than a live workflow.
How should unclaimed consignor balances be handled?
You cannot keep them and you should not quietly zero them. Uncashed cheques and dormant store credit fall under state unclaimed property rules, which carry dormancy periods, due diligence letters and annual filings, and the specifics vary by state, so confirm yours with counsel.
A system should age dormant balances into a due diligence queue with the letter drafted, which turns an audit exposure into a monthly task. No packaged consignment tool does this today, which is one of the quieter reasons larger operators end up building the payout and tax layer.
What is the cheapest credible build in this category?
Around $60,000 for a single store operator with two channels, the reservation state machine, versioned contracts, the append only ledger and a consignor portal, with assisted intake and browser driven channels left out.
Below that you are buying a report or a listing helper rather than a system, and at that price point you should seriously reconsider whether SimpleConsign, Ricochet or ConsignCloud plus a disciplined delist process covers you. Spending sixty thousand to replace a few hundred dollars a month only makes sense if the packaged tool is capping revenue rather than merely annoying you.
How long does it take to develop a custom POS system?
Plan on 12 to 16 weeks for a working first version with checkout, catalog, payments, and reporting, and 6 to 9 months for a full multi-location rollout. In Digital Heroes projects the schedule risk is rarely the software, it is hardware certification and payment processor onboarding, which can add 3 to 6 weeks if started late. Kick off the merchant account and terminal applications in week one, not at the end.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
What should I have ready before I contact an agency about building a POS?
Bring three things: a written list of your 10 to 15 must-have workflows (returns, split payments, voids, shift close), your last three months of processing statements, and every system the POS must talk to, such as QuickBooks, your loyalty program, or a kitchen display. Agencies quote against unknowns, and this preparation tightens estimates by 20 to 30 percent in Digital Heroes scoping calls. You do not need wireframes or a technical spec; producing those is the agency's job.
Should I use a freelancer or an agency to build my POS system?
A POS build needs backend, client app, payments integration, and hardware testing skills running at the same time, which is more surface area than one freelancer reliably covers. Freelancers make sense for narrow additions, like a reporting module on an existing system, at typical rates of $30 to $90 per hour. For a ground-up build, an agency with a dedicated QA function is the safer choice because a register failure stops your revenue at the counter in real time.
Who can build a custom POS software system?
Digital Heroes builds custom POS software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other POS software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Reyansh.
iOS Lead · Delhi · 1 post on the site
Published · Last updated .
