vforgione / balto-api-express Goto Github PK

• customer
• cart
• sales-order
• subscription
• parcel
• dog

when a new sku is created, the system should automatically create its complimentary models

update refs to meet new mangusu methodology of referencing

• sku
• product
• offer
• deal
• sku-quantity
• sku-cost
• brand
• vendor
• diff
• proposal

• purchase-order
• received-shipment
• contact
• warehouse

Kindly update the following fields of the proposal schema:

review_on date

• always a Monday (cause Rosa said we start weeks on Monday. yeah, I pushed for week number.)

state string

• remove enum for now

remove revenue field entirely

cogs

• autocalculated from: warehouse cost + packaging cost + shipping cost + product cost

contribution_margin_percentage number

• autocalculated
  contribution_margin number
• autocalculated from: price - cogs

image_url string

• of image hosted on s3, sourced from an uploaded file or a buyer provided url

sku_weight
skus_per_offer
packaging_weight
shipping_weight number

• autocalculated from: sku_weight * skus_per_offer + packaging_weight

vendor_product_url

rename msrp to retail_price
retail_shipping_price
retail_url

amazon_prime_elgible bool
amazon_price number
amazon_shipping_price number
amazon_url string

comments
I imagine this could end up being a separate model with commenter name, timestamp and notes.

offer_type string
examples include: online; merchant shipped; inventory

shipping_cost

Let us chat about this today to square away, clarify and address the issues ahead.

Keeping historical data and changes along our travels. I lean toward a more optional, timey-wimey date argument for all api queries over a historically accurate response based on a model’s timestamp. What do you think?

These need to include:

• warehouse cost
• credit card processing cost
• zip code to ship to
• packaging cost

docs on how to do this

• create heroku projects
  • stage
  • prod (can do this later)
• follow docs and deploy

• create cogs property
  • test
  • schema
• implement method of creating

when a sales order is created, it needs to have a cogs property. this is computed from the associated offer/product/sku->sku-cost chain.

when the cogs is set, the sku-cost position property should be incremented according to the order, since the schema is just a reference and a queue.

docs can be found here

should be something like this:

{ ...
  "scripts": { ...
    "postinstall": "npm update"
  }
}

use lusca

• csrf
• xframe (clickjacking)
• xss