Opposition · USPTO

Opposition 91275161

OtherUSPTO

Opposition 91275161 at USPTO between The Coca-Cola Company and Putian Mairuntao Electronic Commerce Co., Ltd., over the mark MAXCOCOLA, filed Mar 22, 2022. Status in the office record: other.

View MAXCOCOLAGet this data via the API
Status
Other
Result
Other
Filed
Mar 22, 2022
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

The Coca-Cola Company

Respondent

Putian Mairuntao Electronic Commerce Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the MAXCOCOLA filing.

  1. MAXCOCOLA filed

    Application 90574912 filed at the USPTO.

  2. Opposition filed

    The Coca-Cola Company started opposition 91275161 at USPTO against MAXCOCOLA.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
MAXCOCOLAContested90574912USPTO
COCA-COLARelied on71254696USPTO
COKERelied on71468708USPTO
COCA-COLARelied on73406145USPTO
COCA-COLARelied on73573880USPTO
COCA-COLARelied on74308099USPTO
COKERelied on77153712USPTO
COCA-COLARelied on78263921USPTO
COKERelied on78264397USPTO
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_d5ef8c93-ac62-482a-bba3-285b59aa6310
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d5ef8c93-ac62-482a-bba3-285b59aa6310",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91275161",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-03-22",
  "parties": [
    {
      "name": "The Coca-Cola Company",
      "role": "opponent"
    },
    {
      "name": "Putian Mairuntao Electronic Commerce Co., Ltd.",
      "role": "respondent"
    }
  ]
}