Greenfile turns each client's SKU catalogue into a defensible EPR liability assessment. Every plastic component classified, every rupee computed under the live rule, every determination traceable to the person who signed off on it.
Portfolio EC · settled
₹2,52,511.20
Across 3 of 4 computed · 15 components to review
| Client | Liability | Filing |
|---|---|---|
| Kalp Foods· 3 to review | ₹1,24,880.00 | Ready |
| Rivergrain | ₹86,410.40 | Submitted |
| Neem & Co· 12 to review | Not computed | Not started |
| Saffron House· Estimate stale | ₹41,220.80 | Draft |
from ₹2,900/ tonne
EC your client owes on unmet targets, rising by category
500SKUs
Classified in a single batch upload, per client
2×per year
Half-yearly and annual returns, for every client you file
1screen
Every client's liability, reviews and filing status
⟶ The problem
01
When your client is questioned, your working is the evidence. A spreadsheet cell cannot say who decided, under which rule version, or when. Greenfile writes an immutable snapshot on every recompute and records the person who attested each determination.
02
One file per client answers questions about that client. It cannot tell you which client is at risk this week, whose figure went stale after a review, or what falls due in ten days. That answer lives in your head, until it does not.
03
PWM amendments shift recycling targets, EC rates, exemption registries. Static formulas are stale the moment they are written, and one amendment means re-checking every client file by hand. We read the rule at compute time.
⟶ Platform
Every client on one screen: settled liability, components waiting on review, estimates gone stale, filing status for the year. Open any client to work inside their workspace, then come straight back.
Upload up to 500 SKUs per client in one pass. Each packaging component lands in PWM Categories I–V with a confidence score. One malformed row never fails the batch, and unmapped rows are split into what the client must clarify and what we need to fix.
Components below the confidence threshold queue for review. Confirm, override the category or material, or reject. The classifier's original call and your final one are both kept, never collapsed into each other.
A liability assessment you can hand over: the client's identity and GSTIN, liability by category, per-SKU detail citing the rule it rests on, and a methodology note separating what the client attested from what Greenfile derived.
Every calculation runs under a pinned PWM Schedule II rule version and records it on the snapshot. When CPCB amends a rate, a new version is published, and last year's filing stays reproducible under the rule it was filed on.
Each client's catalogue and sales sit behind row-level security at the database layer, not just in the interface. Hosted in Supabase's Mumbai region (ap-south-1), so client data never leaves India.
⟶ How it works
01
Their workspace, GSTIN, and EPR roles, in about a minute. Each client sits isolated from the rest of your book, and appears on your portfolio from then on.
02
CSV of SKUs and half-yearly sales, up to 500 SKUs per batch. Greenfile reads it server-side and never sends it anywhere else. Each component lands in PWM Categories I–V with a confidence score.
03
Anything below the confidence threshold waits for you. Confirm it, override the category or material, or reject it. Your determination and your justification are recorded next to the classifier's original call, not on top of it.
04
A client-ready liability report, plus a filing pack pinning the snapshot, rule version, and audit trail. Built to accompany the half-yearly and annual returns you file on the CPCB portal. Every figure cites the snapshot it came from.
⟶ Trust & compliance
Every recompute creates an immutable snapshot. Every classification carries an attestation. The number in your client's return equals the number in your working, pinned to a single row, months after you produced it.
Override a classification and both calls survive: what the model said, and what you determined, with your justification as the stated basis. A superseded classification is never printed as though it justified the final answer.
Row-level security separates every client at the database layer, not just in the interface. Hosted in Supabase's Mumbai region (ap-south-1) for DPDPA residency, and service-role keys never leave the server.
⟶ Pricing
Run 3 clients through Greenfile at no charge, with no card, for as long as you like. That is enough to put real catalogues through it and see the portfolio and the reports on your own work rather than on a demo.
Beyond that, plans are priced by the number of clients on your book. SKUs are unmetered on every tier, so a client with four hundred SKUs costs the same as one with four.
No card, no time limit, no feature gates.
For a full book
Up to 15 clients
₹1,000 per client
Up to 60 clients
₹667 per client
Up to 200 clients
₹450 per client
200+ clients
~₹300 per client
Annual billing. We handle paid plans personally at the moment, so you get an invoice and a payment link rather than a checkout page, and a conversation about whether the tier actually fits your book.
⟶ FAQ
Yes, that is the shape of the product. Your agency sits above your clients: add a client and they appear on your portfolio with their liability, review queue, and filing status. Open any client to work inside their workspace, then return to the portfolio. Each client is isolated by row-level security, so one client's catalogue is never visible from another's.
No, and we would rather be plain about it. Greenfile produces the liability assessment and the filing pack, records the filing and its status, and surfaces the deadlines. You submit on the CPCB centralized portal and log the acknowledgement back in Greenfile. There is no automated portal submission today.
Every component carries a confidence score, and anything below the threshold routes to your review queue instead of being treated as settled. We deliberately do not advertise a single headline accuracy number: ours is measured against a corpus the classifier was tuned on, which is not a promise about your clients' catalogues. The design assumes you are the reviewer, and it records your determination separately from the model's.
Any producer, importer, or brand owner (PIBO) handling more than 2 tonnes of plastic packaging per year. The threshold counts cumulative weight across all packaging categories, not per SKU. Where a client operates in more than one role, obligations split across each role with its own subtotal and filing line.
Rates and targets are versioned by amendment date, and every snapshot records the version it was computed under. A rate change becomes a new version, so a return you produced last year still reproduces under the rule that applied when you filed it.
It is reported as not determinable, listed separately, and never folded into a settled figure or quietly shown as zero. Biodegradable packaging is the live example: its EC rate is deferred under the current ruleset, so the assessment states the exclusion and the count of affected components rather than implying a nil liability.
⟶ The next filing window
Add a client, upload their catalogue, and see the assessment Greenfile produces. Free while we are in early access, no card required.