Logistics technology: WMS, TMS and ERP

In short

Logistics technology is the layer of software that plans, executes and records the movement and storage of goods: a WMS runs what happens inside the four walls of a warehouse, a TMS runs what happens between locations, and an ERP is the single transactional and financial backbone that both feed. Together they replace paper challans, Excel trackers and phone calls with scanned, time-stamped, auditable transactions, which is what makes inventory accuracy, on-time delivery and GST/e-way bill compliance possible at scale. The topic is examined in BBA/B.Voc logistics papers (Logistics Information Systems, Warehouse Management, IT in SCM) and in CILT/CSCMP-style professional syllabi, usually as definitions, module lists, WMS-vs-ERP comparisons, barcode/RFID, EDI and a numerical on storage or route cost. In Indian hiring it is the most practical screening topic: Flipkart, Amazon, Delhivery, DHL, Blue Dart, Mahindra Logistics, TVS SCS, Safexpress, Reliance Retail and DMart all ask which WMS/TMS/ERP a candidate has touched (SAP, Oracle, Blue Yonder, Manhattan, Increff, Unicommerce) and what an SKU, bin, ASN or e-way bill is.

Explained

What each system is and how the three fit together

• ERP (Enterprise Resource Planning): one integrated database and set of modules — finance, materials (MM), sales and distribution (SD), production (PP), HR — so a goods receipt automatically creates an inventory entry, a liability to the vendor and a tax record. Examples: SAP S/4HANA, Oracle Fusion, Microsoft Dynamics 365, Infor, and Indian products like Tally Prime, Zoho and Marg, plus open-source Odoo (a Belgian product), in SMEs.
• WMS (Warehouse Management System): execution software for storage and handling — receipt, putaway, bin-level stock, picking, packing, despatch, cycle counting, labour and dock management. Examples: Blue Yonder (JDA), Manhattan Associates, SAP EWM, Oracle WMS, Increff, Unicommerce, Vinculum, Eshopbox.
• TMS (Transportation Management System): execution and planning software for freight — load building, carrier selection, rating, routing, dispatch, tracking, ePOD, freight settlement and audit. Examples: Oracle OTM, SAP TM, Blue Yonder TMS, FarEye, LogiNext, Shipsy, Locus, Fretron.
• Division of labour (standard exam answer): ERP answers *how much do we own and what does it cost*; WMS answers *exactly where it is and who moved it*; TMS answers *how it gets there, with whom and at what freight*.
• Typical flow: ERP sales order → WMS picks and packs, confirms despatch → TMS plans the load, books the vehicle, tracks and delivers → actual freight and delivery proof flow back to ERP for invoicing and payment.
• Related systems often listed alongside: OMS (order management, channel orchestration), YMS (yard), LMS (labour), FMS (fleet maintenance), control tower / visibility platforms, and DMS (distribution/dealer management) in FMCG and auto.

Inside a WMS — modules and processes

1. Inbound: ASN (Advance Shipping Notice) from vendor → gate entry and vehicle check-in → unloading → GRN (goods receipt note) by scanning carton/pallet labels → quality inspection (accept/reject/quarantine) → pallet or handling-unit (HU) label generated.
2. Putaway: system suggests a bin by rule — fixed location, random/chaotic, zone (fast/medium/slow movers by ABC), nearest-empty, weight or temperature constraint, hazmat segregation.
3. Storage and slotting: master data of SKU (stock keeping unit), UoM conversions (each/inner/case/pallet), bin capacity, velocity class. Slotting places high-velocity SKUs in the golden zone (waist-to-shoulder height, near despatch) to cut travel time, which is 50–60% of manual picking labour.
4. Inventory control: batch/lot and expiry tracking, serial numbers, FIFO/FEFO/LIFO allocation, holds, kitting, re-packing, cycle counting (perpetual counting of a few bins daily, instead of one annual shutdown count).
5. Outbound: order release → allocation of stock → wave or waveless picking → pick method (piece/discrete, batch, zone, cluster, wave) → pick-path sequencing → packing and weighing → manifest and despatch, with invoice and e-way bill triggered from ERP.
6. Returns: reverse logistics — RTO/RVP in e-commerce, grading, refurbish, restock or scrap; a large WMS workload in Indian fashion and electronics, where return rates can run 20–30%.
7. Technology at the edge: handheld/ring barcode scanners, voice picking, pick-to-light, WCS/WES controlling conveyors, sorters, AS/RS, AMRs and shuttles (Addverb, GreyOrange, Armstrong in India).

Inside a TMS — modules and processes

• Planning: demand/order aggregation, load consolidation (FTL vs LTL vs milk-run), mode choice (road, rail, air, coastal, multimodal), vehicle-type selection against weight and volume limits, appointment scheduling.
• Procurement and rating: carrier contracts, rate cards by lane/weight slab/zone, spot bidding, indent placement and acceptance.
• Optimisation: route and sequence optimisation (a vehicle routing problem with time windows, capacity and driver-hour constraints), territory design, hub-and-spoke vs direct, backhaul matching to cut empty running.
• Execution and visibility: vehicle allotment, GPS/telematics and SIM-based tracking, geofenced gate events, temperature and door sensors in cold chain, ETA prediction, exception alerts (detention, deviation, long halt).
• Delivery: driver app, digital ePOD with photo/OTP/e-signature, attempt and reattempt handling, COD reconciliation.
• Freight settlement: auto-rating of the actual trip, three-way match (indent vs ePOD vs invoice), freight audit, detention/loading charges, debit notes for damage and shortage.
• Compliance built in (India): e-way bill generation and Part-B vehicle update, FASTag toll data, e-invoice IRN linkage, transporter GSTIN, driver licence/vehicle fitness checks.

ERP for logistics — the modules that matter

• MM (Materials Management): purchase requisition → PO → goods receipt (MIGO-type) → invoice verification → payment; vendor master, material master, valuation (moving average or standard price).
• SD (Sales and Distribution): customer master, sales order, availability check (ATP), delivery, picking, post goods issue, billing.
• WM/EWM and TM: warehouse and transport components inside the ERP, used when a separate best-of-breed WMS/TMS is not justified.
• Costing and MIS: freight cost per kg/per tonne-km, cost-to-serve by customer, inventory carrying cost, GST input credit — only reliable if logistics transactions post into ERP in real time.
• Integration patterns: flat file/FTP batch, EDI (ANSI X12 or UN/EDIFACT messages such as 940 warehouse shipping order, 945 shipping advice, 856 ASN, 214 shipment status), middleware/ESB, modern REST APIs and webhooks, and iPaaS connectors for marketplaces.
• Master-data discipline is the real project risk: one SKU code, one UoM set, one address format across ERP, WMS and TMS; duplicate or dirty masters break every downstream report.

Identification, data capture and tracking technology

• Barcodes: 1-D GS1 standards — EAN-13/UPC on retail consumer units, ITF-14 on cartons, GS1-128 carrying a GTIN + batch + expiry + SSCC (serial shipping container code) in application identifiers. 2-D codes — QR and GS1 DataMatrix — hold more data in less space and are now standard on pharmaceuticals.
• RFID: passive UHF tags read in bulk without line of sight; used in apparel retail (Shoppers Stop, Trent) and asset/pallet tracking. Costlier per tag than a barcode, affected by metal and liquid, so barcode remains the default for cartons.
• IoT and telematics: GPS, temperature and humidity loggers, door and fuel sensors, tyre pressure, driver-behaviour scoring. AIS-140 is the Indian standard specification for vehicle tracking devices and panic buttons in public-service vehicles.
• Other capture: OCR of documents, weighbridge and dimensioning (cubiscan) integration, ANPR at gates, computer-vision damage checks.
• Analytics layer: dashboards and control towers, descriptive → diagnostic → predictive (ETA, demand) → prescriptive (reslotting, route change); increasing use of ML for dispatch and address geocoding, digital twins for network design, and blockchain pilots for trade documents.

Indian regulatory and policy context

• GST and e-way bill: an e-way bill on the GSTN portal is required for most inter-State consignments above ₹50,000 (the threshold and intra-State rules vary by State, and some States set different limits — check the current State notification). Part-A is goods/invoice data, Part-B is the vehicle number; validity runs by distance, and the bill can be generated/updated through API by a WMS/TMS. GST rate slabs are 5%, 18% and 40% since 22 September 2025, with a nil/exempt category.
• e-invoicing: B2B e-invoices with an IRN and signed QR code are mandatory above the prescribed turnover limit (the limit has been lowered in stages — quote the current notification rather than a remembered figure); logistics software must carry the IRN on the despatch documents.
• ULIP (Unified Logistics Interface Platform) under the National Logistics Policy, 2022 and PM GatiShakti gives API access to government transport data (vehicle, permit, rail, port) so private TMS can validate and track; FASTag gives electronic tolling data.
• Labour Codes in force from 21 November 2025 (Code on Wages; Industrial Relations; Social Security; Occupational Safety, Health and Working Conditions) replaced the Factories, Minimum Wages, Industrial Disputes and BOCW Acts — warehouse labour-management modules must compute wages, overtime and records under these Codes, not the old Acts.
• Data and records: the Information Technology Act, 2000 gives electronic records and digital signatures legal validity (so ePOD and e-invoice are admissible); the Digital Personal Data Protection Act, 2023 governs consumer address/phone data held in OMS/TMS — notice, purpose limitation and retention discipline.
• Sector rules: drug traceability and barcoding for exported/notified drug formulations under Drugs and Cosmetics rules and the DGFT trace-and-track requirement; FSSAI licence and temperature records for food; Motor Vehicles Act, 1988 (as amended 2019) and the Carriage by Road Act, 2007 for goods carriage and carrier liability.

Benefits, limitations and selection

• Benefits: inventory accuracy typically rises from the 90–95% of manual systems to 99%+; fewer stock-outs and write-offs on expiry; higher picking productivity and lower travel; freight savings from consolidation, mode mix and route optimisation; audit trail for GST, recalls and claims; visibility that lets a control tower act before a customer complains.
• Limitations: high licence/implementation cost and 6–18-month projects; change management and training in a high-attrition workforce; dependence on network and device uptime; customisation debt that makes upgrades painful; garbage-in from bad masters; cyber and data-privacy exposure; small operators cannot justify full-scale systems.
• Build vs buy vs cloud: on-premise licence (capex, control) vs SaaS subscription (opex, fast go-live, standard processes, used by most Indian 3PLs and D2C brands); best-of-breed WMS/TMS integrated to ERP vs single-vendor ERP modules (simpler integration, fewer features).
• Selection criteria: functional fit to your flows, scalability in orders/lines per day, integration/API maturity, Indian statutory features (e-way bill, GST, State rules), multi-client (3PL billing) support, mobility, total cost of ownership, vendor support in India, and references in your industry.
• Implementation path: AS-IS study → process design and gap/fit analysis → configuration → master-data cleansing and migration → integration build → CRP/UAT → training → cutover (pilot site, big-bang or phased) → hypercare → continuous improvement.

Key points

• WMS - executes and records everything inside the warehouse at bin and batch level.
• TMS - plans, executes, tracks and settles freight between locations.
• ERP - single integrated transaction and financial backbone that both feed and draw master data from.
• Why not ERP alone - ERP tracks stock by plant/storage location and value; it lacks bin-level, task-level, labour and device control.
• SKU - the smallest uniquely identifiable stock item; the key on which all three systems join.
• ASN - advance shipping notice; lets the WMS pre-plan dock, labour and putaway before the truck arrives.
• Putaway rules - fixed, random, zone/ABC, nearest-empty, constraint-based (weight, temperature, hazmat).
• Slotting - placing fast movers in the golden zone to cut travel, which is 50–60% of manual pick labour.
• FIFO/FEFO - first-in-first-out by receipt date; FEFO by earliest expiry — mandatory for pharma and food.
• Cycle counting - counting a few bins continuously instead of an annual shutdown count; keeps accuracy live.
• Pick methods - discrete, batch, zone, cluster and wave; chosen by order profile (lines per order, volume).
• GS1 - global identification standard: GTIN, SSCC, GS1-128 and DataMatrix carry batch and expiry.
• RFID vs barcode - RFID is bulk, no line of sight, costlier; barcode is cheap, accurate, line-of-sight.
• EDI/API - machine-to-machine messaging (856 ASN, 940, 945, 214) or REST APIs/webhooks for real-time links.
• ePOD - digital proof of delivery (OTP, photo, signature) that closes the billing loop and cuts disputes.
• e-way bill - GSTN document generally needed above ₹50,000 consignment value, Part-A goods and Part-B vehicle; State rules vary.
• ULIP / National Logistics Policy, 2022 - government API platform for transport data under PM GatiShakti.
• Master data - the single biggest implementation risk; one SKU, UoM and address standard across all systems.

Formulas and examples

Example 1 — Inventory accuracy after a WMS go-live. A warehouse cycle-counts 1,250 SKU-bin records in a month; 37 do not match the system.

• Matching records = 1,250 − 37 = 1,213.
• Accuracy = 1,213 ÷ 1,250 × 100 = 97.04%.
• Pre-WMS accuracy was 92%, i.e. 100 mismatches in 1,250. Mismatches cut from 100 to 37 — a 63% reduction in error records.

Example 2 — Slotting saves travel time. A picker walks 1,100 m per 50-line pick list; after reslotting fast movers nearer despatch it falls to 790 m. Walking speed 1.1 m/s, 14 pick lists per shift.

• Saving per list = 1,100 − 790 = 310 m → 310 ÷ 1.1 = 281.8 s ≈ 4.70 min.
• Per shift = 4.70 × 14 = 65.8 min ≈ 1.10 hours saved.
• At ₹120 per labour hour, saving = 1.10 × 120 = ₹132 per picker per shift; for 20 pickers, 26 shifts a month → 132 × 20 × 26 = ₹68,640 per month.

Example 3 — Volumetric weight and the right freight. A carton 60 × 40 × 30 cm weighs 9 kg; surface courier divisor 5000, rate ₹28 per kg.

• Volume = 60 × 40 × 30 = 72,000 cm³ → volumetric weight = 72,000 ÷ 5000 = 14.4 kg.
• Chargeable weight = greater of 9 and 14.4 = 14.4 kg → freight = 14.4 × 28 = ₹403.20.
• If the TMS repacks it into 50 × 40 × 25 cm = 50,000 cm³ → 10 kg chargeable → ₹280, saving ₹123.20 (30.6%) on the same goods.

Example 4 — TMS consolidation and cost per tonne-km. Four LTL shipments of 2.5 t each run Pune → Hyderabad (560 km) at ₹9,200 per shipment. The TMS consolidates them into one 10 t FTL at ₹26,500.

• LTL total = 4 × 9,200 = ₹36,800; tonne-km = 10 t × 560 = 5,600 → ₹36,800 ÷ 5,600 = ₹6.57 per tonne-km.
• FTL = ₹26,500 → 26,500 ÷ 5,600 = ₹4.73 per tonne-km.
• Saving = ₹10,300 per consolidation = 28.0%; if this happens 3 times a week, 52 weeks → 10,300 × 156 = ₹16.07 lakh a year.

Example 5 — Payback on a WMS project. Licence and implementation ₹42 lakh, annual SaaS and support ₹9 lakh. Benefits: labour productivity ₹14 lakh, lower write-offs on expiry ₹7 lakh, fewer wrong-shipment penalties ₹5 lakh, lower safety stock carrying cost ₹6 lakh.

• Gross annual benefit = 14 + 7 + 5 + 6 = ₹32 lakh; net of running cost = 32 − 9 = ₹23 lakh.
• Payback = 42 ÷ 23 = 1.83 years ≈ 22 months.
• First-year ROI = 23 ÷ 42 × 100 = 54.8%.

Example 6 — EOQ and reorder level in ERP. D = 36,000 units/year, S = ₹1,250 per order, H = ₹40 per unit per year; lead time 12 days, safety stock 900 units, 300 working days.

• EOQ = √(2 × 36,000 × 1,250 ÷ 40) = √(90,000,000 ÷ 40) = √2,250,000 = 1,500 units.
• Orders per year = 36,000 ÷ 1,500 = 24; average daily demand = 36,000 ÷ 300 = 120 units.
• Reorder level = 120 × 12 + 900 = 2,340 units.

Where it is used

• E-commerce and quick commerce: Flipkart, Amazon, Meesho, Blinkit, Zepto and Instamart run WMS plus OMS plus last-mile TMS; dark stores use lightweight WMS with 10-minute pick-pack SLAs.
• 3PL and express: Delhivery, Blue Dart, DHL, Safexpress, Mahindra Logistics, TVS SCS and Allcargo use multi-client WMS (with activity-based billing) and TMS with ePOD; roles are WMS executive, control-tower analyst, transport planner.
• Retail and FMCG distribution: DMart, Reliance Retail, HUL, ITC and Dabur run ERP (largely SAP) with DMS for distributors, FEFO picking, and TMS for primary and secondary freight.
• Pharma and cold chain: batch/expiry and serialisation in WMS, temperature-logged vehicles and reefers, FSSAI/Drugs rules compliance — Sun Pharma, Cipla, Apollo, Snowman, Coldman.
• Manufacturing and auto: SAP MM/SD with EWM for line-feeding, milk-run inbound TMS, kanban and sequencing — Maruti Suzuki, Tata Motors, Bosch, Hero MotoCorp.
• Job roles that need this directly: WMS/ERP support and functional consultant (SAP MM/SD/EWM), transport planner, dispatch and control-tower executive, logistics MIS/data analyst, implementation and business analyst roles at Shipsy, FarEye, LogiNext, Locus, Increff and Unicommerce.

Interview questions

• Q: What is the difference between a WMS and an ERP inventory module? A: ERP holds stock by plant/storage location with its value for accounting; a WMS holds it by bin, batch and handling unit and directs the physical tasks of putaway, picking and counting.
• Q: Where does a TMS add value that a WMS cannot? A: Outside the four walls — load consolidation, mode and carrier selection, route optimisation, in-transit tracking, ePOD and freight settlement.
• Q: What is an ASN and why does it matter? A: An advance shipping notice sent by the supplier before despatch; the WMS uses it to pre-plan dock slots, labour and putaway so receiving becomes scan-and-confirm instead of count-and-key.
• Q: Explain FIFO versus FEFO. A: FIFO issues the oldest received stock first; FEFO issues the nearest-expiry stock first, which can be a later receipt — FEFO is the correct rule for food and pharmaceuticals.
• Q: Why would a company choose a best-of-breed WMS over the ERP's own warehouse module? A: For deeper functionality — slotting, labour management, multi-client billing, device and automation control — accepting the cost of building and maintaining an integration.
• Q: How does a WMS decide a putaway location? A: By configured rules — fixed bin, zone by ABC velocity, nearest empty bin of the right capacity, and constraints such as weight, temperature, batch mixing and hazmat segregation.
• Q: What is slotting and how do you measure its benefit? A: Repositioning SKUs by velocity and size so fast movers sit in the golden zone near despatch; the benefit is measured in travel distance per pick list and lines picked per labour hour.
• Q: What is the difference between EDI and an API integration? A: EDI exchanges standard structured messages, traditionally in batches over VAN/FTP; APIs exchange JSON/XML over HTTPS in real time with immediate acknowledgement — modern Indian logistics platforms are mostly API/webhook based.
• Q: Which data does a TMS need to generate an e-way bill? A: Invoice/document details, HSN, value, consignor and consignee GSTIN and addresses, distance, transporter ID and the vehicle number for Part-B.
• Q: Would you use RFID or barcodes in a carton-handling warehouse, and why? A: Barcodes by default — cheap, reliable and unaffected by metal or liquid; RFID only where bulk reads without line of sight pay for the higher tag cost, as in apparel retail or returnable assets.
• Q: A go-live caused stock mismatch in week one. How do you investigate? A: Freeze movements for the affected zones, compare the WMS opening balance with the migrated ERP balance, check cut-off transactions and in-transit stock, then cycle-count the bins and correct with documented adjustments rather than a blanket reset.
• Q: Why is master data called the biggest risk in a WMS or ERP project? A: Every rule, allocation and report keys off SKU, UoM, bin and address data; duplicate codes or wrong case quantities silently produce wrong picks, wrong volumes and wrong freight that no amount of software configuration can fix.
• Q: What is a control tower? A: A central team and dashboard that fuses WMS, TMS, ERP and carrier data to monitor exceptions in real time and intervene before SLAs are breached.

Common mistakes

• Describing a WMS and an ERP as alternatives — they are complementary layers, and exam answers must say so with the bin-level versus value-level distinction.
• Mixing up FIFO and FEFO, or assuming the nearest-expiry batch is always the oldest receipt.
• Forgetting volumetric weight when calculating courier freight, so the quoted cost is far below the bill.
• Confusing units in numericals — mixing tonnes with kg, cm³ with m³, or dividing cost by km instead of tonne-km.
• Claiming hardware alone fixes accuracy: scanners and RFID add nothing without clean master data and disciplined process steps.
• Quoting an e-way bill threshold or e-invoice turnover limit as universal — intra-State rules and limits have changed and vary by State and notification; state that it varies.
• Listing software brand names without being able to explain one end-to-end flow (order → pick → despatch → delivery → settlement), which is exactly what interviewers probe.
• Treating warehouse labour scheduling under the old Factories and Minimum Wages Acts, which the four Labour Codes replaced from 21 November 2025.

Related topics

• Logistics KPIs · Warehousing and material handling · Inventory management and EOQ · Transportation modes and freight costing · Supply chain integration and information flow (bullwhip effect) · E-commerce fulfilment and reverse logistics