A product can be complete for your own storefront and nowhere near ready for a marketplace feed. A single “completeness” number hides that. minipim scores readiness per channel, against what that channel actually requires.

How it works

A channel in minipim is a destination with its own requirements — your web store, a wholesale portal, a marketplace feed. On the Channels page, click any attribute to toggle whether it’s required for that channel. That list is the channel’s definition of “ready.”

minipim then scores each product against every channel:

  • Filled, not just defined. A required attribute counts as missing if it’s empty — no value, an empty string, an empty list.
  • Per locale. If a channel sells in English and French and the attribute is localizable, it needs a value in both. A missing French title shows up as exactly that.
  • Per variant, for identifiers. Require gtin, upc, mpn or sku and every variant needs one. A product with GTINs on 4 of 6 variants gets partial credit and a hint that says “Needs GTIN on 2 variants.”
  • Never a false 100%. A product with anything missing tops out at 99%.

Connectors give you a head start: pulling from BigCommerce or Shopify creates a channel already requiring description, price, weight and the usual identifiers, which you can then edit.

Where you see it

On every product page, a Channel readiness card shows an overall score and one row per channel — the percentage, a progress bar, and the most important gap. Expand a row to see every missing attribute. A channel with nothing missing reads “Ready to publish.”

The same scores are available from the API (GET /v1/products/{id}/completeness) and to AI agents through the MCP server, whose find_incomplete_products tool ranks your whole catalog, worst first, with a breakdown by missing attribute. That’s the fastest way to work through gaps across hundreds of products.

Readiness vs. publishing

Readiness is a guide, not a gate: a connector syncs a product whatever its score, and nothing is held back automatically at less than 100%.

Separately, minipim does enforce one hard rule. The attributes your product family marks as required must be filled before a product — or a content page — can be set to active. Use family requirements for what every product must have, and channel requirements for what each destination needs on top.

Good to know

  • Requirements are required-or-not. There are no “recommended” or warning levels yet.
  • Readiness checks that values are present. Whether they’re valid is checked when they’re saved through the admin or API (values imported by a connector aren’t re-validated).
  • The score is shown per product. There’s no readiness column or filter on the product list yet — use the MCP server or the API to find incomplete products in bulk.