Understanding Store EOD Monitoring in Xilnex for Lark

Understanding Store EOD Monitoring in Xilnex for Lark

Overview

Store EOD Monitoring automatically synchronizes end-of-day (EOD) submission data from all your stores into Lark, allowing you to quickly see which stores have completed their EOD process and which are overdue, without having to chase status updates through calls or messages.

This article covers what you'll see once Store EOD Monitoring is set up.

Notes
Before you begin

Ensure that a Store EOD Monitoring base has already been created.
If you haven't set one up yet, see [Creating a Base in Xilnex for Lark] for the instructions.

What's inside your Store EOD Monitoring base

Your base contains two tables:
 Tables
 What it shows you
EOD Session Log
Records each store's EOD submission, including the business date, closing time, store information, cashier details, and other EOD data synchronized from Xilnex ClassicPOS.
EOD Incidents Log
Records EOD-related incidents automatically generated from the EOD Session Log through workflows.


How data gets there

Xilnex ClassicPOS automatically synchronizes EOD data into Lark whenever a store completes its end-of-day process. No manual action is required. As each store completes EOD, the latest session data is synchronized, allowing you to monitor EOD submission progress in near real time.

Reading the dashboard

Your Store EOD Monitoring base includes one dashboard:
  1. EOD Dashboard

    Provides an overview of:

    • Stores that have completed EOD or are overdue
    • Sales and cash declaration summaries
    • Variance incidents
    • Stores with the highest number of variances
    • Incident resolution progress

Automated alerts and summaries

  1. Unverified EOD Session
    1. Detects EOD sessions that have not been verified, allowing operations or finance teams to follow up and complete the verification process.

  2. Unverified Cash Decrease
    1. Detects EOD sessions with unverified cash decrease records, helping ensure cash adjustments are reviewed before reconciliation.

  3. Variance Alert
    1. Detects EOD sessions where the variance exceeds the configured threshold, making it easier to identify submissions that require investigation.

  4. EOD Overdue
    1. Detects stores that have not completed EOD within the expected timeframe, allowing overdue submissions to be tracked and followed up.

Each detection triggers an automated workflow that creates an incident record in EOD Incident Log, eliminating the need for manual monitoring.

Setting permissions

This base is primarily intended for operations teams, finance teams, and IT administrators rather than individual store staff. Access permissions are configured by your IT administrator in Lark, just like any other base.

The following permission settings are recommended for Store EOD Monitoring:
  1. EOD Session Log and EOD Incident Log should be locked by default. The data in these tables is synchronized from Xilnex, and any manual changes will be overwritten during the next synchronization. Edit access should only be granted to IT administrators or designated data stewards.
  2. Operations teams, finance teams, and regional managers: generally should be granted View access so they can monitor EOD submissions without modifying synchronized records.
  3. To allow individual store managers to view only their own store's data, configure row-level permissions as follows:

    1. Navigate to Advanced Permission

    2. Click on the [Turn On Advanced Permissions]
    3. Select the necessary table that need to be set permissions
    4. Navigate to [Record Permissions]

    5. Set the permission to [Records related to members themselves] and save to apply changes.

Notes
Locking specific fields or records like this requires Lark's Advanced permissions feature, which needs a Lark plan that supports it. On workspaces without that plan, this level of control isn't available. You'll only be able to set broad view or edit access per table, not per field.
Info
Good to know
  1. No day-to-day configuration is required. Once the base has been set up, synchronization and monitoring occur automatically.
  2. Like other Xilnex for Lark bases, only data synchronized after the base is created will appear. Historical data is not backfilled.
  3. The tables remain empty until the first EOD event is synchronized from Xilnex.