A printable Viticulture score sheet lives or dies on a kind of argument no other game in this catalogue produces: not an argument about the final tally, but an argument about a point scored three years ago. Viticulture does not wait until the end to score you. Victory points arrive one and two at a time, all game long, on a shared track — a wine order filled in winter, a visitor played in summer, the single point for waking up late on row six of the wake-up chart — and the cork on the track remembers nothing about where any of them came from. So when the game ends with two players level, and the tiebreak walks past lira because both players hold the same amount, and lands on the total value of wine still sitting in the cellar, the table is suddenly trying to reconstruct five years of small, unrecorded gains from memory and goodwill. Or the reverse dispute, earlier and uglier: "you were on nineteen, not twenty," said in year four about a point nobody logged in year two, with the end of the game itself riding on whether the trigger was actually crossed. Every disputed Viticulture finish is the same dispute in different clothes: a running total with no history, a trigger nobody can prove, and three tiebreak values nobody wrote down before the cellar was cleared. That is the seller this vertical rewards. Not the seller with the prettiest Tuscan watercolour, because the board comes in the box and your buyer already owns it. The seller whose sheet is a ledger — one row per year, points recorded by source as they happen, the residual tracker position noted at every year end, and a tiebreak strip at the foot of the page that captures lira, cellar wine and crush-pad grapes before anyone touches the board — so the argument ends at the sheet instead of starting there.
What a printable Viticulture set actually contains (and why it is a ledger, not a tally grid)
A Viticulture set is not a pad of identical tally boxes, and treating it like the end-game scoring games is the first design error in this niche. At minimum a serious set contains five things.
First, the year ledger itself, built for up to six players in the base game. Each player needs one row per year, and each row needs columns for the ways points actually arrive: victory points from wine orders filled, points from visitor cards, the wake-up chart bonus for the year, points from bonus action spaces and any other gains, a running total after the row, and the player's residual payment tracker position at year end. A single box labelled "score" gives a buyer a place to write the current rumour. The ledger gives them the history that settles whether the rumour is true.
Second, a year-end checklist printed on every sheet, in the order the rules run it. Age every grape and wine token by one, up to a value of nine. Return all workers, and the temporary worker to the wake-up chart. Collect residual payments. Discard down to seven cards. Rotate the first-player token and clear the roosters. Five steps, every year, in that order — and the two that get skipped in real games, residuals and the discard, are exactly the two a printed checklist exists to catch.
Third, a residual payment strip. The tracker on the board caps at five lira a year and resets nothing between years, so a player's position is a fact worth one small box per year on the sheet. A buyer who records it yearly never has to argue about whether last year's orders had already pushed the bottle to the cap.
Fourth, a tiebreak strip, printed in full, in order: most lira; then total value of wine in the cellar; then total value of grapes on the crush pad. Three lines, each with a box per player, filled in before the board is cleared. Almost no home-made sheet prints it, and it is needed exactly once — on the night two corks land on the same number and the first tiebreak comes out equal too.
Fifth, the files themselves in the formats a download buyer actually prints: a clean US Letter version, an A4 version that does not shrink the year rows into handwriting traps, a multi-year league version for groups who play weekly and burn through sheets, and a large-print version. Viticulture runs long and finishes late. Type that was legible in your design preview at noon is not the test; the test is a tired player reading a year-two row correctly at the end of the night.
The rules every buyer assumes (and the checks that enforce them)
Get any of these wrong on the sheet and the sheet is wrong, however pretty it is — so check a draft against this list before you list it.
The game ends when a player reaches or exceeds twenty victory points — but not immediately. The current year is played through to the end, including all the year-end steps, and only then does the player with the most points win. A sheet with no room for the rest of the trigger year is teaching a wrong rule, because the player sitting on nineteen when someone else crosses twenty still has a winter to score in.
There is no point limit. Players may exceed twenty, and the winner is simply whoever has the most when the year closes. A ledger that stops printing rows, or a total box that assumes the game ended at twenty exactly, will fail a real table.
The victory point track runs below zero as well as above it. Some visitor cards cost points, and a player may not go lower than minus five — at minus five, a player may not use a visitor card that would cost more points. A ledger that starts every player at a tidy zero and never imagines a negative year will misrecord exactly the games where a visitor-heavy player needs it most.
Points come from more places than wine orders. Filling an order pays the victory points printed on the card. The wake-up chart pays one point for the row-six slot. A bonus action space can pay a point — the fill-an-order bonus space pays one victory point, but only if you actually fill an order with it. Visitor cards pay and cost points all game long. A sheet whose only points column says "orders" will under-record every other source and manufacture the year-two argument it was bought to prevent.
Filling a wine order means removing exactly the wine tokens the card shows, each at or above the value printed on the card, then gaining the points and the residual step shown at the bottom of it. The rulebook's own example is the check to design against: a red wine worth at least two and a white wine worth at least four fill an order worth three victory points and one step up the residual tracker. If your order column cannot record which wines left the cellar, the end-of-game cellar tiebreak is already compromised.
Residual payments are collected at year end, equal to your position on the tracker, and the highest payment any player can receive is five lira a year. Filling more orders after the cap does not move the bottle past five. A sheet that keeps crediting residuals beyond the cap is quietly inventing lira — and lira is the first tiebreak, so invented lira wins somebody a game they lost.
At year end, grape and wine tokens age by one value, up to nine, and the cellar gates the wine: a wine token can only age past three if the medium cellar is built, and past six only with the large cellar. Tokens are not thrown away when they cannot age — they simply stay where they are. A checklist that says "age everything" with no cellar note will have buyers discarding wine the rules told them to keep, and that wine is the second tiebreak.
Hands come down to seven cards at year end. Not eight, not "a reasonable hand" — seven, every year, as its own step. It changes nobody's score directly, which is precisely why it gets forgotten, and precisely why it belongs on the printed checklist rather than in anyone's memory.
Ties break in a fixed order — most lira, then total value of wine in the cellar, then total value of grapes on the crush pad — and the game's own information is public: vineyard mats, workers, lira and cards cannot be concealed. A visible ledger is not a house rule bolted onto Viticulture. It is the game's own information policy, written down.
And the expansions change the product, not the margins. The Tuscany expansion changes the board and adds its own systems; a base-game ledger does not record an expansion game honestly, and claiming it does is how a five-star listing earns a one-star review from the one buyer who checked.
A worked game, and the arithmetic, checked the hard way
Invent three players and run five years in the open, the way your sheet will have to.
Ana scores two points in year one, four in year two, six in year three and seven in year four. Her running totals read 2, 6, 12, 19. In year five she scores five more and reaches 24 — crossing twenty during the year, which triggers the end, but the year is still played out in full before anyone wins anything.
Ben scores three, four, six, five and six. His running totals read 3, 7, 13, 18, 24. He never triggers the end himself, and he does not need to: when the year closes he is standing exactly where Ana is standing, on 24, and the game moves to the tiebreak strip.
Cleo scores one, four, six, six and five, for running totals of 1, 5, 11, 17, 22. She finishes two points behind — while holding twelve lira, more cash than either of the tied players. Her line is the first lesson the sheet teaches: lira is not points. It never converts, it never tops up a total, and the richest player at the table can still simply lose.
Now the tiebreak, in order, from the strip nobody clears the board before filling in. First, most lira: Ana holds nine, Ben holds nine. Equal — the first tiebreak separates nobody, which is the entire reason the strip has more than one line. Second, total value of wine in the cellar: Ana's remaining cellar holds wine tokens worth seven, five and four, totalling sixteen. Ben's holds a nine and a six, totalling fifteen. Ana wins the game on the second tiebreak, sixteen to fifteen, with wine she did not sell — and if the table had cleared the cellars before anyone totalled them, that result is unrecoverable and the argument runs all night.
The residual lines tell the quieter story underneath. Ana ends year five at tracker position four and collects four lira at year end. Ben sits at the cap of five — and his row shows he reached it a year earlier, so the extra orders he filled afterwards paid their points but moved his bottle nowhere, exactly as the rules say. Cleo ends at position two and collects two. Three small numbers per player per year, and without them every one of those facts becomes a reconstruction. Check the running totals by hand before you trust them in a listing graphic: 24, 24, 22, settled sixteen to fifteen on cellar wine. If your sheet cannot produce those lines, row by row, it is not finished.
What the channels actually take from a low-priced set
A score-sheet set is a low-priced download, which means the channel's arithmetic, not your effort, decides most of your margin — and it differs enough by channel that the same file is a good product in one shop and a bad one in another.
On a marketplace with a per-listing fee and a percentage, a cheap set pays the fixed slice on every single sale, so the percentage you think you are paying understates the real cut most at exactly the price point score sheets sell at. Bundling solves part of this honestly: a base set, an expansion set and a league pack sold as one listing pay the fixed fee once on a larger basket, which is a pricing reason to bundle quite apart from the buyer's convenience.
On a percentage-only platform, the same bundle logic runs the other way: there is no fixed per-sale sting, but a flat percentage of a small price is still small money, and the platform that handles tax as merchant of record is taking a real job off your desk along with its cut. That job comes back the moment you sell from your own site, where a flat monthly delivery cost beats a percentage only after a volume threshold most first listings have not reached yet — do the breakeven on your own numbers, at your own price, before moving anything.
Delivery is part of channel economics too, even when nobody lists it as a fee. A buyer who cannot find the file, whose link expires before the weekend game, or whose A4 print clips a year row does not usually ask for help first — they refund or they review. Every support email a clean delivery prevents is margin, because your time is the only cost line that scales with every mistake in the file.
That is also why the honest caveats belong in the listing, not in a reply after purchase. This kind of tool — and FileFreight is the one this guide's author sells from, flat monthly, no per-sale cut — does not handle your taxes or act as your merchant of record, does not import your existing listings from another platform for you, and is not a native app inside a marketplace. A buyer who needs those things should buy the tool that does them. A buyer who mainly needs the right file to reach the right buyer, with the download logged, is the buyer a score-sheet set is built for, and saying so plainly is what keeps the reviews about the sheet instead of about the checkout.
The three delivery failures specific to a game scored year by year
Most digital delivery failures are generic. These three are specific to a product whose entire value is a running ledger, and each one maps to a complaint pattern sellers in this niche repeat.
The first is the clipped year row. The buyer prints the file, the fifth or sixth player column — or the tiebreak strip at the foot of the page — falls outside the printable area on their paper size, and the sheet still looks usable, until the one night a tie actually reaches the third line and the box for crush-pad grapes is half off the page. This is a file-construction failure, not a printer failure: margins tested on one paper size only, columns added until the grid fit the design instead of the page. Test-print both paper sizes, at 100 percent, on a cheap home printer, and run a full six-player game on the printout before listing.
The second is the wrong-version delivery. The buyer purchases the set with the expansion version, receives or opens the base file — because the files were named alike, zipped together carelessly, or attached in the wrong order — and discovers at the table that the ledger has no room for the systems their game is actually using. Version discipline is delivery discipline: one clearly named file per version, the player count on the cover page of each, and a first page that says which game this sheet scores and which it does not.
The third is the dead link on game night. Score sheets are bought close to use — often the day of the game. An expiring link with a short window, a delivery email eaten by a spam filter, or a download limit consumed by the buyer's own failed first attempts all land at the worst possible hour, when there is no support reply fast enough to save the evening. Generous download windows, a recovery path a buyer can use without emailing you, and a delivery log you can check when someone writes in are not luxuries in this niche. They are the product working at the moment it was bought for.
Editions and occasions are different products
The base game and the expansion game are two recording problems, not one sheet with extra columns. Added systems change what needs logging each year; a ledger stretched to cover everything covers each thing badly. Sell the base set cleanly first. List an expansion set as its own product, with its own worked example, when you have actually recorded a game on it.
Occasions split the catalogue the same way. A weekly league wants many sheets cheaply, long year grids, and season standings space. A one-off game night wants one beautiful sheet and the tiebreak strip impossible to miss. A gift buyer wants the set to look like an object, not a spreadsheet. These buyers search differently, review differently and refund for different reasons, and a listing trying to speak to all three usually converts none of them well. Pick the occasion your file actually serves and write the listing to that table, that night, that argument about a cellar nobody totalled in time.
Print format is an edition too. A fillable version a buyer can complete on a tablet at the table is a genuinely different product from a print-only pad — different checks, different failure modes, different buyer. If you offer both, deliver both as clearly separate files. If you offer one, say which, in the first screen of the listing, before the price does its persuading.
The setup that prevents all three (and when to stay put)
The setup that prevents the clipped row, the wrong version and the dead link is boring, which is why it works. Build each version as its own file with the paper size in the filename. Test-print every file at full size and record a worked game on paper — use the 24, 24, 22 game above if you like; a sheet that cannot hold it cannot hold a real one. Attach exactly the files the listing promises, in the order the listing names them. Set download limits and expiry generously enough that a buyer preparing on Friday for a Saturday game is never locked out of their own purchase, and keep a delivery record you can actually look up when a buyer writes in, so "I never got it" is a lookup, not an investigation.
Stay put, though, if your current channel is not actually failing you. If your sheets are selling, delivering cleanly and reviewing well where they are, moving them for a theoretical saving costs you search position and a working setup, and no fee table repays that. Move when the numbers at your volume say the cut is the problem, when delivery failures are reaching your inbox, or when a buyer segment you want — the league that buys the big bundle, the expansion table that needs its own ledger — is one your current setup cannot serve properly.
Viticulture will keep ending the same way it always ends: not with a tally, but with two corks on the same number and a cellar being cleared by helpful hands. The seller who wins this niche is not the one with the prettiest vineyard illustration. It is the one whose sheet recorded the game as it happened — points by source, year by year, residuals capped honestly, and lira, cellar wine and crush-pad grapes captured in order before the board comes apart. Build that sheet, print it, record Ana's sixteen-to-fifteen tiebreak win on it by hand, and only then list it.
Top comments (0)