| Order date | Channel | Order no. | Product | Qty | Units | Batch | Packed on | Dispatch | Status |
|---|
Product master
| Code | Product name (Tally) | MRP ₹ | EAN | Batch code | Type | Made of | Active | Names |
|---|
Combo = several different products sold as one item. Multipack = several of one product. Tick “stock from components” when the godown keeps only the single packs.
Customers & portals
| Name | Type | Pickup | Stock held | Sales report upload | Names in files | Warehouses | Active |
|---|
Type decides where it appears: Retail portal and Own channel in Retail Orders; B2B customer in Purchase Orders; Own godown and anyone with “Stock held” get warehouses and stock.
Warehouses
| Customer / portal | City | Warehouse | Names on PO ship-to | Names in sales / inventory files | Active |
|---|
One name per line. A PO’s ship-to and the warehouse names in portal reports both point here, so GRN, sales and reconciliation land on the same warehouse.
Batches
| Product | Batch no. | Mfg | Expiry | Days left | Godown qty |
|---|
Mfg / Expiry record only. Batch numbers are still typed every time — this list never feeds a dropdown.
Portal names
Units = how many master packs one ordered item contains. Example: "Rajma 1 kg" = 2 × BC008 (500 GM). A combo can have several products.
| Portal | Name as received from portal | Master product × units | Order lines | State |
|---|
Couriers & transporters
| Name | Used for | Retail orders | PO shipments | Active |
|---|
Names typed on orders and shipments appear here automatically. Renaming one corrects it on every order / shipment. Untick Active to hide it from dropdowns.
| Name | User name | Role | Can open | New password | Active | Last login |
|---|
Sales entries
| Date | Customer · warehouse | Product | Qty | Value ₹ | Source | Remarks |
|---|
Uploaded sales files
| Uploaded | Customer | File | Format | Period | Rows | Qty | Value ₹ | Charges |
|---|
| Date | Portal | Order no. | Product (as in file) | Our order | Qty | Sale ₹ | GST ₹ | Fees ₹ | TCS ₹ | TDS ₹ | Net ₹ |
|---|
Other charges (ads, services, adjustments)
| Date | Portal | Type | Description | Order no. | Amount ₹ |
|---|
Saved reconciliations
| As on | Customer | File | Lines | Short | Excess | Diff value ₹ | Booked |
|---|
| Date | Customer · warehouse | Product | Direction | Qty | Open | Value ₹ |
|---|
Orders per day
Last 30 days, by packing dateRetail orders by channel
Last 30 daysNeeds attention
Top products, packs out
Retail + PO, last 30 days| Received | Type | Channel | Order no. | Product | Qty | Condition | Restock | Batch | Reason |
|---|
Balances
Click a product for its batches and ledger. If a product has an Opening entry, only movements from that date count.
| Code | Product | Opening as on | Inward | Retail out | PO out | Returns in | Balance | Nearest expiry |
|---|
Stock entries
Opening, inward and adjustments, newest first| Date | Type | Product | Batch | Qty | Mfg | Expiry | Note |
|---|
Click a row for its ledger.
| Customer | Warehouse | Product | In transit | Received | Transfer in / out | Sold | Damage / RTV | Book stock | Batches (oldest expiry first) | Cover (days) |
|---|
Entries
| Date | Customer · warehouse | Product | Batch | Qty | Source | Remarks |
|---|
Transfers
| Date | Customer | From → To | Product | Qty | Batches moved | Remarks |
|---|
RTV stock comes back to us: add it to the godown with a Stock entry in Godown stock.
Entries
| Date | Type | Customer · warehouse | Product | Batch | Qty | Reason | Ref no. |
|---|
| GRN date | Customer | PO no. | Product | Batch | Qty | Reason | Decision |
|---|
| Risk | Where | Product | Batch | Expiry | Days left | Qty | Note |
|---|
| Dispatch date | Invoice date | Consignee | Address | Invoice no. | PO / order no. & date | Invoice value | Transporter | Docket no. | Cartons | Weight kg | Cost w/o GST | Total with GST 18% | Rate / kg | Transport % |
|---|
| Customer | PO no. | PO date | Expiry | Ship to | PO qty | Dispatched | GRN | Fill rate | Next appt. | Status | Update |
|---|
1 · Choose file2 · Check3 · Import
Formats: Amazon / Flipkart order sheet, Website order sheet (Excel), Website export (Shopify CSV), Flipkart orders CSV. Detected automatically.
New portal names in file
| Name in file | Rows | Treat as |
|---|
Rows that need you
Bad dates: skipped unless fixed · Batch: imported as in file unless corrected| Issue | Sheet row | Order no. | Portal | Value in file | Fix | Skip |
|---|
Same order + product more than once
Quantities will be added together| Sheet row | Order no. | Product | Qty |
|---|
New portal product names
Check product and packs per item. Saved as confirmed on Import.| Portal | Name in file | Master product × packs | Rows |
|---|
Upload history
| When | File | Rows | New orders | New lines | Updated | Skipped |
|---|
One-time import: Ecom Tracker data
Choose ecom_tracker.db (it sits next to the Ecom Tracker’s main.py). You will check how its products and portals match ours before anything is saved. Its stock entries, sales, transfers, damage / RTV, batches, portal names and Amazon / Flipkart charges come in. Own-godown stock is skipped by default (godown stock lives in Godown stock here).