Click a module — its full detail opens in the panel below. The grid stays put.
Click a stage, or hit play to watch one cycle.
The loop never stops: once a sale drops stock below its par level, FMH flags it and you start the next order — automatically tightening cost on every turn.
FMH sits in the middle. Your POS tells it what was sold (so stock + COGS stay live); FMH tells your accounting what was bought (so the books stay current). No double entry.
🛎️ POS systems
INBOUND · sales → inventory
FMH pulls sales on a schedule (queue + cron; offline POS via SFTP file import), maps each POS outlet → FMH branch, syncs menu/recipe, then auto-deducts ingredients per sale → live stock & accurate COGS.
→
F
FMH
Procurement & inventory engine
→
📒 Accounting systems
OUTBOUND · purchases → the books
FMH pushes purchase invoices/bills, credit notes & vendor records, mapped to the customer's chart-of-accounts codes — so procurement spend is booked automatically, no re-keying.
Coverage: ~19 POS and ~18 accounting systems. The two columns above name the connectors live in the codebase. New ones are added as standalone adapters in the integrations layer.