Multi-warehouse, multi-bin, batch and expiry tracking, safety-stock reordering and an audit trail on every movement. When the count is off, you can trace the transaction instead of writing it off.
A stocktake is not a counting problem. It is a question of whether the system can explain every unit that moved.
Stock by site, by zone, by bin. Pick and put-away against a location, so "we have 60" becomes "we have 60, and 12 of them are in the wrong place".
Batch or lot on receipt, FEFO suggestion on issue, and tiered 30/15/7-day near-expiry alerts. Markdown pricing can be triggered from the alert.
Reorder point per SKU per store, based on a rolling sales window you set. Suggested purchase quantities land in the purchasing module, not in a notebook.
Request, approve, dispatch, receive — each step timestamped and attributed. In-transit stock is visible separately, so it is neither double-counted nor missing.
Count a category at a time instead of closing the shop for a full stocktake. Variances post as adjustment documents with a reason code.
Every receipt, issue, transfer, adjustment and sale in one ledger per SKU, with user, timestamp and source document.
Only the fourth is a data-cleaning problem. The first three are process problems, and each one has a control in the system: mandatory goods receipt against a purchase order, returns that must reference the original invoice, and transfers that stay in a pending state until the receiving store confirms.
If you are migrating from spreadsheets, expect the first stocktake to disagree with your old numbers. That is not a bug — it is the first time anyone has had a complete picture.
| Level | Tracked | Typical use |
|---|---|---|
| Product | Category, brand, unit, tax rate, default supplier | Everything |
| Variant | Size, colour, specification, grade | Apparel, hardware |
| Batch / lot | Production or receipt date, expiry, supplier batch | Food, pharmacy, cosmetics |
| Serial | Individual unit identifier, warranty start | Electronics, machinery |
| Location | Warehouse, zone, bin | Multi-site, larger stores |
| Movement | Type, quantity, user, document, timestamp | Audit and discrepancy tracing |
Yes. A product can carry a base unit plus purchase and sales units with conversion factors — piece, box, carton, pallet, kilogram. Conversion applies on receipt and on issue independently.
Alerts appear in the dashboard and can be routed by role and by store. Tiered thresholds mean the 30-day list is a planning tool while the 7-day list is an action list.
Yes, stock can be flagged as owned, consigned in, or consigned out so it is excluded from your valuation while remaining visible on site.
Send a spreadsheet with your SKUs, descriptions, units and prices. We map it and load it during onboarding, including the awkward ones — variants, multi-unit pricing and per-store prices.
We load a sample into a trial so you can see your own catalogue in the system before deciding anything.
Request a free trial WhatsApp us sales@gdyun.online · Reply within one business day · Support 09:00–21:00 GMT+8