Software testing in logistics: flows, integrations and peak periods
In logistics, software moves real goods. A wrong stock level, a mislabelled parcel or a message lost between two systems shows up fast: on the dock, at the carrier or at the customer's door.
- Defects hide between systems: warehouse management, transport, commerce, accounting.
- Stock must stay right after every movement, including after an error or a recovery.
- Peak periods are prepared in advance: a load test before the season, not during it.
- Edge cases are physical: stock-out, partial parcel, return, incomplete address.
Oussama Belakhdar, QA architect and founder of AutomationDataCamp, has contributed to testing projects for logistics software. Here are the checks we put first for a warehouse, a carrier or an e-fulfilment platform, without naming our clients.
What do the logistics figures say?
Figures published by the organisations cited, not results of our own engagements.
Why is logistics software hard to test?
- A flow crosses several pieces of software from different vendors (order management, warehouse or WMS, transport or TMS, carrier portal, accounting), connected through EDI, files or APIs.
- Exchanges are asynchronous: a despatch advice can arrive after the truck, twice, or out of order.
- The software drives physical actions (scanners, label printers, conveyors, docks): a defect stops people and goods.
- Volumes vary sharply with the season and with customers' commercial campaigns.
Which flows should be checked first in a WMS or TMS?
- Receiving: expected despatch advice, quantity discrepancy, unannounced pallet, unknown item.
- Stock: every movement (put-away, replenishment, picking, stock count) leaves correct stock, including after an error and its correction.
- Partial orders, stock-outs, back orders, late cancellations and returns.
- EDI messages: valid, duplicated, out of sequence, malformed, a different message version at one partner.
- Labels and transport documents: logistic unit identifier, readable barcode, data expected by each carrier.
- Tracking: every status change reaches the customer within the expected delay.
Standards and constraints to test
EDI: UN/EDIFACT and GS1 EANCOM. Many logistics exchanges rely on UN/EDIFACT, the international standard for electronic data interchange, or on EANCOM, the subset defined by GS1 for trade and transport. The most common messages are the purchase order (ORDERS), the despatch advice (DESADV) and the invoice (INVOIC). Each partner publishes its implementation guide: that is the contract to test, segment by segment.
Identification: SSCC and GS1-128 barcodes. A logistic unit (pallet, parcel) is identified by an 18-digit SSCC, usually printed as a GS1-128 barcode. Related tests: uniqueness of the number, check digit calculation, readability of the printed label, match between the label and the despatch advice.
WMS and TMS integrations. When warehouse and transport run on two separate systems, the boundary between them concentrates defects: an order sent twice, weights or dimensions rounded, a carrier chosen on stale data. These exchanges are tested through APIs and files, including when one of the two systems is unavailable.
Electronic freight transport information. Regulation (EU) 2020/1056 (eFTI) sets a framework for communicating regulatory information on freight transport electronically to the authorities. For the vendors concerned, the completeness and accuracy of that data become test requirements.
An example test case: the check digit of an SSCC. The 18th digit of an SSCC is a check digit computed with the GS1 method: starting from the right, the first 17 digits are multiplied alternately by 3 and 1, the results are added, and the check digit is what is needed to reach the next multiple of ten. With a fictitious company prefix, the 17 digits 10614141000000123 give a sum of 62 and therefore a check digit of 8: the full SSCC is 106141410000001238. Tests feed the label module with serial numbers chosen to produce every check digit from 0 to 9, then check that the same 18 digits appear in the GS1-128 barcode after application identifier (00), in the human-readable line under the barcode and in the despatch advice. A label that scans correctly can still leave the receiving warehouse unable to match the pallet to its despatch advice.
Real time and peak load: test before the season
A peak day is not a normal day multiplied by three: picking waves overlap, carriers bring their collection times forward, customers check tracking continuously. We build the load scenario from that profile (orders per hour, scans per minute, tracking calls), then run it with k6 several weeks before the season.
Two criteria matter as much as response time: no message lost in the queues, and a clean catch-up when a system restarts after an outage. A load test that does not check the final stock only tells half the story.
How do we organise testing for logistics software?
- Map the flows before the screens. We draw the exchanges between systems and rank each boundary by the impact of a defect: wrong stock, blocked parcel, incorrect carrier invoice.
- Test messages as contracts. API and EDI file tests against partners' guides; Playwright for control screens and portals, k6 for peak-day load, all launched by your pipeline.
- Data that looks like the shop floor. Fictitious items, locations and orders, but with real cases: oversized parcels, items without a barcode, incomplete addresses.
- AI, with a review. An assistant helps generate EDI message variants and error cases. Proposed tests are checked with our 7-question checklist; see also our case study: from a PDF specification to Playwright tests.
Where should you start?
The first workstream is often the most fragile boundary, where incidents keep recurring: between warehouse and transport, or between the online shop and the warehouse.
A QA audit reviews your application: a written assessment, a test strategy adapted to your industry and a costed action plan, in 5 days, for €1,000 excl. VAT as a fixed fee. Delivered remotely, in English or French, for companies in the US, the UK, Canada, Australia, Europe, the Gulf and the Nordics. The first scoping session is free.
See the QA audit at €1,000 excl. VAT
Frequently asked questions about logistics software testing
What should be tested first in logistics software?
Stock accuracy at every movement, exchanges between systems (duplicates, delays, malformed messages), physical cases (stock-outs, back orders, returns) and behaviour under load before peak periods.
Does logistics software need load testing?
Yes, before every peak period. A tool such as k6 can replay a busy day's volume and check response times and that no messages are lost.
How do you test EDI exchanges with a partner?
Starting from their implementation guide: each message sent is validated segment by segment, then error cases are replayed (duplicate message, out of sequence, missing mandatory field, different version). A partner simulator lets you test without waiting for the partner to be available.
How do you test a pallet label (SSCC)?
By checking the uniqueness of the number, its check digit calculation, the readability of the printed barcode and the match between the label and the despatch advice sent to the recipient.
How much does a QA audit cost at AutomationDataCamp?
The QA audit and diagnosis costs €1,000 excl. VAT as a fixed fee, over 5 days: a written assessment, a test strategy and a costed action plan. The first scoping session is free.
Other industries: Healthcare · E-invoicing · Finance · Blockchain · E-commerce · Document management. All industries.
Page signed by Oussama Belakhdar, written with the help of AI. Regulatory references link to the official sources above; they are not legal advice.
Related articles

AI & ML for test automation
What AI concretely changes in test automation.
Read more : AI and ML for test automation
Integrating Automation into CI/CD
Jenkins, GitLab CI, GitHub Actions — practical examples.
Read more : Integrating Automation into CI/CD