Skip to content

Packages

Packages aren't shared between VAST and OverDrive, so for this store they're created and maintained manually in OverDrive to mirror what the retail systems team defines. OverDrive currently has proof-of-concept-level package support, built on an internal inventory search, and this playbook covers keeping packages in sync — not whether a package can be sold.

When this applies

The retail systems team creates a new package or changes an existing one, and it needs to be reflected and kept current in OverDrive.

The process

  1. When the retail systems team defines a new package or changes an existing one, manually create or update the matching package in OverDrive so the two stay in sync — packages aren't shared with VAST, so this is dual maintenance for this one store. (Retail Systems)
  2. Build and maintain the package in OverDrive using internal inventory search, the current proof-of-concept-level package support, and validate components and pricing before it goes live. (Retail Systems)
  3. Retire or deactivate a package in OverDrive as soon as the retail systems team ends it, so OverDrive doesn't keep offering a discontinued package. (Retail Systems)

Go-live & cutover notes

  • New and changed packages originate from the retail systems team; for this first store, package creation in OverDrive is manual — much as it largely is in VAST today. (Retail Systems)
  • Fulfillment note: at the counter, if a package component isn't in internal inventory, transfer the line to the RO and replace it with product sourced from PartsTech. (Store Associate)
  • The fulfillment side of this workaround has a removal target of 30–60 days, once Package Builder supports supplier product via PartsTech. Longer term, a shared catalog removes the manual dual maintenance of package definitions.

Still being confirmed

  • How package information reaches the OverDrive team from the retail systems team, and how the OverDrive team is alerted to a new or changed package. (Retail Systems)
  • Whether the retail systems team needs to do anything different to flag a package for OverDrive. To be settled in the joint item / price / package / coupon meeting. (Retail Systems)
  • Item / Price / Cost Maintenance — the same manual dual-maintenance pattern for the same retail systems team.
  • Coupons — another item covered in the joint item/price/package/coupon meeting.
  • Inventory — where package components are checked against internal stock.