Free consultation 
This solution is for:
Carriers
Own fleet, SENT-GEO geolocation obligation, passing the reference number to the driver, updating notifications
Freight forwarders and logistics operators
You organise transport, but SENT responsibility does not rest solely with the carrier
Senders and recipients
Your goods fall within the SENT catalogue and you are still handling this manually or not at all
SENT has been in force since 2017. Each successive amendment expands the catalogue of products subject to the notification and tracking obligation. Companies without integration and automation pay twice as much for compliance.
For our client we designed and continuously develop an enterprise-class telematics platform. The system has been running in production for 10 years. It includes a web panel for fleet managers, mobile applications for drivers, an analytics layer based on Machine Learning, and integrations with the government SENT system and the ZF Transics platform. The platform has passed independent security audits and meets GDPR requirements.
Expansion of the SENT catalogue
Penalties — specific and absolute
Missing notification or data discrepancy
46% / min. PLN 20,000
Failure to fulfil the geolocation obligation
PLN 10,000
Goods did not reach the destination
PLN 100,000
Driver without a reference number
PLN 5,000–7,500
Delivery pre-notification to the recipient
- Classifying each shipment: whether it requires SENT, which form, which weight and volume thresholds apply
- Completing the notification in PUESC, tracking the reference number
- Passing the reference number to the driver before departure
- Updating the status after delivery, closing the notification by the recipient
- As the catalogue grows, this volume grows with the regulation, regardless of headcount
This solution is not for every company. Check whether you should be interested.
This is for you if
- You are a carrier transporting goods covered by SENT and the SENT-GEO geolocation obligation falls directly on your fleet
- You are a freight forwarder or logistics operator and you know that an error in the notification on the carrier’s side comes back to you
- You are a sender or recipient of goods covered by SENT and the responsibility for registration rests on your side
- Your current SENT handling process is manual, fragmented, or insufficiently integrated with your TMS or ERP
- Shipment classification depends on the knowledge of specific individuals rather than on system logic
- Each expansion of the SENT catalogue means rewriting procedures and retraining the team
This solution is not right for you if
- Your operations do not involve goods covered by the SENT system and you have no plans to expand them
- You are looking for a ready-made SaaS tool for self-service deployment. We build dedicated solutions tailored to the client’s environment and processes
From simple integration to a full
compliance management system — scope
SENT compliance is not a single problem. It is a sequence of steps that can be fully or partially automated. We offer three levels of solution — each is an entry point or a target scope, depending on the need.
Integration
Entry point
We build a connection between your TMS, ERP, or WMS and the SENT register via the PUESC platform. The system pulls data from the source operational systems — sender, recipient, carrier, goods, route data — generates the notification in the required XML format, and submits it through the official PUESC channel. Once acceptance is confirmed, it returns the reference number to the source system and passes it to the driver.
We handle the full spectrum of SENT forms: domestic, intra-Community acquisition, intra-Community supply, transit, import, and export, depending on the nature of the operation and the direction of transport.
- Elimination of manual data re-entry into PUESC and the risk of human error on input
Automation
Classification and lifecycle
The system classifies shipments automatically. Based on goods data — CN code, weight, volume — and the nature of the operation, it determines whether the shipment requires a SENT notification and which form applies. It does not wait for the dispatcher’s decision; it acts at the moment the order is registered.
It handles the full notification lifecycle: registration, status updates, deadline monitoring, and closure after confirmed delivery. It supports SENT-GEO handling — geolocation of the means of transport via ZSL/OBU — without requiring the driver to manually activate any application.
- Automatic classification, without involving the dispatcher on every order
Compliance management system
Full autonomy
The system monitors operational events — order receipt, loading, departure, delivery, receipt confirmation — and responds autonomously. It generates the notification, updates the status, and closes after receipt. Only exceptions reach a human: missing or inconsistent data, events requiring a decision, emergency situations.
The system monitors changes in the SENT goods catalogue and flags their impact on operational processes, before the company learns about a new regulation from an inspection.
- Full operational autonomy — humans intervene only on exceptions
Important note:
The scope of implementation is defined after an environment audit. We can start at level 1 and build up, or design a complete system from the outset. The decision depends on your environment, volume, and the scale of your SENT obligations.
What changes when SENT handling no longer depends on human memory and manual re-entry
Elimination of regulatory risk
The system does not forget, does not skip, and does not confuse CN codes. Every shipment is classified against the current catalogue. Every notification is validated before submission — if data is incomplete, the system flags the issue. A penalty for a missing notification does not arise from an oversight.
Reduction of manual work on notifications
Shipment classification, form selection, data entry, submission to PUESC, reference number tracking, status updates, closure after receipt — the system carries out this sequence without human involvement. Only what genuinely requires a decision reaches a person.
Scalability without proportional headcount growth
More shipments covered by SENT does not mean more people handling PUESC. The goods catalogue expands, volume grows — the system scales without additional operational effort.
Readiness for future regulatory changes
New goods in the CN catalogue mean a configuration change, not a process rebuild. The company does not start from scratch after each amendment — the system adapts to the new scope of obligations without requiring the team to rewrite procedures.
Auditability and control
A complete history of reference numbers and system actions is available in one place — for internal governance, for the client, and for KAS inspections.
We have built systems that communicate with SENT in a production environment
Ecologic.io
Fleet management platform — Europe, Asia, North America
Ecologic.io is a fleet management platform serving clients such as Unilever, PKO Leasing, and Philip Morris across Europe, Asia, and North America. The system processes telemetry data from hundreds of thousands of vehicles in real time and has maintained 99% SLA over a decade of operation in a production environment.
Within this platform we designed and repeatedly deployed the SENT integration as a component of the fleet monitoring architecture. The system handles real-time geolocation data transmission, validation and synchronisation of data from OBD2 devices, and communication with the PUESC platform at enterprise scale — in an environment where a delay or data error has direct operational and regulatory consequences.
This is not familiarity with SENT from documentation. It is years of experience building systems that work with this register in production.
SENT Integration
SENT-GEO / ZSL
PUESC / SOAP XML
Real-time telemetry
Enterprise scale
99%
SLA over a decade in production
50–70%
types of road events analysed
in real time
3H
Unilever, PKO Leasing, Philip Morris
PUESC architecture
SOAP/XML, SENT specification, forms SENT100, SENT105, and derivatives for all directions of operation
SENT-GEO
Integration with ZSL/OBU, location data transmission compliant with KAS specification
TMS/ERP integrations
Experience with enterprise-class systems in a TSL environment
Full notification lifecycle
From goods classification, through registration and geolocation, to status update and closure by the recipient
Questions that typically arise before deciding to get in touch
I already have a SENT module in my TMS. Why would I need anything more?
Most SENT modules in TMS systems handle one form for one direction of operation — typically domestic. They do not automatically classify shipments based on CN code and weight. They do not handle the full lifecycle: status updates, ZSL/OBU geolocation, closure of the notification by the recipient. They do not respond to changes in the goods catalogue. We can fill the gaps in the existing environment without replacing the system.
What if my TMS or ERP has no API?
We assess available integration points as part of the environment audit. If a native API does not exist, we work with available export interfaces or build an intermediary layer. This is part of the diagnosis before the project, not a surprise during delivery.
What if SENT regulations change after deployment?
Changes to the CN goods catalogue mean a system configuration change, not a new deployment. We design the architecture with the assumption that the regulation will change — because it has been changing since 2017 and there is nothing to suggest that will stop.
What if the system submits an incorrect notification to PUESC?
Data validation before submission is part of the architecture, not an option. The system does not generate a notification with inconsistent, incomplete, or contradictory data — it flags the issue and escalates to a human for verification. Submission occurs after confirmation.
Do you handle transit through Poland and WNT/WDT operations?
Yes. We handle the full spectrum of operations covered by SENT: domestic transport, intra-Community acquisition, intra-Community supply, transit, import, and export. Form selection is part of the classification logic.
Is our operational data secure?
The integration model, the scope of data transmitted via API, and the data retention policy are defined at the architecture design stage during the discovery workshop. Security is part of the specification, not a matter to be resolved after deployment.
From the first conversation to a working system — five stages, none of the necessary ones skipped
We do not sell off-the-shelf tools.
We build solutions tailored to your environment, systems, and the scale of your SENT obligations.
Consultation and budget estimate
Free of charge
We discuss your environment, processes, and systems. We present an architecture recommendation and indicative budget range. At this stage intentionally indicative — a precise assessment comes after the workshop.
Discovery workshop
Paid
We map processes, define logic and business rules, design the architecture, and record acceptance criteria. It concludes with a full system specification and a precise production quote. The decision to continue is yours.
Production and testing
We build the system according to the workshop specification. We test against agreed criteria, including edge cases and exceptions.
Production deployment
We launch the system and calibrate the model on live traffic. The first automation metrics appear here.
Maintenance
We monitor, optimise, and expand the scope. The model grows with the data. Maintenance terms are agreed before launch.
What happens after you get in touch
1
We reply with a proposed meeting time
Not an automated response — a person who will handle your project.
2
Call — 45–60 minutes
We ask about your systems, goods covered by SENT, your current notification process, and the areas where you see the greatest risk. You are welcome to bring a technical person or someone responsible for compliance and contact with KAS.
3
Proposed approach and budget range
A concrete architecture recommendation and indicative budget range — before you sign anything.
Decision point
If the scope and budget make sense, we move to the discovery workshop. If not, you leave the conversation with substantial knowledge and no obligations.
Questions we get
most often
Do you handle SENT-GEO and integration with ZSL/OBU?
Yes. Handling geolocation of the means of transport via the External Location System is within the scope we can deliver — both as part of a full system and as a standalone module complementing an existing integration. The specific model is defined after an environment audit.
How does the system handle changes to the PUESC technical specification?
PUESC updates its XML specification with every significant regulatory amendment, as happened with SENT 2.0 and 3.0. Adapting the system to a new specification is part of the maintenance scope. It is not a new project or an additional cost outside the maintenance agreement.
How does the driver receive the reference number?
The reference number generated by PUESC upon acceptance of the notification is automatically passed to the operational system and — depending on the agreed model — to the driver’s mobile application, an SMS message, or a document printed by the dispatcher. The handover model is defined at the workshop stage.
What about transports through Poland carried out by foreign carriers?
From 1 January 2025, the SENT notification obligation also applies to carriers from EU, EFTA, and Switzerland countries carrying out transports to or from third countries through Polish territory. If you are organising such transports as a freight forwarder or sender, it is your responsibility to ensure that the notification exists. The system can handle this scenario on the transport organiser’s side.
How quickly can a basic PUESC integration be deployed?
The timeline depends primarily on the integration readiness of your systems and the availability of an API on the TMS or ERP side. For environments with a ready API, the time from workshop to launch of a basic integration is typically four to eight weeks. A precise assessment requires an environment audit.
Do we need to involve our IT department?
Yes, at the workshop and integration stage — for system access, API configuration, and the test environment. We do not involve IT in the day-to-day operation of the system after launch. This is one of the points we cover during the initial consultation.
What if we have multiple TMS or ERP systems across different entities?
This is a common scenario in corporate groups and logistics operators serving multiple entities. We handle multi-system integrations — a single SENT notification can aggregate data from different sources. The integration scope is defined at the workshop stage.
How we build — a few principles that determine the quality of an implementation
Official communication channel with PUESC
Integration is carried out through the PUESC webservice channel — SOAP/XML, AcceptDocument method, in accordance with the KAS specification. We do not use workarounds or scrape the user interface.
Validation before submission, not after
The system verifies the completeness and consistency of data before submitting the notification to the register. An incorrect notification is harder to correct than an unsubmitted one — and can result in a penalty for data discrepancy.
Architecture built for changing regulations
The SENT goods catalogue is parameterised — new CN codes mean a configuration change,
not a code modification. The system is designed with the assumption that the regulation will evolve.
Full auditability of operations
Every system action — shipment classification, notification submission, status update, exception escalation — is logged with a timestamp and available for review. For KAS inspections and for internal governance.
Geolocation compliant with ZSL/OBU specification
SENT-GEO handling is delivered through an External Location System in accordance with KAS technical requirements — not through a mobile application dependent on driver behaviour and network coverage.
Escalation instead of silence
If the system cannot process a shipment automatically — missing data, inconsistency between systems, unidentified CN code — it does not skip it or submit an incomplete notification. It escalates to a human with the full event context.
You do not yet know whether your environment requires integration, partial, or full automation.
Neither do we — until we talk.
The initial consultation is free. We ask about your systems, volume, and current SENT process. We assess where the gaps are and what makes sense in your environment.
If the project makes sense, we propose a scope. If it does not, you hear that from us, not after signing a contract.
We reply within 24 business hours.
The first conversation is a diagnosis, not a product presentation.