Many legs, one margin you can’t see
- You run a shipment in several legs, and every leg has its own contractor.
- You learn the actual margin weeks after the deal closes.
- Some extra services regularly never make it onto the invoice.
Logistic24 · Industry solution on Bitrix24
The deal that knows how freight moves.
Bitrix24 for multimodal forwarders, rail fleet operators and road carriers — implemented by people who worked in dispatch, sales and forwarding.
Who it’s for
Three profiles. If one is yours, read on.
Wagons in one system, deals in another
- Dislocation lives in one system, deals in another or in Excel, and client reports are assembled by hand.
- Idle time is noticed after the fact — or not at all.
- Wagon turnover is calculated in Excel.
- Month-end close is stitched together from managers’ spreadsheets.
Requests in WhatsApp, status by phone
- Requests arrive in WhatsApp and get lost.
- Trip status means a phone call.
- CMRs and consignment notes live apart from the deal.
- Vehicles aren’t tracked by GPS.
Teams of 20–300 people. Fit two profiles at once? That’s normal — the configuration is assembled from modules.
Where money leaks
Four holes in the margin.
Slow response to requests
A request waits a day for an answer. Whoever replies third hasn’t replied at all.
Requests that were already in progress get lost.
Under-counted rate
Terminal handling, loading and unloading, security, lashing, weighing and overweight come up after shipment.
Margin is eaten by what nobody priced.
Unbilled demurrage and storage
Nobody tracks when the free days ran out.
The carrier pays for excess idle time instead of the client.
Receivables and closing documents
The trip is closed, but there’s no e-invoice or e-act, advances hang, or the money hasn’t arrived.
A cash gap out of nowhere.
None of the four is fixed by hiring another manager.
Limits of a generic CRM
Why a generic CRM doesn’t fix it
| Generic CRM | How freight actually works |
|---|---|
| A deal is one sale | A deal is a chain of legs: road → rail → sea → air |
| One counterparty | The client plus a separate contractor on every leg |
| An amount, and that’s it | Purchase and sale rate for every leg, margin planned and actual |
| Free-text fields | Stations with ESR codes, cargo by ETSNG and GNG, wagon and container types |
| Files in comments | Request, shipping instructions, rail waybill, CMR, consignment note, bill of lading, AWB — each on its leg |
| Deal closed = the end | The deal is closed, but contractor invoices and closing documents keep coming for a month |
It can be configured. The question is how many months it takes to explain re-consignment and re-routing to a vendor.
Logistics core
One deal. Every leg. Live margin.
The route is split into legs, each with its contractor, lead time and purchase rate. The sale rate and margin sit right next to them, and the actual margin is recalculated as contractor invoices arrive.
| Leg | Contractor | Term | Purchase |
|---|---|---|---|
| Road · Almaty → Dostyk | contractor 1 | 4 days | 1,240,000 ₸ |
| Rail · Dostyk → Urumqi | contractor 2 | 9 days | 3,480,000 ₸ |
| Terminal · Urumqi | contractor 3 | 2 days | 310,000 ₸ |
- Sale rate
- 6,150,000 ₸
- Planned margin
- 1,120,000 ₸ · 18.2 %
- Actual margin
- recalculated from contractor invoices
Minimum margin 12%
Generated from the deal
- Commercial offer on your letterhead
- Transport request
- Contract from the template for this transport mode
- Invoice
Documents live on their leg
Rail waybill, CMR, consignment note, bill of lading, AWB and shipping instructions stay on the leg they belong to instead of piling up in the deal’s files.
Architecture
Three layers. Pay for what you connect.
Industry modules
connected by choice- Rail and wagons
- Containers
- Road
- Customs and brokerage
- Tenders
- Finance loop
Logistics core
shared by every transport mode- Shipment deal with legs
- Contractors per leg
- Rate and margin calculation
- Auto-generated request, offer, contract and invoice
- Registry of transport documents
- Cargo status tracking
Core
the same for everyone- Portal and org structure
- Contract and invoice approvals
- Correspondence registers
- Business trips and leave
- HR block with employment contract generation
- Counterparty directory
- Request channels
- Roles and permissions
Read it from the bottom up: the core is the same for everyone, the logistics core is the same for every logistics company, and differences start only on the third layer. That’s why we connect modules instead of rewriting the system for each client.
Industry modules
What connects on top of the core
| Module | For | Inside |
|---|---|---|
| Rail and wagons | Operators and fleet owners | Station directory with ESR codes, ETSNG and GNG, GU-12 requests, rolling stock cards, wagon turnover, idle time, empty runs, dislocation |
| Containers | Multimodal and sea forwarders | Container type directory, container ↔ flat wagon pairing with load capacity control, FCL/LCL, free days, demurrage and detention |
| Road | Road carriers and forwarders | FTL/LTL, vehicle and driver cards, trips, waybills, CMR and consignment notes |
| Customs and brokerage | Brokers and forwarders in foreign trade | Declarations, customs regimes, corridors, temporary storage warehouses, permits, certification |
| Tenders | Anyone bidding in public procurement | Parsing tender newsletters from email, tender funnel, registry of corporate, banking and permit documents with expiry control |
| Finance loop | Everyone | E-invoices (ESF) and e-acts (EAVR), receivables, reconciliation statements, closing documents per trip |
Modules live on one deal: a container from the sea leg lands on the flat wagon of the rail leg without being entered twice.
Configurations
Three ways to start.
Start
Cloud- Core
- Logistics core
- One transport mode
- For
- Forwarders with 5–25 people
- Timeline
- 2–4 weeks
Pro
Cloud or on-premise- Core
- Logistics core
- 2–3 industry modules
- Document flow
- Document generation
- For
- Companies with 25–100 people
- Timeline
- 6–8 weeks
Operator
On-premise, on your server- Everything in Pro
- All industry modules
- Integrations: dislocation, 1C, EDI
- BI export
- Digital signature
- For
- Multimodal operators with their own fleet
- Timeline
- 8–10 weeks
Delivery
How the project runs
- 01Express auditOne meeting, free
- 02Survey and specificationTwo weeks · from you: interviews with department heads, document templates
- 03Deployment and core setup
- 04Logistics core and modules
- 05IntegrationsFrom you: access and APIs
- 06Testing, training, launch
What we don’t do
- We don’t replace 1C or your accounting.
- We don’t build a full TMS or WMS.
- Dislocation data is pulled in only where the provider offers an API.
- Messengers work within official APIs and platform limits.
Better to agree on this at the start than at acceptance.
Case
IFC Colos
A multimodal logistics company. On-premise edition for 50 users on the client’s own server.
50users, on-premise
5approval workflows, from contracts to leave
5transport modes in CRM and SRM
4industry directories: stations, cargo, containers, rolling stock
Portal and processes
- Portal and org structure
- Five approval workflows
- HR block with employment contract generation
- Request channels
Commercial loop
- CRM and SRM by transport mode: wagons, containers, air, sea, road
- Tender module
- Customs block
Logistics core
- Rail logic with station directories and ETSNG and GNG codes
- Container and rolling stock accounting
- Integration with the dislocation system
We don’t publish impact figures until pilot operation is complete.
Next step
Express audit of your commercial workflow
60–90 min
One meeting.
3 people
From your side: commercial director, head of operations and finance lead.
3 leaks
You leave with three concrete margin leaks, an estimate for each, and the configuration you need.
0 ₸
Free, with no obligation.