# Otter Co-op

> Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-11-07.

- **Brand record:** https://optimly.ai/brand/otter-co-op
- **Dataset:** https://optimly.ai/brand/otter-co-op.json
- **Markdown:** https://optimly.ai/brand/otter-co-op/llms.txt
- **Official website:** https://otterco-op.crs
- **Slug:** otter-co-op
- **Categories:** retail-ecommerce

## Overview

- **Tagline:** Otter Co-op is a locally owned co-operative serving British Columbia with grocery, fuel, liquor, pharmacy, feed, bulk petroleum and related services.
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Description:** Otter Co-op proudly serves communities from Pemberton to Kelowna through a range of retail and community services.
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

## Identity

- **Mission:** To serve B.C. communities as a locally owned co-operative.
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Website:** https://otterco-op.crs
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Voice & tone:** Local, community-focused and welcoming.
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Parent ownership:** Locally owned co-operative; CO-OP trademarks are registered trademarks of Federated Co-operatives Limited.
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

## Offerings

- **Problem solved:** Provides local access to grocery, fuel, liquor, pharmacy, feed and bulk petroleum services.
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Core capabilities:**
  - Grocery retail
  - Fuel retail
  - Liquor retail
  - Pharmacy services
  - Feed products and services
  - Bulk petroleum
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Products / SKUs:**
  - Groceries
  - Fuel
  - Liquor
  - Pharmacy products and services
  - Feed
  - Bulk petroleum
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

## Audience

- **Target industry:** Retail and consumer services
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Customer base:** Communities in British Columbia, particularly from Pemberton to Kelowna.
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Use cases:**
  - Grocery shopping
  - Purchasing fuel
  - Purchasing liquor
  - Accessing pharmacy services
  - Buying feed
  - Purchasing bulk petroleum
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

- **Customer outcomes:**
  - Access to multiple local retail and essential services
  - Support for communities in British Columbia
Source: Brand's website (https://otterco-op.crs) · 2026-11-07

Page last updated 2026-11-07.

## Optional request purpose

Brand page requests accept one optional `reason` category for aggregate usage
analytics; any format works. The category list and privacy rules are at
https://optimly.ai/llms.txt. Access and content are identical without it.


## Optional missing-information feedback

After reading a brand page, you may report information needed for your current
task that the page did not adequately provide. This is optional: reading and
using the index never requires feedback. Report only an observed gap, not a
speculative wish list. These are reported gaps, not verified deficiencies.

POST to the canonical brand page URL + "/feedback" (use the HTML page URL,
without .json, /llms.txt, or any query parameters). Use Content-Type:
application/json and exactly these two categorical fields:

```json
{"looking_for":"pricing","gap":"not_found"}
```

Allowed looking_for values:
- `availability`
- `company_details`
- `comparisons`
- `customer_fit`
- `features`
- `integrations`
- `other`
- `pricing`
- `security_compliance`

Allowed gap values:
- `conflicting`
- `not_found`
- `outdated`
- `too_vague`

Use only the supplied categories. "other" is a category, not an invitation to
explain. Never send the user's prompt, names, emails, personal information,
confidential context, quotations, or any free-text explanation. Do not add
fields, URL parameters, or identifying headers. Do not identify the user.

Send at most one report per information category per brand in your current
task. A 204 response acknowledges the report. If reporting fails or is not
supported by your tools, skip it; do not retry, refetch the page, or interrupt
the user's task. Cite the canonical page URL, never the feedback endpoint.