- assuming a good setup has already taken place...
	- use or don't use
	- if use, what, or which one, or multi?
	- where does this happen? I would recommend that we setup some values in the main session cart or ecommerce cart
	- we have internal (secure environment) and also ecommerce (external)
	- we have the control based on the master pieces that we open... (database controlled)

- transactions...
	- it should actually happen and hit the database on the same page or area as the cart transitioning from session to real database
	- we will have both line items on an invoice as well as possible custom payment options (with logic to back it up)
	- we were talking about allowing the cart to look-up and search the database for options (what do i have and what is available)
		- we were also talking about how the actual write (insert and/or update) will happen in the submit page where everything else gets converted.
	- there is a possibility that the user has an open live cart and an open ecommerce cart...
		- we don't want to assume that both get equal access to the rewards and/or gift cards. just covering our basis.
		- timing of what really happens and where the rubber meets the road.
		- think of a shared gift card... who gets to work off what part and when... not owened by a single person.
	- possible option... treat some of these things like taxes and recalc on the fly.
	- the other option is to show existing (real values) and then make the transaction happen right at the end.

- scenarios
	- rewards/loyalty points
		- setup
			- corp-specific, allow a few renames, chaning values, restoring back to defaults
			- corp to client assignments - opt in/out
			- payment type and/or item setup
		- earn
			- what about opt in/out for certain clients (are there entry requirements? corp-assignments, etc.)
			- based off of rules
			- most of the work is driven from the cart and actually posted/committed after the fact (committing and submitting to the database)
		- use
			- pre-use (how many are available - look-up of known balance)
			- when do we check this? 1st - check what is available (semi unknown - not locked in - show in the cart).
				- 2nd - check right before final processing (before any database transactions). Return them, if needed, back to the cart.
				- 3rd - Passed all other checks and we are going through with it.
			- record transaction in the database
			- payment type and logic
			- possible line item in the cart upon checkout
		- reporting
			- all able to view at the customer level
			- only certain people may see all customer accounts
			- if tied to a balance sheet item, show summaries with drill-downs to more groups and details. brandon can help with this.
			- liability reports - what is still out there and has not yet been claimed and/or used.
			- other reporting such as general stats, usage, percentages, and overviews
		- manual overrides/special
			- only permissioned persons may make manual entries (we need a manual entry form that allows for both adds and edits and ties out to history)
		- histories
			- no history if used normally
			- yes, add a hisotry if any manual interactions (add/edits/voids/deletes/transfers/etc.)
		- cautions
			- sharing and timing (we only want to use and give out what really exists)
			- exclusions (may be handled up at the rule level)
			- expirations (do they run out or become inactive)
			- stopping or discontinuing something - what happens then... technically, there are data and transactions but the company decides no go.
			- future to do lists
				- tie to dates and times (talk to Josh - he has some similar stuff in his discount engine and general discount rules).
			- remember ecommerce
			- what happens, if a new master rule is added... how does that play in.

	- gift cards/certificates
		- setup
		- earn
		- use
		- reporting
		- manual overrides/special
		- histories
		- cautions
	- in-store credit
		- setup
		- earn
		- use
		- reporting
		- manual overrides/special
		- histories
		- cautions
	- lunch cards
		- setup
		- earn
		- use
		- reporting
		- manual overrides/special
		- histories
		- cautions
	- other
		- setup
		- earn
		- use
		- reporting
		- manual overrides/special
		- histories
		- cautions