OMS — Order Management System
An Order Management System (OMS) is the software layer that receives customer orders from all channels — D2C website, marketplaces (Amazon, Flipkart, Meesho), and retail — and routes each order to the right fulfilment node. It holds the single source of truth for order status from placement to delivery confirmation, including returns and refunds.
In Indian operations
In India, an OMS must handle marketplace SLA windows (Flipkart dark windows, Amazon dispatch cutoffs), COD order verification, and split-fulfilment across multiple warehouses or dark stores. It must also reconcile marketplace payment settlements — which include deductions for returns, penalties, and commission — against the original order.
Fretron's OMS starts with multi-channel order ingestion and routes each order to the optimal fulfilment node based on stock, SLA, and freight cost. See the full OMS at Fretron OMS.
WMS — Warehouse Management System
A Warehouse Management System (WMS) manages every physical operation inside a warehouse or fulfilment centre: inbound receiving, put-away, storage location management, picking, packing, and outbound dispatch. It eliminates paper-based processes and gives operations managers real-time inventory accuracy at the SKU and bin level.
In Indian operations
Indian warehousing has specific requirements the WMS must handle: GST-compliant inward and outward registers, multi-owner multi-client warehouses (3PL), zone separation for different principals, and FMCG expiry-date management. For quick-commerce dark stores, the WMS must support extremely fast pick cycles (10–15 minutes) across a narrow SKU catalogue.
Fretron's WMS runs beside your existing ERP (SAP, Oracle, Tally) without requiring a replacement. See Fretron WMS.
BOPIS and ROPIS
BOPIS (Buy Online, Pick Up In Store) and ROPIS (Reserve Online, Pick Up In Store) are omnichannel fulfilment models where a customer purchases or reserves online and collects in person at a retail store or collection point. They use retail store inventory as a fulfilment node, reducing last-mile delivery cost and improving same-day availability.
In Indian operations
BOPIS and ROPIS in India require a live store-inventory feed in the OMS, store-staff order notification, and a ready-to-collect confirmation workflow. Major Indian retailers (fashion, electronics, grocery) are adopting BOPIS to compete with quick-commerce delivery windows without incurring last-mile courier cost. The OMS must distinguish "ship to home" from "pick at store" flows and route accordingly.
Fretron's OMS supports BOPIS by routing online orders to the store nearest the buyer and triggering a pick-confirmation notification. This requires the order management system.
RTO — Return to Origin
Return to Origin (RTO) is what happens when a last-mile delivery fails — the customer is unavailable, refuses the package, or the address is undeliverable — and the courier returns the shipment to the seller's fulfilment centre or warehouse. In Indian D2C, RTO is one of the largest margin drains: the brand pays both the forward freight and the return freight, and must process the returned inventory.
In Indian operations
India's D2C RTO rates run 20–40% for high-COD categories (fashion, footwear) and 5–15% for prepaid-heavy categories (electronics, books). The drivers are: address quality in tier-2/3 cities, buyer behaviour on COD orders ("buyer's regret" returns), and carrier delivery attempt limitations. An effective RTO strategy requires: address validation at checkout, COD order verification (call/SMS confirm), carrier selection by serviceability density, and fast RTO reconciliation (returned unit back in available inventory within 24–48 hours).
Fretron tracks RTO events in real time on the control tower and routes the returned unit to the warehouse via the warehouse management system.
ONDC — Open Network for Digital Commerce
ONDC (Open Network for Digital Commerce) is an Indian government-backed open protocol that decouples buyer apps (Paytm, Meesho, Namma Yatri) from seller apps and logistics providers. Unlike marketplace platforms (Amazon, Flipkart), ONDC is not a marketplace — it's a network protocol. Any seller registered on ONDC can receive orders from any buyer app connected to the network.
In Indian operations
ONDC changes the logistics and OMS requirement for sellers: instead of receiving orders from a single marketplace API, an ONDC-enabled seller must handle orders from multiple buyer apps simultaneously, each with their own fulfilment SLA requirements. The OMS must ingest ONDC-protocol order events, match them to inventory, and dispatch via ONDC-registered logistics providers (Loadshare, Shiprocket, Delhivery). As of 2026, ONDC has processed over 100 million cumulative orders across food, grocery, and fashion categories.
Fretron's OMS supports ONDC as a channel alongside D2C and marketplace flows. See Fretron OMS for multi-channel order management.
Dark Store
A dark store is a fulfilment facility designed exclusively for online order picking — not open to retail customers. Dark stores are positioned inside or near dense urban areas to enable 10–30 minute delivery (quick-commerce). They carry a curated SKU catalogue (typically 1,000–5,000 SKUs vs 10,000+ in a supermarket) optimised for high-velocity FMCG, grocery, and daily essentials.
In Indian operations
India's quick-commerce sector (Blinkit, Zepto, Swiggy Instamart, BigBasket BB Now) runs on dark store networks. By 2026, Blinkit operates 1,000+ dark stores across 40+ cities; Zepto covers 80+ cities. The WMS requirements for a dark store are distinct from a traditional warehouse: sub-15-minute pick cycles, no put-away complexity (flow-through receiving), temperature zones for dairy and produce, and direct integration with rider dispatch. For brands selling on quick-commerce platforms, the OMS must also manage replenishment orders to dark stores alongside D2C and marketplace orders.
Fretron's warehouse and order management systems are built to support dark-store operations alongside traditional fulfilment centres. See Fretron WMS.
SKU Rationalization
SKU rationalization is the disciplined review of a product catalogue to remove or consolidate underperforming stock-keeping units (SKUs) — variants that sell too slowly, cannibalise other SKUs, or cost more to hold than they earn. The goal is a leaner assortment that concentrates working capital and warehouse space on the SKUs that actually drive revenue and margin.
In Indian operations
For Indian D2C and retail brands selling across marketplaces, quick-commerce, and their own D2C channel, SKU proliferation is a silent margin drain: every added variant multiplies inventory-holding cost, dark-store shelf pressure (a dark store carries only 1,000–5,000 SKUs), and forecast complexity. Rationalization uses sell-through rate, contribution margin, return rate (high-RTO variants are prime cull candidates), and channel-level velocity to decide what to keep, consolidate, or discontinue. A WMS and OMS that report SKU-level velocity and holding cost turn the exercise into a data-led decision rather than a gut call.
Fretron's warehouse and order data expose SKU-level velocity, return rate, and holding cost across channels — the inputs a rationalization review needs. See warehouse management software.
3PL — Third-Party Logistics
Third-party logistics (3PL) is the outsourcing of warehousing, fulfilment, and transportation to an external specialist provider. A 3PL stores a brand's inventory in its warehouses, picks and packs orders, and manages the handoff to carriers — so the brand operates without owning its own fulfilment infrastructure. Services range from warehousing-only to end-to-end fulfilment including returns processing.
In Indian operations
India's 3PL market spans national players and dense regional operators. For a growing D2C brand, a 3PL removes the capital cost of leasing warehouses across zones and the operational load of staffing them — but it introduces a visibility gap, because the brand's stock and orders now live in the 3PL's system. The fix is an order-and-inventory layer that reads status across owned and 3PL nodes as one position, so a brand isn't blind to stock sitting in a partner's warehouse. The 3PL facilities themselves run multi-client warehouse software with principal-wise zone separation and client-level billing.
Fretron gives brands one order-and-inventory record across owned and 3PL fulfilment nodes, so partner-held stock isn't a blind spot. See Fretron WMS.
NDR — Non-Delivery Report
A Non-Delivery Report (NDR) is the status a courier raises when a delivery attempt fails — the customer was unavailable, the address was wrong or incomplete, the phone was unreachable, or a COD order was refused. Each NDR needs a fast decision: reattempt, correct the address, contact the customer, or return the shipment to origin (RTO). Unmanaged NDRs turn into RTOs, and RTO is one of the largest margin drains in Indian D2C.
In Indian operations
NDR management is a distinct operational discipline in Indian e-commerce, because address quality in tier-2/3 cities and COD buyer behaviour push first-attempt failure rates high. Speed matters: most carriers hold an NDR shipment for only a short reattempt window before defaulting to RTO. An effective NDR workflow pulls the courier's NDR feed into the order record, triggers an automated customer contact (call, SMS, or WhatsApp) to confirm intent and address, and re-pushes the corrected instruction to the carrier before the window closes — cutting the share of NDRs that become RTOs.
Fretron surfaces NDR events on the order record and routes each to a reattempt-or-return decision before the carrier defaults to RTO. See order management software.
SLA Breach
An SLA breach occurs when an order misses a service-level agreement — the committed window for dispatch, delivery, or resolution. In commerce operations, the most costly breaches are against marketplace dispatch cutoffs and delivery-time commitments: a missed marketplace SLA can trigger listing penalties, suppressed search ranking, or account-health downgrades that cut future order volume, not just the one late order.
In Indian operations
Every Indian marketplace — Flipkart, Amazon, Meesho, Myntra — enforces its own dispatch and delivery SLAs, and quick-commerce platforms run the tightest windows of all. Because a breach damages account health and listing visibility, the operational goal is to catch at-risk orders before the cutoff, not to report breaches after they happen. That requires an order layer that clocks each order against its channel's specific SLA, flags the ones trending late, and routes them to the fulfilment node that can still make the window. A control tower makes trending breaches visible across carriers and warehouses in one exception queue.
Fretron clocks each order against its channel SLA and surfaces at-risk orders in a live exception queue before the cutoff. See the supply chain control tower.