The work behind the system.
A polishing job can involve more than one weighing pass. Recording only a final number leaves the customer, issued material, making charge and settlement difficult to reconcile.
Built by PentaForge / Custom software
Jewellery Polishing Management System
A focused system for polishing orders, pieces, weights, making charges, loss and customer settlement history.
Discuss a similar systemA connected way to work.
PentaForge built an order registry with the fields the polishing workflow needs. A customer history brings past jobs together, while daily and monthly dashboard summaries separate fine to return, fine to collect and settled amounts.
The business workflow
From the first record to the final balance.
- 01Customer
- 02Order
- 03Weight in
- 04Weight out
- 05Making charge
- 06Loss & touch
- 07Fine total
- 08Settlement
01 / Inside the system
Polishing dashboard
Daily and monthly views bring together pieces, weights, charges, loss and settlement directions.
02 / Inside the system
Polishing order registry
A table records customers, pieces, two weight passes, making charges, loss and touch, with print and Excel export controls.
03 / Inside the system
Polishing customer history
Customer totals and an order history make previous work and fine settlement positions easier to review.
Key features
Designed around daily work.
- Order registry with customer and date filters
- Pieces and two weight-in / weight-out passes
- Making charge, loss and touch fields
- Customer history and fine settlement totals
- Daily and monthly summaries
- Print and Excel export controls
Engineering considerations
The details matter.
A loss calculation must match the workshop’s units and agreed rules. The supplied workflow uses weight in minus weight out minus making charge; touch and fine settlement follow the applicable business logic. These rules should be agreed for each implementation.
These views show the application’s desktop workspace. For a similar system, we agree device support, deployment, access controls and integration needs during discovery.
Good software starts with a conversation
Have a business problem?
Let’s engineer the solution.
You don’t need a technical specification. Tell us how your business works and where you’re facing problems.