start cart
add to cart
start cross corp bill


possible new table:

customer_wholesale_settings table
wholesale_id auto id int(10) primary key
corp_id int(10) default 1 - index
customer_id int(10) default 1 - index
wholesale_mark_up decimal(5,2) default 0.00
wholesale_status tinyInt(1) default 1 (1=active and 0=inactive)


new session values:
session.myCart_st.myCustomerInfo_st.is_wholesale_customer = 0 or "no"
session.myCart_st.myCustomerInfo_st.wholesale_mark_up = 0

tag team on the invoice_type_id of 6 (transfers)
- setting prices to cost plus the mark-up
- no taxes
- no discounts

tag team on existing add/edit customer permission

need some way to tie in the customer to the wholesale settings - link or button from the custom log page

be able to skip metrc integration

still a regular invoice, just a little magic on top


/////////
cautions

db_field_settings - all customer fields special naming stuff


there are 3 possible options:
1. Leave the customer table alone and add a new wholesale settings table
2. Add two new columns to the core customer table
3. Use the database extension options to do sub attributes
	- this gets more dynamic but allows for tons of options both seen and unseen
	
Steve and Brandon are leaning towards option 3. More power...
	- this is the warehouse door for customer data storage

Research:
known pages: get to the add_edit_customer.cfm page. click on the gear. that takes you to field_settings_customer.cfm
	- this is where we want to store new wholesale settting - will be stored in JSON
	- current JSON id is 779 (aka the web_page_id)
		- this setting will just store the reference or pointer to the other tables
	- On this page (field_settings_customer.cfm) here are the new fields:
		- yes/no use wholesale
		- default mark-up on costs
		- what to call the wholesale piece (optional or we just control it)
		- what is the id or pointer to the sub attribute
			- we may need to build this process in the background
				- the main table is called sub_inventory_attributes
				- make a new one that is capable of doing customers, invoices, quotes, e/r, PO's, users, vendors, time
					- super generic - maybe called "flex_attributes" (new table name)
					- auto id, corp id, app type id (new column and allows us to tie to the 12 main players), then all other fields on the sub_inventory_attributes table. i would also recommend that we have dev flags 1-3 on this table as well. Similar to the special accounts stuff.
	- there is an existing action on field_settings_customer_action.cfm
	- bonus round... we really need to move these core customer settings to the main customer homepage

	////////////// not part of your current project.... where we are headed (customer templates)

	other existing pages that have similar flow - in parts and sub inventory
	- top_secret/secure/sub_inventory_templates.cfm - this page helps to show some of the attributes
		- the sub attrubutes are highest level aka the name and the column
	- eventually, we want a customer sub attributes page for customers. this is where they setup their own attributes.
		- this will be patterened off of the sub_inventory_templates.cfm page but for customers.
		- we may end up calling it sub_customer_templates.cfm
		- the actual values that are entered per customer will end up showing up on the add/edit customer page (add_edit_customer.cfm)