Opposition · USPTO

Opposition 91248639

OtherUSPTO

Opposition 91248639 at USPTO between Chanel, Inc. and Beijing Feili Wende Trading Co, Ltd., over the mark CC COCOBELLA, filed Jun 5, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 5, 2019
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Chanel, Inc.

Company trademarks
Respondent

Beijing Feili Wende Trading Co, Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the CC COCOBELLA filing.

  1. CC COCOBELLA filed

    Application 87429053 filed at the USPTO.
  2. Opposition filed

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

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
CC COCOBELLAContested87429053USPTO
COCORelied on72237534USPTO
COCORelied on73206836USPTO
CCRelied on73239992USPTO
CCRelied on73359660USPTO
CCRelied on73644065USPTO
COCORelied on73818611USPTO
COCO MADEMOISELLERelied on76054884USPTO
CCRelied on76615091USPTO
ROUGE COCORelied on77768562USPTO
COCO NOIRRelied on85360730USPTO
CCRelied on85587416USPTO

+2 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 /v1/proceedings/{id}
ID=prc_bc9d650a-5f59-42f3-96ba-3d365894b84c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bc9d650a-5f59-42f3-96ba-3d365894b84c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91248639",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-06-05",
  "parties": [
    {
      "name": "Chanel, Inc.",
      "role": "opponent"
    },
    {
      "name": "Beijing Feili Wende Trading Co, Ltd.",
      "role": "respondent"
    }
  ]
}