2026 buyer guide
A neutral evaluation framework with 8 categories and 47 features — the exact questions to ask any vendor before you sign a contract.
Most wineries start evaluating software when something has already gone wrong: a TTB audit found gaps, a spreadsheet collapsed at harvest, or a state DTC ruling caught the team off guard. In that mode it is tempting to sign whatever solves the immediate pain and discover six months later that the platform does not actually model the winery you run.
The market is crowded with very different products. Legacy platforms still sell perpetual licenses with 20% annual maintenance. Modern tools designed for Napa garagistes do not always understand the reality of a 200,000-case Central Valley operation. And generic ERPs offer a ‘wine module’ that is mostly an SKU template with no concept of a lot or a vessel. Each category has its own bias, and none of them is right for every winery.
This guide does not compare vendors. It compares questions. The eight categories below are the same framework you would use to interview any vendor — Cepaos included — and make a decision based on data instead of glossy decks. We added a final section about where Cepaos lands inside that same framework, without disguising it as a competitor matrix.
Evaluation framework
Use this framework with any vendor — including us. If a category stays vague in the demo, that is enough information to decide.
Does the system generate TTB-ready records (5120.17, 5120.36 and the supporting documents) from the same data you enter at the crush pad? Can it support both bonded wineries and tax-paid product? If the answer involves intermediate spreadsheet templates, you do not have compliance — you have a manual reconciliation hidden behind a logo.
Ask the vendor to walk through a real case: a lot crushed from three blocks, fermented in two tanks, blended into one cuvee, then split between 750 ml bottles and 187 ml singles. If the demo gets stuck or the rep falls back on database queries, that platform does not have traceability — it has tables.
Harvest, sort, crush, fermentation, racking, aging, blending, fining, filtration, bottling. Real winery software models each step as a stock event with loss accounting, not as a free-text note. Ask how filtration losses are recorded, how free and total SO2 attach to a lot, and how a vintage is finally closed at the last operation of the year.
If you ship outside the US, you need true multi-currency, market-specific pricelists, digital export certificates and the ability to generate proformas and packing lists in the importer's language. Legacy platforms still ask wineries to maintain a parallel Excel in EUR or GBP for distributors. That is not acceptable in 2026.
Integrations are where the difference between a winery platform and a glorified spreadsheet shows up. Ask for live demos: QuickBooks or Xero accounting sync, lab equipment API for analytical instruments, and DTC platform connectors for compliance state reporting. If the answer is 'export a CSV and upload manually', that is not an integration — it is a workaround sold as one.
Subscription monthly or annual vs perpetual license. Per case volume, per user, per site, or flat. Each model has its catch: perpetuals hide maintenance, per-user pricing penalizes large teams, per-volume punishes growth. Ask for a five-year total cost of ownership projection under two scenarios: flat and 30% annual growth.
A small winery can go live in one to two weeks. A mid-size operation, in four to six. If a vendor promises 'go-live in 48 hours' with history migrated, push back: real migration requires mapping vineyard codes, chart of accounts and TTB lot conventions. Confirm support hours, language, real SLA and whether the first month includes scheduled onboarding sessions.
Where is the data hosted? Who is the subprocessor for backups? Is a DPA available? How do you export the complete database the day you decide to leave? You own the data — but ownership only matters if the vendor honors it in practice. Ask for an up-to-date subprocessor list and the data retention policy.
We are not asking you to trust a comparison chart. We are asking you to apply the 8-category framework above and verify each answer in a live demo against your own data.
Lot-by-lot from vineyard block to bottle, including multi-source blends and fractionated bottling. TTB-supporting records generated from daily entries with no intermediate template.
QuickBooks, Xero, ShipCompliant-aware DTC handoffs and lab equipment APIs. No CSV-and-pray exports. Each integration is demoed against your data during the trial.
Transparent monthly pricing published on the website by market. No 20% annual maintenance, no per-user surcharge, no penalty for growth. What you see is what you pay.
Assisted migration from Excel or your previous system in the first 30 days at no extra cost. Scheduled onboarding sessions, not a generic support inbox.
Avoid contracts with long lock-in periods that have no clear exit clause, perpetual licenses that hide an annual maintenance fee of 18-22%, and vendors that will not commit in writing to a full data export in open format. Confirm in writing who owns the data and how it gets exported the day you cancel.
A small artisan winery is usually live in one to two weeks. A mid-size winery with 200-500 tanks and barrels typically takes three to five weeks. Multi-site operations with accounting integrations can take six to twelve weeks. Be skeptical of any vendor promising 'go-live in 24 hours' for a winery with real history to migrate.
A perpetual license is paid once but typically carries 18-22% annual maintenance for updates and support. A subscription bundles updates, support and backups in the price. For wineries producing under 100,000 cases per year, subscription is usually cheaper over five years and avoids the technical debt of running outdated versions.
If you operate a bonded winery in the United States, you file periodic TTB reports (5120.17 and 5120.36 among others). A serious winery management platform should generate the underlying numbers directly from your daily activity, not require you to rebuild the report each month from spreadsheets. Ask for a live demo of report generation from real lot data.
Require in the contract the right to export all your data in CSV or JSON, including movements, lots, vessels, lab results and invoicing. Data portability is increasingly expected, but export quality depends on the vendor. Ask for a test export during the evaluation phase and confirm it can be re-imported elsewhere without losing relationships between records.
Not necessarily, but the cost of running two disconnected systems is real. If your DTC volume is meaningful, an integrated platform means the lot you ship to a club member is the same lot tracked in your TTB-bonded inventory. Disconnected systems mean double entry, occasional disagreements about stock, and one more reconciliation at month-end.
TRANSPARENT PRICING
From $19/month
Boutique plan $149/month
14 days free, no credit card. Excel migration included. We apply the same framework you just read and answer each of the 8 categories against your real data during onboarding.
Start free trial