Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/class-wp-block-list.php on line 199

Deprecated: Optional parameter $value declared before required parameter $field is implicitly treated as a required parameter in /home4/fhabermacher/public_html/wp-content/plugins/my_customfields/api/api-value.php on line 174

Deprecated: Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home4/fhabermacher/public_html/wp-content/plugins/my_customfields/api/api-value.php on line 174

Deprecated: Optional parameter $post_id declared before required parameter $fields is implicitly treated as a required parameter in /home4/fhabermacher/public_html/wp-content/plugins/my_customfields/api/api-field.php on line 395

Deprecated: Optional parameter $id declared before required parameter $field is implicitly treated as a required parameter in /home4/fhabermacher/public_html/wp-content/plugins/my_customfields/pro/fields/gallery.php on line 297

Deprecated: Return type of MyCLabs\Enum\Enum::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce-payments/vendor/myclabs/php-enum/src/Enum.php on line 246

Deprecated: Return type of WC_DateTime::setTimezone($timezone) should either be compatible with DateTime::setTimezone(DateTimeZone $timezone): DateTime, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/includes/class-wc-datetime.php on line 57

Deprecated: Return type of WC_DateTime::getOffset() should either be compatible with DateTime::getOffset(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/includes/class-wc-datetime.php on line 47

Deprecated: Return type of WC_DateTime::getTimestamp() should either be compatible with DateTime::getTimestamp(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/includes/class-wc-datetime.php on line 68

Deprecated: Return type of WC_Meta_Data::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/includes/class-wc-meta-data.php on line 50

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/fhabermacher/public_html/wp-includes/wp-db.php on line 3030

Deprecated: Return type of ActionScheduler_DateTime::setTimezone($timezone) should either be compatible with DateTime::setTimezone(DateTimeZone $timezone): DateTime, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_DateTime.php on line 60

Deprecated: Return type of ActionScheduler_DateTime::getOffset() should either be compatible with DateTime::getOffset(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_DateTime.php on line 48

Deprecated: Return type of ActionScheduler_DateTime::getTimestamp() should either be compatible with DateTime::getTimestamp(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_DateTime.php on line 27

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/functions.php on line 316

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home4/fhabermacher/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/functions.php on line 316

Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/fhabermacher/public_html/wp-includes/formatting.php on line 4975

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/fhabermacher/public_html/wp-includes/class-wp.php on line 173
Our story | Foodoffset – Lighten your Foodprint

Our story

The original motivation for the creation of foodoffset.org came about essentially as a self-help idea. From pondering about: What does it help to have this cheap meat available in shops and restaurants, if we know with certainty that most of it comes from animals held in conditions that are simply appalling if animals are capable of feelings of pain and stress? Unfortunately, even if gradually reducing meat intake, at least dairy products and eggs are not trivial to fully avoid especially in ready-made meals convenient for active persons with short lunches or dinners. There just seemed no easy solution: fully avoiding consumption of animal products of dubious origin was – even if theoretically not very difficult – not trivial. But being a net contributor to the so prevalent animal cruelty just did not make sense either; in fact it seemed increasingly inexcusable.

This is when the idea of compensating animal welfare was born. Why would we not take a bit of time, and search for a place where we can sponsor an elevation of applied welfare standards somewhere in the food chain?

This seemed especially conducive to the reduction of total animal suffering if the improvement of animal standards happened with no lantern being hung on it: if the sponsored producer officially sold its better products as organic or so, she might merely replace a pre-existing organic market participant, rather than increase the total amount of organic producers and products. In other words, in order to really increase the relative consumption of higher standard products as opposed to low standard products, we need to ensure that some of the demand for low standard products is met by higher standard ones. After all, we cannot easily change the general demand for the different types of products, at least not in an easy, centralized way.

Following the initial thoughts about this, we grew more and more confident that the approach would help us have a positive net impact on animal welfare, even if we could not claim to address all fundamental problems associated with the concept of holding and ultimately killing animals just for the sake of eating their flesh or eggs. Eventually we had the insight that this compensation could be helpful also for you – and for the animals for whose welfare you might to some extent want to become patron by donating to our projects.

We liked the idea of stirring up a debate, especially as we think this debate must ultimately result in increasing people’s awareness about the atrocities in the modern food industry. We wanted to create a platform not only for compensation, and certainly not one that hails compensation as the solution to everything. Instead we wanted the platform to also be a starting point for critical thinking about the topic of animal welfare, whose importance one can hardly overestimate.

Ultimately these thoughts gave birth to foodoffset.org. We refined the concept to account for food to lead not only to animal welfare problems but also to severe environmental issues. Accounting for the environmental dimension seemed especially relevant as – somewhat counterintuitively – treating animals better does not necessarily go in hand with betterment for the rest of the environment. Instead, rearing animals more carefully can increase the environmental foodprint. Besides indirect effects on biodiversity and other particular problems, this is notably the case regarding greenhouse-gas emissions, for which compensation solutions are readily available. Therefore we decided to start with adding the option to offset food-related CO2 on our page.