Platform
This is what it looks like inside
Log a collection, issue the manifest and produce the certificate — right here. Then see how it connects to what you already run.
How to read it
Log a collection and follow it to the report
Start on Collection: log an entry and it appears with a folio. Go to Transfers and issue the manifest: the collection is now tied to a destination. Confirm receipt and go back to Report — the documented percentage went up. That is the whole journey, and it is everything you need when you are asked to account for your waste.
What it produces
From a report to a figure somebody can use
Everything that enters the system stays linked to what came before. That is the whole route, and it is what separates a map from traceability.
Today the beta covers the first two steps: the Social Sector report and its validation. The rest opens up as municipalities and companies come in — the data architecture is already built to carry it.
What the system measures
Fields, not figures. None of these counters is published yet: there is no operation to count and we do not put up numbers without backing. When there is, they come out through the public counter above, which queries the live API.
From the Social Sector
From the Public Sector
From the Private Sector
The public counter
Your tonnage, on your own site
A municipality that wants to show progress, or a processor who needs to be believed, drops a counter on their site and shows their confirmed tonnage. ELTrack verifies it, not they themselves. Below is a sample of how it looks.
Example · how it looks
1,240Tonnes on the recordVerified by ELTrackSample figure. On your site the counter pulls your real tonnage from the API, and stops pulling it if your account is not in good standing.
Two lines. That is all.
<div data-eltrack-widget data-key="elt_pub_…"></div> <script src="https://eltrack.mx/api/v1/widget/js" async></script>
The counter queries the API every time somebody opens the page. If the account lapses it stops returning figures and says so instead of showing a stale number. And it only answers from the domains the customer registered, so nobody can copy the key out of the page source and use it on their own site.
There is an API underneath
If your weighbridge can make a request, it can already talk to ELTrack
The collection site’s weighbridge sends the weight on its own. The municipal ERP pulls its folios without opening the site. The processor confirms delivery from their own system. Without an API this is a form someone types into; with an API it is infrastructure.
The full documentation lives in your account
Endpoints, Python and JavaScript examples, key issuing and domain registration. If you are already a customer, sign in. If not, write to us.
Sign in Join the networkOther ways to keep track
ELTrack compared with Excel, an in-house system or an ERP
All three work for keeping your own numbers. What they cannot do is prove them to a third party.
| Excel or paper | In-house system or ERP | ELTrack | |
|---|---|---|---|
| Can a third party verify a folio? | No: it is your file | No: it is your database | Yes, at eltrack.mx/verificar, without revealing the parties |
| Who confirms the tyres arrived? | You | You | The destination, with its receipt acknowledgement |
| Mass balance (in, out, loss) | By hand | If you program it | Automatic, on every certificate |
| How long to get started | Today | Months of development and set-up | The same day, from a phone |
| What it costs | Hours of whoever types it in | Your own development and upkeep | MXN $25 per registered tonne, no minimum |
| Your data | Yours | Yours | Yours: export it all as CSV whenever you like |
ELTrack does not replace your ERP: it connects through the API so your system stays yours and a third party issues the proof.
Shall we run it with your own numbers?
Half an hour, with your volume and your profile. No commitment.
Request a demo