SKUs and identifiers

minipim keeps two kinds of identifier, both on variants. Each variant has exactly one sku, its unique key in the catalog. Barcodes and part numbers (UPC, GTIN, EAN, MPN, ASIN, ISBN and so on) are separate identifier rows attached to a variant. Products don’t carry identifiers themselves.

In the admin

On a product with exactly one variant, the Key details section shows UPC, GTIN-13 and MPN fields. Edit them and click Save changes in the save bar.

For products with several variants, or for other identifier types:

1. Open the product under Catalog → Products and click Open → on a variant.
2. In Identifiers, choose a type (SKU, UPC, MPN, GTIN13, GTIN12, EAN, ASIN, ISBN, CUSTOM), enter the value and click Attach.
3. Use the trash icon on a row to remove it.

The variant’s own SKU is edited in its Identity section.

With the API

Method	Path	What it does
GET	/v1/variants/{variantId}/identifiers	List a variant’s identifiers
POST	/v1/variants/{variantId}/identifiers	Attach one
PUT	/v1/variants/{variantId}/identifiers	Replace the full set ([] clears all)
DELETE	/v1/identifiers/{id}	Remove one

curl -X POST https://api.minipim.com/v1/variants/7f1e…/identifiers \
  -H "Authorization: Bearer pim_…" \
  -H "Content-Type: application/json" \
  -d '{ "type": "upc", "value": "012345678905" }'

Each identifier is { type, value, customLabel? }. To change a variant’s SKU, PATCH /v1/variants/{id} with { "sku": "…" }. Full reference: api.minipim.com/docs.

The MCP server has a set_variant_identifiers tool that adds by default and only replaces the set when asked to.

Identifier types

sku, upc, gtin8, gtin12, gtin13, gtin14, ean, mpn, asin, isbn, custom. Use customLabel to name a custom identifier.

Rules and limits

• A variant’s sku must be unique within the organization. Identifier values are not unique: two variants can carry the same barcode, so check for duplicates yourself.
• upc, ean and the gtin* types are validated on write: digits only, the GS1 check digit must be correct, and the length must match the type (UPC 12, EAN 13, GTIN-8/12/13/14 by name). A bad value returns 422.
• mpn, asin, isbn, sku and custom are free text.
• PUT deletes everything on the variant before inserting your list. To add one identifier, use POST.
• An identifier row of type sku is separate from the variant’s sku field.
• Duplicating a product never copies identifiers.
• Every identifier change emits variant.updated with identifiers in changed_fields.
• The BigCommerce connector imports SKU, UPC, MPN and GTIN values as identifier rows, writing GTINs as gtin13. Imported values don’t go through the check-digit validation.

Readiness

A channel can list identifier codes in its required attributes: sku, upc, gtin, mpn, ean, asin or isbn. gtin is satisfied by any of gtin8, gtin12, gtin13, gtin14 or ean, and ean also accepts gtin13. These requirements are checked against identifier rows, so the variant’s sku field alone doesn’t satisfy sku. Coverage is per variant: if 5 of 7 variants have a GTIN, the product gets partial credit and the gap is reported. See Channels and readiness.