Native cannabis menus
Replacing reverse-proxy-based dispensary menus with native WordPress shopping experiences.
The problem
Dispensary commerce often depends on specialized third-party platforms. In this case, the existing shopping experience relied on a reverse-proxy implementation, which limited how naturally product and menu data could be integrated into the surrounding WordPress site.
That separation also made it harder for the WordPress site to work directly with product and menu data.
The approach
I built a custom WordPress integration that connects directly to the Dispense API and renders the shopping experience as part of the site instead of relying on the existing reverse-proxy implementation.
The integration exposes cannabis product data to native WordPress components, allowing each implementation to use the site's own layout, navigation and visual system.
It supports patterns such as product listings, product carousels and customizable layouts without requiring the surrounding site to reproduce the third-party interface.
Built for reuse
This was not implemented as a one-off page.
The integration was designed to be reusable across different client websites, replacing reverse-proxy-based menu implementations with native WordPress shopping experiences.
Each site can maintain its own design while sharing the underlying integration approach.
Related platform experience
I have also built WordPress themes and integrations using the Dutchie Pro SDK and worked directly with Dutchie's engineering team when implementation questions required coordination.