Menu Items

Menu items are the core of the Menu API, powering both the customer experience on Weedmaps and online ordering functionality.

In 2025-07, there are two available methods for managing menu items:

Direct Management

Full control of menu items through your integration using standard create, read, update, and delete (CRUD) operations.

See Direct Management Guide.

Indirect Management

A simplified approach where you submit product details and Weedmaps handles classification, categorization, and presentation logic.

📘

You can see the request schema, response schema, error schemas, and run live examples with menu items through the API Examples

See Indirect Management Guide.

🚧

Access Control Notice

Retailers can pause your integration at any time. When this happens:

• You will not be able to create, update, or delete menu items (these requests return a 423 Locked response).
• You will still be able to read menu data.

Choosing an Approach

• Use Direct Management if you require fine-grained control over menu content.
• Use Indirect Management if you prefer Weedmaps to handle categorization and product associations on your behalf.

♻️ Keeping our Systems in Sync

You are required to provide an external_id when working with Menu Items.

• The external_id should uniquely identify a Menu Item. It must not be tied to a "batch" or inventory shipment,
  as those change frequently.
• If the external_id changes (i.e., churns), Weedmaps will treat it as a new Menu Item. Even if it appears identical,
  it will lose all curated data—such as Brand links and product Attributes—previously applied through
  machine learning, manual merchandising, or the Weedmaps curation team.
• The external_product_id can be used to help caching efforts for Brand Product Linking for the Menu Item.
  This attribute should reflect your internal Brand Product identifier.