Customer Display (CDS)

How CDS media caching works

Understand why promotional files are downloaded to the device and why an existing playlist can keep working through a cloud interruption.

Overview

CDS Store settings and playlist metadata are fetched from MiniTill's cloud endpoint, but managed media is designed to be cached on the CDS device.
When settings are loaded, the native media-cache module resolves remote media to local device files where available.
During a routine refresh, the currently playing cached playlist stays visible while changed/new files are downloaded before the live settings are swapped.
If a media-cache download fails, the app can retain the remote URL as a fallback.
Cached settings/content remain usable when a routine cloud refresh temporarily fails.

This design is useful for a customer-facing screen that should not re-download/stream the same promotional video for every playback cycle.

Upload and save the Store playlist in Back Office.
Leave the CDS online long enough to fetch the settings and cache new media.
Verify the new content plays.
After that, normal playback can use the cached local asset rather than repeatedly fetching the full file.

Do not assume a newly uploaded large video appears instantly on a CDS that has not downloaded it yet.
Do not confuse the local POS↔CDS live-cart connection with the separate cloud settings/media refresh path.

If old media keeps playing just after a settings change, allow the settings refresh/cache process to finish.
If the cloud is unavailable but cached media still works, that is expected; live order updates still depend on the local POS connection.