From below par to purchase order — inventory and vendors in one flow

Inventory is only useful if it changes what you order and what you pay. When counts live in one place and purchase orders in another, the GM becomes the human API between systems.

The broken loop

A familiar pattern:

1. Manager completes a count on paper or in a spreadsheet
2. Someone texts the vendor or builds a PO in a separate tool
3. Delivery arrives — quantities do not match what was counted
4. Finance approves an invoice that does not tie to the PO

Every step is workable. The gap is shared data — same items, same locations, same audit trail.

Connected flow in Luminix

Luminix inventory and vendors share the item catalog and location context:

1. Count comes in below par for an item at a location
2. Exception surfaces in the portal queue for the GM or purchasing lead
3. Purchase order is raised against the vendor catalog — same SKU mapping
4. Receive against the PO when delivery lands
5. Finance sees matched spend — exceptions flagged, not buried

No re-keying SKUs. No "which spreadsheet was final?"

GM and purchasing roles

GMs often trigger the signal (count, waste, 86 from logbook). Purchasing or the GM acts on the PO depending on how you permission the store. Location-scoped roles keep each store autonomous while owners see consolidated spend.

Tips for rollout

• Align par levels per location before you go live on POs
• Map vendor catalog once — duplicates hurt every receive
• Start with top 20% of items by spend — prove the loop, then expand

Next steps

• Integrations overview
• Explore inventory module
• Book a demo