Skip to content

Item / Price / Cost Maintenance

The VAST master catalog is not shared with OverDrive, so for this store items, prices, and vendor costs have to be maintained manually in both systems. The existing VAST request process through Scott Dow and the retail systems team doesn't change — submitters don't need to know OverDrive exists at all.

When this applies

A new item, price change, or vendor-cost change is submitted to the retail systems team through the existing VAST request form.

The process

  1. The submitter files the same item/price/cost request with Scott Dow and the retail systems team as they always have — no process change, and no need to know OverDrive exists. Price and cost are typically submitted together, with Evan's team supplying cost. (Submitters — Amit, Procurement, Supply Chain)
  2. The retail systems team applies the change in VAST as usual. (Retail Team — Scott Dow)
  3. The OverDrive team receives the VAST change set and checks it against the OverDrive item table, which holds only the few hundred items this express-lane store carries versus roughly 80,000 in VAST, then applies the matching item, price, and cost changes manually in OverDrive. Two separate item sets are maintained in parallel for this one store. (Retail Team — Retail Systems / Derek)
  4. Carry the vendor code from the SATS instance, not the Plaza instance — confirmed with Dan. (Retail Team — Retail Systems / Derek)
  • Packages — the same manual dual-maintenance pattern, defined by the same retail systems team.
  • Coupons — another item covered in the joint item/price/package/coupon meeting.