Optimize Vendor Flow Process to ensure 100% vendor logging for bookings

[Vidiskiu]

Description

Improve and streamline the vendor onboarding and management process to enhance efficiency and accuracy. The availability of vendors and their extra services serves to:

• Enhance the guest experience during their reservation.
• Ensure proper documentation of extra services.
• Generate extra revenue for Bukit Vista.

Problem

• Inefficient Onboarding Process: The current vendor onboarding process is manual and time-consuming, leading to delays and errors.
• Data Inconsistency: Vendor information is stored in multiple places, resulting in data discrepancies and inaccuracies.
• Communication Gaps: Lack of automated communication channels causes missed updates and reminders, impacting vendor engagement.
• Compliance Issues: Manual compliance checks are prone to errors, risking non-compliance with industry standards and regulations.
• Performance Tracking Challenges: Absence of a structured system for tracking vendor performance leads to difficulties in assessing their contribution to the business.

Solutions

• Revise vendor tables and to necessary migrations

https://drawsql.app/teams/bukit-vista/diagrams/vendor-1

• Vendor Booking
• Vendor will open only BVGO. We have to prevent login authorization in BIGRR.
• Product placement: All vendors will be able to declare their own item prices
  • Category of product
  • Product - Price - Description - Attachment
• Vendor user data structure:
  • User -> vendors (through vendor_id) -> roles through role_id in vendors table

BVGO Solutions

• Vendor is able to sign up through BVGO directly. This will be notified to a certain slack channel that there is a sign up. We will notify a certain slack channel for approving their user status.
• Vendor will see the different user types that is available. In the beginning, we will only see options to create Vendor user type. For reference, see:

• If still not active, we will show the page of waiting for approval.
• If user is active, they will see
  • Vendor Dashboard
    • Count of new requests
    • Count of active requests
    • List of pending requests, which with one click can be accept. But clicking outside of the button would reveal the request details.
  • Vendor Bookings
    • Date filter with default value today
    • Button filter with status pending, confirmed (default), cancelled.
    • Vendor booking details
      • Shows only service details.
    • Vendor booking journey
      • Pending
      • Active
      • In progress
      • How to update this status: .....
      • Completed
    • Vendor booking message
  • Vendor company list ("My Company" (?))
    • Different company can be slided like my property
    • Show rounded button for account report that show the month's revenue (this does not lead to anywhere yet)
    • Show service list
  • Notifcations
  • My profile
• If the request is rejected, .....

Measurement metrics

• Number of extra services logged to their booking

Current measurements:

• Some extra services are logged according to their booking, some are logged in CODA

SLA

• All extra services are logged according to their booking

PRD: https://coda.io/d/Tools-Product-Specification_diSmnBlg0yF/Vendor-Management_sufHR#_luGZr

[Vidiskiu]

DESCRIPTION

Our project aims to optimize GAIA, our guest interaction AI, to handle additional services more effectively, creating an opportunity for side revenue. We want GAIA to develop basic sales skills to proactively offer extra services to guests and efficiently communicate their needs to vendors via the BIGRR system.

PROBLEM

• Reactive Service Handling: Currently, GAIA only responds reactively to guest requests. We need GAIA to proactively offer extra services to enhance guest experience and increase revenue.
• Manual Processing for vendor except driver

SOLUTIONS

• GAIA is capable to pro-actively offer extra services to guest depending on certain scenario. The complete scenario for first iteration can be seen here
• We should treat all extra service like transportation where user can input manually on BIGRR without coordination using AS3

MEASUREMENT METRICS

• Percentage of extra service delivered when user has registered the request to BIGRR

SLA

• 100% extra service delivered when user has registered the request to BIGRR

TEAM MEMBER

@RobinNusantara @vitomichael @alimasykur27

UPDATE MAY 31

• We got IDR 49.345.000 revenue from extra service (USD 3035)
• Our may monthly target is USD 405K, therefore the minimum target of extra service should be USD 8100
• We failed to achieve the revenue target, based on MSM meeting, this project should be "on-hold" while we allocate the resource to execute other strategies