Batteries, collection & recovery
A battery to handle, 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 handling. We have developed the modules below across 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 reference data combines model, VIN or BIN, condition, charge, health, dimensions and weight. The declaration completes these characteristics with EWC and UN codes, evidence and photos.
What the application does
- The declaration links the battery to its type and owner information.
- The workflow suggests an EWC code — from the European waste classification — using the existing declaration or reference battery type.
- The declarant can select or correct the code. It is saved in the record and changes are available 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 battery characterized in a record ready for collection, transport and traceability.
Capture battery condition before collection.
A damaged battery requires different preparation from a battery in another condition. Stakeholders need diagnostics and relevant documents before organizing the next steps.
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.
- General photos and, depending on the declaring party and identifier readability, a serial-number photo are requested.
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.
Several declarations and packages may be ready to leave. Selecting them without considering the collector or delivery site can produce a list that does not fit the intended operation.
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 developed workflow, selection prevents mixing delivery sites or collectors incompatible with the current grouping.
The detail that matters
This grouping check is an explicit business rule. For your organization, we define the criteria that permit or prevent a shared departure.
What the team gets
A packing list linked to declarations, packaging, palletization and the planned transport.
Separate processing price from logistics cost.
Negotiation with a provider may cover both battery processing and transport. A single amount does not capture the terms of the agreement.
What the application does
- A proposal includes processing price, logistics price, currency and an optional comment.
- Successive proposals are kept with their author, date and acceptance or refusal status.
- Offer operations are also available to providers through an API. Notifications can inform their system when an offer is created or accepted.
The detail that matters
This example covers price negotiation for batteries and pickup groups. A trading arrangement involving multiple purchase and resale contracts would require specific scoping.
What the team gets
Proposed and agreed terms remain available with the record, without searching an email chain for the latest agreement.
Connect collection, receiving and treatment.
A battery reported as collected must then be received and tracked through treatment. Document status may also condition which actions are available in the tool.
What the application does
- Statuses distinguish batteries ready for pickup, collected, received and processed.
- In a workflow connected to Trackdechets, receiving records a date and receiver’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 stage reached and the actions still required.
What the team gets
A declaration tracked after departure from the owner’s site, with associated steps and documents.
FDTI
Show us a real flow, its participants and the tools already in place.