Designed scope
- declaration preparation and status
- corrections and vehicle data
- links to the logistics operation
Planned product · enquiries only
RDCopilot e-Transport
UIT operations explicitly linked to the source delivery.
01 / Workflow
From intent to a verifiable trail
The operator prepares the declaration, follows status, and retains corrections and confirmation beside the logistics record.
Every operation retains company identity, actor, and source linkage.
Acceptance requires tests against the actual authorized version, integration, and data.
02 / Scope
Capabilities and boundaries
Not yet validated
- Contractual e-Transport scope remains to be clarified.
- The full official workflow has not been proven under authorized conditions.
03 / API
Controlled integrations
Connections use authenticated APIs and durable events. Single sign-on does not replace data synchronization, and each service retains its declared authority.
- ANAF
- ERP
- Warehouse
04 / Docs
Public integration notes
Working contract
Commands require an idempotency key, legal company, actor, source, and timestamp. Corrections use linked reversals and never silently rewrite history.
Access and availability
There is no validated application entry yet. The /app route does not redirect until origin, path, license, and release evidence are approved.
Price and inclusions
No price is published. Commercial, tax, refund, and support policies are unapproved; this page supports enquiries only.
05 / FAQ
Factual answers
Is the product available now?
No. Its status is planned and the offer is enquiry-only.
Can I purchase online?
No. There is no approved price or checkout.
What does this page prove?
It describes planned public scope and its boundaries; it does not prove production availability, certification, or acceptance.