Check whether the relevant customer and transaction records are complete before closing a gold jewellery transaction. Choose the transaction type and review the applicable records instead of using one generic document list for every sale, repair, custom order or buyback.
Gold transactions can create different documentation requirements depending on what happened. A jewellery repair, a customer purchase and an old-gold buyback are not the same transaction, so a single universal checklist can either omit useful records or create unnecessary paperwork.
The purpose of this tool is to provide a practical completeness review. It does not claim that every business has the same legal or regulatory requirements. The business should adapt its documented process to the rules and contracts that apply to its operation.
Each transaction type loads a relevant set of document categories. A record can be marked complete, missing or not applicable. The percentage represents completed applicable items divided by all applicable checklist items.
A purchase workflow may use an order or invoice reference, customer information, item specification, final price and payment record.
A repair can require an intake record, condition notes, requested repair, estimate or approval and final handover documentation.
A bespoke order may need the approved design specification, quotation, order confirmation, measurements, production reference, payment records and delivery confirmation.
A buyback workflow can require item identification, weight and purity information, valuation basis, deductions, offer/settlement information and the records required by the business's applicable procedures.
No. Legal and regulatory documentation requirements vary by location, transaction and business type. This tool is an operational checklist and should not be treated as legal advice.
Different transactions require different records. Marking a genuinely irrelevant record as not applicable prevents it from reducing the completeness score.
Yes. It is specifically designed as a final record-completeness review.
No. It works in the browser and does not create a server-side customer database.