Messenger error 100: Invalid product id
Last verified against Meta for Developers - Messenger Platform error codes
Invalid product idWhat error 100 means
Code 100 with subcode 2018320 comes from the product template, the structured message that renders catalog items in a Messenger conversation. Meta's error-codes table reads "Invalid product id" and advises checking that "the product ID you are using in your Product Template is a valid ID and that your app has permission to access it."
The product template is thin on purpose: you send only id values in elements, and Messenger pulls the image, title and price from the catalog. That makes the ID the entire contract. The product template guide adds the constraint people miss most: it "only supports product_ids owned by the same page." An ID that is perfectly valid in some catalog, but not one connected to the Page you are sending from, fails exactly like a typo.
Retailer IDs (your own SKU, the retailer_id field) are another common mix-up. The template wants the catalog product's Meta ID, not your SKU. A carousel can hold up to 10 product elements, and a single bad ID in that list is enough to reject the request.
What it looks like
{
"error": {
"message": "(#100) Invalid product id",
"type": "OAuthException",
"code": 100,
"error_subcode": 2018320,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- Sending your SKU or retailer_id instead of the Meta product ID.
- Products from a catalog that is not connected to, or owned by, the sending Page.
- Products that were deleted or replaced after your system cached their IDs.
- Product IDs copied between staging and production catalogs.
- The app lacking access to the catalog that holds the product.
How to fix Messenger error 100
- 1Look up the product through the Catalog API or Commerce Manager and confirm its Meta ID.
- 2Verify the catalog is connected to the Page that owns the Page access token you send with.
- 3Send the template with one product at a time to find the bad ID in a carousel.
- 4Refresh cached product IDs from the catalog instead of storing them indefinitely.
- 5Confirm the request uses Graph API v8.0 or later, which the template requires.
How to stop it recurring
Resolve product IDs at send time, or sync them from the catalog on a schedule, and keep a mapping from your SKU to the Meta ID rather than reusing the SKU. Validate carousels before sending by dropping products the catalog no longer returns. Template size rules are in the Messenger limits reference.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
- 100: Product template not supported below v8Product template is not supported below version 8. Use API version 8 or higher…
- 100: Invalid parameterBad Parameter Error: Invalid FBID.
- 100: Unsupported get request - object missing or unreadableUnsupported get request. Object with ID * does not exist, cannot be loaded due…
Error 100 - quick answers
What does Messenger error 100 mean?
Code 100 with subcode 2018320 comes from the product template, the structured message that renders catalog items in a Messenger conversation.
How do I fix Messenger error 100?
1. Look up the product through the Catalog API or Commerce Manager and confirm its Meta ID. 2. Verify the catalog is connected to the Page that owns the Page access token you send with. 3. Send the template with one product at a time to find the bad ID in a carousel. 4. Refresh cached product IDs from the catalog instead of storing them indefinitely. 5. Confirm the request uses Graph API v8.0 or later, which the template requires.
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.