Product businesses live with awkward timing. The customer can be billed before everything is ready, stock can be short, or one order can leave in several batches. Treating invoice status as fulfillment status makes the inventory number lie.
Lynka gives the outbound event its own record so the commercial sale and the physical stock movement can agree without being forced to happen at the same moment.
Stocked products carry inventory quantity and cost in addition to selling information. Services and non-stocked items can still appear commercially without pretending they occupy warehouse shelves.
That distinction determines which invoice lines should create physical movement later.
Products can appear on quotes and invoices with quantities and commercial pricing. Those documents explain the sale; inventory explains the physical movement.
A partial shipment should not require someone to edit the invoice merely to make stock look correct.
Fulfillment can be created from the invoice and its product quantities. Partial quantities are supported, so one invoice can be fulfilled in more than one outbound event.
That gives operations a concrete record of what is being sent today while the remaining quantity stays visible.
For stocked products, fulfillment can respect the workspace negative-stock policy. When negative inventory is disabled, insufficient quantity prevents the outbound posting.
That small control matters when sales and purchasing decisions depend on the on-hand number being believable.
Posted fulfillment creates outbound inventory movement for stocked products. Services and other non-stocked items do not create fake warehouse activity.
Movement history can then explain why on-hand quantity changed and trace the change back to the customer fulfillment.
When accounting is enabled and configured for it, fulfillment can use the recorded product-cost snapshot for cost-of-goods and inventory-value postings.
That gives margin reporting a stronger basis than looking only at the selling price on the invoice.
A fulfillment can be voided through its own process rather than deleting the original outbound event from history. That preserves the trail when something was posted incorrectly.
Lynka is not a full warehouse-management system: bins, waves, carrier orchestration and advanced pick-pack-ship belong in specialist software. This workflow is about keeping invoice and stock movement honest.
Yes. Fulfillment can record partial quantities instead of requiring the full invoice quantity to leave at once.