How long does Ezvento setup take?

Most stores are up and running in under 10 minutes. Create your account, add your store name and address, and start billing. You can add products later or import from Excel.

Is GST compliance automatic in Ezvento?

Yes. Ezvento automatically calculates GST based on your product HSN codes. You can export GSTR-1 and GSTR-3B reports in one click. E-invoices are generated for B2B sales automatically.

Can I use Ezvento on my tablet or phone?

Absolutely. The POS works beautifully on iPad, Android tablets, and any touchscreen device. No expensive POS hardware needed — just a device and a printer.

What happens if internet goes down while using Ezvento?

Ezvento works offline. You can keep billing, scanning barcodes, and printing receipts. When your internet comes back, everything syncs automatically. No sale is ever lost.

What is the price of Ezvento?

Ezvento starts at ₹999/month for the Launch plan (1 store, 3 users) and ₹2,499/month for the Grow plan (3 stores, 10 users). All plans include a 14-day free trial with no credit card required.

Can I track credit (udhar) sales in Ezvento?

Yes. Link a sale to a customer as credit. See all outstanding balances in one place. Send payment reminders. Record partial payments. Full credit ledger for every customer.

Do I need special hardware to use Ezvento?

No. Ezvento works on any device with a browser. For printing, any thermal receipt printer connected via USB or network will work. Barcode scanners plug in directly.

Can I manage multiple stores with Ezvento?

Yes. The Grow plan supports 3 stores, and Scale supports unlimited. See all stores from one dashboard, transfer stock between locations, and get consolidated reports.

API Reference

Ezvento exposes 80+ REST API endpoints under /api/**. Every route uses requireApi() for RBAC permission checks and filters all database queries by tenantId. All mutations are logged to the ActivityLog table for audit.

Routes

80+

REST endpoints

Auth

100%

Permission-gated

Audit

All

Mutations logged

Tenant

Strict

Row-level isolation

Auth Module

Authentication endpoints handle login, signup, password recovery, OAuth callbacks, 2FA setup/verification, PIN-based cashier auth, manager PIN approval, session persona selection, and logout. Some routes are public (no requireApi guard); others are guarded.

Method	Path	Permission	Scope	Description
POST	/api/auth/start	—	—	Start auth flow: signup, recovery, resend, or OAuth. Uses server Supabase client with PKCE cookies.
POST	/api/auth/exchange	—	—	Exchange OAuth authorization code for session. Server-side PKCE exchange.
POST	/api/auth/callback-server	—	—	Post-login callback. Creates tenant, resolves persona type, sets ezvento-persona cookie, returns redirectPath.
POST	/api/auth/2fa/setup	SALE_VIEW	—	Set up TOTP-based 2FA. Returns QR code and secret.
POST	/api/auth/2fa/verify	SALE_VIEW	—	Verify TOTP token and enable 2FA. Returns backup codes on success.
POST	/api/auth/2fa/disable	SALE_VIEW	—	Disable 2FA for the current user.
POST	/api/auth/verify-pin	SHIFT_OPEN	STORE	Verify cashier PIN for shift open. Returns user context with allowed stores.
POST	/api/auth/manager-pin	APPROVAL_GIVE	—	Validate manager PIN for approval-giving. Returns 401 on wrong PIN.
POST	/api/auth/session-persona	—	—	Set session persona cookie and redirect path based on active role assignments.
POST	/api/auth/logout	—	—	Sign out from Supabase auth and clear session cookies.
GET	/api/auth/permissions	—	—	Return the current user's effective permissions and role assignments.

Common Patterns

requireApi Guard

Every mutation route calls requireApi({ permission, scope }) before any database operation. It returns either { ok: true, ctx } or { ok: false, response }.

const auth = await requireApi({
  permission: 'SALE_CREATE',
  scope: { type: ScopeType.STORE, id: storeId },
})
if (!auth.ok) return auth.response
const { ctx } = auth

Approval Override

High-risk actions use allowApprovalOverride: true. When the user lacks the direct permission, the system checks the X-Approval-Id header for a valid, unused, non-expired approval record.

const auth = await requireApi({
  permission: 'SALE_CANCEL',
  allowApprovalOverride: true,
  scope: { type: ScopeType.STORE, id: storeId },
})
// On 403, client requests manager PIN →
// retry with X-Approval-Id header

Tenant Isolation

Every database query includes tenantId: ctx.tenantId. Prisma findFirst / findMany always filter by tenant. There are no cross-tenant reads.

const invoices = await prisma.salesInvoice.findMany({
  where: { tenantId: ctx.tenantId, storeId },
})

Activity Logging

All mutations call logActivity() with action, module, entity, and metadata. Logs are written to ActivityLog with audit hashes for tamper-evidence.

await logActivity({
  tenantId: ctx.tenantId,
  userId: ctx.userId,
  action: 'INVOICE_CREATE',
  module: 'BILLING_CREATE',
  entityType: 'SalesInvoice',
  entityId: result.id,
})

Permission Mapping

Quick reference for which permissions are required for common operations.

Operation	Required Permission	Scope	Notes
Create sale / invoice	SALE_CREATE	STORE	Also checks credit limit for credit sales
Cancel sale	SALE_CANCEL	STORE	Cashiers escalate via manager PIN (allowApprovalOverride)
Process return	SALE_RETURN	STORE	Also requires approval override for cashiers
Create product	PRODUCT_CREATE	ORG	Tenant-scoped catalog
Adjust stock	INVENTORY_ADJUST	STORE	Negative adjustment uses INVENTORY_ADJUST_NEGATIVE
Transfer stock	INVENTORY_TRANSFER	STORE	Source store scope
View reports	REPORT_VIEW_SALES	ORG	Covers sales, inventory, GST, and staff reports
Export GST (GSTR-1/3B)	REPORT_VIEW_SALES	ORG	Same permission as reports; separate endpoint for format
Open shift	SHIFT_OPEN	STORE	Cashier persona entry point
Close shift	SHIFT_CLOSE	STORE	Own-shift close allowed; manager can force-close
Invite user	USER_INVITE	ORG	Enforces plan user limits
Edit settings	ORGANIZATION_SETTINGS_EDIT	ORG	Tenant-wide configuration

Response Codes

200 OK

Standard success response for GET, PUT, PATCH, and DELETE operations. Returns JSON payload or paginated response.

201 Created

Resource created successfully. Used by POST endpoints (invoice, product, user, adjustment, transfer). Returns the created entity.

400 Bad Request

Validation error, missing required fields, or business logic failure (e.g., credit limit exceeded, insufficient stock). Response includes { error: string }.

401 Unauthorized

No valid Supabase session, session revoked, or permission version stale. May include code: SESSION_REVOKED or code: PERMISSION_VERSION_STALE to prompt re-authentication or refresh.

403 Forbidden

Authenticated user lacks the required permission for the requested scope. For approval-gated endpoints, may return code: APPROVAL_REQUIRED or code: APPROVAL_INVALID with the missing permission name.

404 Not Found

The requested resource does not exist or does not belong to the current tenant. Triggered by Prisma P2025 (record not found) via handlePrismaError.

402 Payment Required

Subscription required. Returned by mutation endpoints when requireActiveSubscription fails (no active or trialing subscription).

409 Conflict

Unique constraint violation (P2002) or foreign key constraint violation (P2003). E.g., duplicate SKU, duplicate email in tenant.

429 Too Many Requests

Rate limit exceeded. Next.js middleware or Supabase rate limiting may trigger this on high-volume endpoints.

500 Internal Server Error

Unexpected server error, database connection failure, or unhandled exception. Activity logging silently fails to avoid breaking main operations.

Need more detail?

Explore the source code in src/app/api/**/route.ts for full request/response schemas, Prisma queries, and transaction logic. Every route handler includes inline JSDoc comments describing parameters and behavior.

Method

Path

Permission

Scope

Description

POST

/api/auth/start

—

Start auth flow: signup, recovery, resend, or OAuth. Uses server Supabase client with PKCE cookies.

POST

/api/auth/exchange

—

Exchange OAuth authorization code for session. Server-side PKCE exchange.

POST

/api/auth/callback-server

—

Post-login callback. Creates tenant, resolves persona type, sets ezvento-persona cookie, returns redirectPath.

POST

/api/auth/2fa/setup

SALE_VIEW

—

Set up TOTP-based 2FA. Returns QR code and secret.

POST

/api/auth/2fa/verify

SALE_VIEW

—

Verify TOTP token and enable 2FA. Returns backup codes on success.

POST

/api/auth/2fa/disable

SALE_VIEW

—

Disable 2FA for the current user.

POST

/api/auth/verify-pin

SHIFT_OPEN

STORE

Verify cashier PIN for shift open. Returns user context with allowed stores.

POST

/api/auth/manager-pin

APPROVAL_GIVE

—

Validate manager PIN for approval-giving. Returns 401 on wrong PIN.

POST

/api/auth/session-persona

—

Set session persona cookie and redirect path based on active role assignments.

POST

/api/auth/logout

—

Sign out from Supabase auth and clear session cookies.

GET

/api/auth/permissions

—

Return the current user's effective permissions and role assignments.

const auth = await requireApi({ permission: 'SALE_CANCEL', allowApprovalOverride: true, scope: { type: ScopeType.STORE, id: storeId }, }) // On 403, client requests manager PIN → // retry with X-Approval-Id header

Operation

Required Permission

Scope

Notes

Create sale / invoice

SALE_CREATE

STORE

Also checks credit limit for credit sales

Cancel sale

SALE_CANCEL

STORE

Cashiers escalate via manager PIN (allowApprovalOverride)

Process return

SALE_RETURN

STORE

Also requires approval override for cashiers

Create product

PRODUCT_CREATE

ORG

Tenant-scoped catalog

Adjust stock

INVENTORY_ADJUST

STORE

Negative adjustment uses INVENTORY_ADJUST_NEGATIVE

Transfer stock

INVENTORY_TRANSFER

STORE

Source store scope

View reports

REPORT_VIEW_SALES

ORG

Covers sales, inventory, GST, and staff reports

Export GST (GSTR-1/3B)

REPORT_VIEW_SALES

ORG

Same permission as reports; separate endpoint for format

Open shift

SHIFT_OPEN

STORE

Cashier persona entry point

Close shift

SHIFT_CLOSE

STORE

Own-shift close allowed; manager can force-close

Invite user

USER_INVITE

ORG

Enforces plan user limits

Edit settings

ORGANIZATION_SETTINGS_EDIT

ORG

Tenant-wide configuration