Waste holder
Creates the request, describes the batch, selects participants and starts the agreed workflow.
Menu
Operations layer
Qayta Core
Requests, electronic Waste Transfer Notes, approval chains and batch traceability in one record.
- Industrial organisations
- Operators and disposal sites
- Waste carriers
Platform role
One module in an end-to-end process
Qayta Core connects a request, batch, participants, documents and approvals in one timeline. It provides the operational foundation for fleet, device, reporting and enterprise integrations.
Waste transfer data is often split between requests, paper records and operational systems, making the full chain difficult to verify.
Participants
Who does what
Carrier and receiver
Confirm assigned stages and add operational events and supporting records.
Environmental and control teams
Review continuity, discrepancies and change history before the accountable decision.
Capabilities
What the operating layer covers
One request
Records the parties, material, site, carrier and destination before the operation begins.
Approval chain
Supports assigned assurance levels, including qualified signatures where the deployment requires them.
Batch history
Connects documents and events through barcode or RFID identifiers and keeps an audit trail.
Workflow
How the workflow runs
- 01
Create
The waste holder creates a request and records the batch details.
- 02
Transfer
Participants confirm loading, transport and receipt in the assigned sequence.
- 03
Verify
The responsible specialist reviews documents and operational events in one timeline.
Data and control
Inputs, outputs and human control
Inputs
- batch identity and material details
- participants, sites and vehicle
- weighing data and supporting documents
Outputs
- electronic batch record
- transfer and receipt timeline
- reviewable reporting dataset
Controls
- role-based access
- assigned assurance levels
- action and change audit
Integrations
Integration scope made explicit
The label shows the maturity of the public claim. Final scope is always agreed after discovery.
Qualified signatures
Defined per projectSignature services for selected accountable actions are defined by deployment policy.
Barcode and RFID
Configurable capabilityIdentifiers connect the physical batch to its operational record.
ERP and weighbridges
Defined per projectExchange is implemented through Qayta Bridge under an agreed data contract.
Implementation
Boundaries are agreed before the pilot
Discovery defines roles, the WTN workflow, mandatory fields, assurance levels, retention and integrations. The contracted deployment scope remains authoritative.
Expected outcome: One verifiable operational record instead of a chain reconstructed from separate sources.
FAQ
Common questions
Does Core replace every internal system?
No. It governs the end-to-end batch process while enterprise and operational systems connect through agreed interfaces.
Is a digital signature required for every action?
No. Assurance depends on role, risk and the applicable process.
Can we start with one site?
Yes. Pilot boundaries, reference data and participants are agreed during discovery.