Opposition · USPTO

Opposition 91283555

OtherUSPTO

Opposition 91283555 at USPTO between WooCommerce, Inc. and Wheatfield Guard Technology Co., Ltd., over the mark WOOTECHY, filed Feb 21, 2023. Status in the office record: other.

View WOOTECHYGet this data via the API
Status
Other
Result
Other
Filed
Feb 21, 2023
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

WooCommerce, Inc.

Company trademarks
Respondent

Wheatfield Guard Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the WOOTECHY filing.

  1. WOOTECHY filed

    Application 97164805 filed at the USPTO.

  2. Opposition filed

    WooCommerce, Inc. started opposition 91283555 at USPTO against WOOTECHY.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
WOOTECHYContested97164805USPTO
WOORelied on86796651USPTO
WOORelied on86796654USPTO
WOOCOMMERCERelied on86796658USPTO
WOOCOMMERCERelied on86796666USPTO
WOOCOMMERCE STOREFRONTRelied on88267236USPTO
WOOCOMMERCE PAYMENTSRelied on90707411USPTO
WOOPAYRelied on97425854USPTO
WOOCOMMERCERelied on97480236USPTO
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_20052a2f-dbcf-4738-b70a-4d36a0de32d6
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_20052a2f-dbcf-4738-b70a-4d36a0de32d6",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91283555",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-02-21",
  "parties": [
    {
      "name": "WooCommerce, Inc.",
      "role": "opponent"
    },
    {
      "name": "Wheatfield Guard Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}