Cancellation · USPTO

Cancellation 92084658

OtherUSPTO

Cancellation 92084658 at USPTO between The Wonderful Company LLC and Wonder Natural Foods Corp., over the mark PEANUT WONDER, filed Mar 11, 2024. Status in the office record: other.

View PEANUT WONDERGet this data via the API
Status
Other
Result
Other
Filed
Mar 11, 2024
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Petitioner

The Wonderful Company LLC

Respondent

Wonder Natural Foods Corp.

Timeline

How the case has moved

Dates from the USPTO record and the PEANUT WONDER filing.

  1. PEANUT WONDER filed

    Application 74459451 filed at the USPTO.

  2. PEANUT WONDER registered

  3. Cancellation filed

    The Wonderful Company LLC started cancellation 92084658 at USPTO against PEANUT WONDER.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
PEANUT WONDERContested74459451USPTO
WONDER FRUITRelied on76511963USPTO
WONDERFUL PISTACHIOSRelied on77114811USPTO
WONDERFULRelied on85396734USPTO
WONDERFULRelied on86474680USPTO
THE WONDERFUL NUTRelied on87318539USPTO
WONDERFUL CITRUSRelied on87890973USPTO
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_0a45fec9-7ecc-4a02-b6d4-3ad29c7ee9a2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0a45fec9-7ecc-4a02-b6d4-3ad29c7ee9a2",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92084658",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-03-11",
  "parties": [
    {
      "name": "The Wonderful Company LLC",
      "role": "petitioner"
    },
    {
      "name": "Wonder Natural Foods Corp.",
      "role": "respondent"
    }
  ]
}