FoodCoopShop

Purpose-built software for food coops and local shops, honestly reviewed. If you’re expecting a Shopify alternative, read the next sentence and stop.

TL;DR

• What it is: Open-source (AGPL-3.0) web shop and order management platform built specifically for food cooperatives and local shops that source directly from producers [README].
• Who it’s for: Food coop administrators managing weekly pre-orders from multiple producers — not general e-commerce operators. The difference matters [README][website].
• Cost savings: SaaS alternatives for community-supported agriculture operations (Farmigo, Harvie, Local Line) range from $50–$200+/month. FoodCoopShop self-hosted runs on any PHP/MySQL server with $0 software cost [README].
• Key strength: Ten years of continuous maintenance by a single dedicated developer, 55+ active installations in German-speaking Austria/Germany, and a feature set that genuinely maps to how food coops operate — weekly delivery rhythms, producer dashboards, cashless credit systems [website].
• Key weakness: Single maintainer creates a bus-factor risk. The German-language codebase and community means English support is secondary. The PHP/Apache stack feels dated in a Docker-first world, and 115 GitHub stars signal a small, geographically concentrated user base [README].

---

What is FoodCoopShop

FoodCoopShop is a web application that handles the specific operational problem food cooperatives actually have: coordinating pre-orders for perishable food from multiple local producers with varying delivery schedules, then tracking payments via a member credit system [README].

That’s a narrower problem than “run an online store.” If you want to sell products to anonymous internet customers via Stripe, FoodCoopShop is not your tool. If you manage a member-owned food cooperative where 40 households pre-order from 12 local farms every week, pay via bank transfers into a shared credit pool, and pick up on Friday — FoodCoopShop is built exactly for that workflow [README][website].

The project was started by Mario Rothauer in 2014, making it one of the older self-hosted food coop tools in active development. He maintains it solo and posts to the website in German [website]. As of March 2026, version 4.2 is current. The GitHub repo sits at 115 stars — a small number that accurately reflects the niche rather than the quality [merged profile].

The software is categorized under “Community-Supported Agriculture (CSA)” in the Awesome Selfhosted list [1][4], which puts it in the right bucket. It’s not general e-commerce. It’s not an inventory system. It’s a coordination layer for a specific type of community food organization.

Demos are available in German, English, and Russian, and the website lists 55 active installations [website].

---

Why people choose it

The third-party review landscape for FoodCoopShop is thin. This is a niche tool with a small, localized community, and English-language write-ups are essentially nonexistent outside of listing aggregators [1][4]. What exists is the project’s own history: 10 years of commits, regular releases, and 55 active cooperatives using it in production.

The case for FoodCoopShop isn’t built on reviewer consensus — it’s built on the absence of alternatives that handle its specific domain. Food cooperatives have genuinely unusual requirements:

Delivery rhythms. Products don’t ship on demand. A farm might deliver every second Tuesday, or the first Friday of the month. FoodCoopShop supports configurable delivery schedules per product [README]. Shopify doesn’t do this. WooCommerce can be bent to do it with plugins. FoodCoopShop does it out of the box.

Producer-facing admin. Farms and producers need their own login to manage product listings, view orders, and handle inventory without seeing the whole system [README]. This is a multi-tenant model baked into the core, not bolted on.

Cashless credit system. Most food coops don’t charge per order. Members transfer money to a shared account and draw down credit. FoodCoopShop’s payment system is built around bank transfer reconciliation, not card payments [README]. This matches how European food coops actually operate.

Order adaptions. If a producer’s harvest comes in 10% lighter than expected, orders need to be adjusted by weight and price. FoodCoopShop handles cancellations and weight/price adaptations as a first-class feature [README].

Decentralized network plugin. Multiple FoodCoopShop installations can synchronize product catalogs, supporting a network of cooperatives sharing producers [README]. This is unusual and valuable at scale.

The argument against alternative platforms like Open Food Network or Karrot [2] comes down to scope. Karrot focuses on food saving and group coordination with minimal commerce features [2]. Open Food Network handles the distribution hub model but is more complex to operate. FoodCoopShop occupies a specific middle ground: simpler than Open Food Network, more commerce-capable than Karrot.

---

Features

Based on the README and website content:

Order management:

• Web shop optimized for food from multiple producers
• Configurable delivery rhythms per product (weekly, biweekly, first/last Friday of month, etc.) [README]
• Bulk ordering / Sammelbestellungen (collective orders) [website]
• Order adaptions: weight changes, price adjustments, cancellations [README]
• Minimum order value per producer — if weekly orders fall below threshold, the system auto-cancels [website]

User and producer management:

• Separate admin areas for administrators and manufacturers [README]
• Member management with credit balances
• Cashless payment system based on bank transfers [README]

Stock and self-service:

• Self-service mode for stock products [README]
• Optional barcode scanning support [README]
• Stock tracking by quantity or weight [website]

Platform features:

• Available in German and English [README]
• Decentralized network plugin for multi-installation product sync [README]
• REST API [merged profile]
• Docker deployment available (dev and production) [README]
• Gitpod/Ona cloud development environment [README]
• Automated database backups via bzip2 [README]

Filter / convenience features:

• “Show only products for this week” filter — useful when members have many products with multi-week rhythms [website]
• “Only this week” display mode to reduce ordering confusion [website]

What’s notably absent: payment processing (Stripe, PayPal), multilingual storefronts beyond German/English, mobile apps, and any kind of AI or automation tooling. This is deliberately minimal scope.

---

Pricing: SaaS vs self-hosted math

FoodCoopShop: Free software (AGPL-3.0). No licensing cost [README]. Self-hosting cost is your server: a basic VPS or shared hosting with PHP/MySQL runs $5–15/month.

What it replaces: The SaaS market for food coop and CSA software includes several US-focused platforms. Specific pricing data for direct alternatives was not available in the sources reviewed, but the category includes:

• Local Line — CSA and farm direct software, pricing not in sources
• Farmigo — shut down in 2017, customers migrated elsewhere
• Harvie — SaaS, pricing not in sources
• Open Food Network — open-source with managed hosting options

The honest position is: if you’re running a European food cooperative, the SaaS alternatives are mostly US-centric and may not map to the bank-transfer payment model used in Austria and Germany. FoodCoopShop may be the only tool that handles the specific cashless credit system that German-speaking food coops use [website].

For a coop that would otherwise pay for a managed platform: $0 software + $10/month hosting is the floor. Mario Rothauer also offers paid installation and support services, though pricing is not listed publicly on the website [website].

---

Deployment reality check

The stack:

• Apache with mod_rewrite
• PHP >= 8.4.1 (with intl, Imagick, GD, mbstring, curl, bzip2 extensions)
• MySQL >= 8.0
• Shell access and cronjobs on the server [README]

This is a traditional LAMP stack, not a modern containerized service. The README explicitly requires “basic understanding of Apache Webserver, MySQL Database and Linux Server administration” [README].

Docker is available but feels secondary. A Docker dev environment exists, and there’s a separate foodcoopshop-docker repository for production [README]. The primary install path is still the traditional PHP/Apache route for most deployments.

What this means practically:

• If you’re comfortable deploying a WordPress site on a VPS, you can probably follow the installation guide.
• If you’ve only ever used managed hosting (Heroku, Vercel, Railway), this will require learning Apache configuration.
• If your host is a pure Docker/K8s environment, the Docker path works but the documentation depth is thinner.

Cronjobs are required. The platform relies on scheduled tasks for order processing, automated cancellations, and email notifications [README]. This rules out managed hosting environments that don’t expose cron access.

Legal information is a prerequisite. The README explicitly says to read the legal information before installing [README]. This isn’t boilerplate — food coops in Austria/Germany operate under specific cooperative law, and the software includes features tied to those legal requirements. Running this outside that context requires understanding which features apply to your jurisdiction.

Realistic time estimate: 2–4 hours for someone comfortable with Linux server administration. A full day or more if you’re unfamiliar with Apache/PHP deployment and need to debug PHP extension requirements. The PHP 8.4.1+ requirement is current as of 2026 and may require a recent server setup.

---

Pros and cons

Pros

• 10 years of continuous maintenance. Started 2014, actively releasing in 2026 (v4.2 in March 2026). Rare longevity for a niche open-source project [website][README].
• Feature set matches real food coop workflows. Delivery rhythms, producer portals, credit systems, and order adaptions are first-class features, not afterthoughts [README].
• 55 active installations. Small but real production deployments [website]. The software has been stress-tested in actual cooperatives.
• Decentralized network plugin. Multi-coop product synchronization is a genuinely unusual capability [README].
• Free as in $0. AGPL-3.0, no licensing cost, source code available [README].
• Live demos available. German, English, and Russian demo instances let you evaluate before committing [README].
• Barcode scanning. Self-service stock mode with optional barcode support — useful for larger coops with physical pickup points [README].

Cons

• Single maintainer. Mario Rothauer has maintained this project alone since 2014 [website]. There’s no team, no company, no fallback if he stops. This is the biggest risk for long-term adoption.
• German-first. The website, blog posts, and community are primarily German. The Signal support group is German-language [README]. English support exists but is secondary.
• Traditional LAMP stack. PHP/Apache with explicit extension requirements feels dated. No native HTTPS setup, no reverse proxy bundled, no managed secrets. You’re configuring Apache manually [README].
• AGPL-3.0 license. More restrictive than MIT or Apache 2.0. If you modify the software for a commercial context, the AGPL requires you to publish your modifications [README]. Fine for a cooperative, relevant for anyone building a product on top of it.
• 115 GitHub stars. Accurate reflection of the niche size, but also means limited community contributions, fewer bug reports surfaced, and less third-party documentation [merged profile].
• No card payment processing. The cashless system is built around bank transfers. If your coop wants Stripe or PayPal, you’re building a custom integration [README].
• Cronjob dependency. Shared hosting environments without cron access won’t work [README].
• PHP 8.4.1+ requirement. Current and demanding — requires a recently provisioned server [README].

---

Who should use this / who shouldn’t

Use FoodCoopShop if:

• You’re running or starting a food cooperative that coordinates weekly pre-orders from local producers.
• Your members pay via bank transfers into a shared credit account — not card payments.
• You need configurable delivery schedules per product (weekly, biweekly, monthly).
• Your operation is in German-speaking Europe, or you’re comfortable with a German-first community.
• You have basic Linux server administration skills or someone who does.
• You want a $0 software cost and can afford 4–8 hours of setup time once.

Skip it (look at Open Food Network instead) if:

• You’re managing a food hub with multiple distribution points, complex inventory, and diverse buyer types.
• You need multi-currency support or card payment processing.
• Your operation is in the US or UK and the European bank-transfer payment model doesn’t apply.
• You want a managed cloud option with a company behind it.

Skip it (look at a general e-commerce platform instead) if:

• You’re selling to anonymous customers, not a defined membership.
• You need a product catalog with thousands of SKUs, SEO optimization, and abandoned cart emails.
• Your delivery model is on-demand shipping rather than weekly pickup.

Skip it entirely if:

• You’re not comfortable with Linux administration and don’t have someone who is.
• You need commercial support with SLA guarantees.
• The single-maintainer risk is unacceptable for your organization.

---

Alternatives worth considering

• Open Food Network — open-source, more mature ecosystem, better suited for multi-hub distribution networks. More complex to operate. Available at openfoodnetwork.org with managed hosting options.
• Karrot — open-source coordination tool for food-saving groups and cooperatives [2]. Focuses on pickup coordination and group communication rather than commerce. Different problem.
• WooCommerce + plugins — flexible but requires significant plugin assembly to approximate food coop features. No native delivery rhythm support.
• Local Line — SaaS platform targeting farm direct and CSA operations. No self-hosting option; pricing not confirmed.
• Odoo Community — open-source ERP with e-commerce module. Substantially more complex and general-purpose. AGPL-3.0 as well.
• Erpnext — open-source ERP, could handle the ordering workflow but would require significant configuration to match food coop patterns.

For the specific use case — a European food coop needing a self-hosted order management platform — FoodCoopShop has no direct self-hostable competitor with equivalent depth. The real comparison is FoodCoopShop vs. Open Food Network, and the choice comes down to complexity: FoodCoopShop is simpler to operate for a single-location coop, Open Food Network scales better for multi-hub networks.

---

Bottom line

FoodCoopShop is narrow, mature, and honest about what it is. It doesn’t pretend to be a general e-commerce platform. It’s one person’s decade-long project to solve a specific problem that food cooperatives actually have: pre-ordering food from multiple local producers with variable delivery schedules, tracked against a member credit pool. For that problem, it works, and 55 cooperatives are using it in production to prove it.

The risks are real: single maintainer, German-first community, a PHP/Apache stack that requires traditional server administration, and 115 GitHub stars that reflect a small audience. If your coop relies on this software and Mario Rothauer walks away, you’re maintaining a CakePHP application yourself. That’s a genuine consideration for any organization making a multi-year commitment.

But if you’re running a food cooperative in Austria, Germany, or a German-speaking community elsewhere — or if you’re technical enough to adapt it for your context — there is no equivalent self-hosted alternative that handles delivery rhythms, producer portals, and bank-transfer credit systems out of the box. Sometimes the best tool for a niche problem is just the niche tool, built by someone who needed it too.

---

Sources

1. Awesome-Selfhosted (mirror) — Community-Supported Agriculture listing, git.osmarks.net. https://git.osmarks.net/mirrors/awesome-selfhosted
2. Karrot Community Forum — Weekly development call notes 2025 (mentions FoodCoopShop alternatives context), community.karrot.world. https://community.karrot.world/t/weekly-call-about-karrot-development-2025/2089
3. JankariTech — Our Offer (contributor to FoodCoopShop codebase), jankaritech.com. https://www.jankaritech.com/offer/
4. Awesome-Selfhosted (mirror) — Community-Supported Agriculture listing, git.libox.fr. https://git.libox.fr/Clones/awesome-selfhosted

Primary sources:

• GitHub repository and README: https://github.com/foodcoopshop/foodcoopshop (115 stars, AGPL-3.0, maintained by Mario Rothauer since 2014)
• Official website: https://www.foodcoopshop.com
• Documentation: https://foodcoopshop.github.io
• Production Docker repo: https://github.com/foodcoopshop/foodcoopshop-docker