Leaf UT - Home Delivery
Miles Dinsmore avatar
Written by Miles Dinsmore
Updated over a week ago

As a Pharmacy facility in UT, users now have the option to enable Home Delivery workflows in MJ Platform via third party integrated services. This article describes the functionality that is available to UT licensee users.

Contents

Enabling Home Delivery Workflows

As a Pharmacy (Retail) Organization Administrator, navigate to Facility Settings > Home Delivery. This opens the Home Delivery Setup page.

Next to Enable Home Delivery workflow? select Yes from the drop-down menu, then click Save.

Accessing the Delivery Orders Queue

As a Pharmacy (Retail) user, navigate to Delivery from the main menu. This opens the Delivery Orders page, which shows all completed orders (payment posted and inventory fulfilled) that have a fulfillment status of “delivery”.

The orders are grouped within the tabs beneath the page header by their current status. Use the tabs to view the delivery orders by status:

  • Pending Delivery Orders

  • Delivery Orders Out for Delivery

  • Completed Delivery Orders

Modifying the Attributes of a Delivery Order

To modify the attributes of a delivery order, find the delivery order in the list and click the Modify button on its row. This opens the Modify Delivery Order page. Use the fields on the page to modify the attributes. Required fields are marked with an asterisk.

Modifiable attributes include:

  • *Delivery Method:

    • Select In House if the delivery order will be fulfilled by a driver from the pharmacy facility.

    • Select Courier if the delivery order will be fulfilled by a third party courier service.

  • *Courier: If the Delivery Method selected is Courier, use the Courier dropdown menu to select the courier service that will fulfill the delivery of the order.

  • *Delivery Status: Select the appropriate status for the delivery order from the drop-down menu.

  • Date/Time Expected: Using the date/time selector, specify when the patient is expecting the order to be delivered.

Once all modifications have been made, click Save to update the form.

API Integration

Please have your third party integrator visit partners.mjfreeway.com to request access to our API documentation and integrator sandbox.

Note: The list below provides the simple endpoints that are available to UT users for home delivery. Detailed API documentation is provided through our Partner Portal.

The Home Delivery functionality has been designed to enable licensees to connect with third party integrators that are able to provide online ordering and home delivery to clients.

The following endpoints are provided by MJ Freeway to enable these integrations.

UT Patient Validation

  • POST /leaf_mjp/validate_card_sync

    • Validate a card in the registry and create or update a patient record in MJ Platform

Patient and Partner Details

  • GET /consumers

    • Lists consumers at a facility

  • GET /consumers/{consumer_id}

    • Lists consumer details of a single consumer

  • GET /partner_facilities

    • Lists partner facilities

  • GET /partner_facilities/{partner_facility_id}

    • Lists partner details of a single partner facility

Products and Inventory

  • GET /catalog

    • Listing of sellable products used for digital menu board and online ordering

  • GET /items

    • Listing of sellable inventory items (products with active inventory at a facility)

  • GET /item_transactions

    • Listing of transactions occurring on individual items

  • GET /item_masters

    • Listing of products at a facility

  • GET /item_masters/:id

    • View details of a single product at a facility

Orders

  • GET /orders

    • Lists orders

  • POST /orders

    • Create a new order

  • GET /orders/{order_id}

    • Load the details of a single order

      • New parameters added to this public endpoint:

        • Delivery Method (delivery_method) - enum: ‘in_house’, ‘courier’

        • Partner ID (partner_facility_id) - use GET /partner_facilities to retrieve the ‘partner_id’

        • Delivery Status (delivery_status) - enum: ‘pending’, ‘out_for_delivery’, ‘completed’

        • Date/Time Expected (delivery_expected_at) - date/time

  • PUT /orders/{order_id}

    • Update the order-level details of a single order

  • POST /orders/{order_id}/products

    • Add a product to an existing order

  • DELETE /orders/{order_id}/products/{product_id}

    • Remove a previously added product from an existing order

  • POST /orders/{order_id}/coupons

    • Add a coupon to an existing order

  • DELETE /orders/{order_id}/coupons/{coupon_id}

    • Remove a previously applied coupon from an existing order

  • POST /orders/{order_id}/redemptions

    • Apply reward points against an existing order

  • POST /orders/{order_id}/payments

    • Apply a single payment against an existing order

  • POST /orders/{order_id}/submit

    • Submit an online order for processing

  • POST /orders/{order_id}/cancel

    • Cancel an existing order

  • POST /orders/preview

    • Preview pricing and taxes for an order that has not yet been created

Delivery Orders

  • PUT /delivery_orders/retail/{order_id} endpoint

    • Update existing delivery order details

  • GET /delivery_orders/courier

    • Used by a courier service integrator to retrieve delivery orders assigned to the courier

  • PUT /delivery_orders/courier/{order_id}

    • Used by a courier service integrator to update the status of a delivery order

Did this answer your question?