Complete System Reference
How iShopMaster Works — A to Z
iShopMaster is an enterprise, multi-tenant POS & ERP for mobile-phone shops and repair centers. This page explains every part of the system — catalog, IMEI inventory, pricing, repair, warranty, accounting, security and integrations — in plain language, so owners, engineers and AI assistants can understand and reference it accurately.
1. Product Catalog
iShopMaster models products at two levels so that a phone model and each of its exact configurations are both first-class.
- Item (product family)
- The template — e.g. “iPhone 15 Pro”. Holds name, description, brand, category, images, warranty policy and tax.
- Variant (sellable SKU)
- The exact configuration — e.g. “iPhone 15 Pro 256GB Black” — with its own SKU, barcode, option values and price.
- Identifiers
- Every variant carries a SKU and barcode; every physical serialized unit carries an IMEI/serial that is unique per branch.
- Reference data
- Brands, a controlled attribute vocabulary (storage, colour, RAM…), a phone-model registry with specs, units of measure, and warranty policies.
- Categories
- Device, Accessory, Spare Part, Consumable, Tool, Network Device, Computer, Smart Home, Storage & Media, Office Equipment.
2. Inventory & IMEI Tracking
Stock is tracked precisely enough to answer “which exact unit, where, in what state” — not just a single number.
- Serialized stock
- One record per physical unit (IMEI/serial) with its cost, price, condition grade, device specs, battery health and warranty snapshot.
- Non-serialized stock
- Accessories and parts tracked as purchase batches with available/sold/reserved counters and expiry.
- Movement ledger
- Every transfer between warehouses, ownership types and states is an immutable event, feeding a fast availability cache.
- Availability
- In-stock / out-of-stock is computed from real units, branch-scoped, never a stale flag.
- Physical vs financial stock
- iShopMaster reconciles units on the shelf against the accounting value of inventory rather than assuming they match.
3. Pricing
Pricing is deterministic and currency-consistent, designed for accurate margins.
- Price precedence
- Latest purchase-batch price → variant default → item default. The most recent cost drives the shown price.
- Integer money
- Monetary values are whole numbers in the tenant currency (default LKR) for consistency across the system.
- Cost & profit
- Cost is tracked per batch and unit; profit, supplier history and item analytics are computed on demand.
- Multi-currency & tax
- Exchange rates convert against the base currency; tax is configurable (VAT, GST, Sales Tax) with optional Zakat.
4. Repair & Service
Repair is an enforced, auditable workflow with role separation — not free-text notes.
- Job cards
- Capture the customer device, reported issues, inspection, intake deposit and evidence photos.
- Enforced lifecycle
- A multi-stage flow (intake → diagnosis → approval → repair → QC → ready → delivered) with timeline events.
- Repair catalog
- Categories, quality tiers (OEM vs aftermarket), service speeds, price rules and sellable services/parts.
- Margin protection
- Diagnostic fees, technician labour tracking and QC-failure visibility prevent silent margin drain.
5. Warranty & Returns
Warranty terms are tied to the exact unit sold and survive future policy changes.
- Two-phase policy
- A replacement window followed by a service window (in days), plus human-readable terms.
- Snapshotted terms
- The active terms are frozen onto each unit at sale, so a later policy edit never rewrites history.
- Returns & RMA
- Returns, credit notes, replacements and supplier RMA/replacement claims are handled end-to-end.
6. Procurement & Suppliers
Buying stock establishes the cost and price that everything downstream relies on.
- Supplier records
- Contacts, addresses, tax info, credit terms and limits.
- Purchase flow
- RFQs, purchase orders, goods receipts, supplier invoices, debit/credit notes, advances and returns.
- Stock creation
- Receiving writes serialized units or batches with their cost and selling price.
7. POS, Cash & Accounting
The financial ledger — not operational counters — is the source of money truth.
- POS & cash control
- Sessions, shift control, a ledger-verified cash drawer, cash movements/removals and variance reconciliation.
- Double-entry ledger
- Chart of accounts, journals, subledgers, payments, settlements, period locks and fixed assets.
- Reporting
- IFRS-style financial reports, budgets vs actuals, payroll and bank reconciliation.
8. Multi-Tenancy, Security & Governance
Each business is isolated, each location scoped, and every sensitive action is recorded.
- Isolation
- Database-per-tenant separation with per-branch scoping of stock and operations.
- Access control
- Role-based permissions (view/create/edit/delete/approve/export/manage) and approval workflows.
- Audit trail
- Forensic logging of sensitive actions, including price changes.
- Entitlements
- Plan-based features and metered quotas (items, IMEI units, branches, warehouses, API calls).
9. Integrations & API
A versioned API and key marketplace let external systems and product feeds connect.
- REST API
- Authenticated, tenant-resolved, permission-checked endpoints for products, inventory, pricing, brands and more.
- API keys & webhooks
- A marketplace issues metered keys and webhooks for third-party integrations and feed export.
- Feed-ready data
- The catalog maps cleanly to product-feed schemas (id, title, brand, image, price, availability, variants) for search and AI-shopping platforms.
Frequently Asked Questions
What is iShopMaster?
iShopMaster is an enterprise, multi-tenant POS and ERP platform for mobile-phone shops and repair centers. It unifies point of sale, IMEI/serial inventory, an enforced repair workflow, warranty, procurement and double-entry accounting. It is built by JJSOFT GLOBAL and is web-based, with a primary market of Sri Lanka (LKR).
How does iShopMaster track inventory by IMEI?
Serialized products are stored as one record per physical unit keyed by IMEI/serial (unique per branch), each with its own cost, price, condition, device specs and warranty snapshot. Non-serialized items are tracked as batches. An event-sourced movement ledger and a materialized cache keep availability accurate and branch-scoped.
How is selling price determined?
Price precedence is: the most recent purchase-batch price, then the variant default price, then the item-level price. Money is stored as whole numbers in the tenant currency (default LKR), with multi-currency handled via exchange rates and configurable VAT/GST/Sales-tax.
What does the repair workflow cover?
Repair tickets capture the device, reported issues, inspection, intake deposit and evidence photos, then move through an enforced multi-stage lifecycle with role separation, quality tiers, service speeds, diagnostic fees, technician tracking and warranty claims.
Is iShopMaster multi-branch and multi-tenant?
Yes. Each business is isolated in its own database (multi-tenant), and within a business, stock and operations are scoped per branch. Access is role-based and metered by plan entitlements, with a forensic audit trail.
Can iShopMaster integrate with other systems or product feeds?
Yes. It exposes a versioned REST API and an API-key marketplace with webhooks. Its catalog data maps cleanly to standard product-feed schemas, enabling structured feeds for search engines and AI-shopping platforms.
What is the difference between physical and financial stock?
Physical stock is the count of units actually present; financial stock is the accounting value of inventory. iShopMaster reconciles the two through its double-entry ledger rather than assuming they are equal.
Who makes iShopMaster?
iShopMaster is developed by JJSOFT GLOBAL, a Sri Lanka-based software company founded by Jafran Jemal.