Opposition · USPTO

Opposition 91308913

PendingUSPTO

Opposition 91308913 at USPTO between Alo, LLC and Pretty Little Winks LLC, over the mark ALORA, filed Jul 16, 2026. Status in the office record: pending.

Status
Pending
Filed
Jul 16, 2026
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Alo, LLC

Company trademarks
Respondent

Pretty Little Winks LLC

Timeline

How the case has moved

Dates from the USPTO record and the ALORA filing.

  1. ALORA filed

    Application 99332950 filed at the USPTO.
  2. Opposition filed

    Alo, LLC started opposition 91308913 at USPTO against ALORA.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

2 contested marks, 11 marks the challenger relies on.

MarkRoleApplicationOffice
ALORAContested99332950USPTO
ALORAContested99332954USPTO
ALORelied on77891801USPTO
ALORelied on86741238USPTO
ALORelied on87782928USPTO
ALORelied on88759109USPTO
ALORelied on97411962USPTO
ALORelied on97902657USPTO
ALORelied on98085815USPTO
ALO STACKABLE WELLNESSRelied on98214658USPTO
ALO WELLNESS SYSTEMRelied on98423417USPTO
ALORelied on98805132USPTO

+1 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_1f4a7e5a-3f92-4450-9175-fb31be96078a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1f4a7e5a-3f92-4450-9175-fb31be96078a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91308913",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-07-16",
  "parties": [
    {
      "name": "ALO, LLC",
      "role": "opponent"
    },
    {
      "name": "Pretty Little Winks LLC",
      "role": "respondent"
    }
  ]
}