Ecosystem / Shared package · Shipped
The shared foundation library for the ecosystem — one brain powering every ESTINAD app.
ESTINAD Core is the shared foundation every POS, waiter, and kitchen app runs on: the same business models, data access, and sync engine. Orders, inventory, and customers stay consistent across devices because they all speak the same language underneath.
Capabilities
The shared brain of the ecosystem.
Core is where the platform's promises — one ledger, one identity, one sync engine — actually live as code.
Unified business models
Orders, products, customers, payments, shifts, tables, and loyalty share one schema — data means the same thing everywhere.
Repository layer
Ready-made data access for orders, inventory, customers, payments, shifts, and tables — apps focus on UI, not database plumbing.
Offline-first sync engine
Bidirectional sync between local PocketBase and Supabase with queue processing, conflict handling, and checkpoint recovery.
Network auto-discovery
mDNS/Bonjour service discovery lets companion devices find the POS on the LAN without manual configuration.
Multi-tenant provisioning
License-based device onboarding, hardware fingerprinting, and per-tenant configuration for isolated hybrid deployments — dedicated local servers and cloud workspaces, not a shared operational database.
Auto-update delivery
Check for, download, and apply app updates with version management — keeping terminals on the latest release safely.
Print routing engine
Route receipts and kitchen tickets to the right printer or station by product configuration — shared by POS and KDS.
Role-based permissions
Granular permission definitions power consistent access control across cashier, manager, and admin workflows.
AI business context (Planned)
Structured context for a planned in-app AI capability.
Product import schemas
Declarative CSV import schemas and PocketBase/Supabase sinks wire bulk catalog loading into POS workflows.
Operational error logging
Capture and persist application errors to the local database for support and diagnostics without losing crash context.
Integrations
The data layer it connects.
Ecosystem fit
The foundation every app inherits.
Inside every app
ESTINAD POS, Waiter, KDS, and Clinic all link Core — so they share models, sync, and permissions by construction, not by convention.
Keeps data consistent
Because one schema spans the ecosystem, a customer or payment means the same thing on the counter, the floor, and the kitchen screen.
Designed offline-first
Local PocketBase is the source of truth during service; cloud sync is the backup and multi-site bridge, not a hard dependency.
Tech highlightOne ledger, by construction.
Designed offline-first: local PocketBase is the source of truth during service; cloud sync is the backup and multi-site bridge, not a hard dependency.
FAQ
Questions technical buyers ask first.
Is ESTINAD Core a product I buy?
No. Core is a shared package inside the platform. You buy a product line, and every product inherits Core's models, sync, and permissions.
How does sync handle unreliable internet?
The sync engine queues changes locally, handles conflicts, and uses checkpoint recovery so outages never become lost transactions.
Does Core enforce access control?
Yes. Permission and role definitions in Core power consistent access control across every app that links it.