Corrections and exceptions
A carriage does not always go to plan: the vehicle changes, the consignee refuses to accept the cargo, an error is found in the note. All of this is handled right inside the note — there is no paper document to rewrite.
The system shows the available actions itself: the ETrN block only displays the buttons that make sense at the current step.
An error in an already signed note
While the note is a draft, the data can be edited freely. After signing it cannot be changed: it has gone into the signed document. Instead of editing, a correction is drawn up — a new revision of the title.
Five titles can be corrected, and each has its own action:
| Action | What it corrects |
|---|---|
| Correct the note (T1) | the parties' details, the cargo, the addresses |
| Correct the acceptance (T3) | the details recorded when the cargo was received |
| Correct the price (T5) | the amount for the carriage |
| Correct the redirection (T7) | the consignee, the unloading address, the grounds |
| Correct the relay amendment (T8) | the driver, the vehicle, the reason for the replacement |
The carrier's titles T2 and T4 and the agreement with the price T6 are not corrected separately — they are re-signed once the paired title has been corrected.
Some of the note's data is unchangeable under Russian law. If a field is one of those, the system will say so and suggest the right way forward — usually reissuing the note.
After a title is corrected, the parties that signed after it need to re-sign their titles: they had confirmed the previous revision. The system will prompt you as to what has to be re-signed and by whom.
Replacing the driver or the vehicle
If the driver or the vehicle has changed within the same carrier, a relay amendment is drawn up — the "Заменить водителя или машину" (Replace the driver or the vehicle) action (title T8). The note stays in force and does not have to be redrawn.
The cargo is carried by a different carrier
This is not a relay amendment but a change of carrier, and a single note will not cover it: the carrier is a party to the signed document and cannot be replaced within the same note.
The order is as follows: the current carrier closes this note on their side, and a new note is issued for the second carrier. The system guides you step by step and only shows the action that is appropriate at the moment.
If you simply change the carrier in the record, the note will stop matching the signed original. A relay amendment (T8) is not suitable for this either: it changes the driver and the vehicle, but not the organisation.
Redirection
If the cargo has to be taken to a different consignee or to a different address, a redirection is drawn up (title T7). It is signed by the carrier.
An ordinary redirection is drawn up after the carrier has accepted the cargo (T2) and before the consignee confirms receipt (T3). After T3, redirection remains available only if the consignee refused to accept the cargo or accepted it only in part — in which case the system offers it itself.
The absolute boundary in any case is the signing of the price (T5). After that the state system will reject the changes, and the buttons will disappear.
T7 changes the consignee and the unloading address — and nothing else. New cargo pieces cannot be added to the note by redirection: for additional cargo a separate note is issued.
If the other party refused to sign
A refusal to sign is not the same as a refusal to accept the cargo, and the consequences differ.
A refusal to accept the cargo is handled in LogiFlow: the consignee has the "Отказаться принять груз" (Refuse to accept the cargo) action. The note then stays in progress and moves on to redirection — the cargo is taken to a different consignee or returned to the consignor.
A refusal to sign a title is made by the participant in their own system. Such a refusal ends the document flow: the note is closed, and a new one is issued for the carriage. There is no separate "refuse to sign" button in LogiFlow — if you need to stop the process, use the cargo actions above.
If the other party is silent and the note is not moving, it can be moved to the archive so that it does not clutter the working list. The archive opens on the "Список ЭТрН" (ETrN list) tab in the settings, and a note can be brought back from there as well.
The consignee refused to accept the cargo
There are several options, and each has its own action:
- Hand over to a different consignee — the cargo travels to a new address.
- Return the cargo to the consignor — the cargo goes back.
- Deliver the remainder to the consignor — if part of the cargo was accepted and part was not.
Not all of the cargo was accepted
Partial acceptance is recorded when receipt is confirmed: you specify what has been accepted. The usual acceptance and delivery titles are signed for the accepted part, and the remainder is handled as above — returned to the consignor or taken to a different consignee.
The cargo was refused by mistake
The refusal of acceptance has been signed, but the cargo does need to be accepted after all. This does not kill the note: the carrier draws up a redirection to the same consignee and the same address, after which acceptance is signed again, correctly this time.
If that does not work out, the remaining option is to issue a new note for the leg — see below.
The note has to be drawn up anew
If a correction will not solve the problem, a new note is issued for the leg. The previous one stays in the history: it has already been in the state system and cannot be deleted.
This is done in two steps, right from the carriage record:
- Open the state of the note and click "Архивировать" (Archive) — the document flow for it is closed.
- A "Создать ЭТрН" (Create ETrN) button will appear in the ETrN block at the leg. The new note will be assembled from the leg's current data.
In the service section of the settings a note can be reissued with a single button — it archives the previous one and immediately creates a new one. This option is available only to the platform administrator, but the result is the same as with the two steps above.
Frequently asked questions
The document is stuck — the other party is not signing. Check whose turn it is in the ETrN block. If the driver is being waited for, make sure the phone number is correct. If a counterparty is being waited for, you need to get in touch with them: they sign at their end, from their own system.
The note went to the archive, but it is needed in progress. Bring it back from the archive on the "Список ЭТрН" (ETrN list) tab in the settings.
No action buttons are visible. Actions are not available to every role and not at every step. If there are no buttons, either it is the other party's move right now, or your role does not have the rights for that action.
The status in the system does not match what was expected. The state comes from the operator and is updated with a slight delay. If the discrepancy persists, contact your administrator.