Opposition · USPTO

Opposition 91302326

OtherUSPTO

Opposition 91302326 at USPTO between Alo, LLC and Shenzhen Yishui Hankong E-commerce Co., Ltd., over the mark ALOPNCY, filed Oct 9, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 9, 2025
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Alo, LLC

Company trademarks
Respondent

Shenzhen Yishui Hankong E-commerce Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the ALOPNCY filing.

  1. ALOPNCY filed

    Application 99065636 filed at the USPTO.
  2. Opposition filed

    Alo, LLC started opposition 91302326 at USPTO against ALOPNCY.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
ALOPNCYContested99065636USPTO
ALORelied on77891801USPTO
ALO SPORTRelied on85981400USPTO
ALO YOGARelied on86741208USPTO
ALORelied on86741238USPTO
ALORelied on87782928USPTO
ALOSOFTRelied on88595042USPTO
ALORelied on97902657USPTO
ALO X 01 CLASSICRelied on98007309USPTO
ALORelied on98085815USPTO
ALO RECOVERY MODERelied on98478666USPTO
ALO RUNNERRelied on98590649USPTO

+7 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_3524f6a2-7498-40f7-81c5-f9ac1f6da8dd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3524f6a2-7498-40f7-81c5-f9ac1f6da8dd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302326",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-10-09",
  "parties": [
    {
      "name": "ALO, LLC",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Yishui Hankong E-commerce Co., Ltd.",
      "role": "respondent"
    }
  ]
}