Most downloads are read. A crochet pattern is obeyed — row by row, round by round, often from a printed page balanced on the arm of a chair, by someone whose hands are busy and who cannot scroll back without putting the hook down. When the pattern fails, it rarely fails at the start. It fails on row 38, when the stitch count is off by two, the abbreviation means something different in the buyer's country, or the gauge they never checked turns a sweater into a tent. The buyer does not blame their swatch. They blame the file — and a pattern seller's whole business is whether the file can be followed by a stranger, alone, without the designer in the room.
A pattern is followed with yarn in hand
Your listing shows the finished piece: draped, blocked, photographed in good light. Your buyer works from counts. Those are different documents, and the counts are the product.
Write every row or round so it can be followed without looking at anything else: the stitch count at the end of the row, stated every time it changes and often when it does not; repeats written out in full at least once before they are abbreviated; and special stitches defined where they are first used, not only in a glossary the buyer has to hunt for mid-row. A maker who has to stop, put down the work, and search a PDF for what a cluster means here has already lost their place — and a lost place in counted rows becomes a frogged evening.
Export for the way patterns are actually used. Most buyers print, or work from a tablet propped at arm's length. Ship a clean PDF with type large enough to read at that distance, repeats that never break awkwardly across a page turn if you can avoid it, and page numbers on the pages themselves. Check the exported file, not the drafting document: the PDF is what gets followed, one row at a time, under lamplight.
Gauge is the whole sizing system
For a scarf, gauge is a preference. For anything worn, gauge is the sizing system — the only bridge between your stitch counts and the buyer's body. A pattern that buries it, or states it without the stitch pattern it was measured in, has left its most important number undefended.
State gauge plainly and completely: stitches and rows over 4 inches / 10 cm, in the stitch pattern the garment actually uses, after blocking, with the hook size you used — and say that hook size is a starting point, not a requirement. Buyers do not need your hook; they need your gauge, and permission to change hooks until they match it. Then make the stakes concrete in one honest line: at a slightly looser gauge, this cardigan grows an inch across the bust for every size. Makers who understand what a quarter-inch per repeat costs will swatch. Makers who were never told will not, and their one-star review will say the pattern was wrong.
Put the gauge statement in the listing as well as inside the file. A buyer who discovers after purchase that the pattern is written for a gauge their yarn cannot reach experiences that as a trap, not a detail. The listing is where expectations are set; the file is where they are kept.
Two vocabularies, one stitch: US and UK terms
Crochet is the rare craft where the same words name different stitches in different countries. A double crochet in US terms is a treble in UK terms; a single crochet in US terms does not exist under that name in UK patterns at all. Nothing about the buyer's skill protects them from this — an experienced UK maker following a US pattern literally will produce a taller, looser fabric and a wrong size, correctly, row after row.
So say which vocabulary you are writing in, in the listing and on the pattern's first page, in words a buyer will actually see before they start: "Written in US terms." If you ship a conversion chart, put it inside the file where the first abbreviation appears, not as a separate download the buyer may never open. Better still, expand the first use of every stitch in each section — "double crochet (dc)" costs nothing and anchors the reader in your dialect before habit takes over.
Do not ship an auto-converted second edition you have not re-read line by line. Term conversion is not find-and-replace: stitch names hide inside special-stitch definitions, decrease names, and notes. A converted file with one unconverted instruction is worse than no conversion, because the buyer trusts it completely — right up to the row that ruins the piece.
Written rows, charts, and photos do different jobs
Makers do not agree on the one true format, because the formats do different work. Written rows are precise and searchable. A stitch chart shows the shape of the fabric — where increases lean, how a motif repeats — in a way rows of text never will. Photos of tricky moments (the join, the turn, the first row of a border) settle questions that both text and symbols leave open.
Ship the combination your kind of pattern needs, and name what is included on the listing before purchase. A lace shawl without a chart asks buyers to hold a geometric pattern in their heads as text; an amigurumi pattern without a single photo of the assembly asks them to guess where the eyes go. "Pattern included" is the phrase that generates the support email. "Written rows in US terms, full stitch chart, and assembly photos included" is the phrase that prevents it.
Name the files like what they are and keep versions consistent across them. If the chart is corrected, the written rows must be corrected in the same release — a buyer who follows the chart at home and the text on a train should never be following two different patterns with the same name.
Yardage is a shopping list, not a guess
Before your buyer makes a single stitch, your yardage line sends them shopping — or sends them to their stash. Errors here are paid for in real money and discovered at the worst moment: one skein short, in a dye lot that no longer exists.
Give yardage per size, not a single range for the whole pattern, and give it in both yards and metres with the yarn weight and the specific yarn you used named alongside. State how much the sample actually used, and whether your figure includes a margin; experienced makers add their own buffer, but only if they know whether you already added one. If a substitute yarn changes the character of the fabric — a plant fibre where you used wool, a drapier or stiffer yarn — say so in one honest sentence. You are not responsible for the buyer's substitution, but a warning given is trust earned, and a warning withheld is a review that says the finished piece looks nothing like the photo.
For stash-friendly projects, say what makes them work: the minimum yardage that still completes the smallest size, and which parts of the piece can absorb a contrast colour if the main yarn runs out. That kind of sentence turns a pattern a buyer almost bought into one they buy tonight, because it fits what they already own.
One size is a sample, not a size range
A garment pattern in one size is a photograph with instructions. The grading — how stitch counts, shaping, and yardage change across sizes — is most of the design work, and buyers can tell the difference between a pattern that was graded and one that was merely stretched by adding repeats until the numbers looked plausible.
Be exact about what you are selling. List every size, the finished measurements for each (not just the "to fit" body measurements), and how much ease the sample is shown with, so a buyer can choose a size by the garment they want rather than the body they have. If a size was not tested, say so; testers cannot cover every size in every pattern, and an honest "sizes XL–3X are graded but untested — feedback welcome, corrections free" line brings more goodwill than silence followed by a shaping error at the yoke.
And when a correction does come — a transposed count in one size, a chart symbol that survived proofreading — treat it as part of the product, not an embarrassment. Version the file, note exactly what changed and where at the front of the corrected edition, and make sure past buyers can get the new version as easily as new buyers can. The maker mid-sweater on the error is the person your delivery exists for in that moment.
A short crochet launch checklist
Before the listing goes live, confirm each line against the exported download, not the draft:
- Gauge is stated completely — stitches and rows over 4 in / 10 cm, in the main stitch pattern, after blocking — in the listing and inside the file, with finished measurements per size.
- The terminology is named (US or UK) on the listing and the first page, first uses of stitches are expanded, and any conversion chart sits inside the file itself.
- Every row or round ends with a stitch count where it matters, repeats are written in full before they are abbreviated, and special stitches are defined at first use.
- What is included is listed before purchase: written rows, charts, and photos — each named, none implied.
- Yardage is given per size, in yards and metres, with the sample yarn named, actual usage stated, and any margin disclosed.
- Sizes are honestly labelled: finished measurements and ease stated, untested sizes flagged rather than hidden.
- The exported PDF is the thing you checked: readable at arm's length, page numbers on the pages, and all formats carrying the same version.
A closing note on delivery: none of the above is done by the delivery tool — it does not write patterns, check gauge, convert terms, or grade sizes. What delivery owes a pattern seller is simpler: the right file, reaching the buyer immediately, in a version past buyers can return to when a correction lands. FileFreight is built for that job — a flat $19/month Pro plan with 0% per-sale fees (the free plan is 5% per sale), license keys, and payments that settle into your own Stripe account. It does not handle tax or VAT for you, has no pattern importer, and is not a Shopify app. If your patterns sell one careful download at a time, that trade — your craft in the file, a flat fee for delivering it — is worth pricing out against the percentage your current platform keeps from every single row your buyers follow.
Top comments (0)