Honey ShelfCatalogue & data
Products, BOMs, and materials
Product statuses (including do-not-order), how BOMs and versions work, and where reorder points come from.
Products
A product has a SKU, name, category, optional collection tag (SS25, FW24), and size variants. Its status is active, archived, or do-not-order. Do-not-order blocks exactly three things: NEW production orders, order suggestions, and low-stock alert digests — the product stays visible everywhere, keeps its history, and store sync is untouched. Archive is for products you are done with entirely.
BOMs
Each product has ONE bill of materials, shared by all its sizes — quantities are per finished unit and should include waste and scrap. Saving BOM changes creates a new active version and marks the old one superseded; work orders keep the version they were created with, so mid-production edits never change what a running order consumes. Materials check, shortfalls, purchase suggestions, and product cost all calculate from the active BOM.
Materials and suppliers
Raw materials carry a unit (free text — kg, metres, cones), a unit cost, a reorder point, an optional GST rate and minimum order quantity, and a primary supplier. Lead time comes from the material's own override or its supplier's default — keep these realistic, because reorder points and suggested orders are computed from them. BOMs and POs must use the same unit per material; Honey Shelf does not convert units.
Reorder points
Auto-calculated as daily velocity × (lead time + safety buffer, default 7 days). You can override the number per product in the Catalogue or Settings → Inventory; clearing the override returns to auto.
Custom product fields
Attach your own data points to products — fabric composition, wash care, designer, HSN variant, anything. Admins define up to 30 org-wide fields in Settings → Product Fields, each typed as text, number, select (with your own option list), or date; values are entered per product in the Catalogue row's Details section and are always optional. Renaming a field keeps every saved value; archiving hides the field but retains values, which reappear on un-archive. If a select option is removed after products used it, those products keep the old value (shown with a "no longer an option" hint) until you pick a current one. Filtering and searching by custom fields, and custom-field columns in the CSV import, are planned for a later release.