Opposition · USPTO

Opposition 91295004

OtherUSPTO

Opposition 91295004 at USPTO between Shipt, Inc. and CPM United Kingdom Limited, over the mark SHOPT, filed Nov 7, 2024. Status in the office record: other.

View SHOPTGet this data via the API
Status
Other
Result
Other
Filed
Nov 7, 2024
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Shipt, Inc.

Respondent

CPM United Kingdom Limited

Timeline

How the case has moved

Dates from the USPTO record and the SHOPT filing.

  1. SHOPT filed

    Application 97735856 filed at the USPTO.

  2. Opposition filed

    Shipt, Inc. started opposition 91295004 at USPTO against SHOPT.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
SHOPTContested97735856USPTO
SHIPTRelied on88783670USPTO
SHIPTRelied on88783674USPTO
SHIPTRelied on88783677USPTO
SHIPTRelied on88789431USPTO
SHIPT MEDIARelied on97848981USPTO
SHIPT GREEN ROOMRelied on98085825USPTO
SHIPT GREEN ROOMRelied on98086103USPTO
SHIPT MEDIA REAL REACH, REAL RESULTSRelied on98159193USPTO
SHIPT MEDIA REAL REACH, REAL RESULTSRelied on98164405USPTO
SHIPTRelied on98213155USPTO
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_7562c762-4bf2-4160-854e-d67641895cdc
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7562c762-4bf2-4160-854e-d67641895cdc",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91295004",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-11-07",
  "parties": [
    {
      "name": "Shipt, Inc.",
      "role": "opponent"
    },
    {
      "name": "CPM United Kingdom Limited",
      "role": "respondent"
    }
  ]
}