Requests from every channel
Leads from Meta forms, your website and email come into one Lead Center, and new leads can be pushed to Telegram, so a request is not left waiting until someone checks the inbox.
Logistics & freight forwarding
In a forwarding company the day is a string of calls, trucks, weighbills and payments that usually live in different places. OrgLines keeps them on one freight order, so the team sees whose move it is, the owner sees the margin, and nothing depends on one person's memory.
A typical picture: requests come in by phone, email and ads, and the carrier list sits in a spreadsheet that one manager keeps up to date. Drivers send TTN photos to a messenger, the accountant finds out about a finished trip a week later, and nobody can say quickly how much the company earned on a given order. When the person who ran an order goes on holiday, the order waits for them.
OrgLines connects the parts a forwarder already has. Requests go through the Lead Center and CRM, orders, carriers, trucks and trips through the logistics module, and invoices and payments through the finance desk. Drivers work through a Telegram bot. Each person has a queue that shows what is waiting for them, and the owner has reports on turnover, margin, on-time arrival and debts.
You do not have to switch everything on at once. Many teams start with orders, carriers and trips, connect the drivers' bot in the first week, and move invoicing into OrgLines later. Your statutory accounting can stay where it is.
Leads from Meta forms, your website and email land in the Lead Center. A qualified request becomes a client in the CRM and a freight order with rates, tonnage and a loading window.
The day starts with the call list. Orders with uncovered tonnage wait in the sourcing queue, and the system warns before you book a carrier above the customer rate.
One screen shows today's trucks with their weights, TTNs and registries. Drivers get the route in Telegram and send photos back, and the photos land on the right trip.
Closed registries wait for approval by the senior logistician or the head. Shortage over the norm turns into a claim that reduces the payment to the carrier.
The chief accountant issues invoices from approved registries, records payments, pays carrier advances and final settlements, and tracks the TTN originals until they are back.
Leads from Meta forms, your website and email come into one Lead Center, and new leads can be pushed to Telegram, so a request is not left waiting until someone checks the inbox.
Every order has a senior logistician and a dispatcher assigned, and each role has its own queue. An order cannot quietly stall between two people.
Carriers, their contracts, trucks and drivers are kept in the system, with a call history and the next planned call. When a manager leaves, the base stays.
When a carrier's rate is above the customer rate, the system says so before the batch is created. If the customer rate includes VAT, it tells you to compare the two yourself and does not claim a margin.
Drivers join by an invite link and get the route and trip files in the chat. They send TTN photos and start the downtime clock with one button, and none of them needs an account.
Loss is calculated from the loading and unloading weights and compared with the agreed norm for the crop. A claim goes into the carrier settlement as a minus line with its reason.
Customer and carrier envelopes, versioned documents and tracking of TTN originals until both sets are back. An order counts as completed only when the paper is in place too.
Order participants record who brought the client, who found the carrier and who ran the order. A report by participant shows everyone's results for the period.
Ask which orders are stuck, which trips lack documents or which clients have not paid. The assistant reads the dispatch summary and prepares changes for you to confirm.
Most of the pain in a forwarding business is not missing software but information spread over people and chats. These are the situations OrgLines is built to remove:
Each order carries two prices per tonne, one for the customer and one for the carrier. The difference is visible in the order list as the result. The customer is invoiced for the actually weighed tonnes, after the registry is approved. Carriers are paid through an advance and a final settlement, and claims reduce what is payable.
For the owner, the finance desk shows what is due, what is overdue with the oldest debts first, and what the company owes carriers. If you trade through several legal entities, invoices are separated by the selling entity, and that entity's VAT status decides how invoices and acts are printed. Customer cards keep the payment deferral and credit limit next to the current debt.
Orders manager, carrier manager, senior logistician, dispatcher, accountant, chief accountant and head of logistics each see their own desk and queue. The head has a read-only view of everything. Roles also decide who sees the money: a dispatcher can work the queues without seeing amounts.
Holidays and departures are normal events here. A portfolio is handed to a deputy until a set date or for good, and history stays with the people who did the work. Staff can get their own notifications in Telegram, with quiet hours and an escalation to the head for overdue work.
FAQ
Didn't find an answer? Write to us and we will get back to you.
Ask a questionYes. OrgLines covers operations and management finance, and statutory accounting can stay where it is, or you can connect Business Central. The act of completed work is prepared by your accountant and filed to the order.
No. Drivers use the logistics Telegram bot: they join by invite link, get routes and send TTN photos. Office staff get access by role.
No. You pick your legal entity on each order and contract, and it decides whether invoices carry VAT. The finance desk can be narrowed to one selling entity.
Carriers can be created with three fields and completed later, and the fleet can be imported from a file with a preview before anything is written. Order statuses can start from a ready-made set.
Yes. The head of logistics role is read-only. If it is a person's only role, the server refuses any write from them.
You hand the portfolio to another person with no end date. Queues, buttons and notifications move to them. History and the record of who earned on each order stay unchanged.
Yes. Trucks, trailers and drivers are kept in the fleet directory, and trips, weights, documents, downtime and customer invoices work the same way. You simply use fewer of the carrier-side queues.
Agree a loss norm, a valuation price and a right of set-off in the carrier contract; weigh the cargo at loading and unloading; calculate only the shortage above the norm; send the carrier the claim with evidence; then deduct the agreed amount as a separate minus line in the final payment and pay the rest on time instead of holding the whole invoice.
What makes up the margin of a freight order, why monthly totals hide losing routes and how to see margin per order in OrgLines.
All modules share the same data, so they complete each other.
OrgLines logistics: freight orders with statuses and milestones, trips, vehicles, trailers and drivers, carriers and freight rates, trip documents, weight records and a logistics bot.
Track cash, bank and POS accounts, payments and an append-only financial ledger in OrgLines, plan by periods and categories and consolidate several companies.
OrgLines CRM collects leads from Meta lead forms, web forms and manual entry, qualifies them and turns them into contacts, organizations and deals — with an AI assistant.
Create a free workspace in a minute and invite the AI assistant to your team.
Start free