Inventory and POS

Use This Dashboard Area Safely

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, Inventory and POS narrows that work to eMS LAN guide for inventory stock, point-of-sales transactions, and item records. Because this is a surfaces page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Logistics staff and Finance staff. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/inventory-tracking?id=:eventId and /rego/events/manage/point-of-sales?id=:eventId.
• Records or contracts involved: Inventory stock rows, POS transactions, and POS transaction items.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Inventory and POS.
2. Read the current state before changing it: Use /rego/events/manage/inventory-tracking?id=:eventId and /rego/events/manage/point-of-sales?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the smallest action that matches the task: Keep Inventory stock rows, POS transactions, and POS transaction items in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

Before You Leave The Screen

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook for inventory or POS during LAN operation.

1. Step 1 - Open the exact screen for the event. Confirm the device and page are using the correct event snapshot. This prevents stock or sales from being recorded under the wrong event.
2. Step 2 - Identify what the screen reads and writes. Check starting stock, POS item list, payment handling rules, and who owns cash or settlement follow-up. This sets the baseline.
3. Step 3 - Use one control at a time. Record stock movement or POS sale at the time it happens. This changes LAN-local stock and transaction records.
4. Step 4 - Check who or what was affected. Pause if stock goes negative, item price looks wrong, or payment evidence does not match the sale. This protects finance review.
5. Step 5 - Confirm the screen and history agree. Compare device totals with physical stock and payment notes during shift handoff. This catches drift before import.
6. Step 6 - Leave notes another operator can follow. Give final totals and unresolved mismatches to the import and reconciliation owner. This prepares finance checks.

What import can apply

Record group	Import meaning
Inventory stock rows	Updated stock state from LAN operation.
POS transactions	Sales or transaction records made offline.
POS transaction items	Item lines attached to POS transactions.