Jewellery ERP: Rate-Driven Pricing Software for Jewellers
Case Study
Jewellery ERP is a Kevion product for jewellery retailers who sell from a showroom and an online store. A jeweller records how each piece is made up, enters the day's gold and silver rates, and the system works out every price with a full breakdown. When a rate changes, affected prices are recalculated in the background and sent to the connected Shopify store or Zoho Books organisation. It is live with a free plan and trials on paid plans.
Proof Snapshot
Project Overview
Jewellery is priced by weight and by the day's metal rate, so a jeweller with an online store has to change hundreds of prices whenever gold moves. We built Jewellery ERP to make the price a result, not a field someone types. The jeweller describes each piece once, enters the rate each morning, and the catalogue and the online store follow.
Business Challenge
The hard part is not the formula. It is doing the calculation for a whole catalogue every time a rate changes, sending the new prices to another company's platform within its limits, and being able to show afterwards exactly how any price was reached.
- ✕Jewellers charge for making in three ways (per gram, a percentage of metal value, or a fixed amount), and the engine has to support all three on any piece
- ✕One rate change can alter the price of every SKU of that metal, which is too much work to do inside a single web request
- ✕Shopify limits how much one query can ask for and how fast an app can write, so a careless sync is refused
- ✕A price edited directly in Shopify would quietly disagree with the catalogue
- ✕A jeweller must be able to explain an old price long after the rate has moved on
Project Goals
- ✓One formula path for every price, with the breakdown kept beside the result
- ✓Rate changes that reprice the catalogue without the user waiting
- ✓Store sync that survives platform limits, expired tokens and repeated webhooks
- ✓A complete record of who or what changed each price
- ✓A public API so a jeweller's other systems can read and update the same data
Technical Architecture
Visual pipeline representing customer requests to backend processing data flows:
Technology Stack
| Layer | Technology |
|---|---|
| API | Laravel, PHP 8.3, Sanctum |
| Dashboard | Next.js, React 19, TypeScript, Tailwind CSS |
| Internal admin | Filament |
| Database | MySQL |
| Integrations | Shopify GraphQL Admin API, Zoho Books API |
| Payments | Razorpay |
| API docs | OpenAPI, generated from the code |
Execution Phases
Phase 1: Accounts and plans
Sign-up, plan selection, free trials, feature gating by plan, API keys and usage quotas.
Phase 2: Catalogue and Shopify
Products and SKUs, connecting a store, importing and matching by SKU code, and sending prices.
Phase 3: Masters and rates
Metals, purities and reference lists, then daily rates with history.
Phase 4: Make-up and pricing
The make-up of each SKU, the price calculation with its breakdown, and pricing settings for markup, GST and rounding.
Phase 5: Repricing
A rate change finds the SKUs it affects and reprices them in background batches.
Phase 6: Zoho Books and billing
A second channel on the same design, then Razorpay payments, coupons and add-on packs.
Technical Problems Solved
✕Repricing a whole catalogue
Solution: A rate change raises an event that queues the affected SKUs for repricing in batches, so the person entering the rate gets an immediate response.
✕Shopify query limits
Solution: Our first catalogue query asked for about five times what Shopify allows in one request. We cut the page size and page through large products instead.
✕Prices edited in Shopify
Solution: The ERP owns the price. On stores set to push automatically, a price changed in Shopify is corrected and the correction is logged.
✕One bad variant failing a product
Solution: Price updates are sent so that a refused variant is reported on its own and the rest of the product still updates.
✕Repeated and forged webhooks
Solution: Every webhook signature is checked and each event is handled once by its ID, so a retry from Shopify changes nothing.
✕API docs going stale
Solution: The documentation is generated from the routes and validation rules, and a test fails if a public endpoint is missing from it.
Business Results
Lessons Learned
- •Store how a price is built, not the price. Everything else in the product follows from that decision.
- •Put every price change through one piece of code. History, approvals and store sync all become simple when there is only one door.
- •Read a platform's limits before writing the sync. Our first Shopify query would have been refused by every store.
- •Decide early which system owns a number. Two places that can both edit a price will disagree.
Why Kevion Technologies
- ✦We build and run our own products, so we deal with billing, limits and support ourselves
- ✦Laravel and Next.js engineers who also build Shopify apps
- ✦Money and pricing logic kept on the server and covered by tests
- ✦The same written scope, fixed price and milestones if you want something like this built for your business
Planning a complex platform migration or custom integration?
Let's discuss your project parameters. Get a free custom scoping estimate and architecture consultation with our senior engineering team.
Services used on this project
Similar projects
API Performance Optimization: Logistics Platform
- Problem
- Slow APIs and database bottlenecks delayed shipment tracking and dashboards at peak traffic, while cloud costs kept rising.
- What we did
- Backend and database overhaul for a logistics platform processing thousands of shipment updates daily: faster APIs, Redis caching, and a cloud-ready architecture.
Chatify: Real-time Messaging SaaS
- Problem
- The team needed end-to-end encrypted messaging and calls they could host themselves.
- What we did
- Secure, real-time communication platform utilizing WebRTC and Socket.io to offer video calls, group chats, and end-to-end encryption.
Custom CRM Platform: Sales Automation & Reporting
- Problem
- Leads and customer data were spread across spreadsheets and messaging apps, with manual follow-ups and little reporting.
- What we did
- Custom CRM platform for a growing B2B sales organisation: lead management, automation, dashboards, and secure role-based access.
Related reading
PHP2Shell (CVE-2026-109618, CVE-2026-109619): Patch Every PHP Server Now
Two critical PHP core flaws, patched on October 21, 2026, let an attacker run code on a server with one unauthenticated request. Every PHP site and API is affected, whatever framework it runs.
Read article →llms.txt for Your Website: What to Put in It, and What It Does Not Do
llms.txt is a short Markdown file that tells AI assistants what your site is and which pages matter. Here is what belongs in it, an example to copy, and an honest look at who reads it today.
Read article →Jewellery Making Charges and Wastage Calculation Guide
A practical guide for Indian jewellers on calculating making charges and wastage, and how to automate daily price updates.
Read article →Ready to Start Building?
Tell us what you're working on. We reply to every enquiry within one business day (Mon–Sat, IST) with questions, a rough timeline and a quote. No obligation.
Not ready for a full build? Start with a free call or a small, paid discovery phase. see how we keep it low-risk.
General Enquiries
info@keviontechnologies.in
Support
support@keviontechnologies.in
Call Us
+91 75730 55757
Our Promise
A senior team member reads every enquiry and replies personally within one business day. In the UK, UAE or US? Tell us your time zone and we'll book a call that suits you.