Requests

A request in LogiFlow is a client's order to transport cargo: "we need to take this cargo from this sender to this receiver at this tariff." A request specifies the client, the cargo, the route (sender/receiver/addresses), the carrier and the tariff. The trip itself (the specific vehicle, departure dates and so on) is a separate entity — the shipment — that the request can be attached to.

A request and a shipment are different entities

A request answers the question "what, for whom, from where to where and at what price are we carrying." A shipment is already "which trip carries the cargo and when." They live separately: a request can be created and kept without any link to a shipment (for example, while it is unknown when and by which vehicle the cargo will travel) and attached later. A single shipment can gather many requests (a one-to-many relationship).

How requests and shipments are related

• A request can exist without a shipment — that is a normal state. Attaching one is optional.
• One request is at any moment attached to no more than one shipment.
• One shipment can have many requests attached — this is a consolidated (groupage) transportation, when the cargo of several clients travels in one vehicle.
• The typical process: accumulate requests → decide which shipments they will travel on → attach them. Sometimes the shipment is known right when the request is created — then the link is set in the form.
• If a shipment is deleted, the attached requests are not deleted — their link is simply cleared.

"Shipment type" belongs to the shipment

The mode of transport (road, rail, air, sea, multimodal) is set at the shipment level, not on the request. On the request you describe the cargo, the route, the carrier and the tariff; what exactly carries it is decided when the shipment is formed. See Shipments.

When to create a request

• A client called or wrote and asked to arrange transportation.
• An enquiry arrived via the website or e-mail and needs to be recorded.
• An internal transportation between your own company's warehouses.
• The client created the request themselves in the client portal (the "Client" role can create requests for itself — see the section on roles).

Creating a request: a 4-step wizard

Creating a request is arranged as a step-by-step wizard. Click "Add request" in the Requests section and go through the 4 steps.

The only mandatory field is Client

In the whole wizard only the Client field is mandatory (marked with an asterisk). All other fields are optional — you can create a request filling in the client alone and add the details later in edit mode.

Step 1. General

• Client * (mandatory) — pick one from the list or create a new one right from the form.
• Manager — the responsible employee (assigning a manager triggers a notification).
• Attach to shipment — "Not attached" by default. You can pick an existing shipment right away or leave the request unattached. This item is hidden for the "Client" role.
• Description — free text about the request.
• Comment — an internal comment.

Creating a client quickly

If the client is not in the system yet, click "Create client/counterparty" right in the form — the new counterparty is immediately filled into the "Client" field. The logistics parties (sender/receiver/carrier) on step 2 can also be created on the fly.

The "We are the freight forwarder" checkbox

If your company does not carry the cargo itself but organises the carriage under a forwarding contract, the same step has a "We are the freight forwarder" checkbox. It changes three things: the "Client" field is renamed to "Customer", fields for the number and date of the forwarding contract appear, and a "Customer" block is added to the electronic consignment note.

The checkbox is shown only when the Kontur.Logistics integration is connected (or the flag was already set on the request): without a consignment note it does nothing. It is not available to the client or the warehouse worker. After the T1 title is signed, the flag and the contract details are frozen — changing them requires reissuing the note. See Working as a freight forwarder.

Step 2. Cargo

Cargo parameters:

• Warehouse number — the internal number at the warehouse.
• Number of packages.
• Weight (kg) and Volume (m³) — declared values.
• Actual weight (kg) and Actual volume (m³) — actual values. Hidden for the "Client" role.
• Tariff — the rate for transportation: picked from the tariff directory. A tariff has a rate, a currency, a unit of measurement and a service, so the system calculates the cost from it and builds a bill line. The first item of the list is "No tariff". Hidden for the "Warehouse worker" role; the client sees the tariff but does not assign it.

The "Logistics details" block (route and carrier of the request):

• Sender — who hands over the cargo (a client, a counterparty, your legal entity, or manual input).
• Sender address — the sender's address; next to it is a button for picking an address/geopoint (it can be taken from the address book or from the party's requisites).
• Receiver — who accepts the cargo.
• Receiver address — the receiver's address, also with an address/geopoint picker button.
• Carrier — who carries the cargo (a counterparty, your legal entity, or manual input).

Where the route, the carrier and the tariff are stored

The tariff is stored right in the request — as a reference to the directory plus a "snapshot" of its terms (rate, currency, unit, "per quantity", volumetric weight and the date it was applied). Thanks to the snapshot, later edits in the directory do not change requests that have already been accepted — see Tariff terms snapshot. The route (sender, receiver, addresses) and the carrier are stored in the request's transportation leg — a separate route record that is created together with the request if you filled in these fields. At the user level you can think of them as the "logistics details of the request".

In a request the leg is created without transport fields (no driver and no vehicle number) — the specific vehicle and driver appear at the shipment level. More about legs — Multimodal transportation.

The address is mandatory once a party is specified

If you have selected a sender, you must also specify the sender address; the same goes for the receiver. This is checked on saving.

Step 3. Files

• Drag files into the "Drop files here" area or click to select several files at once.
• You can create a folder and put files into it.
• The "Clear" button removes the selected files from the form (before saving).
• The hint in the wizard lists the formats PDF, DOC, DOCX, XLS, XLSX, JPG, JPEG, PNG, TXT and a maximum size of 50 MB per file; up to 50 files can be prepared at a time.

Formats in the wizard and in the record card

The caption in the wizard lists the main formats. In general the LogiFlow file storage supports a wider list of types and has its own limits per category — the full rules, formats, restrictions and role-based access are described in Files in logistics.

Step 4. Summary

Before saving, the wizard shows a summary:

• General information — status ("New request" by default), client, manager, description, comment.
• Cargo — number of packages, weight, volume, tariff.
• Files — how many files have been uploaded.
• Logistics details — sender, sender address, receiver, receiver address, carrier.

Check the data and click Create. The request is automatically assigned a number (sequential within the company).

The starting status

On creation the request is given a starting status — usually "New request". The system does not substitute the "default" status automatically in arbitrary cases; the exception is copying a request: the copy always gets the status marked as "default" in the directory.

What is stored in a request (in brief)

Directly in the request: the client (mandatory), the number (automatic), the status, the manager, the description, the comment, the warehouse number, the number of packages, the declared and actual weight/volume, the tariff and the snapshot of its terms, the link to a shipment, custom fields (if configured by the administrator — see Custom fields), the creation date (automatic).

The route and the carrier are stored in the transportation leg linked to the request (entered in the "Logistics details" block). In addition, a request can have cargo packages with photos — a breakdown by items; the client sees packages and photos only for their own requests.

The creation date is set by the system

The creation date is set automatically when the request is drawn up and is not edited manually — it is a mark of when the record appeared in the system, not a delivery deadline. The request number is also assigned automatically (sequential within the company). Delivery deadlines are stored on the linked shipment: the planned and the actual delivery dates — see Shipments.

Request statuses

Statuses are configured to match your company's process. The standard installation creates 6 statuses:

Order	Name	Default	Final
1	New request	✅
2	Expected at the warehouse
3	Being formed
4	In progress
5	Ready for pick-up
6	Issued		✅

Every status has the Default and Final flags, an Order field and a Standard time (h) field used to track delays in analytics. For details on configuration see the Statuses section.

The status is changed manually in the request card. There are no hard restrictions on transitions — you can move to any status and in any direction; the logic of the transitions is a matter of discipline, not of the system. Every change is recorded in the history (the history tab of the card): the new status, who set it and when.

Transition into a final status

When a request moves into a status with the "Final" flag, the system automatically sets the end date of the last transportation leg (if it is empty) to the current date. This is needed for a correct time calculation in analytics.

The key principle: declared values versus actual ones

A request has two pairs of values for weight and volume — this is not duplication but a reflection of the real transportation process:

• Declared (Weight, Volume, Number of packages) are the planned values that the manager enters at request creation from the client's words. They state what is expected to be transported.
• Actual (Actual weight, Actual volume) are the real values recorded by the warehouse at cargo acceptance.

Why actual values are needed

The typical work cycle:

1. The manager creates the request with the declared weight/volume/packages (from the client's words).
2. The cargo arrives at the warehouse. At acceptance the warehouse worker enters the packages — for every real cargo package they specify the dimensions and the weight and, if needed, take photos. This serves as acceptance control, real measurement and storage of cargo photos and descriptions.
3. The actual weight and volume of the request are obtained as the sum over the packages (or entered manually). Any "declared vs actual" discrepancy is immediately visible.

This is how LogiFlow combines the client's expectations with the real measurements at the warehouse — the basis for accurate accounting and calculations.

There are two ways to fill in the actual values:

• Automatically from the packages — the "Update actual values" button on the "Package details" tab sums up the weight and volume of all packages and writes them into the request's Actual weight and Actual volume (see below).
• Manually — in the request edit mode or when changing the status (the Actual weight / Actual volume fields).

Request tariff

The "Tariff" field is the rate at which the cargo was accepted. It is filled in by picking from the tariff directory (the "Cargo" step of the wizard or the "General" block in the request card).

What happens when a tariff is selected

The system freezes the tariff terms in the request itself: the rate, the currency, the unit of measurement (weight or volume), "per quantity", the volumetric weight setting and the date it was applied. That is why the card shows not only the name but also a line of terms:

Tariff: Air Istanbul 3.50 EUR / 1 kg, volumetric weight 150 kg/m³ Tariff applied 10.08.2026

Why the terms are "frozen"

The price list changes, but the requests already accepted do not. If tomorrow the rate in the directory goes up, the requests accepted at the old rate keep it, and bills for them are calculated using it too. This protects the price history from being rewritten retroactively.

To recalculate the request at the new terms, select the tariff again (it can be the same one) — the snapshot is refreshed together with the date it was applied. For details see Tariff terms snapshot.

What the tariff gives you further on

• In the Shipment calculation section you can estimate the cost for any request and any tariff.
• In a bill, the "Add from tariff" button appears and calculates the quantity, the price and the line amount by itself — see A bill line from a tariff.
• In print templates the variables {{request.rate}} (terms in one line), {{request.tariff_name}}, {{request.tariff_rate}}, {{request.tariff_currency}}, {{request.tariff_unit}} are available.

Who sees the tariff

• Administrator, head, manager — see it and select it.
• Client — sees the tariff on their own requests: both in the "Tariff" column of the list and in the view card (name, terms from the snapshot, date applied). The client cannot change the tariff — the field is read-only for them. The tariff directory is only partly open to them: public tariffs plus those set on their own requests. The client still does not see the company's whole price list.
• Warehouse worker — does not see the tariff anywhere: not in the card, not in the table column, not in the export, not in print forms (there the tariff variables are substituted as empty).

The tariff is only set manually

The system never fills the tariff into a request by itself — neither at creation nor retroactively. Until a tariff is selected, the card shows "No tariff", and calculating from such a request in a bill is unavailable.

Viewing a request in detail

Clicking a row in the list opens the "View request #N" card. At the top there is the badge of the current status, the pencil button (Edit) and the close control; at the bottom there are the "Print" button (print forms — see Print templates) and "Close". Editing can also be invoked from the context menu (right-click on a request → Edit).

The card is split into three tabs.

The "Information" tab

• General: warehouse number, client, manager, creation date, number of packages, weight (kg), volume (m³), actual weight (kg), actual volume (m³), tariff (name, terms from the snapshot and the date applied — see Request tariff).
• Information: the comment and the description.
• Shipment: if the request is not attached — "Not attached to a shipment"; otherwise the shipment number is shown.
• Logistics: if there is no leg — "No logistics data"; otherwise the route (sender, receiver, addresses) and the carrier.

In edit mode (the pencil button) these fields can be changed and saved with the "Save" button. In particular, "Warehouse number" is exactly the request's warehouse number (the same "Warehouse number" column in the table): it is entered and changed manually here, in the "General" block (unlike the creation date and the request number, which are set by the system).

The "Files" tab

The request documents laid out in folders. For details see Files in logistics.

The "Package details" tab

Management of the request's real cargo packages — see the next section.

Package details and cargo photos

The "Package details" tab is the warehouse's tool for recording the real cargo.

At the top there are the "+ Add package" and "Update actual values" buttons plus a summary: Total packages, Total weight (kg), Total volume (m³).

Every package in the list shows:

• Package — the number and the name (for example, "#1 — 1 pallet").
• Parameters — the dimensions (L×W×H in cm), the calculated volume (m³) and the weight (kg).
• Photos / Actions — the counter of attached photos and the actions: add a photo, edit the package, delete the package.

Adding a package

The "+ Add package" button opens a form:

• Package number — the sequence number (unique within the request).
• Package name — for example "pallet", "box No. 3".
• Dimensions (cm): Length, Width, Height.
• Weight (kg).

Click "Create". The volume of the package is calculated automatically from the dimensions (L×W×H), converted to m³ and is not entered by hand.

Restrictions on packages

• Dimensions are positive numbers from 1 to 1000 cm for each side.
• The package weight is a positive number (up to 100,000 kg).
• The package number is unique within a single request.

Package photos

Photos can be attached to every package (photos taken at acceptance/measurement). Several photos can be uploaded at once; the first one automatically becomes the "primary" one. Photos go through the protected storage, so the general rules for images apply — the supported image formats and the image size limit (see Files in logistics). The photo counter is shown in the package row.

Recalculating the actual values

The "Update actual values" button takes the sum of the weights and the sum of the volumes of all packages and writes them into the request as Actual weight and Actual volume. Example: 2 packages with a total weight of 270 kg and a total volume of 2.688 m³ — after the click, the "Information" card will show Actual weight = 270 and Actual volume = 2.688.

The button is available to the warehouse worker too

Entering packages, measuring them, uploading photos and clicking "Update actual values" is also available to the warehouse worker — this is their acceptance tool, and the actual weight and volume are among the request fields the warehouse is allowed to write. The button is hidden only from the client: the declared values are theirs, the actual ones belong to the warehouse.

The second path remains available: the actual weight and volume can be set in the "Change status" window together with the status. This is convenient when the request is being moved into the next status upon acceptance anyway.

Warehouse worker: edit mode opens, but not everything is saved

A warehouse worker can enter the request edit mode, however the server accepts from them only the comment, the actual weight and the actual volume. All other changes (client, description, declared values, status, tariff) are silently discarded — with no error message. If an edit "did not save", this is usually the reason: the field is not among those permitted to the warehouse.

The request list: selection and operations from the table

In the request table you can work with several records at once.

Selection and the summary

Tick the requests with the checkboxes. At the top right the "Clear selection" and "Change statuses and shipments" buttons appear, and above the table a summary of the selected records: Selected N, Packages, Weight, Volume, Actual weight, Actual volume, Bills (the total amount of bills) and Debt (the total unpaid balance). This is handy for quickly estimating what will fit, for example, into one truck. The Bills and Debt fields in the summary are shown only to the roles that have access to financial amounts (see the section on bills below).

Changing the status of a single request from the table

Clicking the status right in the row opens the "Change status" window with the Status and Comment fields and the "Save" button. (When the status is changed this way — unlike in the bulk operation — notifications are sent.)

Bills for a request: a quick view

The request table has financial columns for quick control — whether a bill has been issued for the request and whether it has been paid. This is a "light" indicator; full bill management (creation, posting, allocation of payments) lives in the Finances section.

The "Bill" column — a status indicator

The icon shows the state of the client's bill for the request. Hovering over it shows a tooltip. There are three states:

Icon/tooltip	What it means
"Bill not issued" (grey)	There is no posted outgoing bill to the client for this request.
"Bill not paid"	A posted bill exists but has not been paid yet.
"Bill paid" (a tick)	A posted bill exists and it has been paid.

How the state is determined

The indicator takes into account the outgoing posted bill issued to the client of the request. As long as the bill is not posted, for the indicator it "does not exist". "Paid" means the corresponding bill is marked as paid. The indicator column is visible to all roles except the warehouse worker: the manager, the head, the administrator and the client (for their own requests). The filter "Bill" is available to an even narrower circle — only to the manager and above; it is not shown to the warehouse worker or to the client.

The "Bills Amount" and "Debt" columns

• Bills Amount — the total amount of outgoing posted bills for the request (for example, "62,860.00 RUB"), converted to the company's main currency.
• Debt — the total unpaid balance of these bills (shown in red if it is greater than zero; "0.00 RUB" if there is no debt).

Who can see monetary amounts

The "Bills Amount" and "Debt" columns (and the same values in the summary above the table) are visible only to the Administrator and the Head. Monetary amounts are not shown to the manager, the warehouse worker or the client — they only get the "Bill" indicator (issued/paid), without amounts.

The "Payments for request No. N" window

Clicking the icon in the "Bill" column opens the "Payments for request No. N (Client)" window — a quick way to check whether a bill has been issued and whether it has been paid, without leaving for the finance section.

In the window:

• The "Create bill" button (it opens the bill creation wizard right from this request) and "Filters".
• A table of the financial documents of this request: No., operation type (incoming/outgoing), payment due date, document type (Bill/Payment), currency, account/cash register, amount, document balance, item, posted (Yes/No), paid (Yes/No), the linked shipment, the operation basis, the author.
• At the bottom — the page size selector, the export to CSV/XLSX and the display settings for the columns.

Here it is only quick control; bill management lives in Finances

In the requests section the "Payments for request" window exists so that you can quickly see the picture of the bills for a specific request and, if necessary, start issuing a bill right away. The full mechanics — creating a bill (a multi-step wizard), posting documents and allocating payments — are described in the finance module:

• Financial operations — bills, payments, document types.
• Posting documents — what "posted" means and how it affects the bill status and the debt.

Bills can be created and edited by the manager, the head and the administrator; the client only views financial documents (on their own requests), without editing. The monetary totals — "Bills Amount" and "Debt" — are available to a narrower circle: the head and the administrator see them.

Attaching a request to a shipment

A request can be attached to a shipment at creation (step 1) or later:

1. Open the request card.
2. In the "Attach to shipment" field select an existing shipment (or set it back to "Not attached").
3. Save.

Several requests attached to one shipment form a groupage cargo.

Synchronisation with finances

When a request's shipment is changed, the system automatically transfers the link of its financial operations to the new shipment, so that income and expenses are counted against the correct transportation. For details see Financial operations.

Copying a request

It is convenient to copy a similar request rather than fill it in from scratch. When copying you can choose which sections are carried over: the general fields, the cargo, the link to a shipment, the logistics (the leg with the route/carrier), the custom fields, the files, the packages with photos. The copy gets a new number and the "default" status.

The tariff in the copy

The tariff is carried over into the copy, but the snapshot of its terms is taken anew — from the current state of the directory and with today's date applied. A copy is a new request accepted today, so its terms are today's ones too.

Copy limit

Copying is limited — no more than 30 copies per hour per user (a safeguard against accidental mass duplication).

Summary of the selected requests

Tick the requests with the checkboxes (the checkbox in the "Number" column) — a summary panel for the selected records appears above the table. This is a quick way to look at the aggregated figures for a group of requests without opening each one. In the panel:

• Selected — how many requests are ticked.
• Packages — the total number of cargo packages.
• Weight and Volume — the sum of the declared weight (kg) and volume (m³).
• Actual weight and Actual volume — the sum of the actual values.
• Bills — the total of the bills issued to the clients for these requests.
• Debt — the total debt on them (shown in red if greater than zero).

The "Clear selection" button resets the choice; "Select all" ticks all the requests on the current page.

The summary is calculated over the current page of the list

Only the requests of the visible page of the table are included in the total. If the requests you need do not fit on one page, increase the page size at the bottom of the list (15 / 30 / 50 / 100) or narrow the list down with filters so that all of them end up on one page, and only then make the selection.

"Bills" and "Debt" are not for every role

The financial totals "Bills" and "Debt" in this panel are visible only to the administrator and the head. The amounts are converted to the company's base currency (bills in other currencies are recalculated at the rate on the bill date). The other figures (packages, weight, volume) are available to all roles.

Bulk changes to requests

Tick the requests with the checkboxes and click "Change statuses and shipments" — the bulk operation window opens (up to 50 requests at a time). In the window:

• The heading "Selected requests: N" and the list of the selected records (No. + client).
• The "Status" field — "No change" by default; select a status to apply it to all of them.
• The "Shipment" field — "No change" by default. You can select a specific shipment (to attach all the selected requests to it) or the "Without shipment" option — to detach the requests from their current shipment.
• The "Update N requests" button.

This is the main tool for putting together a groupage truck: tick the requests → assign one shipment to them → set the required status.

Specifics of the bulk operation

• You have to specify at least one of the two — the status or the shipment; otherwise there is nothing to update.
• On a bulk status change no notifications are sent (unlike a one-by-one status change from the table). If it is important to notify clients/colleagues, change the status request by request.
• Other companies' requests will not get into the operation — it works only within your company.
• The "Without shipment" option specifically detaches the requests (clears the "Shipment" field), it does not delete them.

Files and documents

The request card has a Files tab for documents: the client's specification, correspondence, agreed tariffs, commercial offers. Files are laid out in folders. Formats, limits and access rules — in the Files in logistics section.

Is the request paid: the "Bill" column

The request table has a "Bill" column — it shows whether a bill has been issued to the client for the request and whether it has been paid. The state is shown by an icon (hovering over it reveals a caption):

• A grey icon — the bill has not been issued (there is no posted bill to the client for the request yet).
• A blue icon — the bill has been issued but not paid.
• A green tick — the bill has been paid.

There is no separate "partly paid" marker — a partial payment is visible through the "Debt" column (the balance is greater than zero).

Clicking the icon in the "Bill" column opens the "Payments for request" window — the list of the bills and payments for this request. The manager, the head and the administrator can create and post bills and payments right there; the client sees the window for viewing only.

What counts as "paid" and who sees the amounts

"Paid" is marked by the posted outgoing bill to the client of the request. The monetary columns "Bills Amount" (issued) and "Debt" (the balance due, in red if greater than zero) are visible to the administrator and the head. The indicator column "Bill" itself is visible to all roles except the warehouse worker. Payment is tracked at the level of financial operations — for details on bills and payments see Financial operations and Settlements.

Search and filters

Above the request table there is a search box (by number and the main fields) and the "Filters" button. The button opens the selection of a column to filter by; the general filter mechanism (condition types, several filters at once, badges, "Clear all") is described in the Tables and filters section.

Requests can be filtered by columns:

• Client — selecting one or several clients from the list (with a search by name). This is the main way to look at all the requests of a specific client — their "cargoes".
• Manager, Author — the responsible one / the one who created the record.
• The request Status and the Shipment status.
• Creation date — a specific date or a range.
• Shipment — a specific trip or the "Without shipment" option (this is how you find all the requests not yet attached to any shipment — for example, in order to put them on a trip); Warehouse number — including "Without a warehouse number".
• Bills Amount and Debt — a range of amounts / the presence of debt (available to the administrator and the head).
• Bill — "not issued", "not paid", "paid".
• Tariff — there is no separate filter by tariff. The "Tariff" column can be sorted (by the tariff name), and the name goes into the CSV/XLSX export. The column is not shown to the warehouse worker and does not get into their export.
• Text ones: Number, Description, Comment, Shipment comment — they search by substring: for example, the "Description" filter with the word Spare parts will show all the requests whose description contains "Spare parts".

How to look at the cargoes of a single client

Click "Filters" → "Client", find and tick the client you need — the table will show only their requests. You can add a second filter (for example, by status) to narrow the selection down. There is no direct "by client" filter in the Shipments table — a client's shipments are viewed through their requests (the attached trip is visible in the request).

The applied filters are saved in your browser between sessions. A selection cannot be shared through an ordinary link (the address bar only stores the transition to the requests of a specific shipment) — it is easier for a colleague to reproduce the filter on their side.

Who can do what with a request (roles)

LogiFlow distinguishes the roles: Administrator, Head, Manager, Warehouse worker and Client.

Action	Administrator	Head	Manager	Warehouse worker	Client
See requests	✅ of their company	✅ of their company	✅ of their company	✅ of their company	⚠️ only their own
Create a request	✅	✅	✅	✅	✅ (only for themselves)
See the actual weight/volume and the link to a shipment in the form	✅	✅	✅	—	❌ (hidden)
See the request tariff and its terms	✅	✅	✅	❌ (hidden everywhere)	⚠️ view only
Select/change the request tariff	✅	✅	✅	❌	❌
Edit a request (in full)	✅	✅	✅	⚠️ only the comment and the actual weight/volume are saved	⚠️ only their own and only in the primary status
Change the request status (one by one, and the actual weight/volume during a status change)	✅	✅	✅	✅	❌
Bulk change (status/shipment)	✅	✅	✅	✅	❌
What exactly is saved on editing	everything	everything	everything	comment, actual weight, actual volume	comment, description, packages, declared weight/volume, route
Add/edit/delete packages	✅	✅	✅	✅	⚠️ only in their own requests
Upload package photos	✅	✅	✅	✅	⚠️ only in their own requests
The "Update actual values" button (direct recalculation into the request)	✅	✅	✅	✅	❌
Manual entry of the actual weight/volume in edit mode	✅	✅	✅	✅	❌
Copy a request	✅	✅	✅	✅	✅ (their own)
Delete a request	✅	✅	✅	❌	⚠️ only their own
Work with the request files	✅	✅	✅	⚠️ delete — only their own files	⚠️ views and downloads always; uploads and deletes — in the primary status
See the "Bill" indicator (issued/paid)	✅	✅	✅	❌	⚠️ on their own requests
Filter the list by the "Bill" column	✅	✅	✅	❌	❌
See the "Bills Amount" and "Debt" amounts	✅	✅	❌	❌	❌
Open the "Payments for request" window	✅	✅	✅	✅	⚠️ view on their own
Create/edit a bill from the window	✅	✅	⚠️ subject to finance permissions	❌	❌

Notes on the roles

• The client sees only their own requests (those where they are named as the client), even within a single company. In the wizard the actual weight/volume, the tariff and the link to a shipment are hidden from the client. The client sees packages and photos only in their own requests.
• The client edits a request while it is in the primary status — the starting status configured in your company (in the out-of-the-box set it is called "New request", but the administrator may have renamed it or created their own). The client does not edit everything: the description, the comment, the packages, the declared weight and volume, the sender/receiver with their addresses. The status, the customer, the manager, the tariff, the warehouse number and the actual measurements are unavailable to them in any status.
• The warehouse worker is a full participant in acceptance: they create requests, change the status, enter packages, take measurements, upload photos and transfer the actual weight/volume into the request — both with the "Update actual values" button and through the status change window. What they cannot do: delete requests, see the tariff and the "Bill" column, and out of their edits to a request only the comment and the actual measurements are saved.
• A request cannot be deleted if it has posted financial documents — sort out the finances first.

Common mistakes when working with requests

• The request will not save. Most often the mandatory "Client" field has not been filled in.
• A sender/receiver is specified but there is no address. If a party is selected, its address must be specified — otherwise saving will not go through.
• Arbitrary text cannot be entered in the "Tariff" field. The tariff is selected from the tariff directory. If the rate you need is not in the list, ask the administrator or the head to create the tariff (the manager only reads the directory).
• The tariff you need is not in the drop-down list. The list contains only active tariffs. Check the "Active" flag in the directory.
• The request card shows "No tariff". No tariff has been selected in the request — select it manually, see Request tariff.
• The tariff terms in the request do not match the directory. That is by design: the request stores a snapshot of the terms as of the moment the tariff was selected. To update them, select the tariff again.
• The warehouse worker does not see the tariff. The rate is hidden from the "Warehouse worker" role everywhere, including print forms.
• A client complains that they cannot see a request. The client only sees the requests where they are named as the client. Check the "Client" field.
• The client did not get a notification about a bulk status change. That is expected — bulk operations do not send notifications. A one-by-one status change from the table does send them.
• A warehouse worker's edit to a request "did not save". The server accepts only the comment and the actual weight/volume from the warehouse; the other fields are discarded without a message. Edit them under a manager account or higher.
• The package volume cannot be set. The volume is not entered — it is calculated from the dimensions (Length×Width×Height). Check the dimensions.
• A package with the same number cannot be added. The package number is unique within a request — use a different number.

What's next

• Shipments — how to assign a trip and deliver the cargo.
• Multimodal transportation — the legs and the route of the transportation.
• Statuses — how to configure the workflow.
• Files in logistics — the documents of a request.
• Financial operations — the income and the expenses of a request.
• Tariffs and Shipment calculation — the rates and the cost calculation for a request.