UC3::View Sales
Overview
Allows merchants to view a report on sales activity for products that have been purchased via the system. The merchant can choose different report types, view the report online, print it or save it locally in a different formats.
Document History
  1. Current Version1.3
  2. 1.1odlingsmee; 01 Jan 2006 ; Initial Revision
  3. 1.2odlingsmee; 10 Nov 2009 ; Completed sequence of events and added description.
Properties
  • TriggerA merchant wishes to review recent sales on the system.
  • GoalTo review the volume / value of sales of the merchants products.
  • Primary ActorMerchant
  • Pre-RequisitesThe merchant shall be [UC1] logged on and registered as a merchant.
  • Success OutcomeThe merchant will have been able to view (and print) the volume / value of sales for the period they were interested in.
  • Failure OutcomeThe merchant will not have been able to access the sales reports - the system will have generated error messages and advice as to the appropriate recourse should they wish to obtain the details immediately.
  • Priority2
  • Complexity3
  • Packagemerchant
Basic Flow
  1. The merchant selects the type of sales report they wish to see.
  2. The merchant enters parameters. Paremeters include product class, promotional codes and date range.
  3. The system validates that the report parameters have been entered correctly.
  4. The system executes the report with the parameters supplied by the merchant.
  5. The system presents the report results to the merchant.
  6. The use-case ends.
Alternative Flows
Export Report

At step 5 of the Main flow when the merchant wishes to save a copy of the report

  1. The merchant selects the output format of the report.
  2. The merchant selects where the report should be exported to.
  3. The flow of events continues from step 5 of the Main flow.
Select a new report

At step 5 of the Main flow when the merchant wishes to run a different report

  1. The merchant selects a different report to the one currently displayed.
  2. The flow of events continues from step 2 of the Main flow.
Exception Flows
Invalid report parameters

At step 3 of the Main flow when invalid report parameters entered

  1. The systems highlights validation errors to the merchant and prompts the merchant to correct the errors.
  2. The flow of events continues from step 2 of the Main flow.
Report error

At step 4 of the Main flow when the system fails to succesfully execute the report

  1. The system cannot run the report due to a technical fault.
  2. The systems informs the merchant of the issue and (where possible) advises them of the best possible course of action.
  3. The use-case ends.
Activity Diagram