Commander files
5
Period list, ruby summary, department, fuel hose, cashier period
StationMind AI replaces 2-4 hours of daily back-office paperwork with review-gated AI decisions. Invoices, fuel reconciliation, daily close, and pricing — automated with guardrails, not blind trust.
Commander files
5
Period list, ruby summary, department, fuel hose, cashier period
AI decisions
14
Review-gated suggestions with source evidence
Owner actions
4
Only true exceptions are waiting
Unsafe automation
0
No price push, no POS write-back, no auto-finalized accounting
79+ routes
Full-featured Next.js 16 app with app router, covering every operational workflow
200+ tests
Vitest unit tests and Playwright E2E tests covering security, tenant isolation, and data flow
270+ lib files
Structured domain services for AI, connector, accounting, fuel, pricing, and operations
5,300-line schema
Prisma schema with 30+ enums, 50+ models, and strict tenant-scoped relations
Multi-tenant
Organization > Store hierarchy with privacy layers and audit-logged data access
Zero-trust AI
Every AI decision is review-gated, confidence-scored, and source-evidence-backed
Operating flow
Commander data is arriving read-only
The demo shows direct CGILink-style report pulls, file receipts, heartbeat status, and archive training without showing credentials.
Evidence: Sanitized connector heartbeat and five sample Commander XML receipts
Owner sees decisions, not raw system objects
Documents and POS signals become simple approval cards: what it is, where it goes, why AI thinks that, and what happens next.
Evidence: Four sample review cards with confidence, routing, and money impact
Draft close is ready but not finalized
StationMind AI can draft the close from POS-side evidence, then keeps final accounting locked until the owner approves missing or uncertain data.
Evidence: Department totals, cashier periods, fuel summary, missing EFT match warning
POS fuel sales are visible; tank/SIR remains pending
Commander hose data is treated as POS sales truth only. Certified fuel reconciliation waits for fuel invoice and tank/SIR/ATG evidence.
Evidence: Sample hose report, invoice-pending status, tank/SIR missing exception
Suggestions only, no auto-order
The demo surfaces fast movers, missing counts, and invoice-driven reorder clues while keeping purchase orders approval-gated.
Evidence: Three sample reorder suggestions, no vendor submission
Production guardrails are visible
Read-only Commander integration, secret redaction, tenant isolation, audit events, and high-risk approval requirements are shown as first-class product behavior.
Evidence: Safety checklist with disabled write-back and disabled price push
Review Inbox
Each card shows what the item is, where it goes, why AI thinks that, and what money/report it affects. The owner approves or rejects — StationMind AI never auto-finalizes.
Core-Mark
Amount
$2,184.42
Destination
Purchase / Inventory
Known vendor and invoice pattern; new tobacco item mapping needs owner confirmation
Updates vendor spend and inventory cost basis after approval
Fuel supplier
Amount
$18,460.17
Destination
Fuel Purchase
Fuel invoice detected, but grade mapping needs review
Feeds fuel inventory and margin draft; not compliance-certified without tank/SIR
Processor email
Amount
$6,932.28
Destination
Credit Card Settlement
External deposit source is present, but fee split is not certified
Matches POS expected card totals to deposit candidate
AT&T
Amount
$244.18
Destination
Telecom Expense
Recurring sender and vendor, low payment-risk language
Updates expense report and P&L draft after approval
Impact
Sample data — these represent the target workflow improvements, not measured production metrics.
Before
Owner manually opens emails, identifies vendor, enters line items into spreadsheet — 20-30 min per invoice
After
StationMind AI classifies the document, extracts fields with OCR, routes to correct account, and presents a one-click approval card
Before
Owner manually cross-references POS register report, cashier periods, and card settlements — error-prone, 45-60 min daily
After
StationMind AI drafts the close from POS evidence, flags discrepancies, and waits for owner approval before finalizing anything
Before
Owner manually tracks fuel deliveries, hose readings, and tank dips on paper or Excel — compliance gaps are invisible
After
StationMind AI ingests hose data automatically, flags missing tank/SIR evidence, and refuses to generate compliance reports without proper proof
Before
Owner tracks costs in head, updates shelf labels based on gut feel, misses margin erosion until month-end P&L
After
PricePilot surfaces cost changes from invoices, recommends margin-aware prices, and keeps all changes review-gated via StationMind AI
AI Explainability
Every AI capability is review-gated and confidence-scored. The owner sees inputs, outputs, and reasoning. StationMind AI uses AI as a tool under human supervision, not as an autonomous agent.
Routes incoming documents (invoices, fuel deliveries, EFT statements, expenses) to the correct accounting category
Inputs: OCR text, sender metadata, document structure
Outputs: Category, confidence score, routing destination
Identifies vendors from invoice patterns, maps line items to products, learns from corrections
Inputs: Invoice text, historical vendor patterns, product catalog
Outputs: Vendor match, item mappings, confidence per field
Suggests price changes based on cost changes, competitor data, and margin targets
Inputs: Cost basis from invoices, margin rules, competitor prices
Outputs: Recommended prices with explanation and margin impact
Cross-references POS hose data with delivery invoices, tank readings, and ATG data
Inputs: Commander hose reports, fuel invoices, tank/SIR readings
Outputs: Variance reports, missing evidence flags, exception cards
Drafts end-of-day accounting from POS evidence, flags gaps, keeps finalization owner-gated
Inputs: Cashier periods, department totals, card settlements, fuel summary
Outputs: Draft close sheet, missing data warnings, approval queue
Identifies fast-moving products, low stock signals, and vendor deal opportunities
Inputs: Sales velocity, invoice history, vendor catalog, stock estimates
Outputs: Reorder suggestions with urgency and savings potential
System design
Next.js 16 app router with 79+ routes, React 19, Tailwind CSS 4, dark/light mode
TypeScript, React 19, Next.js 16, Tailwind CSS 4, TanStack Table
NextAuth 4 with role-based access, tenant-scoped middleware, and audit logging
NextAuth 4, Zod validation, middleware route enrichment
PostgreSQL with Prisma ORM, 30+ enums, 50+ models, strict tenant isolation
PostgreSQL, Prisma 6, tenant-scoped queries
Document OCR, classification, confidence scoring, learning feedback loops
LLM provider abstraction, Zod-validated extraction, trust engine
Read-only Verifone/Commander integration with heartbeat, evidence archiving
Windows service, XML/CSV parsing, S3 archiving
BullMQ background processing for document ingestion, report parsing, training
BullMQ, Redis, worker runtime, scheduled jobs
Development
Responsible AI
Every AI decision requires explicit owner approval. StationMind AI will not push prices to the POS, auto-finalize accounting, or place vendor orders without the owner clicking Approve.
Every classification, routing, and extraction decision shows a confidence score. Low-confidence items are flagged for review. The owner can see why AI made each decision.
When the owner corrects AI, the system captures the correction, stores it in the learning pool, and improves future classifications — but only within the privacy-safe learning boundary.
Store A's data never influences Store B's AI. Learning happens in privacy layers: store-private corrections stay private, only anonymized patterns reach the platform pool.
Build story
StationMind AI is built by a solo founder using AI-assisted development tools (Claude, Copilot) alongside traditional engineering. AI tools accelerate code generation, pattern implementation, and documentation — but every architectural decision, security boundary, and business rule was designed and verified by a human engineer.
The platform is currently in development and demo/pilot-readiness stage. The demo uses sanitized sample data to show the platform's capabilities without exposing real store operations. Features labeled “Real” have production-ready code. “Demo” features work with sample data. “In Progress” features are actively being built.