Cannaflow Migration

We’ve progressing on alignment of the core shape of the migration: Cannaflow will act as the pharmacy connectivity and fulfilment layer, while Releaf keeps ownership of the customer journey, payments and pricing presentation. We’ve also clarified key implementation decisions around product and pharmacy sync, the prepaid order flow, and how pricing should be handled on the storefront.

Delivery is moving forward across both backend and frontend. Core integration work is in progress for pharmacy onboarding and the new product page, while pharmacy & product sync and database changes have already been developed and queued for testing. Several customer-facing UI changes are completed (How it works page, Filters, Hero block, Product card), so a meaningful part of the front-end first implementation pass is already built and being tested.

The main open items are now less about direction and more about final external dependencies and edge-case decisions. We still need closure on comms details, a few Cannaflow API details for onboarding and order creation, and confirmation of how some checkout and shipping validation scenarios should work in the live journey.

• Tech team ia also waiting on Cannaflow to complete support for the affiliation-program webhook - i.e. when a pharmacy opts in to work with Releaf — as well as an easy way to trigger it for testing;  this is in progress on Сannaflow side.
• Additional test account from Cannaflow side is required for dev team
• Work on decigion on mapping between our existing products and Cannaflow products is in progress.
• QES signing has been moved to discovery and will be delivered post-launch.