Skip links
Table of Contents
    blog_placeholder

    Frappe HRMS FMCG Case Study: Automating Payroll and Attendance Across Plants

    This Frappe HRMS FMCG case study covers how a multi-plant ice cream manufacturer in Gujarat replaced manual, plant-by-plant attendance tracking and payroll reconciliation with a single automated system built on ERPNext/Frappe HRMS, achieving zero-error attendance processing and automated payroll across all its manufacturing locations.

    If you run HR or operations for a multi-plant FMCG business, the pattern behind that summary probably sounds familiar: attendance gets logged differently at each site, payroll runs on spreadsheets stitched together at month-end, and every plant manager has their own workaround for shift changes.

    Frappe HRMS FMCG Case Study: The Multi-Plant Attendance and Payroll Problem

    The manufacturer operates across several production locations, each running its own shift patterns tied to seasonal demand. Ice cream production ramps up sharply in summer months, which means shift rosters, overtime, and headcount all shift with it. Before working with Aavatto, attendance and shift tracking were handled manually at each plant, with payroll assembled separately for each location and then reconciled centrally.

     

    This created two connected problems. First, accuracy: manual attendance entry across multiple sites is where FMCG manufacturers typically lose the most time. Supervisors log hours on paper or in disconnected spreadsheets, someone re-keys that data, and errors compound before they’re caught, if they’re caught at all. Second, compliance: statutory payroll requirements in India (PF, ESI, professional tax, overtime rules) apply per employee per location, and reconciling that manually across plants each month is the kind of work that produces missed deadlines and audit exposure — not just a one-time inconvenience.

    What Aavatto implemented

    Aavatto implemented a customized ERPNext/Frappe HRMS deployment built specifically to handle multi-plant attendance and payroll for this manufacturer, rather than a generic HR module rollout. The system was configured so attendance, shift assignment, and payroll processing worked as one connected workflow across all manufacturing locations, instead of each plant operating as its own silo.

    Standard HRMS setup handles a single location well out of the box. A multi-plant FMCG business needs shift and attendance rules that can vary by plant while still rolling up into one payroll run a central HR or finance team can review. That’s a configuration and workflow design problem as much as a software one, and it’s where a generic implementation tends to fall short and where Aavatto’s Frappe specialization, applied specifically to manufacturing operations, made the difference for this client.

    Talk to us about your FMCG operations if attendance and payroll across your plants currently rely on the same kind of manual reconciliation this manufacturer moved away from. It’s a narrower, more solvable problem than it feels like from inside it.

    The outcome: zero-error attendance and automated payroll

    Following implementation, the manufacturer achieved zero-error attendance processing and automated payroll across all its manufacturing locations. Attendance data now flows directly into payroll calculation instead of passing through manual re-entry, which removes the point where errors were previously introduced. Payroll processing itself is automated rather than assembled by hand each cycle, which closes the compliance gap that manual, location-by-location reconciliation had created.

    It’s worth being precise about what “zero-error” means here rather than treating it as a marketing line. It reflects the elimination of the manual re-entry step that was the source of attendance errors in the original process, not a claim that the system prevents every possible data-entry mistake at the point of capture. That distinction matters if you’re evaluating this for your own operation: the gain comes from removing a specific failure point, so it’s worth understanding exactly where your own failure points sit before assuming the same fix applies identically.

    Why this matters for multi-plant FMCG operations specifically

    FMCG manufacturing has a few characteristics that make attendance and payroll automation more valuable than in a single-site office environment, worth naming plainly rather than assuming they’re obvious:

    Shift volume and seasonality

    Production output tied to demand cycles means headcount and shift patterns change more often than in a stable back-office environment, so attendance systems built for static schedules tend to break down.

    Multi-location compliance

    Statutory requirements apply per plant, and consolidating that correctly requires the system to handle location-specific rules automatically rather than relying on someone tracking it manually across sites.

    Plant-floor realities

    Attendance capture needs to work for a production workforce, not just office staff logging in from a desktop, which affects how attendance is actually captured at the source.

    None of this is unique to ice cream manufacturing. It applies to most FMCG businesses running more than one production or distribution site, which is why this multi-plant attendance automation case study is a useful reference point even if your product isn’t food.

    What to evaluate if you're considering this for your own plants

    If you’re an owner or ops leader looking at Frappe HRMS for a similar setup, a few questions are worth working through before you start:

    How many distinct shift/attendance rule sets do you actually run across plants?

    This determines how much configuration work is involved versus a straightforward rollout.

    Where does payroll currently break down?

    Is it attendance accuracy, statutory compliance calculation, or the manual reconciliation step between the two. The answer changes what needs to be prioritized in implementation.

    How is attendance captured today?

    Paper, spreadsheet, biometric, or something else — and what does that mean for how quickly a new system can be adopted on the plant floor without disrupting production.

    There’s no single timeline or configuration that fits every multi-plant FMCG business. The answers to those three questions shape the scope of work more than the size of the company does.

    Frequently Asked Questions

    Yes. Shift and attendance rules can be configured per location within a single Frappe HRMS deployment, which is what allows a central team to manage multiple plants without each one operating as a separate system.

    Frappe HRMS can be configured to apply statutory payroll rules (PF, ESI, professional tax, overtime) automatically per employee and location, which reduces manual compliance work in regulated manufacturing environments. The specific configuration needed depends on your state and industry requirements.

    It depends on the number of plants, how many distinct shift/attendance patterns you run, and how attendance is currently captured. There's no fixed timeline that applies across every FMCG manufacturer.

    Yes. The underlying problem this multi-plant attendance automation case study addresses, consolidating attendance and payroll across sites, is common to most FMCG manufacturing and distribution operations, not specific to ice cream production.

    No. Automation removes the manual re-entry and reconciliation steps that introduce errors, but plant and central HR teams still review and approve attendance and payroll data within the system.

    If manual attendance and payroll reconciliation across plants is costing your team time every month, or creating compliance risk you’d rather not carry, talk to us about your FMCG operations. We’ve implemented this exact kind of multi-plant Frappe HRMS setup before, and can walk through what it would take for yours.

    Read the full case study: HRMS Implementation for a Leading Ice Cream Manufacturer in Gujarat

    Author
    Niraj Gohel
    Meet Niraj Gohel, the “Problem Solver”, and occasionally the problem creator at Aavatto. When he’s not traveling, watching a film, or having a cup of tea, he spends his days solving problems, debating ideas, and occasionally distracting the team with completely unrelated conversations. His philosophy is simple: technology is important, but being a good human is more important.
    gohel-niraj
    This can be a new journey !

    Have a Project in Mind?

    This can be a new journey !

    leaf