Opposition · USPTO

Opposition 91306519

OtherUSPTO

Opposition 91306519 at USPTO between Hugo Boss AG and ZHUJI BENTU E-commerce Co., Ltd, over the mark BOSSUN, filed Apr 10, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 10, 2026
Marks involved
23
Parties

Who is involved

The parties as named in the office record.

Opponent

Hugo Boss AG

Company trademarks
Respondent

ZHUJI BENTU E-commerce Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the BOSSUN filing.

  1. BOSSUN filed

    Application 99345414 filed at the USPTO.
  2. Opposition filed

    Hugo Boss AG started opposition 91306519 at USPTO against BOSSUN.
Marks

Marks involved

1 contested mark, 22 marks the challenger relies on.

MarkRoleApplicationOffice
BOSSUNContested99345414USPTO
BOSSRelied on73036140USPTO
BOSS HUGO BOSSRelied on73665965USPTO
HUGO BOSSRelied on73674099USPTO
BOSS HUGO BOSSRelied on73747911USPTO
BOSSRelied on74074962USPTO
BOSSRelied on74075953USPTO
BOSSRelied on74323654USPTO
BOSSRelied on74326997USPTO
HUGO BOSSRelied on75349754USPTO
BOSS HUGO BOSSRelied on75350360USPTO
BOSS HUGO BOSSRelied on75811451USPTO

+11 more marks in this case

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_ef6c9642-1cf3-4e1b-bd47-db3de1cbcacd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ef6c9642-1cf3-4e1b-bd47-db3de1cbcacd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91306519",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-04-10",
  "parties": [
    {
      "name": "HUGO BOSS AG",
      "role": "opponent"
    },
    {
      "name": "ZHUJI BENTU E-commerce Co., Ltd",
      "role": "respondent"
    }
  ]
}