Trying here to formulate a better conceptualization of SCV (supply chain visibility) in the cloud. Let me just call this concept: Visibility Clouds. Yes, Clouds as in many clouds – crossing country borders and jurisdictions. We will not touch on those legal and political issues here now. Visibility Clouds is a concept where your self-service visibility is readily available in the cloud across all related supply chains in the clouds. The visibility is on-target when the RFID-IS resides in the clouds as it would be avail for Hadoop-type apps to glean information off RFID event data. What is required for this Visibility Clouds (VCs) is to push with some redesign of the visibility platform (VP) to be active in the cloud. The plug-sync-play by each supply chain party to VC will be resulted as an instance of a personalized VM in the cloud with synchronization of both on-cloud and off-cloud supply chain data (such as from the ERP-IS). Such instance will be destroyed along with data for and in the session. We must also look into inter-cloud interoperability and synchronicity. More importantly, how would, e.g., a private cloud (say, a supplier with ezTrack) gives access to a request from a party in a community cloud. We understand that this can be leveraged with the ReBAC model (Relationship-Based Access Control model, based loosely from the Role-based Access Control model) that we have developed. In principles, we argue that the conceptualization of VC is preliminary ready for reference and some realization (or verification as in design science terminology) of VC can be articulated at the technological level.