Opposition · USPTO

Opposition 91310966

PendingUSPTO

Opposition 91310966 at USPTO between Chanel, Inc. and Shanghai Hua'er and Sister Biotechnology Co., Ltd., over the mark PERICOCO, filed Oct 7, 2026. Status in the office record: pending.

View PERICOCOGet this data via the API
Status
Pending
Filed
Oct 7, 2026
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Chanel, Inc.

Company trademarks
Respondent

Shanghai Hua'er and Sister Biotechnology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the PERICOCO filing.

  1. PERICOCO filed

    Application 99734453 filed at the USPTO.

  2. Opposition filed

    Chanel, Inc. started opposition 91310966 at USPTO against PERICOCO.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
PERICOCOContested99734453USPTO
COCORelied on72237534USPTO
COCORelied on73206836USPTO
COCORelied on73818611USPTO
COCO MADEMOISELLERelied on76054884USPTO
ROUGE COCORelied on77768562USPTO
COCO NOIRRelied on85360730USPTO
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_465f084d-a69d-4de2-8fe0-bda1081d86b1
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_465f084d-a69d-4de2-8fe0-bda1081d86b1",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91310966",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-10-07",
  "parties": [
    {
      "name": "Chanel, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shanghai Hua'er and Sister Biotechnology Co., Ltd.",
      "role": "respondent"
    }
  ]
}