Winery Management Software: Custom Build Versus Commerce7, Vintrace and ShipCompliant
Buy, and most wineries should stop there. Under roughly 8,000 cases with one tasting room and a club below 800 members, Commerce7 plus Vintrace plus ShipCompliant is a good stack and a build is a vanity project.
On this page
Buy, and most wineries should stop there. Under roughly 8,000 cases with one tasting room and a club below 800 members, Commerce7 plus Vintrace plus ShipCompliant is a good stack and a build is a vanity project. The line moves when platform fees pass about $85,000 a year, or when a household ships against a state cap through three channels that cannot see each other.
What the off-the-shelf products actually do well
You are running four businesses under one roof: a manufacturer with a work in process cycle measured in years, a federally regulated excise filer, a hospitality operation and a subscription commerce company. No single vendor sells all four, which is why you have a stack. Be fair to the stack, because most producers should keep it.
Vintrace and InnoVint are properly good at cellar operations. Tank to tank movements, additions, work orders, barrel tracking and lot lineage, built by people who have stood in a cellar. Rebuilding that is money burned. Commerce7 is a strong direct to consumer storefront with a club engine and a point of sale (POS) that works, and eCellar and WineDirect each have real strengths in club and fulfilment. Sovos ShipCompliant is the incumbent for state rules and tax filing and it deserves that position, because maintaining fifty states of tax tables is not a job you want.
On the hospitality side, Tock handles seated reservations well and Toast or Square handle a bar. QuickBooks sits underneath most of it and NetSuite sits underneath the larger producers.
If you make under 8,000 cases, run one tasting room, ship to fewer than a dozen states and your club is under 800 members, that stack is genuinely the right answer. Per order fees at that volume are cheaper than engineering, and the honest advice is to spend the difference on fruit. We give that advice regularly and it costs us projects.
Where they stop: one household, three channels, one state cap
The workflow that breaks this stack is not the cellar. It is identity, and it costs you at the moment of a sale you should have refused.
Several states cap how much wine a single household may receive from one winery in a year. Your club shipment, an online reorder, a library release and the case a guest bought at the bar and asked you to ship all count against the same household ceiling. Those four transactions live in four systems with four customer records, and one of them spells her name differently from the others. So the cap gets blown, and you find out through a carrier rejection or a state audit rather than through a warning at the register.
ShipCompliant checks the order it is given. It cannot check the orders it never saw, and it never sees the tasting room sale until somebody syncs it. That is not a product failing. It is a boundary.
The second thing that breaks is lineage. Vintrace knows 4,180 gallons left tank 14. Commerce7 knows a customer bought a case. Nothing owns the transformation between them, where gallons become bottles minus library pulls, minus lab samples, minus staff pours, minus breakage. So when a club member calls in three years about a corked bottle, or when a monitor asks, you cannot walk from her order back to the bottling run to the ferment lot in under an hour. The regulations that make this matter are concrete: the Report of Wine Premises Operations on TTB Form 5120.17, the excise return on Form 5000.24, and the record retention requirement in 27 CFR Part 24 that expects your books to stand up for at least three years.
The arithmetic: percentage fees against a build at your volume
This category prices on transactions rather than seats, which changes the shape of the comparison entirely. Your platform cost grows with revenue whether or not you use more of the product.
Take your own statements. Add the percentage of direct to consumer revenue, the per order fees, the club billing charges, the branded application add-on and the payment processing spread if it runs through the platform rather than through your own merchant account. Then add the tasting room point of sale, the reservation tool and the compliance subscription.
Worked shape. A producer at 30,000 cases doing 45,000 direct orders a year, with a platform charging a low single digit percentage plus a per order fee, commonly lands somewhere near $85,000 to $110,000 annually across that whole set. Three years of it is roughly $300,000, rising every year your revenue rises.
Against that, a focused first release sits at $60,000 to $130,000 once. The crossover in this industry is close to 45,000 direct orders a year, or about $85,000 of combined annual platform fees, whichever you reach first. Below it, buy. Above it, a build costs a fixed amount and your platform bill does not.
One caveat worth stating plainly. Building does not remove ShipCompliant. Keep it and integrate. What a build replaces is the percentage, not the compliance filing.
What a custom build actually costs
These are Digital Heroes delivery bands from more than 2,000 projects. A focused first release runs $60,000 to $130,000 and ships in 12 to 16 weeks. For a winery that is almost always one of two things: the lot to bottle ledger with the 5120.17 and household volume control on top, or the unified customer and club engine with allocation and churn scoring. Pick whichever currently costs the most in labour and risk. A full platform covering cellar integration, cost accounting, compliance, direct to consumer, club and tasting room runs $150,000 to $400,000 phased over 6 to 12 months.
The two lines almost nobody quotes:
- Migration is 10 to 25 percent of the build. Fifteen years of order history is the easy part. The work is identity resolution, collapsing duplicate customer records into households by matching address, payment fingerprint and fuzzy name, then rebuilding per state volume history against those households. Every duplicate you find is a compliance exposure you did not know you had.
- From year two, expect 15 to 20 percent of build cost each year. State rules change, your cellar system's application programming interface changes, label approvals expire and payment providers deprecate endpoints. Budget it as a line rather than meeting it as a surprise in month fourteen.
Other drivers here: keeping Vintrace in place with a bidirectional sync is usually right and is harder than replacing it, because you need a written conflict resolution policy for when both systems touch the same lot. Multiple brands across two bonded premises with a custom crush client makes the ledger meaningfully more complex. And an offline tolerant point of sale is not optional if your tasting room sits in a valley where the connection drops.
The four situations where building wins
Four conditions. You probably have two already.
- Regulatory fit. A household volume ledger every channel writes to before an order is accepted, so the register refuses the sale in real time. Reason codes on every non revenue depletion, because topping losses, library pulls, samples and comps hit your excise arithmetic differently. Certificate of label approval records wired to the SKU with a renewal clock. None of that exists in a product because no vendor owns all your channels.
- Scale economics. Past roughly 45,000 direct orders a year, percentage pricing is a tax on growth.
- A workflow that is your competitive advantage. Allocation is the example. If the logic that decides who gets the reserve lives in a spreadsheet on one laptop, that spreadsheet is your business and it has no backup, no audit trail and no successor.
- Integration sprawl across three or more systems. Cellar, storefront, compliance, reservations, register and accounting is six places holding one customer and one lot. Somebody reconciles them for a living.
Not on the list: case production alone. A producer at 40,000 cases selling through distribution with a small club should still buy.
How to decide in a week
Run one test. Pick a bottle sold to a club member last year and walk it backwards to the tank, on paper, with a stopwatch. Every hop counts: order to bottling run to lot to fruit intake. Write down each system you had to open and each person you had to ask.
If it takes under an hour and one system, your stack is fine and your problem is discipline. If it takes a day and four people, you have measured the cost of not owning the ledger, and you can price it by asking your controller how many days a month she loses to reconciliation.
Second test in the same week: pull one household that bought through the club, the web and the tasting room, and add up what shipped to that address against the state cap. If nobody can produce that number without a spreadsheet, you now know what your exposure looks like.
After that, run a paid discovery phase. At Digital Heroes that means a signed product requirements document before any code is written, covering the lot model, household identity resolution, the integration boundary with Vintrace and ShipCompliant, and acceptance criteria. The document is yours whichever firm you choose. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under law your own counsel reads, and we build and run our own products, including Section Vault and ShopScore, so the people choosing your architecture live with those decisions on their own revenue.
We are the wrong firm if you want someone walking your cellar weekly, or a quote before a specification exists. We work remotely, with a named team you meet first, and you can check us on Clutch, Trustpilot and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
Frequently asked questions
Should we replace Vintrace or keep it alongside a custom build?
Keep it in almost every case. Vintrace and InnoVint are good at cellar operations, work orders and lot lineage, and rebuilding that spends budget on solved problems. The build is a bidirectional integration where your ledger consumes their movement and bottling events while your system owns the money, the SKU, the household and the compliance arithmetic. Insist on a written conflict resolution policy for when both systems touch the same lot.
How long does migrating fifteen years of order history take?
Budget three to five weeks inside the project rather than treating it as an afterthought. Moving orders is straightforward. The real work is collapsing duplicate customer records into households by matching address, payment fingerprint and fuzzy name, then rebuilding per state volume history against those households. Duplication in the double digits is common in customer bases that have run through two platforms.
Do we still need ShipCompliant if we build our own system?
Yes, and you should want to. Maintaining fifty states of tax tables and rule changes is a full time product, not a feature. The sensible division is that your system owns operational truth, meaning the household ledger, the lot record and the channel data, and ShipCompliant owns the state filing and tax calculation. Integrate rather than rebuild, and check the contract for export terms.
Who owns the code and the customer database?
You should own the repository, the cloud tenancy, the payment account and the member database from the first commit, written into the contract before kickoff rather than tied to final payment. At Digital Heroes the client owns the code from day one. In this category the customer and household model is the durable asset, so name the data explicitly in the agreement rather than assuming it travels with the code.
What happens if our club manager leaves and the allocation spreadsheet goes with her?
That is the risk worth pricing before any other. Allocation logic held in one workbook on one laptop has no audit trail, no version history and no successor, and rebuilding it from memory takes a season. Moving allocation rules into a system with stored versions is often a smaller project than a full platform and removes the single largest operational dependency a winery carries.
Can a build fix club churn on its own?
No. Software surfaces the members worth saving and drafts the outreach, but a save still costs a phone call from a person who knows the member. What a build adds is the timeline that no single vendor holds: tasting room visits, club shipments, web orders, email engagement and reservation history against one household record, scored on your own cancellation history rather than a generic model.
Is it worth building at 15,000 cases?
Usually not on its own. At that size the question is not volume but channel count and club size. If you run one tasting room, ship to under a dozen states and your allocation fits on a page, stay on the stack. If you already run three tasting rooms and a club above 2,000 members at 15,000 cases, the arithmetic can work earlier than case production suggests.
What is the difference between the 5120.17 and the 5000.24?
The 5120.17 is the Report of Wine Premises Operations, which accounts for what moved in and out of your bonded premises in gallons. The 5000.24 is the excise tax return, which reports what you owe on wine removed for consumption or sale. They are different documents on different cycles, and a developer who cannot tell you which is which will learn your regulatory model on your budget.
Can the tasting room register enforce a state cap while offline?
It has to, if your tasting room loses connectivity, and that requirement changes the architecture. The workable pattern holds a cached household ledger on the device, enforces the cap locally, and reconciles on reconnect with an exception queue for anything that raced. Ask any developer how they handle two registers selling to the same household during an outage, because that is the case that decides the design.
How do we prove what a bottle actually cost us?
Accrue cost to the lot at every event rather than allocating at year end: fruit contract cost at intake, labour at each work order, barrel cost amortised per month of occupancy, glass and dry goods at bottling, and non revenue depletions charged back to marketing or hospitality instead of buried in cost of goods. Then per bottle cost becomes a query rather than a two week project.
Is customizing Odoo cheaper than building an ERP from scratch?
Usually yes in year one, and often no by year three if your workflows sit far from Odoo's assumptions. Odoo's published pricing starts around $25 per user per month and the Community edition is free, but heavy customization means every version upgrade can break your modules and needs paid rework. If you expect to rewrite more than about a third of the core flows, a scratch build with clean ownership tends to cost less over the life of the system.
Is SAP overkill for a mid-sized company?
For most companies under about 500 employees, yes. SAP S/4HANA is built for multi-entity, multi-country enterprises with implementations measured in years and seven figures, while SAP Business One, the mid-market product, still forces your processes into its mold. If your competitive edge lives in how you operate, a custom ERP scoped to your actual workflows ships faster and costs a fraction of an SAP program.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
What mistakes kill ERP projects most often?
The three we see most in rescue work at Digital Heroes: recreating the old system's broken process in new software, launching everything at once instead of module by module, and having no single internal owner with authority to decide. A fourth is skipping the parallel run on data migration to save two weeks, which trades a short delay for months of distrust in the numbers. None of these are technical failures, which is why vendor selection should weigh process discipline over demo polish.
Will a custom ERP scale as we grow from 50 to 500 employees?
Yes, if it is designed for that from the start, which mostly means clean database design, permissions that handle new departments, and modules that stay separable. Adding users to software you own costs nothing in licenses, the opposite of the per-seat scaling penalty on NetSuite or Dynamics. What does need budget as you grow is new modules and integrations, so keep a small standing development arrangement rather than restarting a vendor search every two years.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Can we keep our current ERP and just build custom modules around it?
Often yes, and it is frequently the smartest first move. Digital Heroes regularly builds custom scheduling, quoting, or warehouse tools that sit on top of SAP, NetSuite, or Odoo through their APIs, which fixes the painful 20 percent without a risky replacement. The hybrid route costs a fraction of a full rebuild and tells you within months whether a bigger migration is even necessary.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 .
