Cancellation · USPTO

Cancellation 92072475

OtherUSPTO

Cancellation 92072475 at USPTO between FCH Enterprises, Inc. and Fashion Division, S.A., over the mark ZIPPY, filed Oct 4, 2019. Status in the office record: other.

View ZIPPYGet this data via the API
Status
Other
Result
Other
Filed
Oct 4, 2019
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Petitioner

FCH Enterprises, Inc.

Respondent

Fashion Division, S.A.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the ZIPPY filing.

  1. ZIPPY filed

    Application 85968026 filed at the USPTO.

  2. ZIPPY registered

  3. Cancellation filed

    FCH Enterprises, Inc. started cancellation 92072475 at USPTO against ZIPPY.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
ZIPPYContested85968026USPTO
ZIPPY'S HOME OF THE CHEEZY BEEF!Relied on74144389USPTO
ZIPPY'SRelied on86742614USPTO
NEXT STOP ZIPPY'SRelied on87073147USPTO
Z ZIPPY'S RESTAURANTSRelied on87074627USPTO
NEXT STOP ZIPPY'SRelied on87077912USPTO
Z ZIPPY'S RESTAURANTSRelied on87082436USPTO
ZIPPY'SRelied on88240784USPTO
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_d22b661f-c5b0-4b79-8aa2-59c87fd5d00a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d22b661f-c5b0-4b79-8aa2-59c87fd5d00a",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92072475",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-10-04",
  "parties": [
    {
      "name": "FCH Enterprises, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Fashion Division, S.A.",
      "role": "respondent"
    }
  ]
}