Choosing Logistics Software for Manufacturers, Exporters and SMEs
A guide for the side that buys transport, not the side that provides it. Your daily flow is opened step by step, from the moment a shipment need arises to the reconciliation of the freight invoice; at each step you get what to expect from software and how to test it in a demo. This guide was prepared by Logistivo; the criteria are written around what happens in the field rather than around any one product, and where Logistivo itself sits in the comparison is stated openly in its own section. For a shipper, choosing logistics software comes down to one question: do the quote, the shipment, the documents and the invoice sit on the same record, or in four separate places? In manufacturing, export and e-commerce operations software is usually bought to answer “where are my goods”, yet the real losses accumulate in quote comparison, in document inconsistencies, and in the month-end freight invoice check. This segment's business is not carrying goods but buying carriage. You own no trucks; you have a loading date, a buyer commitment and a handful of carriers. What you should assess is therefore not fleet management but the ability to attach outside parties to your own record: can you bring the carrier in while it quotes, the customs broker while it prepares the declaration, and the buyer while it asks for status — all onto the same screen? Below, that flow opens step by step: the capability to expect at each step and what breaks without it. Then come criteria you can verify in a demo, an honest comparison of four approaches, a readiness checklist and the mistakes buyers make most often.
Workflow steps and what software must do
The shipment need appears: an order, a production batch or a stock release — Sales closes an order or production finishes a batch; the loading date, package count, gross and net weight, dimensions and Incoterms rule become known. The logistics owner usually receives this by email or verbally and retypes it into a spreadsheet. Opening the shipment record in one place together with product, pallet and dimension data, so package count, weight and volume flow identically into every document produced later. The same data is typed into three places by hand. You ask for a quote saying 12 pallets, the packing list says 13; the difference surfaces either on the carrier's invoice or at a customs check.
Defining the request and opening it to your own carrier pool — Collection point, destination, vehicle type, date and special conditions (reefer, ADR, ramp access, loading slot) become a single request that goes out to the carriers you work with. In practice this step is still mostly the same email written separately to five companies. In e-commerce models with many small shipments, this step and the quoting step run on periodically agreed rates instead of shipment-by-shipment quotes, and the loading paperwork is a courier or parcel label. Entering the request once and sending it to several carriers at the same time, and choosing company by company who can see it, so the request does not land on a public freight board without your knowledge. Different companies receive different information and the quotes that come back cannot be compared. If the request reaches the open market against your wishes, your volume, your lane and your price range are read by parties you never chose.
Collecting, comparing and accepting quotes — Quotes arrive in different shapes: one is a total per vehicle, another is per tonne or per loading metre (LDM), a third itemises waiting time and customs handling separately; procurement copies them all into a spreadsheet by hand. Collecting quotes in a common structure and lining them up side by side; a revised quote superseding the old one; the moment of acceptance, the person who accepted and the accepted amount going on record. Old and new prices get mixed up and which quote came with which condition is forgotten. At month end the "but this is not what we agreed" conversation starts and you hold no written trace.
Loading day: the vehicle at the gate, the paperwork on the desk — Vehicle and driver details arrive, the truck is loaded and a despatch document is issued (in Türkiye the irsaliye, a legally required delivery note); for export the commercial invoice and packing list are prepared, and on international road moves the contract of carriage is normally evidenced by a CMR consignment note. Every one of these documents repeats the same shipment data. Producing the commercial invoice, packing list and transport document from the single data set on the shipment record, and updating all of them together when weight, package count or a party changes. For documents subject to approval — EUR.1, A.TR in Türkiye–EU traffic, certificates of origin, the customs declaration — the expectation is not generation but keeping the same data consistent and handing it to the broker complete. Weight or package count does not agree across documents. The load waits at customs; on letter-of-credit business the bank rejects the presentation and the vehicle waits until the correction is made.
Tracking in transit, border and customs stage — The vehicle departs; waiting begins at the border gate, in the customs compound or at the port, and a transit movement (a T1 declaration under EU and common transit rules, or a TIR carnet) can add its own steps. At this stage the shipper's only source of information is usually calling the carrier and waiting for an answer. Shipment status and position visible in the system — driver position by road, container and vessel tracking by sea; every status change stored with a timestamp; the customs broker attachable to the same shipment as a party. Waiting is not visible in real time; the delay reaches the customer only when the customer asks. When the storage or demurrage invoice arrives, you cannot prove where the time was lost.
Keeping the buyer and internal customers informed — The buyer, the sales team or production planning asks when it will arrive. To produce an answer the logistics owner first calls the carrier, then forwards it by email; the same task repeats several times per shipment. External visibility that can be adjusted field by field. Either nobody gets information, or sharing it also exposes your rate and your supplier list. Both are expensive: the first costs trust, the second costs negotiating power.
Delivery, POD and post-delivery claims — The goods are unloaded and the signed transport document and proof of delivery come back. From time to time a damage, short-landed package or late delivery claim appears and the parties start quoting dates and times at each other. Attaching the signed document to the shipment record; archiving every status change and message with its date and time on that same record; keeping it searchable months later. The POD stays on somebody's phone. Six months later the insurer or the customer asks for it and it cannot be found; the dispute is argued from memory instead of from a neutral record.
Freight invoice reconciliation and recording the cost — The carrier's invoice arrives; waiting time, customs storage, delivery order fees, terminal handling or exchange-rate differences may have been added to the agreed amount. The check is mostly done by eye and a mismatch is noticed months later. Storing the accepted quote amount on the shipment and linking the incoming invoice to the same record so the two can be seen side by side; cost accumulating by lane, period and carrier; the data exportable to Excel. Overcharging is paid quietly. At year end you cannot say what you paid on which lane or which carrier is genuinely expensive, and you enter the next rate negotiation without data.
Selection criteria
Comparing quotes like for like — Carriers price the same job in different shapes: one gives a total per vehicle, another per tonne, per cubic metre or per loading metre (LDM) as is common in groupage and LTL, a third itemises waiting time and customs handling separately. Lined up without a common structure, the lowest figure is usually not the cheapest offer. For a shipper this is the single largest savings lever. In the demo, have three quotes entered for the same lane in three different shapes — one per vehicle, one per tonne, one with extra line items — and ask the system to rank them in a single table by total cost.
Choosing who sees the request, company by company — Your lanes, your volume and the price you pay are commercial information. If a request drops onto a public board, your shipping pattern can be read by your buyer and your competitor alike. Against that, an open freight exchange gives reach to carriers you do not know and wider capacity in spot periods; which matters more depends on the lane and the urgency. What you want is not one extreme but the ability to set visibility per request. Ask the vendor to share their screen live from a third company account that should not see the request; separately, check yourself whether open requests in the system are findable through a search engine, and get in writing which setting decides visibility.
Trade documents produced from one data set and consistent with approved certificates — The commercial invoice, the packing list and the transport document largely repeat the same information; copied by hand, gross weight comes out one way on one document and another way elsewhere, and on international road moves, when the data on the CMR consignment note does not match the rest, the load stops at customs or at bank presentation. Movement certificates such as EUR.1 and A.TR (the latter used in Türkiye–EU customs union traffic), certificates of origin and the customs declaration are not papers you simply print: they are certified, endorsed or registered by a chamber of commerce or by the customs authority. What to expect from software is not to finish these, but to keep the same data consistent across every document prepared. Change the gross weight and package count on a shipment; watch the invoice, the packing list and the transport document all show the new value and recalculate their totals. Ask in writing whether correcting a document and reissuing it carries any extra cost — a fee, a quota or a fresh approval step.
The agreed price meeting the incoming freight invoice — A shipper's quietest loss of money is a freight invoice that differs from the quote that was accepted. Once waiting time, storage and terminal lines are added the gap looks small, but it repeats on every shipment. If the accepted amount does not sit on the shipment, the control depends entirely on one person's attention. Check whether the amount of the quote you accepted is stored on the shipment record and whether the incoming freight invoice attaches to that same record; ask the vendor plainly whether the difference is flagged by the system or whether the comparison is yours to make.
Freight cost broken down by lane, period and carrier — Procurement negotiation runs on data. If you cannot see what you paid on which lane this quarter, how the average per vehicle moved and which carrier is expensive on which lane, you rediscover the same price every year. That breakdown is also the only real basis for an annual freight budget. Load three months of past shipments and have the question "what did I pay in total on this lane this quarter, and what is the average per vehicle?" answered on one screen, then export the same table to Excel.
Controlled visibility for buyers and internal customers — A shipper has to share information but cannot share everything. Letting the buyer see shipment status ends the phone traffic; letting the same screen expose your freight rate, your supplier list and your other shipments erases your negotiating position. Visibility has to be adjustable field by field. Create a user in a buyer or observer role and log in as that user. It should see status and estimated arrival, and it should not see the freight amount or the quotes received.
Duty and trade-measure cost visible before the shipment moves — Whose pocket the tariff risk comes out of depends on the Incoterms rule. Under DDP, anti-dumping duty and additional charges in the destination country are directly your cost; under FCA, FOB or CIF the bill goes to the buyer, but noticing a measure late still ends in a cancelled order or a reopened price negotiation. On the import side the cost lands on you outright. In all three cases, being able to run the check before the shipment against data with a stated source becomes critical when you open a new product or a new market. Run a lookup for an HS code and destination country you actually ship; ask where the result came from and when it was last updated. Do not rely on a rate whose source cannot be shown while you are preparing a declaration.
Getting your data out whenever you want — Shipment history, the quote archive and the documents are your commercial record; they have to survive a change of software. Without export, changing system a year from now becomes impractical and you enter the renewal talk with nothing in hand. Some documents may also have to be retained for years. During the trial, download your full shipment, quote and document lists to Excel and PDF, and check that documents can be pulled in bulk. If you cannot, ask for the data-return clause of the contract in writing.
Pricing that measures shipment volume, not headcount — Per-user pricing backfires on the shipper side: as the buyer, the warehouse supervisor, the accountant and the export specialist are added, the cost grows and the team starts sharing one login. The moment an account is shared, who did what disappears and the data the system produces becomes unreliable. Against that, in a small and stable team a per-user model can still be cheaper overall; make the comparison with your own user and shipment numbers, not with a general rule. Give the real shipment and user counts of your busiest month and ask for a billing simulation; get in writing whether there is a user cap and how the amount moves at seasonal peak.
Comparing the approaches
Quotes by email, follow-up by phone, documents in a folder (manual coordination) — Companies sending a handful of shipments a month on one lane with two or three carriers, where the whole operation still fits in one person's head. The money goes into time, not licences: hours spent chasing quotes, typing documents and asking for status. Because that cost is invisible it cannot be defended to management; the real bill appears in the missed delivery date and the overcharge nobody noticed.
General-purpose software and shared spreadsheets (ERP shipping module, spreadsheet, shared drive) — Manufacturers who already run an ERP or accounting package and want to handle logistics through its shipping module or through a carefully maintained spreadsheet. The cost is not in licences but in maintenance: the person who built the sheet and keeps it current. When that person leaves, the structure collapses; on the ERP side every new field or report is billed as consultant days and joins a queue.
Single-purpose point tool (tracking only, quoting only or documents only) — Companies bleeding in exactly one place: few shipments but "where are the goods" asked ten times a day means tracking only; everything else settled but export paperwork typed by hand means document generation only. The shape is a separate subscription per tool plus the effort of wiring them together. Integration is never done once: when either side changes a version, maintenance comes back, and that work is usually nobody's actual job.
End-to-end transport management system (TMS) — Companies with regular, repeating shipments that want the quote, shipment, document and invoice chain on one record, and want carriers, customs brokers and buyers on the same screen. A predictable subscription plus one-off setup and data migration effort. The real variable is the unit of measure: per user, or per shipment or vehicle. On the return side sit the repeated data entry that disappears and the document corrections that stop happening.
Common buying mistakes
Buying because the map screen looked good — The live map is the most impressive screen in any demo, but it does not fill itself: the data comes from the driver's phone or from a status the carrier types in. Ask one question before you buy: where does this position come from, who fills it, and what do I see on screen if nobody does? If the answer is "the carrier enters it", measure during the trial whether your carrier actually will.
Assuming the carrier will use the system — The shipper buys the software and the carrier still writes on WhatsApp; within a month the system becomes a second workload. Before purchase, get trial accounts opened for your two busiest carriers and ask them to quote a real request from there. If you believe they will not log in, the system must still be able to pull those companies into the process by email or invitation link.
Letting per-user pricing punish the operation — In a system billed per seat you avoid adding the warehouse supervisor, the accountant or the second buyer. The outcome is predictable: the team shares one login, who did what disappears, and the data the system produces stops being auditable. Test the pricing model not only against your shipment count but against how the cost grows with the number of people who genuinely need to touch the system.
Finding out later that you cannot get your data out — Shipment history, the quote archive and the documents you uploaded turn into a serious commercial record over the years. Without export, the decision to change system becomes impractical and you walk into the renewal conversation with no leverage. Test this in the trial phase, not at contract stage; actually attempt one download.
Choosing a tool that produces documents but does not tie them to the data — Some tools generate a handsome PDF but never link the document to the shipment record; a small correction means retyping the information and, in some cases, paying again. The test is simple: change a consignee address or a package count and see whether the document updates by itself.
Running the pilot on sample data — Every system is flawless on the sample data the vendor prepared. The real test is running your hardest lane and the shipment with the most complicated document set from end to end: open the request, collect quotes, accept one, produce the documents, track the vehicle, upload the invoice. One real shipment carried all the way through tells you more than any demo presentation, however long it takes.
Frequently asked questions
What does logistics software do for a manufacturer, and how is it different from an ERP?
Logistics software manages the life of the goods after they leave the plant: collecting quotes from carriers, the shipment record, transport documents, tracking in transit, proof of delivery and freight invoice reconciliation. An ERP manages the order, production, stock and accounts; its shipping module is usually little more than a goods-issue record and cannot bring outside parties inside. The two are not rivals: the ERP knows what the order is, logistics software knows how and with whom it moves. Plenty of companies run both together.
What should an exporter expect from shipment tracking software?
For an exporter, tracking is more than a dot on a map. Three things are worth expecting: every status change stored with a timestamp, waiting at the border and customs stage made visible, and controlled visibility that can be granted to the buyer. Add the document side to that: invoice and packing list produced from the same data, so a gross weight or package count mismatch is caught before the truck leaves. Position alone does not prevent delay; records and document consistency do.
Does freight quote comparison software really reduce freight cost?
It does not force prices down directly; it makes comparison and negotiation possible. The gain comes from three places: because quotes land in a common structure you pick the genuinely lowest total cost rather than the lowest headline figure; because the accepted price is on record you catch the extra line on the incoming invoice; and because history accumulates by lane you walk into the next rate discussion with data. On a one-off shipment the effect is limited; on repeating lanes that third point does the real work.
I own no trucks, I only buy transport. Do I still need a shipment tracking system?
For companies without a fleet the need is not fleet management but coordination and record-keeping. Because you own no vehicles, every piece of information arrives from outside: the carrier, the driver, the customs broker. Without a shared place to collect it you stay dependent on phone and email traffic, and you hold no evidence when a dispute starts. So the system is more necessary for an asset-light shipper, not less; the focus simply moves from the vehicle to the shipment record and to bringing outside parties in.
Is the software any use if my carrier will not log in?
Partly, but you lose a large share of the return. If the carrier stays out, you enter the quotes by hand, live position never arrives and correspondence stays outside; what remains is record-keeping, document production and cost reporting. That is why you should bring your two busiest carriers into the trial before you buy. In practice carriers turn out more willing to log in than expected when the customer giving them the work asks for it; do not make that decision on their behalf.
Where does the live position of a shipment come from, and can I trust it?
On road, position usually comes from an app on the driver's phone or from the carrier's own vehicle tracking; at sea, container and vessel tracking rests on data from the shipping line. Reliability follows the source: if the driver never opens the app the map does not update, and sea-side updates are inherently sparser. In a demo, ask where the position comes from, how often it refreshes and what the screen shows when nothing arrives. A system that honestly displays "no data" beats one that quietly keeps showing the last known point.
How many shipments a month justify moving to software?
The threshold is repetition, not shipment count. If you move goods every month on the same lanes, with the same carriers and the same document set, software pays for itself; if you ship a one-off consignment abroad a few times a year, it does not. A practical measure: multiply the coordination time one shipment costs you — chasing quotes, typing documents, asking for status — by your monthly shipment count. Divide the hours by one person's monthly working hours and compare the staff cost with the subscription; the comparison figure comes from you, not the vendor. In e-commerce models with many small shipments the threshold arrives earlier.
Is supply chain visibility software the same thing as a transport management system (TMS)?
Not the same, though the edges overlap. Visibility tools focus mainly on "where is it and when will it arrive", usually pulling data from many carriers and displaying it; you watch rather than transact. A TMS runs the work: it opens a request, collects quotes, creates the shipment record, produces documents and links the invoice. If all you need is to watch, a visibility tool is enough. If quoting, documents and invoicing are still manual, visibility alone will not solve the problem — it will only show it more clearly.
Can software handle customs duty and anti-dumping checks?
Software speeds up the lookup; it does not take on the responsibility. A good system helps you find the tariff code, puts the destination country's import duties and the trade measures in force in front of you, and archives the lookup as it stood that day. Final classification and declaration responsibility stay with the company and its customs broker. When evaluating a tool, look at whether it shows the source of the result: a rate with no stated source and date may come from an old table and will not support a declaration.
If I leave the system, can I move my data somewhere else?
You should be able to, but verify it in the trial rather than in the contract. During the trial, try downloading your shipment list, your quote history and the documents you uploaded yourself; if table data comes out as Excel or CSV and documents download in bulk, you are fine. If not, ask in writing how, in what format and within what period data will be returned, and confirm separately that documents are included. Handle this in the first days before signing, not at the moment of migration. Asked later, you have no leverage: the data is already on the other side and the time pressure is on you.