Opposition · USPTO

Opposition 91283699

OtherUSPTO

Opposition 91283699 at USPTO between WooCommerce, Inc. and Shukexingqiu (Zhuhai) Information Technology Co., Ltd., over the mark WOOGIFTBOX, filed Feb 15, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 15, 2023
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

WooCommerce, Inc.

Company trademarks
Respondent

Shukexingqiu (Zhuhai) Information Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the WOOGIFTBOX filing.

  1. WOOGIFTBOX filed

    Application 97088260 filed at the USPTO.
  2. Opposition filed

    WooCommerce, Inc. started opposition 91283699 at USPTO against WOOGIFTBOX.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
WOOGIFTBOXContested97088260USPTO
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 /v1/proceedings/{id}
ID=prc_502b7ffb-3b53-4160-a5f1-817f0d9a2d68
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_502b7ffb-3b53-4160-a5f1-817f0d9a2d68",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91283699",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-02-15",
  "parties": [
    {
      "name": "WooCommerce, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shukexingqiu (Zhuhai) Information Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}