User stories for Plone Commerce features

The first case here starts with a simple case of payment processing. Additional information to expand this into a full store are listed separately below.

Overall Payment Workflow:

• Overall Payment Workflow

Site Administrator:

A role that installs, sets prices and then collects $$!

[jdp....maybe there should be a config "set" that bundles certain options together...like for...donations...commercial shopping cart...memberships...etc...then the default for the skin and the business process would be appropriate...would allow us to circumvent custom naming conventions?...]

Product Installation and Configuration

• Add Payment Processing to Site
• Configuration Panel for site-wide options
• Set up Payment Processor
  
• Choosing a Currency
• Configure Emails notification and standard messages
  
• Configure Discounts for setting codes and amount of discounts
• Configure Payment Disclaimer Text and link to privacy policy that show in checkout
  

Payable Delivery Types Configuration:

• Configure Membership Types for setting premium memberships and access information
  
• Configuring Shipping
• Configuring Pricing - ie "make payable"; Deferred on site-wide level, currently only on the object level
  

Payable Content Management

• Make Object Payable (see Configuring Pricing )
  
• Add Donation Form
• Setting Means of Delivery to be web, shipping, or subscription-based, on a particular content object
• Configure Premium Content Access for what levels of membership can use content
  

Financial Account Management

This part may be handled by the payment processor itself, but for some processors will need an interface to complete.

• View History of Payments

End User Experience:

• User Pays specific scenario for the checkout or payment processing
• Payee and Merchant Receive Email Confirmation of order
• Member Views Transaction History
  
• Member Updates Profile Information , address, credit card, etc

Specific Payment Cases

• Member Makes Donation to a non-profits
• Member Purchases Subscription for recurring expenses
• Member Purchases Access to Content for an article or section of site
  
• Member Purchases Registration for Event+

older stories...

• View Payable Object
• View Payment Confirmation
• Payee Prints Receipt+
• Payee Specifies Repeat Payment Option+
  

Questions

• Does user have to take an action to accept the disclaimer? or is it presented as "by completing this purchase, you accept..."

Assumptions

• Someone who pays/purchases must be a member of the site
• We don't want to store the credit card number ever...
  
• Reporting is done in another application. This app gives you history information.
  
• We are not making a persistent cart, but you can...ie you can't save your cart and come back later
  

Ecommerce Store

These stories are beyond the scope of the current project, but may be related to the work others wish to see. The stories are noted and/or elaborated here for that purpose.

• Catalog
• Inventory Management
  
• Tax Handling on Orders
• Shipping Charges and FedEx/UPS integration

Deferred

Payment information customizations: The Admin can edit the default fields (what screen are we talking about here, what are the default fields???) by adding additional fields or removing existing ones. This can be applied to all payments or payments made on a particular content type (verify this). The form also allows the admin to specify different information necessary for the different payment types (ie check vs cash vs credit)

• Admin Issues Refund
• Admin Processes Credit Card Manually for handling the payment processing when someone calls via phone, for example. Not for now...