Ask any seller managing stock across a warehouse and a handful of marketplaces, and inventory is rarely the problem in isolation — the problem is that stock, HSN codes, and GST filings live in three different places that never quite agree. GST inventory software is meant to close that gap by tying what you hold in stock directly to what you report and file. This article covers what OneBooks GST already supports today around inventory-adjacent GST data, and the roadmap for full inventory management — item master, stock ledger, warehouses, and valuation.
As with any roadmap, treat the items below as planned direction, not a shipped feature list. We are describing them here so you can see how they are intended to connect to the GST and marketplace workflow already available.
What's live today around stock data
OneBooks GST does not yet manage stock quantities or item masters, but it already handles the GST-facing side of inventory-driven sales: marketplace sales imports from Amazon, Flipkart, Meesho, Myntra, AJIO, and JioMart carry SKU and product-level detail, and GSTR-1 preparation includes an HSN summary drawn from that sales data. In practice, many sellers today are already tagging products with HSN codes purely for filing purposes, without a connected stock system behind those codes. The roadmap below is about building that missing layer.
The inventory roadmap in detail
Item master and SKU mapping (planned)
A central item master — one record per product, with your internal SKU mapped to each marketplace's own listing ID — is the planned starting point. Today, a seller listing the same product on Amazon, Flipkart, and Meesho typically tracks three different SKU codes manually; the plan is for the item master to unify these under one internal product record.
HSN/SAC-linked stock (planned)
Because HSN and SAC codes already drive the GSTR-1 HSN summary, the roadmap ties each item master entry to its HSN or SAC code, so that stock movements and GST reporting draw from the same source instead of being tagged separately in two systems.
Stock ledger and warehouses (planned)
A stock ledger recording every inward and outward movement — purchases, sales, transfers, returns — per warehouse or storage location is planned, aimed particularly at sellers operating from more than one location or using marketplace fulfilment centres.
Valuation methods (planned)
How you value stock on hand affects both your balance sheet and your cost of goods sold. The roadmap includes support for standard valuation approaches:
| Method | How it works | Typically suits |
|---|---|---|
| FIFO (First In, First Out) | Oldest stock is treated as sold first; remaining stock is valued at more recent purchase cost | Businesses where costs rise steadily and matching physical flow to accounting flow matters |
| Weighted average | Stock is valued at the average cost of all units held, recalculated as new stock arrives | Businesses with frequent, small purchase batches at varying prices |
Both are common, accepted approaches; the right one depends on your business, purchase patterns, and what your accountant recommends.
Low-stock alerts (planned)
Once a stock ledger exists, threshold-based low-stock alerts are a natural addition, aimed at reducing stockouts on fast-moving marketplace listings without requiring manual stock checks.
What "roadmap" means here
Everything described above is a statement of planned direction, not a commitment to a specific release date. Feature priority on any roadmap can shift as regulations change, as customer feedback comes in, or as the underlying engineering work turns out to be more or less involved than expected. If accurate stock quantities and warehouse tracking are a hard requirement for your operations right now, continue using your current inventory system or spreadsheet alongside OneBooks GST's GST-side features, rather than planning around a specific rollout date.
How this is meant to connect to GSTR-1 and accounting
The design intent is that inventory should not become a fourth disconnected system. Stock movements recorded against an item's HSN code are meant to reconcile directly against the HSN summary already produced by GSTR-1 automation, so a mismatch between what you filed and what you actually sold becomes visible rather than something discovered during an audit. On the accounting side, stock valuation is planned to feed cost of goods sold on the profit and loss statement described in our accounting software roadmap, so inventory and books stay aligned rather than being reconciled manually at year-end.
Getting your data ready before the rollout
You do not need to wait for the feature to start preparing. A few habits now will make the transition smoother whenever item master and stock ledger features become available:
- Standardise SKU naming across your own records, even if each marketplace still uses its own listing ID.
- Assign HSN codes consistently at the product level rather than per-invoice, so the same product always carries the same code.
- Keep a basic running stock count today, in a spreadsheet if nothing else, so there is a known starting balance to migrate from.
- Note which warehouses or fulfilment locations you actually operate from, including third-party fulfilment centres that may carry your stock.
For sellers managing stock and GST across more than one registration, this pairs naturally with a clear approach to managing multiple GSTINs, since warehouses in different states are often tied to separate registrations.
A note on marketplace fulfilment stock specifically
Sellers using a marketplace's own fulfilment network face an extra wrinkle: stock physically sitting in a marketplace-operated warehouse in another state can itself trigger a GST registration requirement in that state, separate from your own warehouses. The planned stock ledger and warehouse tracking are intended to help make this visible by letting you record marketplace fulfilment centres as locations in their own right, rather than treating all marketplace-held stock as a single undifferentiated pool. Until that is available, keep your own record of which marketplace fulfilment centres are holding your stock and in which states, since this affects both your inventory visibility and your registration obligations.
Check the inventory software page for the latest status of these features, and the OneBooks GST plans page for how inventory capability is expected to be positioned across tiers as it rolls out.
Frequently asked questions
Can I track stock quantities in OneBooks GST today?
Not yet. Item master, stock ledger, and warehouse tracking are planned roadmap features. Today, the platform handles GST-side inventory data such as HSN summaries drawn from marketplace sales imports.
Which stock valuation method should I plan to use?
Both FIFO and weighted average are planned, accepted approaches. The right choice depends on your purchase patterns and is worth confirming with your accountant rather than defaulting to one method.
Will stock data connect automatically to my GSTR-1 filing?
That is the intent of the roadmap — tying stock movements to the same HSN/SAC codes already used in GSTR-1's HSN summary, so the two stay aligned rather than being maintained separately.
Do I need to prepare anything before inventory features launch?
Standardising your SKU naming, assigning consistent HSN codes per product, and keeping a basic stock count now will make any future migration smoother.
Will multi-warehouse tracking be supported?
Yes, that is part of the planned stock ledger functionality, aimed at sellers operating from more than one location or using marketplace fulfilment centres.
