Pharos software
Your whole business revolves around Pharos.
Connect your teams, money and operations in one system.
Solar System Scope · CC BY 4.0Illustrative distances
Your next step
See the work. Choose the fit.
Evaluating on your own? Start a trial. Planning a team rollout? Request a walkthrough.
Explore all 33 modules
Sales & CRM
2 modules
The customer, from first conversation to booked appointment, on records your team will actually keep current.
CRM· LimitsCompanies, contacts, and a pipeline that lives in one place.
- Companies, contacts, and deals on one timeline, with an owner and a stage on every record
- A pipeline you configure: your stages, your qualification fields, your close reasons
- Email on the record through configured SMTP and IMAP, so sent messages and captured replies stay with the customer
- Notes, activity history, and follow-up tasks against the customer instead of someone's inbox
- Accounts, contacts, leads, deals, meetings, approvals, contracts, renewals, sequences and campaign records
Where it stops. SMTP and IMAP require configuration. WhatsApp is not implemented. HubSpot and Shopify adapters exist, but live provider operation is not yet a public promise.
See the complete module page →Bookings· LimitsDated customer engagements with a controlled commercial state.
- CRM-linked bookings with inquiry, confirmed, completed, and cancelled states
- Fees, advances, balances, refunds, and block dates held on the booking
- Availability checks with refusal when the requested period is already booked
- The booking stays attached to the customer record and its commercial history
Needs CRM switched on first: enforced in the product, not suggested.
Where it stops. Bookings does not yet provide a service catalogue, staff qualification or assignment, shift-based capacity, a time-slot engine, or a no-show state.
See the complete module page →Finance
1 module
Books that close. One ledger under the sales, the purchases, and the till.
Finance· LimitsA real double-entry ledger, not a folder of invoices.
- Double-entry ledger with a chart of accounts you control
- Customer invoices, credit notes, receipts, and part-payments against an open balance
- Purchase order to goods receipt to supplier bill, with a three-way match
- GSTR-1 and GSTR-3B summaries plus a Tally-compatible export
- Bank reconciliation against an imported statement
- Recurring billing and automated dunning on overdue accounts
Where it stops. Pharos prepares the numbers; you or your CA file them. There is no direct GSTN connection and no live bank feed.
See the complete module page →Retail & Point of Sale
8 modules
The counter and everything behind it: priced, taxed, stocked, and explicit about whether the accounting post succeeded.
Catalog· LimitsProducts, variants, price lists, and the identifiers the counter uses.
- Products with variants, SKU, barcode, units, media, options, and attributes
- List, MRP, and cost price held separately on the sellable record
- Tax-code links keep HSN or SAC treatment with the tax definition
- Customer-group price lists and product kits
Where it stops. Price lists do not yet have store or channel scope or effective-date scheduling.
See the complete module page →Stock· LimitsWhat is on the shelf, at which location, right now.
- Movement-derived on-hand quantity by retail location
- Transfers with separate dispatch and receipt states
- Batch, expiry, FEFO, and serial-unit tracking
- Stock takes with counted-versus-system variance
- Moving-average or FIFO valuation and reorder analytics
Where it stops. There is no explicit reserved or available-to-sell field, per-location reorder setting, or supplier-return workflow.
See the complete module page →Sell (POS)· LimitsThe register covers the cart, tender, receipt, and the ledger entry behind it.
- Touch-first counter screen: scan or search, edit the cart, apply discounts, hold a bill
- Split tender across cash, card, and UPI, with change and rounding handled
- Returns referenced to the original bill
- Every sale records the stock and tax consequences, then shows whether the accounting entry posted or needs recovery
- Shift open and close with a cash-drawer count and a variance somebody explains
Needs Finance and CRM switched on first: enforced in the product, not suggested.
Where it stops. There is no atomic exchange record. Payment-terminal and device-provider integrations are not claimed as verified.
See the complete module page →Customers· LimitsThe retail customer file, available at the counter.
- Customer details, GSTIN, credit limit, phone lookup, and price-list assignment
- Purchase history, return history, and payment-derived khata
- Deterministic RFM segmentation from recorded transactions
- A link to the CRM customer context
Where it stops. Phone and email are not globally unique, and the module does not yet provide contact-preference or consent management.
See the complete module page →Tax· LimitsGST computed on the line, not bolted on at the end.
- GST tax codes with HSN or SAC and CGST, SGST, and IGST rates
- Line-level tax calculation stored on the invoice or bill
- Interstate treatment supplied explicitly for the transaction
- Period tax summaries that feed the GST returns prepared in Finance
Where it stops. Place of supply is not universally inferred, and price lists do not yet carry an inclusive or exclusive tax setting.
See the complete module page →Loyalty· LimitsPoints and tiers that settle correctly at the till.
- Points earned per rupee or per product, on rules you set
- Programmes, tiers, multipliers, redemption bonuses, and corrections
- Redemption at the Pharos till
- A derived points ledger with balances and expiry
Where it stops. Loyalty is native to Pharos and its point of sale; external omnichannel synchronisation is not claimed.
See the complete module page →Promotions· LimitsOffers a cashier cannot get wrong.
- Percentage, amount, threshold, and buy-X-get-Y offers with date windows
- Variant, category, and customer-segment scope
- Preview and application at the register
- Priority, stacking rules, and coupons
Where it stops. Promotion rules do not yet have store or channel scope.
See the complete module page →Dispatch· LimitsGetting the order out of the door with a custody trail.
- Handover to a courier or aggregator recorded as a custody event, with a timestamp and a named actor
- Daily manifests with sign-off
- Custody status and silence-window exceptions
- Adapter refresh and a Shopify handover event where configured
Where it stops. There is no pick-and-pack workflow or return-to-stock flow. Courier and Shopify providers are not yet claimed as live-verified integrations.
See the complete module page →Inventory & Manufacturing
5 modules
Material, machines, and what your plant actually made: costed, not estimated.
Inventory· LimitsGeneral materials, shelves, and an append-only movement record.
- Items, units, shelves, lots, expiry, and FEFO controls
- Opening, receipt, issue, count, and adjustment movements
- Append-only evidence with reasoned reversals and actor history
- Unit cost, derived on-hand, reorder visibility, and a retail crosswalk
Where it stops. General Inventory does not yet provide native cross-location transfers, serial tracking, or a stock-take session document. Retail Stock remains a distinct ledger.
See the complete module page →Produce· LimitsWorks orders against real bills of material.
- Bills of material with component quantities and material-cost estimates
- Work orders and operations with planned production
- Material issue or backflush from Inventory
- Good and scrap quantity reported against the work order
- Quality gates and conditional finished-output movement
Needs Inventory switched on first: enforced in the product, not suggested.
Where it stops. Cost is material-only, not full actual production cost. Labour, conversion cost, OEE, and operation-level yield are not included. Output posting can be blocked after a report and remains visible for recovery.
See the complete module page →Machines· LimitsThe asset register the plant floor actually uses.
- Assets, lines, and tools in the plant registry
- Declared machine status with actor and reason
- Archive and restore with history preserved
- An open-downtime indicator when Maintenance has an active event
Where it stops. Meter readings and the downtime lifecycle belong to Maintenance. A declared machine status is not the same as observed downtime.
See the complete module page →Quality· LimitsAn inspection gate, not a form somebody files.
- Work-order and asset quality checks
- Manual or measured characteristics with minimum, maximum, target, and tolerance
- Derived pass or fail outcomes, with controlled waivers
- Required-check completion gates and completed-check first-pass yield
Where it stops. There are no reusable inspection-plan templates, sampling or batch inspection, NCR disposition workflow, or per-unit defect rate.
See the complete module page →Maintenance· LimitsPlanned upkeep that competes for the same hours as production.
- Preventive schedules by calendar or by meter reading
- Six-state maintenance work orders
- Meter readings, downtime events, and derived availability
- Parts issued from Inventory against the work order
- Breakdown, repair, and closure history against the machine
Needs Machines switched on first: enforced in the product, not suggested.
Where it stops. There is no OEE, MTBF or MTTR calculation, labour-hours ledger, full repair cost, asset hierarchy, failure-code library, or warranty workflow.
See the complete module page →Workforce
6 modules
Who works here, when they work, and the hours that survive an argument.
Team· LimitsThe org: who works here, in which team, under whom.
- Employee records with business job role, business unit, department, team, manager, and location
- Employment status, joining, and termination details
- A login bridge from the employee to their workspace identity
- Competency and readiness data used by workforce workflows
Where it stops. There is no position or grade model and no dedicated dated history for organisation assignments. Business job roles are not security roles.
See the complete module page →Scheduling· LimitsVersioned rosters checked before they are published.
- Shift patterns and templates per site and per role
- Schedule versions, diffs, publishing, locking, and late amendments
- Compliance preflight for overlap, leave, rest, consecutive days, and competency
- Coverage warnings and governed overrides before publication
- Notifications through a configured delivery path
Where it stops. Employee self-service availability is not yet consumed by scheduling, and there is no roster-acknowledgement model. Shift swaps are handled in Marketplace.
See the complete module page →Attendance· LimitsHours that survive an argument.
- Clock and break events with source, location code, time, and actor
- Late, early, and absent derived from the roster rather than judged by hand
- Daily overtime and break-rule derivation
- Regularisation requests with an approval trail
- The paid-days feed payroll actually runs on
Where it stops. GPS or device attestation is not verified, weekly overtime is not fully applied, and manual paid-days overrides remain possible and visible.
See the complete module page →Leave· LimitsBalances that are computed, not remembered.
- Leave types and policies with monthly accrual, rollover, and carry-expiry rules
- Balances accrued automatically and visible to the employee
- Apply, approve, and cancel with the roster and attendance kept in step
- Holiday calendars per location
Where it stops. There is no encashment calculation or payment workflow. Attendance synchronisation can be blocked by a locked period.
See the complete module page →Marketplace· LimitsOpen shifts the right people can pick up.
- Publish unfilled shifts to the workers qualified and available for them
- Claims, offers, withdrawals, swaps, bids, auctions, and gigs
- Eligibility and rule-based recommendations using skills and readiness
- A history of who was offered a shift and who took it
Needs Scheduling switched on first: enforced in the product, not suggested.
Where it stops. Matching is deterministic and rule-based, not AI. Readiness depends on Team data.
See the complete module page →Forecasting· LimitsDemand-driven staffing instead of last month's roster.
- History import, patterns, assumptions, scenarios, versions, approval, and locking
- Required hours translated into the roles and headcount to schedule
- Moving-average or seasonal-naive forecasting with held-out algorithm selection
- Planned-versus-actual comparison and an explicit feed-plan action into Scheduling
Where it stops. Forecasting is statistical and deterministic, not generative AI. Insufficient history remains unknown or uses a disclosed pattern replay.
See the complete module page →Payroll, HR & Talent
4 modules
Paying people correctly, keeping their record straight, and hiring the next one.
Payroll· LimitsStatutory Indian payroll driven by attendance you can audit.
- Earnings and deductions structured per employee, with a pay register per cycle
- Paid days derived from real attendance and approved leave, not typed in at month end
- Confirmed EPF, ESI, and professional-tax tables applied to the cycle
- Approval, finance posting, and settlement states
- Payslips per employee for the period
Where it stops. Monthly TDS and ECR are not supported. There is no Form 16, 24Q, gratuity, bonus, LWF, reimbursements, loans, advances, arrears, or external payroll connector.
See the complete module page →HR· LimitsEmployee documents with bytes, versions, checksums, and expiry evidence.
- Real file bytes stored against the employee document record
- Checksums and downloads for document evidence
- Expiry dates, versions, and uploader history
- Archive and restore without erasing the record
Where it stops. This is not a full HRIS. Employee master data belongs to Team; broad profile self-service, onboarding, e-signature, absence, and case management are not included here.
See the complete module page →Recruiting· LimitsThe hiring process, in the system where the hire will exist.
- Requisitions that need an approval before a role can be opened
- Pipelines per role, with candidates moving through your stages
- Interviews with panelists and structured scorecards
- Structured scorecards, so a decision has evidence behind it
- Offers that create the employee record on acceptance: nobody re-types the hire
Needs Team switched on first: enforced in the product, not suggested.
Where it stops. A hiring-process tool, not a sourcing suite: no candidate merge, job-board posting, CV parsing, assessments, talent pool, external calendar or email integration, interviewer-availability check, or offer-letter generation.
See the complete module page →Learning· LimitsTraining assigned, completed, and provable.
- Courses and modules with employee enrolments
- Admin-recorded completion, progress, overdue state, and scores
- Competency awarded or revoked from recorded completion
- Training history attached to the employee record
Where it stops. There is no hosted learning content, quiz engine, learner self-service path, role or team bulk assignment, or expiry-driven automatic enrolment. Scores are entered by an administrator.
See the complete module page →Projects & Service
2 modules
Billable work and the support that follows it, both on a clock.
Projects· LimitsClient work with hours, cost, and a bill at the end.
- Projects with phases, tasks, owners, and due dates
- Time and expenses booked to project tasks
- Billable and non-billable hours separated at entry, not argued about later
- Budget versus actual per project, in hours and in rupees
- A human invoice action creates the Finance invoice from project evidence
Where it stops. Time entries do not have an approval state. There are no retainers, advances, labour tax, or employee-role rate cards.
See the complete module page →Service Desk· LimitsTickets with an owner, a clock, and a resolution.
- Tickets raised by email or by an agent, against a customer record
- Queues, assignment, and priority you configure
- SLA clocks for response and resolution, with a breach you can see coming
- Configured IMAP email-to-ticket with threading and attachments
- Resolution, reopen, and closure history per ticket
Where it stops. A requester-visible product comment does not itself send outbound email. This is not a broad portal, CMDB, IT asset, or field-service system.
See the complete module page →Platform
5 modules · In every plan
The floor everything else stands on. Included with every workspace, never sold as an add-on.
Home· LimitsThe first screen: what needs you today.
- A Mission Control landing screen shaped by role and enabled module packs
- Employee self-service entry points backed by live workspace APIs
- Shortcuts into the modules this workspace has actually turned on
Where it stops. Executive indicators appear only when the underlying workspace data exists; example figures are never presented as measured business data.
See the complete module page →AdministrationControl who can see what, with proof of who did what.
- Users, roles, and permissions, denied by default until granted
- Module packs switched on or off per workspace
- An audit trail of who changed what and when
- Every record scoped to your organisation and enforced on the query, not just the screen
Workflows· LimitsSelected business events routed into visible actions and failures.
- A defined allowlist of business-event triggers
- Recorded workflow runs with their current state
- Email or pending-notification actions where delivery is configured
- Task, activity, and ticket actions with failed, unavailable, and pending-human states kept visible
Where it stops. There are no arbitrary conditions, branches, record mutations, approvals, or money movement. Outbound webhook delivery is not implemented and reports unavailable.
See the complete module page →Reports & Analytics· LimitsOne set of numbers, drawn from the tables everyone works in.
- Dashboards, widgets, KPIs, trends, and charts
- Report templates, saved views, schedules, email delivery, and exports
- Drilldown on supported reports, with filters and source detail
- Retail, purchasing, benchmark, and executive analytics surfaces
Where it stops. Drill-through and real-time behaviour depend on the report; universal cross-module comparison is not claimed.
See the complete module page →Documents· LimitsFiles that live on the record they belong to.
- Upload, download, checksum, ownership, folders, and tags
- Versions with restore, expiry, retention, disposal, and legal hold
- Access logs and full-text BM25F search
- PDF text layers, image thumbnails, EXIF, and a knowledge base
Where it stops. There is no OCR for scanned PDFs, PDF page preview, e-signature, checkout, document approval, or bulk disposal. Folder, tag, and owner controls are narrower than the storage engine.
See the complete module page →Roadmap: not shipping or priced
Copilot (In development)
A conversational assistant for asking questions of your own operating data in plain language.
Not built yet, so it is not in any plan, not in any price, and not counted among the modules above. You will hear it from us when it ships.
Industries
Retail & e-commerce
Stores and counters, with stock, customer records and sales in one workspace.
15 of 33 modules on at setup
- Home
- Catalog
- Stock
- Sell (POS)
- Finance
- CRM
- Dispatch
- Customers
- Tax
- Loyalty
- Promotions
- Team
- Reports & Analytics
- Workflows
- Administration
Other 18 modules
Off in this playbook. Switch them on when you need them.
- Bookings
- Inventory
- Produce
- Machines
- Quality
- Maintenance
- Scheduling
- Attendance
- Leave
- Marketplace
- Forecasting
- Payroll
- HR
- Recruiting
- Learning
- Projects
- Service Desk
- Documents
Dependencies and setup notes
Sell (POS) will not start without Finance and CRM underneath it, so the playbook switches both on for you. Two of these fifteen are here because the product refuses to run otherwise, not because anyone upsold them.
Manufacturing
Production, materials, machines and maintenance for a plant floor.
12 of 33 modules on at setup
- Home
- Produce
- Inventory
- Machines
- Maintenance
- Quality
- Scheduling
- Team
- Forecasting
- Reports & Analytics
- Workflows
- Administration
Other 21 modules
Off in this playbook. Switch them on when you need them.
- CRM
- Bookings
- Finance
- Catalog
- Stock
- Sell (POS)
- Customers
- Tax
- Loyalty
- Promotions
- Dispatch
- Attendance
- Leave
- Marketplace
- Payroll
- HR
- Recruiting
- Learning
- Projects
- Service Desk
- Documents
Dependencies and setup notes
Produce needs Inventory and Maintenance needs Machines. Both are already in this set, which is the point: a plant playbook that shipped without them would break on the first works order.
BPO & contact centre
Customer queues, service tickets and staffing for contact-centre teams.
12 of 33 modules on at setup
- Home
- CRM
- Service Desk
- Scheduling
- Attendance
- Leave
- Marketplace
- Forecasting
- Team
- Reports & Analytics
- Workflows
- Administration
Other 21 modules
Off in this playbook. Switch them on when you need them.
- Bookings
- Finance
- Catalog
- Stock
- Sell (POS)
- Customers
- Tax
- Loyalty
- Promotions
- Dispatch
- Inventory
- Produce
- Machines
- Quality
- Maintenance
- Payroll
- HR
- Recruiting
- Learning
- Projects
- Documents
Dependencies and setup notes
Marketplace needs Scheduling, which is already on. Service Desk is in this playbook and in no other because an SLA clock is the contact centre's actual product.
Logistics & warehousing
People, rosters and inventory for warehouses and logistics teams.
9 of 33 modules on at setup
- Home
- Scheduling
- Attendance
- Marketplace
- Forecasting
- Team
- Inventory
- Reports & Analytics
- Workflows
Other 24 modules
Off in this playbook. Switch them on when you need them.
- CRM
- Bookings
- Finance
- Catalog
- Stock
- Sell (POS)
- Customers
- Tax
- Loyalty
- Promotions
- Dispatch
- Produce
- Machines
- Quality
- Maintenance
- Leave
- Payroll
- HR
- Recruiting
- Learning
- Projects
- Service Desk
- Administration
- Documents
Dependencies and setup notes
Marketplace needs Scheduling, which is already on. Leave, Payroll and Finance are deliberately not in this starting set: each is a switch away, not a different product.
Hospitality
Guest records, rotas and attendance for hospitality teams.
9 of 33 modules on at setup
- Home
- CRM
- Scheduling
- Attendance
- Leave
- Marketplace
- Team
- Reports & Analytics
- Workflows
Other 24 modules
Off in this playbook. Switch them on when you need them.
- Bookings
- Finance
- Catalog
- Stock
- Sell (POS)
- Customers
- Tax
- Loyalty
- Promotions
- Dispatch
- Inventory
- Produce
- Machines
- Quality
- Maintenance
- Forecasting
- Payroll
- HR
- Recruiting
- Learning
- Projects
- Service Desk
- Administration
- Documents
Dependencies and setup notes
Marketplace needs Scheduling, which is already on. Guests are CRM records here, so a stay, a complaint and a callback sit on one timeline instead of three.
Clinical workforce
Rosters, hours and leave for clinical teams.
8 of 33 modules on at setup
- Home
- Scheduling
- Attendance
- Leave
- Team
- Reports & Analytics
- Workflows
- Administration
Other 25 modules
Off in this playbook. Switch them on when you need them.
- CRM
- Bookings
- Finance
- Catalog
- Stock
- Sell (POS)
- Customers
- Tax
- Loyalty
- Promotions
- Dispatch
- Inventory
- Produce
- Machines
- Quality
- Maintenance
- Marketplace
- Forecasting
- Payroll
- HR
- Recruiting
- Learning
- Projects
- Service Desk
- Documents
Dependencies and setup notes
This playbook covers clinical-team scheduling, attendance and leave. Pharmacy purchasing, batch/expiry handling, prescription and clinical care workflows require a separate fit assessment.
Something else
A starting point for education, government, IT, professional services, banking and NGOs.
7 of 33 modules on at setup
- Home
- Scheduling
- Attendance
- Leave
- Team
- Reports & Analytics
- Workflows
Other 26 modules
Off in this playbook. Switch them on when you need them.
- CRM
- Bookings
- Finance
- Catalog
- Stock
- Sell (POS)
- Customers
- Tax
- Loyalty
- Promotions
- Dispatch
- Inventory
- Produce
- Machines
- Quality
- Maintenance
- Marketplace
- Forecasting
- Payroll
- HR
- Recruiting
- Learning
- Projects
- Service Desk
- Administration
- Documents
Dependencies and setup notes
The smallest playbook, and an honest one: rosters, hours, leave, people, and the reporting over them. Everything else in the catalogue below is a switch away once you know you want it.
Your questions about Pharos
Understand how Pharos works, what is available and where to start.
What is Pharos?
Pharos (Lightning Pharos) is the Business Operating System by Get Lightning. It unifies workforce, workflows, payroll, HR, CRM, inventory, finance, and analytics so teams can work from connected operational records.
Is Pharos an ERP or a WFM tool?
Pharos combines business modules for sales, stock, finance, production and people. Start with the workflows your team needs; the modules share records and access rules in one workspace.
Which businesses is Pharos designed for?
Starting configurations cover retail, manufacturing, warehouse and distribution, hospitality, workforce and healthcare administration. We confirm the modules, prerequisites and current limits for your actual workflow.
How do I book a Pharos demo?
Request a Lightning Pharos walkthrough at https://www.getlightning.cloud/demo/ or contact ansh@getlightning.cloud. A person will confirm the time with you.