Batteries, collection & recovery
A battery to handle, along with its specifications, constraints, and take-back terms.
A battery is more than a reference and a pickup address. Its type, condition, documents, and agreed terms affect how it is handled. We have developed the modules below for recycling and second-life projects.
- EWC code
- Condition / diagnostics / ADR
- Packing lists & price offers
Examples from several applications developed for an automotive manufacturer and a battery recycler. The modules are presented together to explain the operations they support.
Identify the battery and record its waste code.
The declaration combines VIN or BIN identifiers with reference characteristics: model, dimensions, and weight. The holder adds condition, charge, state of health, EWC and UN codes, supporting documents, and photos.
What the application does
- The declaration links the battery to its type and holder information.
- The workflow suggests an EWC (European Waste Catalogue) code using the existing declaration or reference battery type.
- The declarant can select or correct the code. It is saved in the record, and any changes can be viewed in the history.
The detail that matters
Prefilled information comes from reference data. It does not replace validation of the waste classification by the responsible stakeholders.
What the team gets
A fully characterized battery record ready for collection, transport, and traceability.
Capture battery condition before collection.
The declarant records the battery’s condition and attaches diagnostics, photos, and a checklist. The interface displays the ADR transport information associated with the selected condition.
What the application does
- The declarant records battery condition and attaches the diagnostic and checklist documents required by the workflow.
- ADR transport information associated with the selected condition is shown in the interface.
- Overview photos are requested, along with a serial-number photo when required based on the declarant and the readability of the identifier.
The detail that matters
Required documents depend on context. Transport and packaging rules are defined with the responsible specialists; the portal does not infer them from a photograph.
What the team gets
A record bringing together declared condition, photos and documents needed to assess handling.
Build a consistent packing list.
The user groups packages from several declarations into a packing list. The application checks collector and destination-site compatibility to prepare a shared shipment.
What the application does
- Users review declarations with their owner, collector, delivery site, chemistry, packaging, and status.
- They select the packages to include in the packing list.
- In the workflow we developed, the selection controls prevent incompatible delivery sites or collectors from being included in the same group.
The detail that matters
This grouping check is an explicit business rule. For your organization, we define the criteria that allow or prevent packages from being shipped together.
What the team gets
A packing list linked to declarations, packaging, palletization and the planned transport.
Separate the treatment price from the logistics cost.
Providers propose separate treatment and logistics prices, with a currency and comment. Each offer is retained with its author, date, and acceptance or rejection.
What the application does
- A proposal includes the treatment price, logistics cost, currency, and an optional comment.
- Each successive proposal is retained with its author, date, and acceptance or rejection status.
- Service providers can also manage proposals through an API. Notifications can inform their systems when a proposal is created or accepted.
The detail that matters
This example covers price negotiations for batteries and pickup groups. A trading arrangement involving multiple purchase and resale contracts would need to be scoped separately.
What the team gets
Proposed and agreed terms remain available with the record, without searching an email chain for the latest agreement.
Connect collection, receipt, and treatment.
The application tracks ready-for-pickup, collected, received, and treated stages. Receipt records the date and operator; Trackdéchets exchanges update the waste tracking form in the relevant workflows.
What the application does
- Statuses distinguish batteries that are ready for pickup, collected, received, or treated.
- In a workflow connected to Trackdéchets, the receipt step records a date and the recipient’s name, then updates the linked waste tracking form and declaration.
- Partners can be notified of status changes to update their own tracking.
The detail that matters
Physical and document tracking are linked but remain distinct. The workflow shows the current stage and any actions still required.
What the team gets
A declaration tracked after departure from the holder’s site, with the associated steps and documents.
FDTI
Show us a real workflow, the people involved, and the tools already in place.
FDTI / Contact
Let's keep it simple.
We only use your contact details to reply: no newsletters, no unsolicited outreach, and no commercial sharing with third parties.