PMI

Hawker Management App

As per our understanding, the purpose/Usage of the App is as following -:

• To lookup nearest shop to sell/buy
  • Case BUY -: Without actually knowing if the product is available.
  • Case SELL -: Without actually knowing if there is a demand of that product.

• When the actual Sale/Purchase is done, then for book-keeping the hawker looks up the product [scan/manual], selects the quantity and mark it as sold/bought in the records [inventory update].

Q: Are we correct upon this ? Also did we miss anything ?

APP FLOW

The app resolves three main purpose -:

Usage of the app -

• In a nut shell it's a  a record-keeping app.

• Maintain history of hawker activities [sale/purchase] in terms of shop/product.

App Flow (Hawker View)

Daily Routine -:

Additional Feature (apart form daily routine) -:

• Hawker logs-in to app [phone-number login / OTP validation]
• Has a pre-defined inventory for himself or an empty inventory
• Starts his day by looking up the nearest shop to buy/sell
• Reaches shop location [Geo Tag validation of current location with shop-location]
• Scans a product to be sold/bought
• Chooses quantity of the product
• Checkout the same [Inventory update]
• Move on to next stop.

• Hawker adds a new shop. [Geo tagging, Image upload feature]

Clarification

• Re-set password feature
  • For the auto-generated user-email [to be used in SDFC].
  • Required as a separate feature which will be available for both Hawkers and Retailers.
  • No app-login is required for accessing this feature.

• The app does not deal with any kind of  payment options, only records.
• Inventory simply means the the total package load a hawker is carrying.
• The app is strictly for hawker-use only.

• Sales force integration needs to be explained.
  • Where and how much is required ?
  • Will the APIs be provided for us for the integration ?

• E-Mail Feature
  • Apart from generating an auto email for the registered user, what all does the app needs to fulfill in this regard?

SIGN UP

Q: How much the hawkers [users] can scale up to ?

Q: Is the password to be set for auto-generated user-email?

Assumption: The users here can only be hawkers.

As in we don't have any kind of role management for cases such as shop-login or administer-login.

Are we correct to assume this ?

SIGN IN

Assumption:  Multiple/simultaneous login with same number is NOT allowed.

Are we correct to assume this ?

Reset Password

Assumption: 

• Separate feature
• Works without any kind login [phone-number or email]

Are we correct to assume this ?

[Screen will be prepared shortly]

• Works for both Hawkers/Retailers
• Modify password for the auto-generated user-email
• Works via OTP validation.
• Auto-populate OTP [Needs research]

Q: From where do we need to lookup for retailers data.

Q: Which field shall we use for uniquely identifying retailer records.

OTP Validation

Q: Does the App requires max login attempts validation ? [To prevent kind of DOS attack]

Q: Does the App requires max re-send attempts validation ?

Home Screen

After successful login, hawker lands here.

Q: On what basis do we segregate the shops into Buy/Sell categories ?

As in does a scenario exist where a shop behaves as a dealer [buy from] and retailer [sell to] both ?

Find Nearest-shop

Clicking upon Buy/Sell this screen  pops up.

Q: Do we need to show the nearest shop in a particular radius?

Q: How and by whom the shops-delete / update will be maintained ?

Suggestion - soft-delete

Q: Do we need to manage a Race Condition for hawkers ?

[user scenario -: when two hawkers select the same shop to buy/sell]

Find Nearest-shop

Capacity [buying/selling] of each shop

Q: Should we have a measure of shop size ? [Does the hawker needs to know the same before selecting a shop to buy/sell ?]

OR

Should we look into trends for that ?

• Mentions Point of Purchase (typically 3 to 4 per hawker) and Point of Sale(Typically 30 per hawker)
• Does this means shops will be pre-assigned for each hawker ?

One time data collection

Find Nearest-shop

User Case Scenario -: Sell

Q: How will a hawker get to know about a product order?

OR

If we are dealing in daily targets [to sell] then where and by whom would that be managed [added/edited] for each hawker ?

User Case Scenario -: Buy

Q: How will the hawker know that his demand will be fulfilled by the nearest shop [or which shop] ?

OR

This doesn't matter at all, as in the hawker has to visit various shops to try his luck!

Add-shop

Q: Does the shop existence and business-of-the-shop needs to be validated ?

Product Search

Selecting any shop and searching for a product via text-code/scan-bar-code, this screen pops up.

Q: How and by whom product properties [create/update/delete] will be maintained?

Q: Do we have an initial data seed for available products ?

Q: How much the products can scale up to ?

Product Search

Q: Can the price of the product vary as per shop ? How is price modification to be handled ?

Q: Does the selling-price for a product remains fix ? Are we correct to assume that the hawker strictly sticks to the mentioned price ?

Product Search

Needs Clarification

Are we correct to assume the above ?
PS-: The same concept is to be used when managing the product quantity in cart screen as well

User Case Scenario -: Sell
   -> While increasing the count of product [to be sold], the app should validate the same with max-capacity. [from total hawker-inventory details]       

User Case Scenario -: Buy
  -> This operation might be triggered after the actual purchase is done, so there shouldn't be any checks on product-quantity [to be bought] evaluation.

Purchase

• Is the hawker not allowed to scan for products if Geo-validation of selected shop with his current location fails ?
• Product scanning uses codentify database. Will we get an API to the same ?
• Product can be -:
  • Pack
  • Carton
• Successful scan pulls out both "Variants" [~8] and "SKU" [~16] information
  • Does this means each scan pulls out approx 24 items to be added in the inventory ?
• What is a SKU ?

Sale

• Is the hawker not allowed to scan for products if Geo-validation of selected shop with his current location fails ?
• Who sets routes for the day (for each hawker)?
• Please explain the activity link process to tasking page at SFDC.
• Does the scan work same as Purchase case [regarding "Variants" [~8] and "SKU" [~16]]

Points / Rewards

• Who are backend users ?
• Please explain edit-points function. How and by whom is the points-function managed ?
• How is the scan functionality to be linked with Rewards ?

Cart

Assumption: 

• Cart will be maintained at client-side

Disclaimer: 

• Cart won't be synced between devices.

Are we correct to assume this ?

Splash Screen

User Case Scenario -:

In case after the checkout-splash screen the transaction failed [uncertain reason].

Q: Do we need a transaction confirmation option ?

Q: Do we need a revert option ? [To sync up the inventory]

Inventory

Assumption: 

Opening inventory will be empty for first time users and

will be last-days closing inventory for regular users.

Are we correct to assume this ?

Q: Inventory update is to be done on checkout or at the time of scanning ?

Trade Report

Optimal use of trends

Q: Do we need a way by which the hawker may leverage the use of trends optimally.

Suggestion -:

• From the most selling product list a user can select a product to obtain/copy-to-clipboard the product code or maybe know the current count of same in his inventory.
• From the most buying shop list the user may select a shop and see how far it is from current location.

• Live tracking
• Daily outlet visited [only recorded when a transaction is made]

Profile

User can view/edit his profile

If the user modifies registered phone-number -:

• We in-validate the earlier user-token.
• Route him to OTP screen for validation and complete the login with new token.