Globerz

The constraint

What the system had to solve before a line of it was designed.

Globerz brought Solonomous three distinct problems under one roof. Financial operations were manual and non-compliant by design — invoicing, expenses, payments, and ledgers lived outside any system that understood Indian tax law. There was no enforced double-entry discipline, no GST/TDS automation, no approval trail, and no reconciliation between bank statements and books. Every month-end was a reconstruction exercise. Corporate events had no operational backbone — events were run on calendars and inboxes with no structured way to manage capacity, take bookings, collect and reconcile payments, route events through approvals, or show what events actually returned. Commerce was a disconnected storefront — Globerz needed a modern shopping experience with a guided checkout, a wide range of payment options, and an admin surface for products and orders that plugged into back-office systems rather than living as an island. Cutting across all three: the platform had to be bilingual (English and Arabic, full RTL), multi-currency, secure by default, and fast — heavy finance pages were initially shipping multi-megabyte bundles that had to be brought under control.

Architecture

The stack read top down, from what the user touches to what keeps it running in production.

Modules delivered

Each one shipped production-grade, not as a demo surface.

• 01Finance — Invoicing across nine document types with e-Invoice (IRN/QR) and e-Way Bill
• 02Finance — Quotations with versioning, e-signature acceptance and one-click invoice conversion
• 03Finance — Double-entry GL with hierarchical Chart of Accounts and period locking
• 04Finance — Bank-statement reconciliation with confidence scoring and period locking
• 05Finance — GST/TDS/TCS tax master with HSN/SAC mapping and enforced double-entry
• 06Finance — Multi-level approval workflows and immutable field-level audit log
• 07Finance — Razorpay integration (orders, HMAC verification, refunds, webhooks)
• 08Events — Full event lifecycle across fifteen event types (physical/virtual/hybrid)
• 09Events — Booking engine with ticket types, capacity enforcement and waitlist promotion
• 10Events — SLA-tracked multi-step approval workflows with overdue tracking
• 11Events — Multi-channel notifications and complete field-level audit log
• 12Events — FullCalendar-based interactive calendar with revenue analytics dashboard
• 13E-Commerce — Branded storefront with guided multi-step checkout
• 14E-Commerce — Fifteen-gateway payment selection with Razorpay order API
• 15E-Commerce — Admin suite for products, orders, customers and sellers

Scope delivered

What the build covered, end to end.

1. 0125+ data models
2. 02~196 secured API routes
3. 03EN/AR (RTL)

Design decisions

What we learned before building, and what the built system moved.

Solonomous treated the three modules as one platform problem, not three projects. A single architectural spine let each module stay independent in domain logic while sharing security, internationalisation, and design language. Three principles governed delivery: compliance and correctness are features, not afterthoughts — finance was modelled around real Indian statutory requirements (GST, TDS/TCS, e-Invoice, e-Way Bill) and enforced double-entry accounting at the data layer; every privileged route is guarded server-side on the API surface, not assumed from the UI; and ship production, not demos — approval workflows, audit trails, soft-deletes, and reconciliation were built in from the start. Security hardening was delivered alongside the build: server-side authentication enforcement applied across the privileged API surface, permission checks restored on destructive operations, an auth-bypass switch fenced behind a non-production guard, removal of console/PII logging leaks, and webhook PII redaction.

The platform compiles cleanly with TypeScript reporting no errors and 35/35 static pages generating successfully. Approximately 196 API routes are verified and guarded across the application. Bundle-size optimisation on the heaviest finance pages brought bundles from approximately 2.52 MB down to approximately 150 kB — a greater-than-90% reduction — via dynamic imports and barrel-export pruning, materially improving load times on data-entry-heavy screens. Forty-six API route files across thirteen directories were brought under authentication during the hardening pass. The platform is bilingual (English and Arabic, RTL) and multi-currency across all three modules. Globerz now has a GST- and double-entry-grade finance system, a full event lifecycle platform with SLA-tracked approvals and revenue analytics, and a branded multi-gateway commerce experience — all on one secure, audited platform.