Currently the offline Data packages for a register are created on the same schedule as the channel DB.

This increases the bandwidth requirements from a store perspective (especially with an RSSU in place).

Allowing a different schedule (data group?) for the offline DB allows flexibility for a retailer to control when offline data updated (e.g. daily), or a on a different schedule to that of the main channel DB.

This is more critical with the introduction of the RSSU, given this will also synchronize to the store.

Ideas Administrator

This functionality exist by use of duplicating distribution schedule jobs and separating Channel database groups between offline DBs and CSUs.  If this is believed to be incorrect or not enough, please generate a new idea with further details to illicit newer interest.