Warehousing ERP Consultant, India

Moving a floor from registers to barcode scanning

Many Indian warehouses still run on a handwritten inward register at the gate, a material movement register on the floor and an Excel sheet that the accounts team reconciles to the ERP. Stock is booked when the paperwork reaches the office, which can be the next day. Pickers work from printed lists, and bin locations, if they exist, live in the heads of senior staff.

I recommend introducing scanning in stages rather than all at once:

1. Label every rack, level and bin with a code that matches the system exactly.
2. Start scanning at receiving and dispatch, where errors are most expensive.
3. Add scanned putaway so every received pallet or carton has a known location.
4. Move picking to scanner-directed tasks, with the system rejecting wrong items.
5. Replace the annual physical count with cycle counts by zone.

Item barcodes need attention too. Imported and branded goods usually carry them, but loose items, spares and private-label stock often do not, so the warehouse prints its own labels. Units of measure must be clear: piece, inner box, carton and pallet, each with a defined conversion. I document this in a BRD through requirements gathering and agree each stage's success measure with the warehouse manager before the next one starts. The Odoo Inventory India page covers godowns, GST registrations and e-way bills; this page stays inside the building.

Contract manpower, shifts and multilingual crews

Indian warehouses often rely on large crews supplied through manpower contractors, working in multiple shifts with significant turnover. Loaders, pickers and packers may speak different languages, and some have limited experience with handheld devices. A system designed for a small, stable, English-reading team will struggle here.

Scanner workflows for these floors should be short and visual: one instruction per screen, scan confirmation for every item and location, clear error sounds and minimal typing. Where the platform allows, screens in Hindi or a regional language can help, though this should be checked rather than assumed. Supervisors carry the most responsibility, so I train them first and make them the owners of exception handling, while operators learn only the tasks they perform.

Productivity data by person and shift helps manage contract crews and verify the manpower contractor's own invoices. Compliance for contract labor, including registers and statutory payments, sits with your HR and legal advisors, not the warehouse system. Safety is similar: fire safety arrangements and racking inspections are managed by your facility team, but damaged or unsafe locations should be blocked in the system as soon as they are reported. I include these exception paths in training material so new joiners learn them in their first week.

Bonded warehouses, FTWZ units and customs-controlled stock

Importers and 3PLs in India use customs bonded warehouses to defer duty until goods are cleared for home consumption or re-exported, and free trade warehousing zones to hold goods for trading, distribution or re-export, with duty arising only when goods move into the domestic tariff area. The procedures, documentation and permissions for each are set by customs and SEZ rules, which your customs broker and chartered accountant should confirm.

For the warehouse system, these schemes create the same core requirement: stock under customs control must be identifiable by status, location and the bill of entry or other reference it arrived under. I design:

• separate statuses and locations for bonded, FTWZ and duty-paid stock
• the inbound reference captured at receipt and carried on each lot
• movement types for clearance, re-export and inter-unit transfers
• balance reports by client, reference and period for audits and reconciliation

Partial clearances are common, so the system must track quantities cleared against each inbound reference rather than treating the whole consignment as one unit. The India logistics ERP page handles the clearance and container freight side of the same imports.

Cold storage, marketplace inbound and multi-client billing

Cold storage in India serves pharmaceuticals, vaccines, dairy, frozen foods, seafood and fresh produce, and much of it operates as multi-client facilities. Food storage requires FSSAI licensing and pharmaceutical storage follows drug regulations, both of which your quality and regulatory teams interpret. The system then enforces their rules: batch and expiry at receiving, temperature zones as location types, first-expiry-first-out picking and hold statuses for any excursion.

Brands selling on marketplaces also need warehouses that can prepare inbound shipments to marketplace fulfillment centers. Those shipments carry appointment slots, labeling and packaging rules that change over time, so I treat them as a configurable outbound profile rather than hard-coding them.

For 3PL operators, billing ties it together. Contracts in India commonly combine storage per pallet or square foot, handling charges, value-added work such as kitting or relabeling and transport arranged on the client's behalf. I break every contract into the activities it charges for and the quantity each is measured by, and your chartered accountant confirms the GST treatment of each charge. A parallel month, comparing system-calculated charges with what was invoiced manually, often reveals revenue that was never billed. The India eCommerce ERP page covers the marketplace sales side.

Choosing between ERP warehouse functions and a WMS

Many Indian businesses first try to run the warehouse inside the accounting system they already use, which works until bins, scanning and multiple clients enter the picture. The options then are an ERP with proper warehouse functions and a mobile scanning app, a dedicated WMS connected to the ERP, or a combination where the WMS runs the floor and the ERP handles finance and GST.

The deciding factors are familiar but weighted differently here: the size and stability of the floor team, the number of clients, order volumes from marketplaces, the presence of bonded or FTWZ stock and the budget for hardware such as handhelds and label printers. I compare options with scripted Indian scenarios, including a partial bonded clearance, a marketplace inbound shipment and a monthly client invoice, as part of ERP evaluation.

Workshops and reviews happen remotely over video, supported by recorded floor walk-throughs timed around your shifts. To see the underlying method, visit the warehousing ERP overview; ERP consulting for Indian companies lays out engagement models, and the India section covers the wider market.