The short version: General e-commerce is built to put a package in the mail. Cottage food is built around a person collecting something on a specific day, made in a home kitchen, under state rules that often restrict or prohibit shipping altogether. That difference produces seven requirements no general platform is designed for, and the most important is the least glamorous: room on the product page for ingredients, allergens, and a shared-kitchen statement, because on a cottage food listing that text is doing legal work rather than marketing work. No platform makes you compliant. What good ones do is stop making compliance harder.
Four constraints that general e-commerce does not assume.
You cannot always ship. Many state cottage food laws restrict or prohibit shipping, and most exclude anything needing refrigeration. So the entire shipping apparatus that Shopify, Etsy, and Squarespace are built around may be unusable to you regardless of how good it is.
Your kitchen is your home. Which means your pickup point may be your address, and that has privacy consequences a normal retailer never thinks about.
Your labelling is regulated. Ingredients, allergens, net quantity, and in many states the producer's name and address. Some of that has to appear on the package, and the sensible place for it to also appear is the listing.
Your capacity is a hard limit. You can make forty loaves, not forty-seven. A running inventory count designed for a warehouse does not express "forty per Saturday, resetting weekly."
Everything below follows from those four.
Those four constraints are the whole checklist that follows, and each one has a ninety-second test you can run inside any trial. Our platform scorecard turns the same requirements into a fill-in sheet.
The one that matters most and gets the least attention in any comparison.
A cottage food product page needs to carry:
The FDA's food allergies guidance covers the major allergens that belong in that text, and NIST's packaging and labeling program maintains the model regulations states adopt for net-quantity statements.
The practical test on any platform: can the description field hold all of that without becoming unreadable, and does it display before someone adds to cart rather than in a collapsed tab?
This is also the single highest-return thing you can do for your own workload, because allergen questions are the most common message any food vendor receives, and a page that answers them is a message you never have to write.
Not "pickup as a fulfilment option," which everything offers.
What a cottage food business actually needs:
A platform with one global cutoff either blocks orders you could have taken or leaves you no prep time. There is no configuration that fixes it, and the loss is invisible because nobody tells you they wanted to order on Tuesday.
The cost of getting this wrong is invisible, which is what makes it dangerous. A platform with one global cutoff loses you the Tuesday orders you never knew were attempted, and no report will ever show them.
Per item, per day, resetting each week.
A running stock count is designed for a shop with things on shelves. You need "forty croissants this Saturday," and next Saturday it is forty again. Those are different mechanics, and plenty of platforms only offer the first.
Test it directly: set a cap of two, try to order three. Ninety seconds, and it eliminates more candidates than any feature list.
The cost of getting this wrong is not abstract. A platform that accepts the forty-seventh order for forty items has produced a morning of refunds, apologies, and customers who are slightly less likely to return.
One number worth writing down before you test anything: your true weekly capacity per product, in units. If a platform cannot hold that number as a hard per-day cap that resets weekly, every busy week ends in refunds.
Worth checking deliberately, because defaults vary.
What good looks like:
The test takes thirty seconds: open your own storefront logged out, in a private browser window, and read what a stranger sees. Do it again after any settings change.
Worth knowing the limit, though. Many state cottage food laws require the producer's name and address on the label, so a customer holding your jar may have it regardless of what your storefront shows. Ask your state agency whether a business address or permit number is acceptable instead, and do that before printing anything.
Three jobs, and most platforms do one.
Calculating the right rate at checkout is common. Filing a return with each state is rare. Remitting the money is rarer still. A feature name tells you nothing: Big Cartel lists "Sales tax autopilot" without defining which of the three it covers.
For a cottage food vendor selling at markets in more than one town, this gets complicated quickly, because the rate usually follows where the sale happens rather than where you baked. Three markets can mean three combined rates, and a platform applying your home rate to all of them is quietly producing wrong returns.
So the question is: do you calculate, file, and remit, and do you apply the rate for the pickup location? The second half of that is rarely asked and it matters as much as the first.
Because a meaningful share of cottage food orders arrive by text, by phone, or at a market stall.
If you cannot create an order on a customer's behalf, you keep a second list. Two lists means two stock counts, a pick list that is always incomplete, and the reconciliation you bought software to stop doing.
Shopify calls this a draft order, Square lets you build one from the dashboard, and Bakesy is built around it. Plenty of platforms cannot. Test it, and check the manual order reduces stock like a normal one, since some record the order without touching inventory, which is worse than not having the feature.
The volume makes this a requirement rather than a convenience. For most market vendors, somewhere between a fifth and a half of orders arrive by text, phone, or in person, and every one of them needs to land in the same stock count.
The thing you use every week, in a hurry, often with wet hands.
What you need on a Thursday night is not a list of orders sorted by customer name. It is per-item totals: 62 sourdough, 24 focaccia, 18 brownies. That is what you bake from, and a platform that only gives you the first means you rebuild the second in a spreadsheet every week.
Then on Saturday you need the same information grouped by collection point, so you load the van correctly.
Test this with a real weekend of orders and ask one question: could I work from this as it is? If the answer is no, the spreadsheet you were trying to eliminate has just come back.
Worth being explicit, because software marketing implies otherwise.
The most a platform can do is not make it harder: give you room for the label text, let you express your real collection schedule, and cap what you can actually make.
Anything claiming more than that is worth a careful read. Our guide to cottage food labeling requirements covers what actually has to appear, and your state agency is the binding authority on all of it.
Worth settling before the software question, because it can eliminate whole categories of both.
Most state cottage food laws work from a permitted list or a prohibition on anything requiring refrigeration for safety. Which means the constraint on your catalog is legal rather than technical, and no platform will warn you.
Three practical consequences:
Our guide to the Big 9 allergens on a cottage food label covers the labelling side of whatever does make the list, and it is worth reading before you write product descriptions rather than afterwards.
Once you know what you are allowed to sell and how people will collect it, the software question becomes straightforward. Loading that real catalog and those real collection rules into a trial is what turns a shortlist into an answer.
Four tells, and they are quick to check.
Does the pickup flow assume a day, or an address? Platforms built for shipping treat pickup as a shipping method with the postage removed. It shows immediately.
Are quantity caps per-day or a running total? Warehouse thinking versus kitchen thinking.
Does the product page have room for a real ingredient list? Some fields are built for one line of marketing copy.
Does the checkout ask when, or just where? A cottage food order has a collection date, and platforms that treat it as an afterthought make you type it into a notes field.
None of those is about branding. A platform can call itself bakery software and fail all four, and a general storefront can pass three of them.
Six things, in the order that eliminates fastest.
Then the commercial questions, which matter less than any of the above: the subscription, the processing rate, and whether either multiplies by the number of places you sell.
Our guides to selling at multiple farmers markets and writing product descriptions that sell food online cover the two places most of this work actually lands.
If your requirements look like that list, Homegrown is $10 a month billed annually with 0% commission and 2.9% plus $0.30 processing published up front, and it handles pickup at each place you sell with its own schedule and cutoff, local delivery with a radius and a route, and sales tax calculated, filed, and remitted in all 50 states. The honest bounds: it does not ship nationally, has no point-of-sale, no drop countdowns, no sell-by-weight, and no CSA subscriptions. If your state permits shipping and posting parcels is your model, a general storefront does something this does not. You can test all six checks in a trial with your longest ingredient list and your two hardest pickup points, which is the version of this article that produces an answer rather than a shortlist.
Every platform below shows the same four commercial facts, because a table that lists one platform's transaction fee and not another's is not a comparison. "Not published" means exactly that: the company does not state it publicly.
| Platform | Room for ingredients and allergens | Subscription (annual) | Free trial | Platform fee | Card processing |
|---|---|---|---|---|---|
| Homegrown | Product description carries a full ingredient list | $10/mo billed annually | 7-day free trial | $0 platform fee (0% commission) | 2.9% + $0.30 processing |
| Bake.Shop | Baker-shaped listings with description space | $149/yr (= $12.42/mo) | 14-day free trial | $0 platform fee (0% commission) | 2.9% + $0.30 processing |
| Bakesy | Custom-order forms rather than fixed listings | $9.99/mo Standard (monthly only) | 30-day free trial | $0 platform fee | 3.9% + $0.30 processing, optional |
| Square Online | General description field, no allergen structure | Free tier; paid from $29/mo per location | 30-day trial on paid plans | $0 platform fee | 3.3% + $0.30 free tier, 2.9% + $0.30 paid |
| Etsy | Description field, but shipping-first and often not permitted | No subscription | n/a | $0.20 listing + 6.5% commission | 3.0% + $0.25 processing |
| Cottage CMS | Built for cottage food specifically | Free tier; Pro $200/yr | No trial needed, free tier | Platform fee not stated | Square's processing rate, not restated |
General e-commerce assumes shipping a package. Cottage food assumes collection on a specific day, from a home kitchen, under state rules that often restrict shipping entirely, with capacity limits and mandatory label information.
Room on the product page for full ingredients, explicit allergens, and a shared-kitchen statement, displayed before someone adds to cart. On a cottage food listing that text does legal work, not just marketing.
Only if your state permits shipping cottage food, and many restrict or prohibit it, particularly for anything needing refrigeration. If you cannot ship, everything a platform offers around postage and carriers is capability you will never open.
Because you can make forty, not forty-seven. A running stock count is warehouse thinking; you need per-day caps that reset weekly. Set a cap of two and try to order three, which takes ninety seconds.
No. Your permit, labels, registrations, and knowledge of your state's permitted products are yours. The most software can do is not make it harder, by leaving room for label text and expressing your real schedule.
Check the pickup address appears only after payment and that the pickup location is a separate field from your account address. Open your own store logged out in a private window and read what a stranger sees.
Its pickup flow will treat collection as a shipping method with the postage removed, its caps will be a running total rather than per-day, and its checkout will ask where rather than when.
Cottage food is not small-scale e-commerce. It is a different shape: collection rather than shipping, a home kitchen rather than a warehouse, hard daily capacity, and label information that has to appear whether or not it helps you sell.
The requirement that decides most of it is the least discussed: room on the product page for full ingredients, explicit allergens, and a shared-kitchen statement. That text is doing legal work, it removes the most common message any food vendor receives, and plenty of platforms give you a field built for one line of marketing copy.
Then test the two things that take ninety seconds each: set a cap of two and try to order three, and give two pickup points different days and cutoffs. Between them they eliminate more candidates than any amount of reading, and no amount of strength elsewhere compensates for failing either. Both produce a yes or a no, which is more than most comparisons manage.
