A recycling processor in Maharashtra collected, sorted, and granulated 80 tonnes of plastic waste over the quarter. The weight was real. The processing happened. The EPR certificates should have been straightforward. But when the application went to the CPCB portal, a portion of it came back flagged for verification, because the inward collection records did not match the batch processing logs, and two consignments had aggregator details that could not be cross-referenced.
Three weeks later, after document requests and clarifications, most of it resolved. But the certificates were delayed, one producer's deadline was missed, and the relationship cost more to repair than the documentation gap would have cost to prevent.
This is not unusual. It is the most common operational problem facing registered EPR recyclers in India right now, and it is entirely preventable.
What the CPCB portal actually requires
The EPR portal for plastic waste, e-waste, and battery waste operates on a chain-of-custody principle. For a certificate to be valid and audit-defensible, the recycler must be able to demonstrate:
- The source and quantity of every inward consignment, with aggregator or collection agent details
- That inward material was processed within the facility, with input weight, process type, and output weight recorded per batch
- That the processed output weight reconciles with the certificate claim, accounting for processing losses, rejections, and material that was not certificate-eligible
- That the material category on the inward record matches the certificate category (MLP vs rigid plastic vs e-waste, etc.)
None of this is theoretically difficult. It is exactly what a well-run processing plant should be recording anyway. The problem is that most recycling operations are tracking this in disconnected systems: inward weights in a gate register, processing in a manual batch log, outputs in a separate Excel sheet, and the linkage between them existing only in someone's memory.
The five documentation failures that delay or void certificates
The gate register shows 4.2 MT arrived on March 14 from aggregator X. The batch processing log shows 4.1 MT was processed on March 15 and 16. But there is no explicit link between the two records, different numbering systems, different formats, recorded by different people. When the auditor asks you to show that the March 14 consignment became the March 15 batch, you cannot prove it.
The CPCB requires that the collection source be traceable. Aggregators and collection agents need to be registered and their details recorded against each consignment. In practice, many recyclers work with informal aggregators who are not registered, or whose details are incomplete. Every such consignment is a liability in an audit.
No recycling process has 100% yield. You receive 10 MT of plastic waste and produce 6.8 MT of granules, the rest is contamination, moisture loss, rejection material, and processing waste. If your certificate claims 6.8 MT but your inward records show 10 MT, an auditor who does not see documented yield losses will question the reconciliation. Processing losses need to be logged by batch, with a reason code.
A consignment arrives labelled as rigid plastic. During sorting, a significant portion turns out to be MLP (multi-layered plastic), which has different certificate eligibility. If the inward record stays as "rigid plastic" and the processing output goes into the MLP certificate, the categories do not match. This is a common reason for certificate queries on the CPCB portal.
The quarterly certificate submission is approaching and the batch logs for weeks 4 through 7 were never properly completed. Someone fills them in from memory or from the gate register. Auditors increasingly cross-reference timestamps, and records that were clearly created in a batch shortly before submission raise flags even when the underlying processing was legitimate.
What a documentation system that works looks like
The fix is not more paperwork. It is structured digital recording that links inward consignments to processing batches to output weights in a single, timestamped record, created at the time of the event, not reconstructed later.
When a consignment arrives at the gate, a work order is created for it immediately, recording aggregator name and registration, weight, material category, and date. This work order becomes the root record that everything else traces back to. The consignment has a unique identifier that follows it through sorting, processing, and output.
When processing begins on a batch, the processing work order references the inward consignment work order IDs that make up the batch. Input weight, process type, operator, and start time are recorded at the beginning. Completion records the output weight and any documented yield loss with reason codes. The chain is unbroken and timestamped.
At the end of each certificate period, the system generates a report showing total inward weight by category, total processed weight, total yield loss with documented reasons, and net certificate-eligible output. This is the reconciliation document that satisfies the CPCB's traceability requirement, and it generates automatically from the work order records, not from a manual compilation exercise.
The recycler with an unbroken digital record from inward consignment to certificate claim does not just survive audits, they process them faster than competitors and build the credibility that leads to preferred recycler status with large producers.
The competitive advantage of clean records
As EPR enforcement tightens and producers become more careful about which recyclers they work with, documentation quality is becoming a commercial differentiator. Producers who have faced scrutiny on their own EPR submissions are increasingly selecting recyclers who can provide clean, detailed processing records, not just a certificate number.
The recycler who can deliver a full processing record alongside each certificate, showing source, batch, processing date, yield, and output weight, commands a stronger market position than the one who can only provide the final number. The documentation infrastructure that protects you from audits is the same infrastructure that wins you better contracts.
Build an unbroken record from inward consignment to EPR certificate
RakuOps lets you link inward consignments, processing batches, and output weights in a single timestamped work order trail, so your certificate submissions are always audit-ready.
Start Free Trial