Opposition · USPTO

Opposition 91306375

OtherUSPTO

Opposition 91306375 at USPTO between BBY Solutions, Inc. and Buy Best LLC, over the mark BUY BEST USA, filed Apr 6, 2026. Status in the office record: other.

View BUY BEST USAGet this data via the API
Status
Other
Result
Other
Filed
Apr 6, 2026
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

BBY Solutions, Inc.

Company trademarks
Respondent

Buy Best LLC

Timeline

How the case has moved

Dates from the USPTO record and the BUY BEST USA filing.

  1. BUY BEST USA filed

    Application 99293365 filed at the USPTO.

  2. Opposition filed

    BBY Solutions, Inc. started opposition 91306375 at USPTO against BUY BEST USA.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
BUY BEST USAContested99293365USPTO
BESTBUY.COMRelied on76142158USPTO
BEST BUYRelied on76681653USPTO
BEST BUYRelied on85815565USPTO
BEST BUYRelied on87912152USPTO
BEST BUYRelied on87912167USPTO
BEST BUYRelied on87914153USPTO
BEST BUYRelied on87914165USPTO
BEST BUYRelied on87915633USPTO
BEST BUYRelied on87915638USPTO
BEST BUYRelied on97634681USPTO
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_5317be75-34d9-4526-bd52-f9013687c367
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5317be75-34d9-4526-bd52-f9013687c367",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91306375",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-04-06",
  "parties": [
    {
      "name": "BBY Solutions, Inc.",
      "role": "opponent"
    },
    {
      "name": "Buy Best LLC",
      "role": "respondent"
    }
  ]
}