Skip to content
Byke PRD
PRD: [Merchant Dashboard]
Project Data
More
Share
Explore

PRD: [Merchant Dashboard]

Byke's Merchant Dashboard Product Requirement Document
Damilola Ajiboye
Project:
Merchant Dashboard
⁠
EDIT INFO
⁠
Team:
@Product Management
⁠
⁠
Contributors:
Damilola Ajiboye
Damilola Ajiboye
Damilola Ajiboye
⁠
⁠
TL;DR:
Merchant dashboard to help restaurants accept orders, receive payment, manage inventory, track sales performance, and run targeted marketing campaigns.
⁠
⁠
Status:
@Planning
⁠
⁠
Shipping:
[ ]
⁠
⁠
⁠
Problem Alignment
The Problem
Merchants currently struggle with fulfilling orders, collecting payment, tracking sales and improving their revenue. This problems affects their growth and causes revenue loss.
High-level Approach
A dashboard that allows merchants to accept orders based on ingredient availability, time to prepare and other factors. The dashboard will also enable merchant to keep track of sales, manage inventory, and run remarketing campaigns to their customers.
Success Metrics
Order Fulfillment Time.
Month on Month Sales.
Customer Return Rate.
Month on Month Net Revenue.
⁠
Solution Alignment
Assumptions
Restaurants have reliable internet connection to use product functionalities.
Customers own debit cards.
Key Features
0
Feature
Description
Importance
1
Point of Sale
Accept card payment from customers.
HIGH
2
Inventory Management
Connect sales with physical inventory to avoid ingredients waste and loss.
HIGH
3
Omnichannel
Accept orders from multiple platform like UberEat, Glovo, Social Media.
HIGH
4
Analytics
Real-time tracking of store performance to inform business decisions.
MEDIUM
5
Remarketing
Re-engage previous guest through marketing campaigns.
LOW
There are no rows in this table
⁠

User Interface Design

⁠
⁠
⁠
Constraints
Integration with third party platform is largely facilitated by APIs and Webhooks.
Customers who are not smartphone users cannot be retargeted with digital campaigns.
Payment Service Provider downtime will impact POS functionality and disrupt transaction.
Dependencies
Partnership with third party platforms.
License to practice in certain regions.
⁠
Open Questions
Search
Area
Question
Answer
Instructions if "Yes” (or unsure)
Onboarding / Usability
Do restaurants have digitally savvy staffs that can manage the dashboard?
Yes
Talk to the Product team.
Will the onboarding process require us to provide support materials like how to guides for staffs?
Yes
Talk to the Product team.
Customer Support
Are staffs able to manage customer dispute effectively?
​
​
How can we empower staffs to be able to resolve complaints and dispute?
​
​
Marketing
Are we running a Beta for this?
​
Talk to the PMM team.
Do we need an onboarding experience?
​
Talk to the PMM team.
Growth
Will this be available only for restaurants in the cities?
​
Talk to the Growth team.
Platform
Are we turning this feature on for everyone immediately (versus a gradual rollout)?
​
Defend in this section why you’re opting for an instant ramp to 100%.
Would this affect our existing mobile app and web stack?
​
​
Could this break any existing integrations (e.g., with Google Map, Payment Gateway)?
​
Talk to the Engineering team.
Security & Privacy
Will this involve introducing new data models, changing our authentication process or anything currently in our security?
​
Talk with the DevOps team.
Are we collecting any data that we did not already, or are we using any data in a manner that we did not already use it in?
​
Talk with the Legal team.
Do we need to procure additional license to include these services to our existing offering?
​
Talk to the Legal team.
⁠

⁠
CREDIT: This PRD Template is inspired by
Figma’s approach to modern PRD
⁠
by
Yuhki Yamashita
⁠
.

Problem Alignment
The Problem
High-level Approach
Success Metrics
Solution Alignment
Assumptions
Key Features
User Interface Design
Constraints
Dependencies
Open Questions
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.