BBY Dual-Tender High-Level Requirements

Dual-Tender High-Level Requirement Review October 2024

*Contains Confidential Best Buy and RAZR content. Do not distribute.

Product Development Process

We are here!

Modeling (Clients, Programs, Volume, 3-, 5-year picture)

More Detailed Requirements + Assumptions

Pricing/Scope/ Timeline

High-Level Review

Build

Ideation Whiteboarding Session

Each section in this high-level review represents a bucket of work that needs to be completed in order to build and launch this new product. For each section, we have outlined what we know, and what we think is still missing and will require additional requirements gathering.

Other

Experience

Data

Rules

Program Setup

Write your title here

Write your title here

Write your title here

Write your title here

Write your title here

High-Level Review

Program set up comprises all of the configurable aspects of a program requested by a client. As a reminder the program configuration will be the same across ALL client types/industries.

• Site Configuration:
• Tiles? Can promote a specific SKU
• Suggested products?
• Another landing page?

• Product Selection: Class / Sub-class, Manu/OEM, Price binding?
• Fulfillment Fencing - Designate options in setup

• Pricing Method
• Other methods
• Delivery charges?
• Tiered pricing?
• Individual SKU Setup
• Rollover Rule

Other considerations?

What do we know?

• Site Configuration:
• Branding
• Logo
• Content
• Product Selection:
• Categories / Sub

• Pricing Method = Actual BBY.com Price + taxes & fees
• Currency Label (i.e. Points or $)
• Expiration Rules at Program Level

• Program ID (Unique RAZR ID that is created to differentiate multiple programs part of the same client)

Program Setup

*May be one file vs two (TBD at this point)

Data contains the requirements for how RAZR will receive data and what types of data will be required to run programs on this new product.

• APIs for real-time registration
• Is this required at launch? Or future?

• If a client doesn't have the data outlined in File 1, what are their options?
• Consider how the data will be recieved by RAZR. Needs to be secure.
• Participation Flag - need ability to offboard a user either by flag or by file.

• **Really important that we come up with a common data set. This could be 1, or 2 different sets OR have a way to identify a specific field by use case.

Other considerations?

What do we know?

File 1:

• Client ID
• Unique ID (could be Member ID, Employer #, etc.) - must be the same every time
• Name
• Email
• Address (optional)
• Phone (optional)
• Other unique information used for registration

*This file must be loaded first. *This file would create initial end user records & update records each time file is uploaded. File 2*: One-time Loads

• Client ID
• Amount (deposit amount in points or $)
• Description (public facing - in history & email notifications)
• Unique ID (same as File 1)
• Award Date
• Expiration Date (related to the reward specifically)
• Program ID (If can earn in multiple)

Data

Rules refer to the set of prewritten rules used to make decisions using the data being ingested.

Other considerations?

What do we know?

• Create: Create an end user in RAZR
• Update: Ability to update an end user in RAZR
• Deposit: Awarding points/$

• No award calculations: RAZR will not be scoring; the client will explicitly tell RAZR the amount to deposit on an end users account (either by file or other mechanism)

Rules

• Need to determine a set of common data elements that EVERY Client is expected to provide to RAZR to verify a DSO end user at registration.
• For example, for FIs using DSO RAZR requires card number, email address + last for of SSN + postal code
• Single Sign-on (SSO) Login directly from Client to RAZR

• Other triggered communications
• Reminder Emails
• Expiration Emails
• Cancelled, delayed, etc.

Experience refers to how an end user uses the product, what they can see, and what they can expect throughout their journey.

Other considerations?

What do we know?

• Redirect using a URL to Direct Sign On (DSO)
• Registration mechanism
• Login
• Reset
• Triggered Communications
• Welcome email: Triggered once at registration
• Award Email: Triggered everytime a file with a deposit/award is processed
• Confirmation Email: When order is placed
• Shipment Emails: When order is shipped (include tracking)

Experience

Experience refers to how an end user uses the product, what they can see, and what they can expect throughout their journey.

• Other pages needed?
• FAQ page?

• PDP Pages: Bundles, Also viewed, Suggested

• BBY Supplier Plug-ins to consider:
• Fulfillment
• Services
• Tax Remittance
• As-is
• No consideration of dual-tender
• Email: ISP Ready

• Shipping: Do we need to have all shipping options or just standard?

• BBY Product Exclusivity: can clients have non-BBY products? What would need to be true in order to support this? No trevi pay.

Other considerations?

What do we know?

End User Site

• Profile
• Home Page
• Search Functionality
• List w/ filters
• Product Details Page (PDP)

• Cart
• Checkout (Dual-tender available)
• Shipping - Ship to home is standard & included
• In Store Pickup
• Delivery

• Install
• Add on services paid by end user
• Include what comes back in API
• History/Statement (Earned & Redeemed)
• Contact Us Page w/ email & phone number to support

Experience: Site

Other includes all other buckets of work that need to be considered as we determine upfront and ongoing costs related to the use of this product.

Other considerations?

What do we know?

• Sales/Marketing
• Demo site (one per use case)
• Sales collateral? Videos, sell sheet, etc.

• Account / Operations
• Time is takes to setup
• Check list

• Reporting
• Fields expected
• Cadence of reports

• Billing (includes Trevipay)
• Trevipay
• Deposit Accounts

• Customer Service
• Who will support?
• Expectations on who would fund?

Other

Thank You!