Opposition · USPTO

Opposition 91277899

OtherUSPTO

Opposition 91277899 at USPTO between Amazon Technologies, Inc. and Shenzhen Yehai Technology Co., Ltd., over the mark AMZLOGO, filed Aug 10, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 10, 2022
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Amazon Technologies, Inc.

Company trademarks
Respondent

Shenzhen Yehai Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the AMZLOGO filing.

  1. AMZLOGO filed

    Application 97001053 filed at the USPTO.
  2. Opposition filed

    Amazon Technologies, Inc. started opposition 91277899 at USPTO against AMZLOGO.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
AMZLOGOContested97001053USPTO
AMAZONRelied on75981644USPTO
AMAZONRelied on77572206USPTO
AMAZONRelied on77572552USPTO
AMAZON BASICSRelied on77983416USPTO
AMAZONRelied on78005143USPTO
AMAZON BASICSRelied on86086382USPTO
AMAZONRelied on86315391USPTO
AMAZONRelied on86315405USPTO
AMAZON BASICSRelied on86508762USPTO
AMAZONRelied on86983875USPTO
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_ba43f14f-13bd-43a7-b55e-1ea46212934e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ba43f14f-13bd-43a7-b55e-1ea46212934e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91277899",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-08-10",
  "parties": [
    {
      "name": "Amazon Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Yehai Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}