Opposition · USPTO

Opposition 91304494

OtherUSPTO

Opposition 91304494 at USPTO between Chanel, Inc. and Benson HSIAO, over the mark CC COCOBELLA, filed Jan 14, 2026. Status in the office record: other.

View CC COCOBELLAGet this data via the API
Status
Other
Result
Other
Filed
Jan 14, 2026
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Chanel, Inc.

Company trademarks
Respondent

Benson HSIAO

Timeline

How the case has moved

Dates from the USPTO record and the CC COCOBELLA filing.

  1. CC COCOBELLA filed

    Application 99249798 filed at the USPTO.

  2. Opposition filed

    Chanel, Inc. started opposition 91304494 at USPTO against CC COCOBELLA.
Marks

Marks involved

2 contested marks, 14 marks the challenger relies on.

MarkRoleApplicationOffice
CC COCOBELLAContested99249798USPTO
CC COCOBELLAContested99249837USPTO
COCORelied on72237534USPTO
COCORelied on73206836USPTO
CCRelied on73239992USPTO
CCRelied on73359660USPTO
CCRelied on73644065USPTO
COCORelied on73818611USPTO
COCO MADEMOISELLERelied on76054884USPTO
CCRelied on76615091USPTO
CCRelied on85587416USPTO
COCO CRUSHRelied on86572525USPTO

+4 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_af2836a1-c163-485d-9184-5bf5dc5a1d03
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_af2836a1-c163-485d-9184-5bf5dc5a1d03",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91304494",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-01-14",
  "parties": [
    {
      "name": "Chanel, Inc.",
      "role": "opponent"
    },
    {
      "name": "Benson HSIAO",
      "role": "respondent"
    }
  ]
}