Cancellation · USPTO

Cancellation 92088310

OtherUSPTO

Cancellation 92088310 at USPTO between Starwood Hotels & Resorts Worldwide, LLC and Junhe (Shenzhen) Trading Co.,Ltd.., over the mark W BOUTIQUE·M, filed May 7, 2025. Status in the office record: other.

View W BOUTIQUE·MGet this data via the API
Status
Other
Result
Other
Filed
May 7, 2025
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Petitioner

Starwood Hotels & Resorts Worldwide, LLC

Company trademarks
Respondent

Junhe (Shenzhen) Trading Co.,Ltd..

Timeline

How the case has moved

Dates from the USPTO record and the W BOUTIQUE·M filing.

  1. W BOUTIQUE·M filed

    Application 88863529 filed at the USPTO.

  2. W BOUTIQUE·M registered

  3. Cancellation filed

    Starwood Hotels & Resorts Worldwide, LLC started cancellation 92088310 at USPTO against W BOUTIQUE·M.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
W BOUTIQUE·MContested88863529USPTO
WRelied on75464250USPTO
W HOTELSRelied on76289383USPTO
WRelied on85655810USPTO
WRelied on85656350USPTO
WRelied on87283815USPTO
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_802bd804-a194-441d-9c19-55afccdba31e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_802bd804-a194-441d-9c19-55afccdba31e",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92088310",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-05-07",
  "parties": [
    {
      "name": "Starwood Hotels & Resorts Worldwide, LLC",
      "role": "petitioner"
    },
    {
      "name": "Junhe (Shenzhen) Trading Co.,Ltd..",
      "role": "respondent"
    }
  ]
}