Manually Uploaded Images Taking Priority

Weedmaps has updated its logic around menu item imagery to prefer images manually uploaded in the Weedmaps menu interface. This means images sent and/or ingested from external parties will no longer be assigned to menu items where those images were manually set.

Why Did Weedmaps Make This Decision

In order to provide a best-in-class experience for our listing owners, we want changes they made in Weedmaps to stick. They took the time to change that image in Weedmaps vs in the associated integration and we want to do our best to respect that time.

How Can We Get Images Showing Up Now?

If an item on a Weedmaps menu did not get its image set manually, there is no impact on how things work currently. Sending a downloadable url should still update the item in question.

In cases where someone has set an image manually, there is nothing you can do through the integration itself to remove that image. The image will need to be manually removed in Weedmaps in order for incoming updates to be accepted again.


Removing The Menu Item

While it's not recommended, a menu item could be recreated via the API. This would reset the image, but it would also reset any history on that menu item. That means removing it from any active carts and favorites. This should be used as a last resort or not at all.

How Do I Know If An Image Was Manually Updated?

Unfortunately there's no way to determine this via the API alone. In cases where you don't see images uploading, we would recommend fetching the menu item in question and opening up the picture_url provided in the response. If that image does not match what you have in your system--and not a placeholder image generated by weedmaps--you can safely assume that image was manually uploaded.

curl \
  --url '{menu_item_id}' \
  --header 'accept: application/json' \
  --header 'authorization: Bearer [ACCESS TOKEN HERE]'

Please keep in mind the picture_url is the new URL we generated when downloading an image. We do not expose integrator provided URLs in our API response.