Ledger-First by Design
Every stock change is captured as an immutable append-only ledger entry. No direct edits, no silent rewrites, and no lost movement history.
Blemense ERP connects inventory, procurement, finance, production, quality, HR, and sales in a single ledger-first platform. Built for the complexity of Indian manufacturing. Invitation-only.
8
Solutions
6
Industry Verticals
100%
Audit Coverage
0
Negative Stock Tolerated
1
Ledger
Current Stock
1,847 SKUs
GRNs This Month
34
Pending Approvals
7
Plants Active
3
Every stock change is captured as an immutable append-only ledger entry. No direct edits, no silent rewrites, and no lost movement history.
There is no public signup path. Every user is explicitly granted access so onboarding, permissions, and org boundaries stay controlled.
Built for multi-plant, multi-org, and procure-to-pay operations from the start, not adapted from a generic ERP template.
The Problem
01
Inventory movement is spread across spreadsheets and WhatsApp threads, so numbers diverge by shift.
02
There is no trustworthy record of who issued what, when it moved, or why stock changed.
03
Unmatched invoices and paper POs break purchase control and force manual reconciliations.
Solutions
Track stock across plants, stores, and racks with a single source of truth. Every movement is recorded instantly so physical inventory and financial position remain synchronized.
Multi-plant stock tracking
Rack/bin-level location management
Batch and serial number control
Real-time stock valuation
Connected Platform
Every solution - from a purchase order to a payroll run to a quality rejection - writes to and reads from the same immutable ledger. This is not integration. This is architecture.
No reconciliation between modules - they share the same transaction record.
An approval in HR triggers a budget check in Finance automatically.
A quality rejection in Incoming Inspection cancels the corresponding payable.
A stock transfer between plants creates dual ledger entries in one atomic transaction.
Every action by every user is in the audit log. Forever.
Ledger & Data
Solutions
Business Logic
Interface & AI
Procure-to-Pay
Purchase Requisition
Request for Quotation
Purchase Order
Advance Shipment Notice
Goods Receipt Note
Quality Check
Vendor Invoice
4-Way Matching
PO
Ordered qty
Unit price
GRN
Received qty
Inspection
Accepted qty
Invoice
Billed qty
Unit price
Success path
Exception path
AI IN ERP
Traditional ERP records what happened. Blemense ERP tells you what is about to happen, flags what shouldn't have happened, and handles what doesn't need a human. AI is not a separate module - it is a capability layer embedded in every transaction.
Analyses historical consumption patterns across plants to predict material requirements before reorder points are breached.
Flags statistically unusual transactions - a GRN quantity 3x the historical average, a supplier invoice with a mismatched unit price - before they propagate into your ledger.
Calculates dynamic safety stock and reorder quantities by combining actual lead time data from your own PO-to-GRN history with consumption velocity.
Applies learned matching rules to run 4-way match automatically on routine invoices, surfacing only genuine discrepancies for human review.
Continuously scores each supplier on delivery accuracy, quality acceptance rate, and price variance to surface underperformers before they become risks.
Ask your ERP in plain language - "Which materials are below safety stock at Plant B this week?" - and receive a structured data response without writing a report.
Operations don't wait. Neither does the ledger.
REAL-TIME
Every stock mutation - GRN, issue, transfer, or damage - is written to the immutable ledger the instant it happens.
PER BATCH
Quality inspection lots are created and linked to each inbound GRN, ensuring no uninspected material enters usable stock.
DAILY
MRP recalculates reorder points, safety stock, and supplier lead times from actual operational data - not estimates.
PER INVOICE
4-way matching runs automatically against PO quantity, GRN accepted quantity, inspection disposition, and invoice amount.
CONTINUOUS
AI anomaly detection monitors every transaction for deviations from established patterns and flags exceptions before they close.
VERTICALS
Blemense ERP ships with industry-specific configurations, terminology, workflows, and compliance checkpoints for six manufacturing verticals.
For plants that make things from parts.
BOM and production order tracking
Component inventory with shelf-life control
Finished goods dispatch and challan
Supplier quality and rejection management
GST · Quality Inspection · MRP
For plants where batches are the unit of work.
Batch master with yield tracking
Raw material consumption recording per batch
Quality parameter testing per lot
Wastage and rework recording
Batch Control · Yield Tracking · Compliance Logs
For Tier 1 and Tier 2 suppliers to OEMs.
JIT inbound logistics aligned to OEM schedules
Part number and revision control
PPM tracking per customer line
Tool and die lifecycle tracking
PPM Tracking · Revision Control · JIT Supply
For regulated manufacturing with traceability requirements.
Lot traceability from RM to FG
CoA and QC parameter management
Expiry and FEFO stock management
Regulatory document linking
CoA · Lot Traceability · FEFO
For projects where materials move across sites.
Site-wise material indent and issue
Contractor billing and labour reconciliation
Equipment and machinery tracking
Project cost-to-complete reporting
Project Costing · Site Inventory · Contractor Controls
For processors where freshness and compliance intersect.
Lot and harvest date tracking
Cold chain inventory management
Yield recording per processing run
Regulatory and FSSAI compliance support
FSSAI · Lot Traceability · FIFO
ONBOARDING
ERP rollouts fail not because of bad software but because of bad onboarding. Blemense ERP ships with a structured onboarding system that gets every role to their first meaningful action before overwhelm sets in.
YOUR ONBOARDING PATH
Organisation Created
Your organisation, subscription plan, and initial plant structure are set up by the Blemense onboarding team. You receive your ORG_OWNER invitation within 24 hours.
Account Activated
You accept your invitation, set your password, and log in as ORG_OWNER. The system is live with your organisation context. No installation. No configuration files.
Foundation Setup
Configure your master data: add plants, build your material type and category hierarchy, create your material master, define rack structures, and add your supplier list.
2 of 5 tasks complete
Team Onboarded
Invite your team with role assignments and plant access. Each member receives their own invitation and follows a role-specific onboarding checklist tailored to their function.
First Transactions
Create your first GRN, run your first material issue, and complete your first inter-plant transfer. The system walks you through each with contextual guidance on the first attempt.
Fully Operational
Procurement cycle running, quality inspection active, MRP calculating. Your operations are in the ledger. Every transaction is auditable from day one.
HOW WE SUPPORT YOU
Dedicated Onboarding Manager
A named Blemense specialist manages your rollout from invitation to first month of operations. Not a chatbot. Not a ticket queue.
Role-Based Training Paths
Each user role gets a tailored onboarding sequence. A Store Manager sees GRN and issue walkthroughs. A Finance user sees invoice matching and payable workflows. No one is shown everything at once.
Contextual In-App Guidance
First-time actions in the ERP surface contextual tooltips and step-by-step walkthroughs directly inside the interface. Guidance appears when and where it is needed, not in a separate manual.
Knowledge Base & Documentation
A searchable library of step-by-step guides, FAQs, and troubleshooting documentation covers every module. Accessible before day one so users can familiarise themselves ahead of their first login.
Direct Support Access
Reach the support team directly via email or scheduled call. For critical operational issues, response SLA is 4 hours during business hours.
Ready to begin? Onboarding starts with a single email.
Request OnboardingFIRST VALUE BY ROLE — WHAT EACH USER ACHIEVES IN SESSION ONE
ROLE
FIRST ACTION
VALUE DEMONSTRATED
Complete master data setup: plants, materials, racks
The entire operational foundation is configured and the team can be invited.
Create the first GRN against a purchase order
Stock enters the system with a full audit trail and the ledger records the first entry.
Approve a pending material issue request
The maker-checker workflow fires end-to-end and stock decreases with a linked approval record.
Match a purchase invoice to its GRN and PO
4-way matching runs and the first payable is recorded with full traceability to the receipt.
Record inspection results on an inbound lot
Accepted quantity releases to stock; rejected quantity triggers a return-to-supplier workflow.
PRE-BOARDING
The Blemense ERP knowledge base and role-based training materials are made available to your entire team the moment your organisation is created - before anyone has logged in for the first time. Users arrive on day one with context, not confusion.
Module overviews and terminology glossary for your vertical
Role-specific quick-start guides for Store Manager, Plant Manager, and Finance
Master data setup templates (material codes, rack naming conventions, supplier format)
Video walkthroughs of the first five actions for each role
How It Works
01
Request access and receive a time-bound invitation so onboarding is intentional and environment setup is controlled.
02
Configure plants, stores, users, and approval rules so every transaction follows your operating model from day one.
03
Execute procurement and stock movements on a single ledger with maker-checker governance and full audit visibility.
Access Control
Every organisation starts with five predefined roles covering the full authority hierarchy. Roles can be customised - permissions scoped per module, per plant, per action - to match your exact operational structure.
01
Full organisational authority, policy control, and role delegation across the enterprise.
ALL PLANTS
02
Operational configuration, master data governance, and workflow administration for all modules.
ALL PLANTS
03
Manage inventory, production, and approvals for plants explicitly assigned to the user.
ASSIGNED PLANTS
04
Execute day-to-day store operations, inward/outward movement, and stock controls for assigned plants.
ASSIGNED PLANTS
05
Read-only access to operational and audit records within assigned plants and permitted modules.
ASSIGNED PLANTS
Plant access is enforced at the database query level - not just the UI. A user with no access to Plant B cannot retrieve Plant B data regardless of how the request is made.
CUSTOM ROLES
Default roles cover most structures. But manufacturing operations are not generic. A Quality Inspector should be able to record inspection results without accessing financial data. A Dispatch Supervisor needs issue rights at the outbound dock but not at the raw material store. Custom roles let you define exactly that.
Can record inspection lot results and disposition. Cannot access procurement, finance, or HR modules.
Can create outbound issues at assigned dispatch plants. Cannot approve high-value requests or view cost data.
Can create and match purchase invoices. Cannot modify purchase orders or access stock mutation records.
Can record BOM consumption and production orders for assigned lines. Cannot view supplier pricing or employee data.
▸Role permissions are enforced server-side on every API request
▸Plant access is validated from the JWT, not from request parameters
▸Self-approval is blocked at the database level regardless of role
▸Custom roles inherit the same enforcement architecture as default roles
▸Permission changes take effect on the user's next token refresh
Security
An ERP centralises your most sensitive business data - stock valuations, supplier contracts, payroll, financial ledgers. Blemense ERP is built on a multi-layered, proactive security architecture where every layer independently enforces integrity. Compromising one layer does not compromise the system.
No public signup path. Every organization and user is provisioned deliberately with scoped access controls.
Stock movements are append-only and traceable, creating a complete forensic history across plants and processes.
Users can operate across mapped organizations with explicit context boundaries and no shared-credential shortcuts.
No user can approve their own request - ever. The membership ID that raises an issue, damage report, purchase order, or high-value stock movement is architecturally blocked from approving it. This is not a UI restriction. It is enforced at the database query level on every approval action, regardless of role. Segregation of duties is structural, not procedural.
SECURITY ARCHITECTURE — LAYERS OF PROTECTION
LAYER 01
Identity & Authentication
Every user is a global Identity authenticated with bcrypt cost-12 passwords, optional MFA via time-limited OTP, and account lockout after 3 failed attempts. There is no anonymous access. There is no public signup.
LAYER 02
Token & Session Security
Org-scoped JWTs expire in 15 minutes. Refresh tokens are stored only as SHA-256 hashes - never plaintext. Every token refresh rotates the token and marks the previous one consumed. Reuse of a consumed refresh token immediately revokes the entire token chain and alerts the user.
LAYER 03
Authorisation & Access Control
Every API request is validated against the membership record in the database - not just the JWT claim. OrganisationId is read from the token, never from the request body. Plant access is verified per request. Role permissions are enforced server-side on every action. Cross-organisation data access is architecturally impossible.
LAYER 04
Maker-Checker & Segregation of Duties
High-value stock movements, damage write-offs, and purchase approvals require a second actor. The approver cannot be the same membership that raised the request - this is a database-level constraint, not a UI check. A 24-hour minimum separation between creation and approval prevents collusion on time-sensitive transactions.
LAYER 05
Data Integrity & Immutability
The stock ledger and audit log are append-only tables. PostgreSQL triggers fire on any UPDATE or DELETE attempt and raise an exception - no application code, no admin privilege, and no direct database connection can modify a posted entry. Stock quantities have a CHECK constraint preventing negative values at the database level.
LAYER 06
Monitoring & Continuous Vigilance
Every login, role change, stock mutation, approval action, and organisation switch is written to the immutable audit log with IP address, user agent, session ID, and a risk level tag. Failed login spikes, MFA disables, and cross-plant access attempts trigger alerts. AI anomaly detection flags statistically unusual transaction patterns before they compound.
IMMUTABILITY GUARANTEE
The Blemense ERP stock ledger and audit log cannot be edited or deleted by any user, any admin, or any system process. This is enforced at the database level by triggers, not by application policy.
This means your financial audit trail, stock reconciliation history, and compliance records are permanently tamper-proof from the moment they are written.
▸Refresh token rotation on every use
▸Token reuse detection · full chain revocation
▸Serializable transaction isolation for transfers
▸Append-only stock ledger · database trigger enforced
▸Append-only audit log · database trigger enforced
▸Multi-Factor Authentication via time-limited email OTP, authenticator apps, other MFA methods
▸Cross-org data isolation
▸Plant-level access control on every query
▸JWT expiry in 15 minutes
▸Account lockout after repeated failed logins
▸Role enforcement on every API action
▸Immutable risk-tagged audit events
Security in Blemense ERP is not a feature layer added on top. It is the foundation every other capability is built on.
Get Started
For the plant manager who needs to know what left the warehouse and when.
For the owner who needs an audit trail that survives any scrutiny.
For the finance team that is done reconciling three different spreadsheets.