Web clock-in and Remote clock-in are 2 different features and are not synchronous in any way.
Web clock in usually used by organizations that don’t have bio-metric devices installed at their office locations. For such organizations, Keka provides an option to log attendance using the laptop/desktop, the employees might have access to. Web clock-in is a web interface that can be accessed by employees (logged in) on web browsers.
Web clock-in is recommended for those organizations that either want to restrict employees to mark their attendance only when in office premise or (organizations) are not concerned about the location of employees when marking their attendance. This is because the web lock-in locations are IP address based and thus can be different from actual location at times based on ISP.
Related: How do I enable web clock-in?
Remote clock-in on the other hand is meant for organizations that have employees who are working from outside office premise and are always out on field, e.g. Sales team. For such employees, it is important to track their attendance timings along with their location of clock-in/clock-out. Keka provides Remote clock-in option for such employees, that can be used both from web interface (using laptop-desktop) as well as Keka mobile app.
Remote clock-in can either be used from web or from mobile app of Keka and are always in sync irrespective of the mode of clock-in. It is recommended for those organizations that want to track the exact location* of their employees when they are doing clock-in.
*Location is exact when the clock-in/clock-out is done from Keka mobile app
Related: How do I enable remote clock-in?
Confused if your organization should use Web clock-in or Remote clock-in? Write to firstname.lastname@example.org, and the folks might be able to help you out.