Opposition · USPTO

Opposition 91303169

OtherUSPTO

Opposition 91303169 at USPTO between Moet Hennessy USA, Inc. and Henessey Food Consulting, LLC, over the mark HENNESSY FOOD, filed Nov 17, 2025. Status in the office record: other.

View HENNESSY FOODGet this data via the API
Status
Other
Result
Other
Filed
Nov 17, 2025
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Moet Hennessy USA, Inc.

Company trademarks
Respondent

Henessey Food Consulting, LLC

Timeline

How the case has moved

Dates from the USPTO record and the HENNESSY FOOD filing.

  1. HENNESSY FOOD filed

    Application 98484706 filed at the USPTO.

  2. Opposition filed

    Moet Hennessy USA, Inc. started opposition 91303169 at USPTO against HENNESSY FOOD.
Marks

Marks involved

2 contested marks, 6 marks the challenger relies on.

MarkRoleApplicationOffice
HENNESSY FOODContested98484706USPTO
HENNESSY FOODContested99167141USPTO
HENNESSYRelied on72298047USPTO
RICHARD HENNESSYRelied on75249953USPTO
HENNESSYRelied on77521652USPTO
JAMES HENNESSYRelied on97218460USPTO
HENNESSY 8Relied on97647365USPTO
HENNY WHITERelied on97937054USPTO
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_3042c3f5-4b6e-4288-8212-60ef55d36f39
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3042c3f5-4b6e-4288-8212-60ef55d36f39",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91303169",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-11-17",
  "parties": [
    {
      "name": "Moet Hennessy USA, Inc.",
      "role": "opponent"
    },
    {
      "name": "Henessey Food Consulting, LLC",
      "role": "respondent"
    }
  ]
}