FF - Recurring Billing

Plan your projects and define important tasks and actions

Get Started. It's Free
or sign up with your email address
Rocket clouds
FF - Recurring Billing by Mind Map: FF - Recurring Billing

1. Story 1 - User Purchases Magazine Subscription

1.1. User Adds Magazine to Cart

1.1.1. Add to cart succeeds

1.1.1.1. Proceed to commit transaction

1.1.1.1.1. Transaction: Magazine Subscription

1.1.2. Add to cart fails

1.1.2.1. generates user error reports

1.1.2.1.1. 1. reports error to log file and/or database (define the nature of the error)

1.1.2.1.2. 2. reports via email to dev & MGMT

1.1.2.1.3. 3. send message to user's screen (define the nature of the fail).

1.1.2.1.4. 4. present user the add screen again to retry.

2. Story 2 - User Purchases a 6 Month CSA

2.1. user adds CSA to cart

2.1.1. Add to cart succeeds

2.1.1.1. 1. get current date from server

2.1.1.2. 2. check if currently in black out date for CSA

2.1.1.2.1. Yes: If in black out date

2.1.1.2.2. No: Not in black out date

2.1.2. Add to cart fails

2.1.2.1. generates user error

2.1.2.1.1. 1. reports error to log file and/or database

2.1.2.1.2. 2. reports via email to dev & MGMT

2.1.2.1.3. 3. send message to user's screen

3. Story 3 - User Purchases a 3 month CSA

3.1. user adds CSA to cart

3.1.1. Add to cart succeeds

3.1.1.1. 1. get current date from server

3.1.1.2. 2. check if currently in black out date for CSA

3.1.1.2.1. Yes: If in black out date

3.1.1.2.2. No: Not in black out date

3.1.2. Add to cart fails

3.1.2.1. generates user error

3.1.2.1.1. 1. reports error to log file and/or database

3.1.2.1.2. 2. reports via email to dev & MGMT

3.1.2.1.3. 3. send message to user's screen

4. Dev Concerns 1 - Price Change

4.1. When do prices change?

4.1.1. not often.

4.2. What is the internal process to determine price changes?

4.2.1. vendors and FF set retail up together - 15% for retail

4.3. This WILL impact recurring billing year to year

4.4. When are prices determined for the season?

5. Dev Concerns 2 - Date Changes

5.1. How are cards handled if the date expires before the next billing date?

5.2. Separate systems must be developed to handle cards expiring and cards that have expired.

6. Dev Concerns 3 - Interval Change

6.1. What happens when an interval changes?

6.1.1. Dates have to be all recalculated & system could be thrown off.

6.2. How often do you expect to change the interval in the CSA?

7. Dev Concerns 4 - Voided, Refunded & Canceled Transactions

7.1. What happens if a transaction is voided?

7.2. How are refunds handled currently in the business?

7.3. What happens when a user cancels a transaction in the business?

7.4. What is the rate that you're refunding money?

7.4.1. When they are moving (refunding for subscriptions)

7.5. Itemized Refund

7.5.1. Subscription

7.5.2. "widgets"

7.6. Tax

7.6.1. How to calculate and refund

7.6.1.1. CPA - if we refund, refund the total.

7.6.1.2. Storage table of taxes refunded

8. Dev Concerns 5 - Shipping

8.1. How does shipping currently function?

8.1.1. ship station charges uses USPS

8.1.2. Stamps.com account

8.1.2.1. talks to ShipStation

8.2. What ties to ShipStation are handled programmatically?

8.2.1. Automatic currently (program)

8.2.1.1. prints picking station

8.2.1.2. Manual picklist

8.2.1.3. Manual Weight

8.2.1.4. Manually USPS Pickup

8.3. How will the 'manual' processing of orders take place?

8.4. Who handles the shipping? Same people every time?

8.4.1. one person shipping

8.5. Is this trainable?

8.5.1. yes

8.6. Do you have a procedure documented?

8.6.1. recommend

9. Story 4 - Manual Shipping of Product

9.1. See Dev Shipping concerns