- Home
- Skills
- Agents & Orchestration
- POS SaaS Engineering Skills — v1.0.0
Works with the AI Agents you already use
POS SaaS Engineering Skills — v1.0.0
Complete engineering framework for building offline-ready, multi-tenant POS systems with hardware integration.
Free
POS SaaS Engineering Skills — v1.0.0
Example session with this skill installed
Design a multi-tenant database schema for a POS SaaS that needs to support inventory across multiple branches and warehouses, ensuring strict data isolation between different business clients.
- Read your context and instructions
- Compiled the pos saas engineering
I have designed the multi-tenant architecture and schema for your POS SaaS. The design utilizes a shared-database, isolated-schema approach to balance scalability with strict data boundaries.
Multi-Tenant Inventory Schema
-- Core Tenant Isolation
CREATE TABLE tenants (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
business_name VARCHAR(255) NOT NULL,
tax_id VARCHAR(50) UNIQUE NOT NULL,
created_at TIMESTAMPTZ DEFAULT NOW()
);
-- Branch and Warehouse Hierarchy
CREATE TABLE branches (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
tenant_id UUID REFERENCES tenants(id) ON DELETE CASCADE,
name VARCHAR(100) NOT NULL,
is_active BOOLEAN DEFAULT TRUE,
metadata JSONB -- For location/contact info
);
CREATE TABLE warehouses (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
branch_id UUID REFERENCES branches(id),
tenant_id UUID REFERENCES tenants(id),
code VARCHAR(20) NOT NULL,
UNIQUE(tenant_id, code)
);
-- Inventory Ledger (Immutable Movements)
CREATE TABLE inventory_ledger (
id BIGSERIAL PRIMARY KEY,
tenant_id UUID REFERENCES tenants(id),
warehouse_id UUID REFERENCES warehouses(id),
product_id UUID NOT NULL,
movement_type VARCHAR(20), -- 'SALE', 'PURCHASE', 'TRANSFER', 'ADJUSTMENT'
quantity DECIMAL(18,4) NOT NULL,
reference_id UUID, -- Links to sale_id or purchase_id
created_at TIMESTAMPTZ DEFAULT NOW()
);
-- Indexing for Multi-tenant Performance
CREATE INDEX idx_ledger_tenant_warehouse ON inventory_ledger (tenant_id, warehouse_id);
CREATE INDEX idx_branches_tenant ON branches (tenant_id);
Architectural Directions
Row-Level Security (RLS): Enable Postgres RLS using SET app.current_tenant_id to ensure queries cannot leak data between businesses at the database level.
2.
Global Product Catalog vs Local Stock: Products are defined at the tenant level, but availability (stock_on_hand) is calculated per warehouse via the ledger to maintain an audit trail.
Next steps
- Implement a Row-Level Security policy function to automate tenant filtering.
- Define the
inventory_summarymaterialized view for fast stock lookups. - Configure the transactional outbox pattern to sync stock changes to the search index.
Connects securely to your tools. The creator never sees your data.
About this skill
Build a mission-critical POS SaaS with a professional engineering toolkit designed for retail, restaurants, and pharmacy. This package solves the high-stakes problems of inventory races, offline sales synchronization, and hardware peripheral chaos. It provides a structured methodology for building multi-tenant architectures that remain functional when the internet drops.
What it does
- Multi-industry Modeling provides domain structures for retail, pharmacy, and restaurants including recipes, batches, and variants.
- Offline-First Synchronization handles local persistence with IndexedDB and re-executable, idempotent sync protocols.
- Hardware Abstraction integrates thermal printers, barcode scanners, and scales via a secure Rust-based local agent.
- Fiscal Compliance manages electronic invoicing, tax engines, and audit trails for regulatory environments like SUNAT.
- Concurrency Control prevents stock collisions and numbering conflicts across multiple terminals and branches.
How it works
- Model the Domain using pre-defined patterns for multi-tenant isolation and industry-specific attributes.
- Implement Frontend Layers with Angular modules, PWA capabilities, and robust offline UI states.
- Configure Hardware Integration through the local device agent to bridge the web-to-peripherals gap.
- Deploy Scalable Backend services using .NET Core with transactional integrity and PostgreSQL optimizations.
Frameworks & tools
Angular, .NET Core, Rust, PostgreSQL, IndexedDB, Docker, and ESC/POS thermal printing protocols.
Why this beats prompting it yourself
Generic prompts fail to account for the ACID requirements of a cash register or the specific timing issues of USB HID scanners. This skill provides the architectural constraints and edge-case handling needed to pass fiscal audits and prevent data loss during network outages.
Use cases
- Build a multi-tenant retail SaaS with branch-level inventory isolation.
- Implement a restaurant POS that prints kitchen commands via local thermal printers.
- Develop a pharmacy system requiring batch/lot tracking and electronic invoicing.
- Create a mobile-first POS with full offline sales and background sync.
Known limitations
Requires a local agent for direct hardware access from browsers. Does not provide the specific tax logic for every global jurisdiction out of the box.
Requires a local resident agent for hardware communication. Initial setup requires mapping specific hardware VID/PID. Fiscal rules are currently focused on Peruvian (SUNAT) and general UBL standards.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 11 days ago
- Free with an Agensi account
Requires