Primary measure
- Counter sale
- Product weight and the applied pricing rule could be retained.
- Workshop dispatch
- Dispatched and returned weights and fineness could be compared.
Developed on request
Jewellery Retail & WorkshopRead weight, fineness and money movements meaningfully within each transaction. We will define calculation rules, workmanship charges and workshop reconciliation for the jewellery software we will build using your examples. Rate changes affecting new quotations will remain separate from completed sales.

Keep weight and fineness together to compare products of different purities. A table counting pieces cannot explain bullion and workmanship-priced jewellery in the same way. Separate workshop and customer-safekeeping notes may blur physical stock and account balances.
The software we will build will relate weight, carat and fineness in parts per thousand to fine gold equivalent. Calculation precision and rounding will follow your practices. Sales, scrap purchases, safekeeping and deposits could be scoped as separate movements. The record structure will allow separate reviews of the sources behind money, weight and fine gold balances. Branch transfers will also be distinguished from sales.
Our sample transaction will cover selling an incoming item and buying another item from the customer. Both could share a customer account while purchase quantities and sale amounts remain distinct. Your weighing, purity recording and workmanship methods will determine when pricing occurs. This example gives us a starting point for checking calculation fields together.
Weight, carat, fineness and workmanship charges could join the product record. You define fine gold precision and rounding.
Applied rates and pricing rules could be linked to each movement. Scrap purchases and sales will have separately scoped stock and account effects.
Cash, weight and fine gold summaries could use distinct measures. Material at workshops and physical shop stock will be reviewed separately.
The first release can centre on product measures and transaction calculations. Select rules for money balances and gold debts as separate measures. Deposits, safekeeping and scrap purchases will follow your document examples. A workshop module could address comparison of dispatched and returned material. Branch consolidation will separately consider physical locations and the central fine gold total.
Handing an item to a customer creates a sale; dispatching material to a workshop needs a different movement. Treating workshop dispatch as a sale could incorrectly link stock and customer balances. Share your workshop examples of weight, fineness and tolerances to define reconciliation measures. The scope we will build will define physical location and account impact separately for each movement; counter and workshop records could join a common fine gold overview.
| Counter-sale calculations and workshop-return reconciliation | Counter sale | Workshop dispatch |
|---|---|---|
| Primary measure | Product weight and the applied pricing rule could be retained. | Dispatched and returned weights and fineness could be compared. |
| Account side | Customer payment or gold accounts will be linked. | Workshop accounts and agreed tolerances will be defined separately. |
| Closing basis | Handover and payment checks could be selected. | Return measures and reconciliation decisions will be scoped. |
Viewing sale prices need not grant access to purchase-cost changes or all customer balances. In the software we will build, pricing-rule changes, discounts and corrections to earlier weights may have separate permissions. You can determine which stock branch staff see and who approves workshop reconciliation. Exporting and reopening closed movements will also be discussed during discovery.
Sale entry, discount requests and cost visibility could follow separate responsibilities. Activity records for rate changes will be designed in the project.
Changing dispatch measurements and explaining return differences will have separate permissions. Corrections will be scoped with links to earlier values.
KVKK, Turkey's personal data protection law, identity and contact details, safekeeping retention and fiscal requirements are considered in scope. Your business remains the data controller.
If a rate changes while a customer considers an item, you must choose how an unfinished quotation is renewed. Applied rate, source and transaction time could be scoped. Your pricing policy will determine whether new rates affect open quotations. Completed sales will be designed to retain their applied values separately from later market rates.
Fineness behind weight and fine gold calculations will also be distinct from pricing rates. We will consider how weighing corrections affect stock and accounts. During a data outage, use of the last known rate and permission to continue will be scoped separately. Measurement corrections, repricing and reviews of older transactions will therefore be separate decision points.
We will review which old columns contain weight, carat and fine gold equivalent. Customer totals alone will not be imported as item-level history. Share separate shop, branch and workshop sources to confirm physical locations. A sample transfer will check units, decimal formats and rounding so the basis of opening calculations can be explained.
Product weight, fineness and existing fine gold fields could be compared. Missing purity or differing units could be flagged for authorised review.
Customer money, gold debt and safekeeping balances will be checked separately. Workshop material will be reviewed independently of shop stock.
If your selected source offers a connection, access and usage conditions will be assessed. Manual rates, outages and reconnection behaviour will be discussed.
Weight, fine gold and money relationships may need more detail than a general product list. Our web service explains turning your calculations into custom application scope. The workflow article offers a framework for counter and workshop decisions. Use these resources to identify entered values, calculated values and totals that you review yourself before our conversation.
Prepare anonymised product records, sale examples and workshop dispatch and return records. Explain today’s decision on open quotations when rates change. Together, we will select measures and customer movements for the first release we will build. Branch fine gold consolidation and rate-source connections could be discussed separately from daily counter scope.
The quotation follows clarification of measures and pricing rules. Use is considered on a subscription basis; support and alternative agreements will be discussed in writing.
We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.
We listen to how your business works, your team and the tools you use today.
Modules, priorities and price are set out in a written quote.
We show working versions at short intervals and move on with your feedback.
We move your existing records across and help your team get started.
We run the software on a subscription and keep it up to date and secure.
The rate can be entered manually or fed from a data source of your choice; that connection is scoped per project. Which source to use is your commercial decision. In both cases, prices are recalculated from the rate entered.
The weight and fineness of each item are recorded, and the fine gold equivalent is derived from these two values. We agree the calculation rules and rounding preferences with you in the discovery meeting, based on the way you work.
This module can be part of the scope. Outgoing and returning weights and fineness are recorded, and the difference is compared with the tolerance agreed with that workshop, so loss becomes a recorded figure rather than a dispute.
We design the software so that prices are recalculated from the current rate, whether entered or fed in. That way nothing is sold at yesterday's rate until someone changes the labels, and the rate applied to every sale stays on record.
We address outages in the scope. The counter can be designed to keep working on the last known rate and to show this clearly on screen; records sync when the connection returns.
Cash register (ÖKC) and card terminal connections are scoped per project and made only with devices that meet the regulations. Your accountant advises on which document is issued for which transaction and on any tax questions; the software does not make those decisions for you.
We could scope a workflow retaining completed-sale rates and requiring a separate decision to renew open quotations. Your shop’s record procedures will define when a transaction is complete.
Safekeeping could be designed with separate customer accounts and physical locations. We will select which material belongs to shop stock and which checks apply at handover during discovery.
After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.
In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.
We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.
Grocery & Corner Shop
Software we build on request for grocers and corner shops: barcode sales, stock, a digital credit book and what you owe your wholesalers, all kept in one place.
ViewEstate Agency Operations
Software we build on request for estate agencies: one record per property, matching buyer and tenant requirements to listings, authorisation deadlines and agent commission.
ViewTextile & Garment Manufacturing
Software we build on request for textile and garment manufacturers: colour and size breakdowns, stage tracking from cutting to packing, subcontract units, fabric and waste records.
ViewLet us define jewellery software scope from weighed stock through workshop returns using your examples.