Products can carry a name, description, SKU, barcode, brand, category, unit of measure, tags, image and custom fields. Lynka also distinguishes stocked items from non-stocked items and services so not everything sold is forced into quantity tracking.
That same product identity can be referenced by quotes, invoices, purchase orders, goods receipts and stock movements.
A product can store its selling price and current cost, which gives Sales and Finance the basic numbers needed to discuss price and margin without maintaining a second catalog.
For stocked goods, posted receiving can update the product cost using the weighted cost of prior stock and the newly accepted quantity at its base-currency cost.
Stocked products keep a current stock level and a minimum-stock threshold. The Reorder List uses that threshold to identify items at or below the level the business has chosen.
The report is an attention list, not an automatic purchase order. A buyer can still review incoming supply, sales activity and supplier terms before deciding what to order.
Each product can be connected to several suppliers. A supplier-product relationship can keep the vendor SKU, supplier price, currency, lead time, minimum order quantity and preferred-supplier flag.
That gives Purchasing a useful comparison on the product itself instead of burying alternate sourcing options in old POs or email.
Products can carry revenue, cost-of-goods-sold and inventory-asset account mappings.
Those mappings give Accounting a defined destination when invoicing, receiving or fulfillment produces an accounting effect.
Product reporting can show availability, reorder needs, incoming supply, value, margin, slow-moving stock and movement history.
The product catalog is therefore not only a setup screen. It is the common identity used by the operational reports that follow the item through buying, stock and sales.
A product can be treated as stocked, non-stocked or a service. Posted receiving only creates physical stock for stocked products, which prevents a service or non-stocked item from inflating warehouse quantity just because it appeared on a purchasing document.
The same catalog can therefore support what the business physically stores and what it sells without stock movement.
For posted receipts, Lynka can use the accepted quantity and a trusted base-currency unit cost to update the weighted average cost of a stocked product. The receiving record keeps the source cost, currency and rate behind that change.
That gives later product-margin and inventory-value reporting a cost basis connected to receiving activity instead of a cost field that never changes after setup.
A product catalog becomes expensive to maintain when every department keeps its own copy. Lynka uses one product identity across customer sales, supplier purchasing, receiving, stock movement and accounting.
Name, description, SKU, barcode, brand, category, unit of measure, tags, selling price, cost, stock level, minimum-stock threshold, supplier relationships, custom fields and accounting mappings.
