> For the complete documentation index, see [llms.txt](https://docs.tempomonitors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tempomonitors.com/miscellaneous-commands/target-upc-tcin-lookup.md).

# Target UPC/TCIN Lookup

### Looking up a product by UPC

To look up product details using a UPC or EAN barcode, use the `upc` command with the store name and barcode. Example:

```
!m upc target 196214141506
```

### Looking up a product by SKU/TCIN

You can also look up a product directly by its SKU or TCIN if you already have it. Example:

```
!m upc target 95120834
```

### Supported stores

Currently the following stores are supported:

* `target`

### What information is returned

The lookup will return as much information as is available for the product, which may include:

* Product name
* TCIN / SKU
* Price
* Product image
* Online availability status

Some products may only return partial information depending on how recently they were added to the store's catalog.

### Command format

```
!m upc <store> <upc/ean/sku>
```

* `store` - The store to look up the product on (e.g. `target`)
* `upc/ean/sku` - The numeric barcode or SKU to look up

### Notes

* UPC codes are typically 12 digits and EAN codes are 13 digits
* SKU/TCIN codes can vary in length
* The code must be numeric


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tempomonitors.com/miscellaneous-commands/target-upc-tcin-lookup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
