StationIQ Management
bridge armedCommander Raspberry Pi Appliance

Put the Raspberry Pi beside Commander and use it as the site-level bridge for transactions, webhook intake, and inventory sync.

This starter is built for the exact on-site pattern you described: the Pi lives on the Commander network, exposes a local dashboard, can manually pull transaction data, can receive `SALES_MONITOR` events, and stages inventory edits before pushing them upstream.

Transactions today
0

$0.00 gross

Fuel volume
0.00 gal

Posted sales captured on the Pi

Queued inventory
3

Rows waiting to push to Commander

Low stock
3

SKUs at or below reorder point

Transaction Pulse

What the Pi is seeing now

This chart makes the bridge feel alive by showing the most recent tickets landing on the box in real time.

Pi stream
Latest flow from the live store feed
$41.02 latest
5:11 PM5:22 PM5:31 PM5:35 PM5:41 PM
Average ticket
$36.02
Peak ticket
$78.20
Recent points
5

Inventory Health

Sync posture by item

Inventory rows are grouped by sync state so owners can see whether the bridge is caught up or accumulating risk.

TRACKED ITEMS6
In sync
3
Pending push
2
Error
1

Bridge Mix

How data is entering this site

Compare transaction source mix with sync outcomes to see whether the feed is being driven more by webhooks or manual pulls.

Webhook
$151.70
Manual Pull
$28.41
Success
2
Partial
1
Failed
0

Bridge Snapshot

Site and device details

TX-ROUTE66-014
Store
Route 66 Fuel & Market
Commander release
56.01
Base URL
https://192.168.31.11
Command path
/cgi-bin/partner
Last handshake
Apr 18, 5:48 PM
Relative status
12 hours ago

How the Pi should be wired

Put the Raspberry Pi on the same Ethernet network as the Commander site controller or on a secure routed segment that can reach Commander over HTTPS. The Pi does not need to replace the POS lane; it acts as a local bridge appliance beside it.

Webhook Inbox

Recent Commander events

2 stored
SALES_MONITOR
2 parsed
Apr 18, 5:41 PM · Commander Event Manager

{"eventType":"SALES_MONITOR","transactions":[{"transactionId":"TLOG-9001551","amount":41.02}]}

SALES_MONITOR
1 parsed
Apr 18, 5:31 PM · Commander Event Manager

{"eventType":"SALES_MONITOR","transactions":[{"transactionId":"TLOG-9001549","amount":78.20}]}

Transaction Intake

Latest Commander sales on the Pi

5 recent rows
$41.02
TLOG-9001551
webhook
Apr 18, 5:41 PM
REG-02 · PUMP-03
Visa · 2 items · 11.28 gal
$19.98
TLOG-9001550
manual-pull
Apr 18, 5:35 PM
REG-01 · Inside sale
Cash · 5 items
$78.20
TLOG-9001549
webhook
Apr 18, 5:31 PM
REG-03 · PUMP-07
Fleet · 1 items · 23.10 gal
$8.43
TLOG-9001548
manual-pull
Apr 18, 5:22 PM
REG-02 · Inside sale
Mastercard · 2 items
$32.48
TLOG-9001547
webhook
Apr 18, 5:11 PM
REG-04 · PUMP-01
Amex · 1 items · 8.94 gal

Bridge Activity

Pi sync timeline

Commander accepted 1 update, 1 item still needs a command map review.
Apr 18, 4:49 PM · 13 hours ago
inventory-push

Starter adapter marked TOB-207 for follow-up because the response looked non-committal.

Imported 18 new transactions and skipped 3 duplicates.
Apr 18, 4:31 PM · 13 hours ago
transactions-pull

Latest pull used the last known transaction timestamp as the cursor.

Connector handshake succeeded.
Apr 18, 3:48 PM · 14 hours ago
handshake

Validated access using the configured connector mode.

Inventory Queue

Local inventory staging on the Raspberry Pi

Edit pricebook rows here first. The Pi keeps those changes locally, marks them `pending-push`, and then sends them to Commander when you hit the push action.

6 total SKUs0 unsaved local edits3 low-stock items
ItemCategoryPriceCostOn HandReorderPLUState
in-sync
pending-pushreorder now
errorreorder now
in-sync
pending-pushreorder now
in-sync

Production Notes

What still gets mapped per Commander site

Transaction pulls

The Pi-side app is ready to poll. For live use, you fill in the exact transaction command name and any response-mapping tweaks from your Verifone partner documentation.

Inventory pushes

Local inventory edits already queue correctly. The final step is matching the outbound payload key and XML or field contract to the command your Commander reseller enables.

Event-driven sync

The webhook route is already there. Once Commander Event Manager points at this Pi, new sales can arrive without waiting for the next manual pull.

Automatic polling

A dedicated Pi puller service can now call a protected internal route on a schedule, so the remote web app keeps refreshing even if live Commander webhooks are not set up yet.