Opposition · USPTO

Opposition 91237999

OtherUSPTO

Opposition 91237999 at USPTO between PRL USA Holdings, Inc. and Shenzhen Huachuanghengda Technology Co., Ltd, over the mark FITPOLO, filed Nov 22, 2017. Status in the office record: other.

View FITPOLOGet this data via the API
Status
Other
Result
Other
Filed
Nov 22, 2017
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

PRL USA Holdings, Inc.

Respondent

Shenzhen Huachuanghengda Technology Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the FITPOLO filing.

  1. FITPOLO filed

    Application 87364353 filed at the USPTO.

  2. Opposition filed

    PRL USA Holdings, Inc. started opposition 91237999 at USPTO against FITPOLO.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
FITPOLOContested87364353USPTO
POLORelied on73333206USPTO
POLORelied on73630297USPTO
POLO SPORTRelied on74660375USPTO
POLO RALPH LAURENRelied on75057171USPTO
POLO GOLFRelied on76401536USPTO
POLO SPORTRelied on78187389USPTO
POLORelied on78528483USPTO
POLO RALPH LAURENRelied on86093122USPTO
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_41c12322-ead2-4aa2-b96c-afdf97d439d2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_41c12322-ead2-4aa2-b96c-afdf97d439d2",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91237999",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-11-22",
  "parties": [
    {
      "name": "PRL USA Holdings, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Huachuanghengda Technology Co., Ltd",
      "role": "respondent"
    }
  ]
}