Garden Center Software: Build on Counterpoint, or Just Buy It?
The threshold is how much of your stock changes identity, not how much revenue you do.
On this page
The threshold is how much of your stock changes identity, not how much revenue you do. If you pot up more than roughly fifteen per cent of your units, your cost basis on everything you pot is guesswork and no register can fix it, which is the point at which a plant lot layer starts paying for itself. Below that, at a single location under roughly $2 million with no landscape crews and no propagation, buy NCR Counterpoint or Epicor Eagle plus a disciplined spreadsheet and put $100,000 into irrigation instead. Where you do build, keep the register: a first release covering the lot model, mobile receiving and the shrink ledger runs $60,000 to $130,000 in 12 to 16 weeks.
When is off the shelf genuinely the right call here?
Single location, under roughly $2 million, no landscape crews, no propagation, and an owner who still walks the yard every day: buy. Counterpoint or Epicor Eagle plus a disciplined spreadsheet will genuinely carry you, and $100,000 spent on greenhouse repair or irrigation returns more. That is the right answer for most of this market and we would say so on the first call.
Buy the register in every scenario, including the ones where you build. Rebuilding payment processing, tax tables, gift cards and loyalty is expensive, carries compliance obligations and improves nothing a customer will ever notice. Those are also the parts of your current system that actually work.
Keep Aspire or LMN for landscape scheduling, crew hours and job invoicing. They handle that well and replacing either adds six figures for no operational gain, because neither of them was ever the problem.
The limit of the packaged retail tools is a data model rather than a feature list, and it is worth stating precisely. They assume one stock keeping unit has one cost, one price and one condition until it sells. A hydrangea in a number one container in April and the same physical plant in a number three in August is a different grade, a different price and a different shrink risk with an accumulated cost that came with it. There is no field for that, so it lives in a spreadsheet, and the spreadsheet is wrong by Thursday.
When does a custom build actually pay off?
The signals are structural rather than aspirational and you will recognise at least three without checking. Your November count variance runs above four per cent of inventory value and nobody can attribute it by cause. You re source landscape material at broker prices more than twice a month because retail sold it out from under a signed job. Your availability list goes out by email weekly and your own designers do not trust it. You run three or more sites and cannot see stock at another site without a phone call. Or you pot up more than roughly fifteen per cent of your units.
The shrink case is the one that converts a suspicion into a decision. Today a physical count says you are short and nobody can say whether that is dead plant, unrecorded pot ups, theft at the front gate, cashiers ringing a number three as a number two because the tag faded, or flats a crew loaded at six in the morning and never mentioned. It goes into one bucket, you write it off, and you learn nothing that changes next year.
The holds case is the one with a number attached. A designer sells an install with fourteen multi stem trees that are standing in your yard, retail sells six on Saturday, and the project manager calls a broker on Thursday at a price well above the line item. Aspire and LMN cannot prevent that because they have no visibility into what is standing in block nine, and your register cannot because it has no concept of a job.
How do they compare on the things that matter in this industry?
The atom. A packaged system models the stock keeping unit. A build models the lot: a batch with a taxon, container size, grade, location, source, landed cost and a running cost roll, where pot up, grade change and consolidation are events that split or merge lots and carry cost with the units. The point of sale (POS) item becomes a projection off the lot so the register still works and nobody touches the plumbing.
Attribution. Eagle and Counterpoint give you an adjustment reason code list and the trail ends there. A shrink ledger with typed reasons, a responsible location and a photo lets you see that one block loses a share of its material every August and another does not, which is an irrigation problem you can go and fix rather than a write off you absorb.
Commitment. Soft and hard holds driven by job stage are not a reserve flag. A soft hold at proposal shows on retail availability as spoken for, a hard hold when the deposit clears prints tags and stages plants, and the register warns and requires a manager if someone rings a held lot.
Demand signal. Suggested order logic built for hardgoods with steady velocity has no weather, no season and no concept that demand for a number seven arborvitae is not demand for a number three. Forecasting at taxon, size and week needs clean demand rather than sales, which means recorded lost sales and days actually available on a sellable bench.
Where the products win. Tender, tax, gift cards, loyalty and a support desk. Keep every bit of it.
What does total cost of ownership look like at your scale?
A first release covering the lot and event model, an offline first mobile app for receiving and cycle counts and shrink capture, document extraction on grower paperwork, the shrink ledger, live availability and a two way sync with the register runs $60,000 to $130,000 in 12 to 16 weeks. A worked three site operation around $6 million on Counterpoint, with Aspire for jobs, lands at $130,000 across roughly sixteen weeks. A single site with an online only tablet app and a one way feed comes in nearer $70,000. Swap Counterpoint for Epicor Eagle and add four to six weeks and roughly $12,000 for the scheduled bridge and its reconciliation reporting.
A full platform adding job holds, forecasting, dynamic markdown, multi site transfers and grower portals runs $150,000 to $400,000 phased over 6 to 12 months.
Running costs are 15 to 20 per cent of build annually, so $20,000 to $26,000 against a $130,000 release. Three lines are specific to this trade: durable bench and block tags plus replacement phones, since both live outdoors and neither lasts; a regression test of the register sync at every version upgrade; and a review queue for document extraction that needs an owner at each site.
The register renewal is not the comparison. It is small and you are keeping it. The comparison is the leak, and you already hold the figures: the count variance you wrote off, the material re sourced at broker prices, the markdowns taken too late plus what went to compost, and the manager hours spent on manual counts and rebuilding the availability spreadsheet.
What does the hybrid look like, and when is it the honest answer?
The hybrid is the answer nearly every good operator lands on and it is not a compromise. Keep the register for tender, tax, gift cards and loyalty. Keep Aspire or LMN for crews and job costing. Build the layer neither of them can see, meaning lots, grades, locations, shrink and holds, and let it own the truth about what is standing in the yard.
Build the lot model first and nothing else. Everything in this category hangs off it and none of it works without it, so a first release that does the spine properly and defers the rest is both cheaper and lower risk than a broad shallow one. Job holds come second, because that is where the recovered money is most visible. Forecasting, dynamic markdown and grower portals wait, and forecasting in particular needs two seasons of clean demand data, which is a reason to start capturing it in phase one and build the model later.
Two things belong to you rather than the developer. Clean your taxon naming before kickoff, because most operations have the same cultivar entered six different ways across years of history, and reconciling that is evening work for your buyer at their salary cost rather than at a developer's day rate. And time go live for a slow window, late autumn or January, because the opening lot position has to be established with a full physical count using the new mobile tool and you cannot do that in May.
Defer vision grading. It needs several thousand of your own labelled photographs before it beats a person walking the bench, so it belongs after a season of the shrink ledger collecting cull photos. Anyone quoting it at launch has not built it.
Which should you choose, by operator size and stage?
Single site under $2 million, no crews, no propagation: buy. Counterpoint or Eagle and a disciplined spreadsheet, and spend the difference on the greenhouse.
Single site with landscape crews: buy, then measure one thing for a season. Count how often retail sells material a signed job needed. If that is once a quarter, keep the spreadsheet. If it is twice a month, the holds problem is real and the lot model is the only way to hold anything.
Two sites, potting up under fifteen per cent: buy, and fix taxon naming and count discipline now. Both are free, both are prerequisites for any build, and doing them may resolve enough of the variance that you never need one.
Three or more sites, or potting up more than fifteen per cent: build the spine. The lot model, offline mobile capture and the shrink ledger is a $60,000 to $130,000 project and the payback is unusually fast here because the underlying data problem is specific enough that the mass market products have never had a commercial reason to solve it.
Anyone propagating patented cultivars: scope royalty tracking explicitly rather than assuming it is included. Per unit accrual and licensor reporting is a genuine subsystem, and a developer who has never heard of a propagation licence has not built for a nursery.
If you would rather someone argued with your brief than agreed with it, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
Frequently asked questions
What does it cost to leave Counterpoint or Eagle later if we build the lot layer?
Less than you would expect, because the lot layer already owns the data that is hard to reconstruct. Unit level state, grades, locations, cost rolls, shrink history and holds live in your own store from release one, and the register only ever held a projection of them.
What you would be replacing is tender, tax, gift cards and loyalty, which is the part the register does well and which is genuinely cheap to keep renting. Most operators who build the layer never move the register, and that is the intended outcome rather than a shortfall.
What happens if our point of sale vendor changes its pricing?
Run it over three years and include the modules you pay for separately and any per site charges, because the headline figure is rarely the whole bill. Then set that against what the register is actually doing for you, which is tender and tax rather than inventory truth.
Owning the lot layer caps your exposure rather than removing the invoice. A repricing becomes a question of whether to move a register, which is a contained project, instead of a question of whether to move your entire inventory record, which is not.
How long does a garden center build take, and when can we go live?
Twelve to sixteen weeks for the first release, plus two to three weeks of discovery, then 6 to 12 months of phases for holds, forecasting and markdown.
Timing matters more here than in most industries. The opening lot position has to be established with a full physical count using the new mobile tool, which means going live in a slow window such as late autumn or January rather than attempting a cutover in April. Plan the calendar before you plan the budget.
Should we replace Counterpoint or Epicor Eagle, or build on top of them?
Build on top. Rebuilding payment processing, tax, gift cards and loyalty is expensive, carries compliance obligations and improves nothing your customers experience. Keep the register for tender and build the layer it cannot see.
Counterpoint exposes a usable database layer and a documented interface, so a two way sync takes a few weeks. Eagle is harder to write into and typically ends up as a scheduled bridge rather than a live sync, which adds roughly four to six weeks and around $12,000 for the reconciliation reporting a non live sync makes necessary.
Why does the offline mobile app add so much to the price?
Because genuine offline behaviour is a different piece of software from a web page in a wrapper. It needs local storage, a sync engine and a defined rule for what happens when two people count the same lot with no signal and both sync at four in the afternoon. That adds roughly $20,000 to $35,000.
It is also the line with the least room for negotiation. There is no reliable coverage in the far blocks in April, and an app that needs a signal gets abandoned in the second week, which wastes the whole mobile budget rather than part of it.
Can we integrate with Aspire or LMN instead of replacing them?
Yes, and you should. Aspire and LMN handle scheduling, crew hours and job invoicing well. Keep them and build the bridge that pushes committed material and actual plant cost into the job.
The custom layer owns the yard truth, Aspire owns the crew and the invoice, and the integration carries holds and substitution cost deltas between them. Substitutions logged against the job with the delta are how you find out in week two, rather than at year end, that designers are specifying material you never stock.
What compliance work should we budget for?
Plant patent and royalty tracking is the significant one. If you propagate patented cultivars you need per unit royalty accrual and reporting to the licensor, and that is a genuine subsystem rather than a field, so scope it explicitly rather than assuming it is included.
State agricultural inspection records and phytosanitary certificates for interstate shipping also need to be auditable and tied to lots and their sources. Ask any prospective developer about propagation licences early, because if they have never heard of one they have not built for a nursery.
What is the cheapest useful version we could build?
A single site with the lot and event model, an online only tablet app for receiving at the loading dock and a one way availability feed, which lands nearer $70,000. That proves the model before you spend on a yard rollout.
Below roughly $60,000 you are dropping either the lot model or the offline mobile capture, and the lot model is the reason the system exists while the mobile app is how data gets into it. A cheaper version buys you a more precise version of the number you already do not trust.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What are the most common mistakes companies make on inventory software projects?
Three failures dominate: quoting from a one-line brief so real requirements arrive later as change orders, skipping concurrency testing so the first peak season produces oversells, and going live without running the new system in parallel with the old one. All three are process failures rather than coding failures. A two-week parallel run where both systems track the same stock catches most launch disasters before they cost money.
How does moving our data from spreadsheets or Fishbowl into a new system work?
The agency exports your current records, maps fields to the new schema, deduplicates SKUs, and runs a trial import that you verify against physical counts before cutover. Plan for one to three weeks, and expect to find discrepancies, because migration always exposes drift the old system was hiding. The safest cutover happens right after a physical stock take, so the new system starts from a verified baseline.
What should I have ready before I contact an agency about inventory software?
Bring four things: your SKU count and how stock is identified (plain SKUs, or lots, serials, and expiry dates), every channel and system the software must talk to, a plain-language walkthrough of one order from purchase to shelf to shipment, and a sample export of your current data. With those, an agency can produce a real quote in days instead of a placeholder that doubles later. A one-line brief gets you a demo-sized quote for an operations-sized problem.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
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.
What's a realistic timeline for building a custom inventory system?
A usable first version covering receiving, stock movements, scanning, and low-stock alerts ships in 8 to 12 weeks across Digital Heroes inventory builds. Full multi-warehouse systems with Shopify, Amazon, and accounting integrations run 4 to 6 months. Any quote under 6 weeks usually means the vendor has not scoped concurrency handling or data migration.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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.
Who can build a custom inventory management software system?
Digital Heroes builds custom inventory management 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 inventory management 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
Published · Last updated .
