Opposition · USPTO

Opposition 91240845

OtherUSPTO

Opposition 91240845 at USPTO between Costco Wholesale Membership, Inc. and Beijing Bentudou E-commerce Co. Ltd., over the mark COSTGO, filed Apr 25, 2018. Status in the office record: other.

View COSTGOGet this data via the API
Status
Other
Result
Other
Filed
Apr 25, 2018
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Costco Wholesale Membership, Inc.

Company trademarks
Respondent

Beijing Bentudou E-commerce Co. Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the COSTGO filing.

  1. COSTGO filed

    Application 87459676 filed at the USPTO.

  2. Opposition filed

    Costco Wholesale Membership, Inc. started opposition 91240845 at USPTO against COSTGO.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
COSTGOContested87459676USPTO
COSTCORelied on74648956USPTO
COSTCO BUSINESS CENTERRelied on75177199USPTO
COSTCO WHOLESALERelied on75252261USPTO
COSTCO.COMRelied on75896643USPTO
COSTCORelied on76009450USPTO
COSTCO.COMRelied on77338185USPTO
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_3e3f0f41-dc3b-4d17-92af-4eee6b75303d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3e3f0f41-dc3b-4d17-92af-4eee6b75303d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91240845",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-04-25",
  "parties": [
    {
      "name": "Costco Wholesale Membership, Inc.",
      "role": "opponent"
    },
    {
      "name": "Beijing Bentudou E-commerce Co. Ltd.",
      "role": "respondent"
    }
  ]
}