How do you choose a WMS for a D2C brand in India?
Updated:
Short answer: Choose a WMS by testing it on your own orders, not a demo script. A D2C brand in India should check scan-checked picking and packing, marketplace labels and manifests, stock sync back to every channel you sell on, order allocation across locations, returns QC and expiry handling, then pilot it on one site before switching over.
In Fretron CommerceOS, pickers scan the bin, then the item or serial, and each piece is scanned again at the pack bench before the carton is closed.
A warehouse management system (WMS) records where every unit sits and directs the work on the floor: receiving, putaway, picking, packing, dispatch and returns. For a D2C brand, the WMS also decides whether the stock your marketplaces and webstore show for sale is the stock actually on the shelf. That is why a D2C brand should judge a WMS on its order flow, not on its feature list.
If you want a general scoring sheet covering GST, ERP links and 3PL needs, use the India WMS buyer's scorecard. This guide covers the warehouse-ops checks a D2C brand should run on top of it.
When does a D2C brand need a WMS?
Most brands start with spreadsheets and the seller panels of each marketplace. These are the usual signs that this has stopped working:
- The stock in your sheet, on the shelf and on each channel no longer match, and you cancel orders after a sale because the item was not there (overselling).
- Wrong items, wrong sizes or missing pieces reach customers, and you cannot tell whether the fault was at picking or packing.
- Returns pile up because nobody knows which units can go back on sale.
- You now hold stock in more than one place: your own warehouse, a 3PL, a store or a marketplace fulfilment centre.
- You sell products with a shelf life and need to ship the earliest expiry first (FIFO and FEFO).
- Sale days take extra staff, and new people cannot work without someone senior watching them.
The D2C WMS checklist: what to check and how to test it
Ask each vendor to run these on your own SKUs and orders, using your own labels.
| Area | What to check | How to test it in a demo |
|---|---|---|
| Receiving and GRN | Receipt against the purchase order or ASN, a GRN, and QC that can accept, reject or quarantine each piece | Receive a short-shipped PO with one damaged unit |
| Putaway and bins | Rules that direct each SKU to a bin, and stock held at bin level | Put away a mixed carton and ask where each SKU goes and why |
| Picking methods | Single-order, batch, cluster and zone picking, plus waves. A scan of the bin and then the item at every pick | Load a sale-day mix of single-item orders and see how they are grouped |
| Batch and expiry | Where FEFO is applied: when stock is reserved, when it is picked, or both | Hold two batches with different expiry dates and see which one is reserved and whether a wrong-batch scan is stopped |
| Packing | A scan of each piece at the pack bench before the carton is closed, with the packing slip, invoice and label produced at the bench | Scan the wrong size at packing and see what happens |
| Labels, manifests and handover | Marketplace-generated labels and courier labels from one screen, and a scan of each carton onto the shipping manifest at handover | Take one marketplace order and one webstore order all the way to courier handover |
| Marketplace and webstore sync | Orders pulled in and stock pushed back to each channel you sell on, SKU mapping, and what happens to an unmapped SKU | Change stock on one SKU and ask when each channel will show it, and what limits each channel sets |
| Order allocation | Which warehouse fulfils which channel location, split shipments, backorders and order holds (order allocation) | Place an order where one SKU is out of stock at the main site |
| Returns and RTO | QC on each returned unit, a disposition per line, restock to sellable stock, and a link back to the original order | Process a used customer return and an undelivered RTO parcel |
| Counts and audit | Blind cycle counts, adjustments with a reason, and a stock ledger you can trace | Count a bin that has a variance and follow the adjustment |
| Devices | Handheld scanners or Android phones, behaviour when the network drops, and where labels print | Scan in the aisle with the weakest signal |
| Sale-day peaks | How waves are released, how temporary staff are trained, and what the vendor's support covers on sale days | Ask how a new picker is trained and who answers the phone on a sale day |
| ERP and accounts | How stock, invoices and returns reach your ERP or accounting system: API, webhooks or file, and who builds the mapping | Ask for a sample export of one day's dispatches |
| Rollout | SKU master and bin set-up, opening stock count, channel connections, training, a pilot and the cutover plan | Ask for a written plan with named steps, owners and what your team must supply |
Questions to ask WMS vendors
- Can you run a demo on our SKUs, our bin layout and a sample of our real orders?
- Which of our sales channels are connected in production today, and which are planned? What does each connection pull in and push back?
- How often is stock pushed back to each channel, and what limits does each channel put on that?
- What happens to an order for a SKU that is not yet mapped?
- At which steps does the system ask for a scan, and what happens when a picker or packer scans the wrong item?
- Where is FEFO applied: when stock is reserved, at the pick scan, or both?
- Can the floor team work on Android phones? What happens when the network drops, and where do labels print?
- How are returns checked, and how does a returned unit get back into sellable stock?
- How does data reach our ERP or accounting system, and who builds and maintains that mapping?
- What does onboarding include, what do you need from our team, and can we pilot one site or one channel first?
- What support do you give on sale days, and how do we reach it?
- How is pricing set: per order, per user, per site or per channel? What costs extra?
Red flags when choosing a WMS
- The vendor won't walk through how your own SKUs and order types would run, only its own script.
- "Real-time sync with every marketplace" with no list of which channels are in production use today and which are planned.
- No scan at packing, or a scan that can be skipped without a supervisor seeing it.
- FEFO is mentioned, but nobody can show where it is applied.
- Returns go straight back into sellable stock with no QC step.
- Stock can be edited without a reason and without a trail.
- Onboarding promised in a fixed number of days before the vendor has seen your SKU count, channels and locations.
- The ERP connection is described as "plug and play", but nobody can say who maps the fields.
Do you need a WMS, an OMS or both?
An order management system (OMS) takes orders from every channel and decides where each one ships. A WMS runs the work inside the warehouse. A brand selling on many channels from one warehouse often feels the OMS gaps first, such as overselling and orders stuck between systems. A brand with picking and packing errors feels the WMS gaps first. Many D2C brands need both working on the same order record. Read OMS vs WMS for D2C brands, and for the OMS side, the order management software buyer guide.
How does Fretron CommerceOS fit?
Fretron CommerceOS is order, warehouse and shipping software for Indian consumer brands, running orders, warehouse and delivery on one live record beside your ERP. There is no prebuilt ERP connector. ERP data moves through Fretron's REST API, webhooks or CSV, with the mapping set up per customer.
Here is what it covers from the checklist above:
- Inbound stock is received against the ASN with a GRN, and QC can accept or reject each piece and quarantine it.
- Putaway is directed to zone-compliant bins by product type.
- Picking can run single-order, batch, cluster or zone, and orders can be grouped into scheduled waves. Pickers scan the bin, then the item or serial.
- Stock is tracked by batch and expiry date, and orders can be reserved first-expiry-first-out (FEFO) when they are allocated.
- Each piece is scanned at the pack bench before the carton is closed, and cartons are scanned to the courier manifest at handover.
- When stock changes, the available quantity is recalculated and pushed to each connected channel automatically, in batches within each channel's limits. It's designed to reduce overselling.
- Each channel's SKUs and locations are mapped to your catalogue and warehouses; an unmapped SKU doesn't come in until you map it.
- Orders are confirmed and allocated per facility, with stock reserved first-in-first-out or first-expiry-first-out (FIFO/FEFO). An allocated order line can be split across facilities.
- In Fretron CommerceOS, returns come back through QC on the same record, with a disposition recorded per line.
- Cycle counts in Fretron CommerceOS are blind counts taken on the phone and posted from the office, not updated with each scan.
- Your warehouse team works the floor on a phone — fifteen scan stations from gate entry to dispatch handover. No handheld hardware required. There is no printing from the phone and no iOS app.
- Onboarding scope is set per account.
See the warehouse management system, the full Fretron CommerceOS suite and CommerceOS pricing. To compare Fretron CommerceOS with other systems, see the comparison hub.
Frequently asked questions
- What is a WMS for a D2C brand?
- A warehouse management system (WMS) records where every unit sits in your warehouse and directs receiving, putaway, picking, packing, dispatch and returns, usually by barcode scan. For a D2C brand it also has to keep the stock shown on marketplaces and your webstore in step with the stock on the shelf.
- When should a D2C brand move from spreadsheets to a WMS?
- Move when stock in your sheet, on the shelf and on your channels stops matching, when wrong items or sizes reach customers, when you hold stock in more than one place, or when you sell products with an expiry date and need to ship the earliest batch first.
- Do I need a WMS or an OMS first?
- An OMS takes orders from every channel and decides where each ships. A WMS runs the work inside the warehouse. If your main problem is overselling across channels, look at the OMS first. If it is picking and packing errors, look at the WMS first. Many D2C brands need both on the same order record.
- Can a WMS run on Android phones instead of handheld scanners?
- Yes, a phone camera can scan barcodes. Test it on your own labels, aisle connectivity and printing needs first. With Fretron CommerceOS, your warehouse team works the floor on a phone — fifteen scan stations from gate entry to dispatch handover. No handheld hardware required. There is no printing from the phone and no iOS app.
- How long does WMS implementation take?
- It depends on your SKU count, locations, channels and ERP links, so ask each vendor for a written plan before you accept a date. The plan should name the SKU master and bin set-up, channel connections, opening stock count, training, a pilot and the cutover. With Fretron CommerceOS, onboarding scope is set per account.
- What should I ask WMS vendors in a demo?
- Ask them to run your own orders: a multi-item order, a pick with a wrong-item scan, a return, and a stock change pushed to each of your channels. Then ask what each step needs from your team and which of your channels are connected in production today.
- How do I compare WMS software on picking and packing accuracy?
- When comparing order and warehouse software for picking and packing accuracy, check what the system makes the team scan: the bin and the item at pick, and every piece at the pack bench before the carton is closed. In Fretron CommerceOS, pickers scan the bin, then the item or serial, and each piece is scanned at the pack bench before the carton is closed.
- Should a D2C brand use a 3PL or run its own warehouse?
- Use a 3PL when you want storage, picking and shipping handled by someone else and paid per order or per unit stored. Run your own warehouse when you want control of stock, packing quality and dispatch cut-offs; then you need warehouse software for receiving, bin locations, picking, packing and courier handover, linked to your sales channels. Fretron CommerceOS is order, warehouse and shipping software for Indian consumer brands, running orders, warehouse and delivery on one live record beside your ERP. There is no prebuilt ERP connector. ERP data moves through Fretron's REST API, webhooks or CSV, with the mapping set up per customer.
- What is a GRN in a warehouse?
- A goods received note (GRN) records what actually arrived against the supplier's purchase order or advance shipping notice (ASN). Receivers count or scan each item, note shortages, extras and damage, and send doubtful items to quality check or quarantine. Stock becomes available to sell only after the GRN is posted and the items are put away. In Fretron CommerceOS, inbound stock is received against the ASN with a GRN, and QC can accept or reject each piece and quarantine it.
- How much does a WMS cost in India?
- Many WMS vendors in India charge a monthly or annual subscription, priced on some mix of order volume, warehouses, users and modules, plus a one-time fee for setup, integrations and training. Get a written quote at your normal and peak order volumes, and check which channel and courier connections, support and sale-day help are included. For Fretron CommerceOS, pricing is worked out one-on-one, with founding-partner terms for early brands.
See how your orders would run in Fretron CommerceOS.
Bring a sample of your SKUs and a day's orders to the demo, and we will walk through how they would be received, picked, packed and synced to your connected channels.
Book a demo →