Opposition · USPTO

Opposition 91251728

OtherUSPTO

Opposition 91251728 at USPTO between Industria de Diseño Textil, S.A. aka Inditex, S.A. and Zala Group Pty Ltd, over the mark ZALA, filed Oct 11, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 11, 2019
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Industria de Diseño Textil, S.A. aka Inditex, S.A.

Respondent

Zala Group Pty Ltd

Timeline

How the case has moved

Dates from the USPTO record and the ZALA filing.

  1. ZALA filed

    Application 88218564 filed at the USPTO.
  2. Opposition filed

    Industria de Diseño Textil, S.A. aka Inditex, S.A. started opposition 91251728 at USPTO against ZALA.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
ZALAContested88218564USPTO
ZARARelied on74568363USPTO
ZARARelied on75545485USPTO
ZARA BASICRelied on75557948USPTO
ZARARelied on76101030USPTO
ZARA HOMERelied on78301068USPTO
ZARA HOMERelied on79058378USPTO
ZARARelied on79088579USPTO
ZARA BASICRelied on79103350USPTO
ZARA HOMERelied on85642277USPTO
ZARARelied on87516415USPTO
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_fd184b68-ac9b-44e6-9ed1-879a9e0f6d9e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fd184b68-ac9b-44e6-9ed1-879a9e0f6d9e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91251728",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-10-11",
  "parties": [
    {
      "name": "Industria de Diseño Textil, S.A. aka Inditex, S.A.",
      "role": "opponent"
    },
    {
      "name": "Zala Group Pty Ltd",
      "role": "respondent"
    }
  ]
}