Skip to main content
All case studies
LiveEnterprise SaaS

Ram Pottery Hub

Enterprise ERP and accounting platform developed for Ram Pottery Ltd, covering invoicing, quotations, credit notes, inventory, customers, VAT reporting and real-time business analytics.

Ram Pottery Hub — product screenshot
Live DemoPrivate Repository

Role

Full Stack Developer

Technologies

Next.jsTypeScriptSupabasePostgreSQLREST API

The Problem

Ram Pottery Ltd was running invoicing, quotations, credit notes, stock and VAT reporting across disconnected spreadsheets and manual processes, making it hard to get an accurate, real-time view of the business.

The Solution

A dedicated ERP and accounting platform was built to centralise invoicing, quotations, credit notes, inventory, customer records and VAT reporting in one system, with real-time dashboards for day-to-day decisions.

Approach

  • Mapped existing invoicing, quotation and VAT workflows before writing any code
  • Designed a relational schema covering customers, products, stock and tax rules
  • Built the platform in incremental modules, validated against real business documents at each stage

Features

Invoicing & quotationsCredit notesInventory managementVAT reportingReal-time analytics

Challenges

Keeping VAT calculations and credit-note logic accurate across edge cases such as partial refunds and mixed-rate invoices required careful, tested business logic rather than generic accounting shortcuts.

Architecture

Built on Next.js with a Supabase/PostgreSQL backend, using REST APIs to separate the accounting logic from the presentation layer and keep reporting queries performant as data volume grows.

Current Outcome

The platform is in active production use at Ram Pottery Ltd, handling day-to-day invoicing, stock and VAT reporting for the business.

Future Improvements

Planned next steps include deeper analytics and automated VAT filing exports.

Lessons Learned

Enterprise accounting software lives or dies on getting the edge cases right — the unglamorous validation work mattered more than any single feature.

Have a similar problem to solve?

Every project on this site started with a conversation.