Selling printable Catan score sheets as downloads: the sheet your buyer trusts when a victory point is argued over

A printable Catan score sheet is judged at the one moment the board stops being complete evidence: the declaration. For two hours the island has been public — anyone can count the settlements and cities standing on it, and anyone can see who holds the two special cards. What nobody can see is the one thing that most often decides the game: the victory point cards lying face down in front of a player who has been quietly buying development cards since the middle of the game. Then that player says "ten," on their own turn, and the table has to settle three different kinds of points at once — the points standing on the board, which can be recounted; the two special cards, whose ownership changed hands during the game and whose history is written nowhere; and the hidden cards, which exist as points only in the moment they are revealed. Someone says "you were on eight when I took the army," someone else says "that road was broken an hour ago," and both of them are looking at a board that shows the present and proves nothing about the past. The board has no memory of who held what, when. The only evidence is the sheet: a record that either logs every point-changing event as it happens — a settlement built, a city upgraded, a knight played, a road card taken or lost — or shows a running total in pencil that nobody can rebuild once it is disputed. That is why this vertical rewards a particular kind of seller. Not the seller with the prettiest island artwork, because the island, the pieces, and the cards come in the boxed game and your buyer already owns them. The seller whose sheet separates the three kinds of points this game pays — board points that only grow, special-card points that move between players, and hidden points that are private until the win — and gives each kind its own labelled place, so a declared ten can be rebuilt from the sheet alone after the island has been packed away. Nobody refunds a score sheet because a game was dull. They stop reordering when a victory was argued over and the sheet could not settle it. This guide walks through what a serious printable set actually contains, the rules every buyer assumes your sheet enforces, a worked game with the arithmetic checked the hard way, what the main channels really take from a low-priced set, the delivery failures specific to a game whose winning point is hidden until the end, and the setup that prevents each one — including the honest cases where you should stay exactly where you are.

What a printable Catan set actually contains (and why an event log is the product)

Open a serious printable release — the kind a regular game group reorders instead of searching again, and a host prints without being asked — and count what is in it, because the contents are the product. A single total box per player is a notepad. A set is a system for making three different kinds of score survive being written at three different speeds, in pencil, by people who are also trying to win.

• An event log, not a totals box, is the core component: one row per point-changing event, one block per player, and in each row room for what changed and what the running total became. In Catan almost every dispute is about one event: a city counted as two new points instead of one, a special card still counted by the player who lost it. If the sheet stores only the running total, that event is gone. If it stores events, anyone can re-add a column in a minute and the argument ends at the row where it started.
• The victory point table printed on the sheet itself — settlement 1, city 2, victory point card 1, Longest Road 2, Largest Army 2, game to 10 — because the two commonest scoring errors in this game live in that table. A city replaces a settlement, so upgrading is worth one new point, not two; and each special card is worth two points to its current holder and zero to everyone else, including the player who held it an hour ago. The sheet that prints the table next to the log turns both mistakes into visible ones at the moment they are written.
• A special-card tracker with a holder line, not a points box. Longest Road and Largest Army each need a small strip of their own: who took the card, at what count (a road of five, six, seven; a third knight, a fourth), and who took it from them, in order. The card's two points belong on the current holder's build line and nowhere else, and the only way a table can prove that at the declaration is if every change of hands was written down when it happened — a road built an hour ago cannot be re-measured once three settlements have been built across it.
• A knights-played tally and a longest-road count, per player. Neither special card can be checked at the end from its points alone; both are races with thresholds. The army needs at least three knights played and more than anyone else; the road needs a continuous chain of at least five, forks excluded, and longer than anyone else's. A tally row for knights and a count line for each player's longest single branch give the table the two numbers each race actually turns on, instead of a claim typed by confidence.
• A private victory-point-card line. Each player needs a place to record development cards that are worth a point — written at the moment of purchase, kept private during play, and revealed only at the declaration. On paper this is a line at the edge of that player's block, designed to be covered by a hand or folded; the design detail matters less than the principle: the sheet must let a player prove a hidden point was held all along without forcing them to announce it when they bought it. A sheet with no private line forces the table's most honest players to choose between leaking their score and having nothing to show at the end.
• A final build line, below the log and visibly not another event row: board points (settlements at one, cities at two), plus a special card's two if currently held, plus hidden cards at one each, in that order. The single most expensive Catan argument is a lost special card counted twice — once by the player who took it and once, from habit, by the player who used to hold it. The build line forces the transfer to happen in writing, at the table, while the cards are still face up in front of their current holders.
• A "won on their own turn" line. Ten points only wins during the winner's own turn. A player can sit on ten through everyone else's turns — a road broken here, an army taken there can pull them back below it — and the sheet should say so at the build line, with room to note whose turn the declaration happened on. It is the rule most often forgotten by a table that has just watched someone reveal a fistful of point cards on the wrong turn.

The rules every buyer assumes (and the checks that enforce them)

A score sheet is a rules document whether its seller meant it to be or not: whatever the printed blocks imply is what the table will play. These are the rules buyers assume a Catan sheet enforces, stated the way a sheet has to state them — as things to write down, at the moment they happen.

• The game is won at ten victory points, on your own turn, and not before. If you reach ten during another player's turn you have not won yet; you must still hold ten when your own turn comes, and scores can fall in between — a special card can be taken, a road can be broken. Every player starts on two points, from the two settlements placed in setup, and the log's first row should say so, because a column that starts at zero makes every later total two points short and invents an argument at the declaration.
• Board points: a settlement is one point, a city is two — and an upgrade is one new point. A city is built on top of your own settlement and replaces it, so the day a settlement becomes a city the player's score rises by one, not two, and the log entry should read as an upgrade with a net gain of one. Each player has only five settlements, four cities, and fifteen roads in supply; a build line that shows six settlements is not a strong game, it is a recording error, and the sheet's component counts are what catch it.
• Longest Road: first continuous road of at least five, and only a longer road takes it. Count one unbroken chain of your own road pieces; branches do not add together, and only the single longest branch counts. The first player to reach five takes the card and its two points. A challenger must build a longer road to take it — matching the length takes nothing. Building your own settlement on an open intersection along an opponent's road breaks that road into pieces, which is why a road count written an hour ago can stop being true; and if a broken road leaves two or more players tied for the new longest — or nobody at five — the card is set aside until one player alone holds a road of at least five. If the broken road's owner still ties for longest, they keep the card.
• Largest Army: first to three knights played, and only more knights take it. Knights are counted when played, not when held. The first player to play three takes the card and its two points; a rival who also reaches three takes nothing — they must play more knights than the holder. A tally that counts unplayed knight cards in hand overstates two different players in most games, which is why the tally row belongs next to the words "played," in print.
• Victory point cards are hidden until the win. There are five of them in the twenty-five-card development deck — alongside fourteen knights and two each of road building, year of plenty, and monopoly — and each is worth one point, kept face down and revealed when their owner declares victory at ten on their own turn. The private line on the sheet is a record, not an announcement; a table that makes buyers write hidden points in the public total has changed the game, not just the paperwork.
• The robber is a scoring event too, because it stops production, not points. On a roll of seven no hex produces; every player holding more than seven resource cards discards half, rounded down — nine cards means discarding four — then the roller moves the robber onto a hex, which produces nothing while he sits there, and steals one card from a player with a settlement or city beside it. The sheet does not score the robber, but a game log that notes robber moves explains the production droughts that otherwise make a build entry look impossible when the column is re-read later.
• Costs and the distance rule are the sheet's quiet checks. A road costs brick and lumber; a settlement costs brick, lumber, wool, and grain, must connect to your own road, and must sit at an intersection whose three neighbouring intersections are all empty; a city costs three ore and two grain on top of your own settlement; a development card costs ore, wool, and grain. A settlement produces one resource from each neighbouring hex that fires, a city two. None of this is scored on the sheet — all of it is how a reader auditing a log knows whether the event in a row could legally have happened at all.

A worked game, and the arithmetic, checked the hard way

Four players — Ana, Ben, Cleo, and Dan — base game, first to ten. The builds below are what the sheet holds at the declaration; every total was re-added from its components, which is the check the sheet exists to make possible.

Ana finishes with two cities and three settlements standing: 2 × 2 + 3 × 1 = 7 board points. She holds Longest Road, for 2 more, and she turns over one victory point card she bought in the middle of the game and recorded on her private line when she bought it: 1 more. Her build line reads 7 + 2 + 1 = 10. Note what the table saw before she spoke: nine. Her public points — board plus road card — totalled nine, and the tenth point was hidden exactly as the rules require, which is why her win had to wait for her own turn: she reached ten in secret during Ben's turn, when she bought nothing and nothing changed hands, and had Ana's road been broken before her turn came round, she would have been declaring eight plus one, and playing on.

Ben finishes with two cities and two settlements: 2 × 2 + 2 × 1 = 6 board points. He holds Largest Army — four knights played, the tally row shows — for 2 more, and he holds no point cards. His build line reads 6 + 2 + 0 = 8. Cleo finishes with one city and four settlements: 1 × 2 + 4 × 1 = 6 board points, no special card at the end, and one victory point card: 6 + 0 + 1 = 7. Dan finishes with five settlements — his whole settlement supply on the island — and nothing else: 5 × 1 = 5. Ana 10, Ben 8, Cleo 7, Dan 5, and every component count sits inside its supply limit, which a totals-only pad could never show you.

The special-card tracker earns its keep in the middle of those finals. Cleo was the first to a road of five and took Longest Road and its two points; Ana later built a continuous six — one branch counted, forks excluded — and took the card, because six beats five and a tie would have taken nothing. Counted from the final builds, that one transfer is a four-point swing in the gap: with the card still Cleo's, the same boards would read Ana 8 and Cleo 9, and Cleo, not Ana, would have been a point from winning. The army race shows the matching trap in the other direction: Cleo played her third knight while Ben already held the card with three, and took nothing, because a tie does not take the army either; Ben's fourth knight, written in the tally when he played it, is what kept the card his. And the upgrade trap is sitting in all three city counts: each of the five cities on the island added exactly one point when it was built, not two — a scorekeeper who logged even one of them as two new points would have declared a winner a full point early, in a game whose real margin at the top was earned by a hidden card.

What the channels actually take from a low-priced set

A printable Catan score sheet is a low-priced consumable, typically in the same few-dollars band as the other score sheets in this series, and at that price the channel arithmetic — not the sticker — decides what you keep. Work it on a representative sale, and put your own current figures in before you list, because these rates change and your product page should never quote this guide's numbers as the channel's promise.

On a marketplace sale, the buyer finds you, and you pay for being found: a listing fee where the marketplace charges one, a transaction percentage on the total including any shipping-equivalent or tax handling the marketplace applies, and a payment-processing percentage plus a fixed amount. On a five-dollar sheet those fixed amounts are not rounding — the fixed processing piece alone can take a larger share than any single percentage line, which is why bundling matters more in this vertical than in almost any other: a pad-length file, a three-to-four-player and a five-to-six-player pair, or a score-sheet plus robber-tracker set sold as one listing spreads every fixed fee across more value without changing your per-game price in the buyer's head. On your own storefront, there is no marketplace transaction percentage, but there is still processing on every order, and there is the delivery cost the next sections are about — a failed download on a two-dollar-margin product does not cost two dollars, it costs the support exchange, and support time is the only input in this business that does not scale.

Two honest consequences follow. First, never price a single bare sheet so low that one refund — issued, as refunds usually are, without the platform fees coming back to you — wipes out several good sales; price the bundle, and let the single sheet be the entry listing if you list one at all. Second, a score sheet is a reorder product only if the file is the same file every time: a buyer who reorders and receives a log with the special-card tracker moved will not complain, they will simply learn not to trust the new pad at the declaration, and the reorder after that goes to someone else. Version discipline — one canonical file, changed deliberately, announced on the listing — is a pricing decision as much as a quality one.

The three delivery failures specific to a game whose winning point is hidden until the end

Digital delivery fails in generic ways for every product — a link that expires, a file that will not open — and those are covered by every platform's help pages. A Catan score sheet has three failures of its own, and all three happen after a technically successful download, which is why sellers who only check "did the file arrive" never see them coming.

• The wrong-edition delivery. The buyer ordered the base-game sheet and received one built for an expansion — with lines for harbours-as-points, progress cards, or a thirteen-point game — or the reverse, and their table's sheet has no line for a card their edition actually pays. The scoring blocks differ exactly where it matters, and the sheet gets blamed for a picking error that happened in your fulfillment settings. It happens when several near-identical files sit behind similar listings and the mapping between listing and file was set once and never re-checked after an edit. The symptom in reviews is never "wrong file" — it is "not as described," which costs more.
• The print-scale failure. The buyer's printer dialog shrinks the sheet to fit a different paper size, the event-log rows compress, the component pairs ("city — net +1") no longer fit inside the row, and the scorekeeper starts writing across row boundaries — recreating, in the buyer's kitchen, exactly the unauditable record the product exists to replace. A file cannot control a printer dialog, but it can defend itself: the print specification on the sheet itself, a row height chosen with margin rather than at the minimum, and a one-line test in the instructions — print one sheet, enter a full city upgrade and a special-card transfer in it, and check both stay inside the lines before printing the pad.
• The version-drift failure. You improve the sheet — you add the set-aside note to the road tracker after one review too many — and you update the listing's preview image but not the delivered file, or the file but not the preview. The next buyer plays a different sheet from the one they thought they bought, and when their longest road is broken into a tie, their copy genuinely does not have the rule your support reply tells them to use. Every element of the product — preview, description, delivered file — has to change in the same edit, or not change at all.

None of these three is a platform bug. All three are mapping and versioning discipline, which is unglamorous and entirely within the seller's control — and that is good news, because it means a careful seller can be visibly better than the field at the exact moments buyers remember.

Editions and occasions are different products

The fastest way to ruin a good Catan sheet is to keep adding to it. The base game, played to ten with the standard table and the two standard special cards, wants one event log, one special-card tracker, one private line, and nothing else on the page. Everything else a buyer might want is a different product for a different table, and should be sold as one, with its own listing, its own preview, and its own delivered file.

A five-to-six-player edition is the clearest case: the extension adds pieces, a bigger island, and a build phase between turns that changes when events happen, so it wants more player blocks and a log that survives a longer, slower game, not the four-player grid with two columns squeezed in. An expansion edition — for the well-known variants that add cities-and-knights progress, seafaring scenarios, or a thirteen-point target — is a genuinely different product, because its point sources are genuinely different, and should be labelled as that edition everywhere, never bundled silently with the base file. A classroom or club edition wants the opposite trade — more games per page, a smaller log, and a results strip a teacher or club host can collect — because its buyer is buying throughput, not audit depth, and should be told so honestly on the listing. And a large-print edition is a real product, not a setting: bigger rows, heavier rules lines, fewer events per page, for players for whom the standard log is genuinely hard to write in — its buyers are loyal precisely because most sellers treat their need as a printer setting.

What does not belong in any edition is island artwork pretending to be the game. A score sheet seller does not sell Catan, does not sell hexes or robbers, and should never imply the boxed game's maker endorses the pad. Name the game because buyers search by it and because nominative use is how a compatible accessory is honestly described; do not copy the box art, the logo, or the island into your preview. The sellers who get into trouble in game-adjacent verticals are almost never the ones who wrote their own scoring block — they are the ones who made their listing look official.

The setup that prevents all three (and when to stay put)

The setup is boring, and it is the product. One canonical file per edition, named so the edition is in the filename itself. The listing, the preview image, and the delivered file changed in the same edit or not at all, with the preview re-exported from the delivered file rather than kept as a separate image that can drift. A delivery check you actually run: place a test order for each edition, download what the buyer downloads, and confirm the file in hand is the edition the listing promised — the wrong-edition failure survives every proofread and dies to a single test order. Keep the file light, the rows honest sizes, and the print specification printed on the sheet, so the buyer's first print is the test print.

For delivery itself, what you need is unglamorous: a fixed price you can read before your best month starts, expiring download links, and a file that arrives the same way every time. That is the shape to demand from any delivery tool, and it is the shape FileFreight is built around — flat-rate delivery with license keys for sellers who need them. Be honest about the limits before you move anything: it does not handle sales tax or merchant-of-record duties, it has no importer yet, and it is not a Shopify app, so if your store lives on Shopify it is not a drop-in replacement today. If your current setup already delivers the right edition, every time, at a cost you can state in one sentence, stay put — a score sheet business runs on reorders, and reorders run on the file never changing underneath a returning buyer. Move when the mapping, the versioning, or the bill is the thing you cannot state in one sentence, and not before.