Jewellery Barcode Tags: One Code per Gold Piece

In a gold shop, jewellery barcode tags work differently from barcodes in a supermarket. A supermarket code identifies a product type, and every can of the same product shares it. A gold shop code has to identify one physical piece, because two rings that look identical never weigh exactly the same, and weight is what you sell. One code, one piece, one weight and one karat: that is the whole rule.

TL;DR. Give every piece its own code that is never reused. Store weight, karat, stone weight, item type and source against that code in your system; print only what the counter needs to read. Leave the price off the tag, because gold prices move daily and the system computes them at sale. Tag at receipt, scan to verify before the piece reaches the display, retire the code when the piece is sold or melted, and issue a fresh code to anything that comes back from the workshop changed.

Why a gold shop needs a code per piece, not per product

Retail barcodes are designed around identical items. Jewellery breaks that assumption. Two 21 karat bangles from the same mould leave the workshop at slightly different weights, and a price computed from weight is only correct for the exact piece in the customer's hand.

	Code per product type	Code per piece
What the code identifies	"21 karat bangle, model X"	This bangle, weighed and recorded
Weight at the counter	Typed in or weighed each time	Pulled from the record
Stocktake	Count of pieces per type	Each piece found or missing by code
Missing item	"One bangle short"	Exactly which piece, with its weight
Fits	Packaged goods with fixed prices	Gold sold by weight and karat

The per-piece column is what makes a gold stocktake answerable. When the scale and the book disagree, you want a list of codes not found, not a number.

What goes on the tag, and what stays in the system

A jewellery tag is small. A ring tag has room for a code and two or three short lines at most. So split the data into what the counter must read without a scanner and what only the system needs.

Field	Printed on tag	Stored in system	Why
Unique code + barcode	Yes	Yes	The key to everything else
Karat	Yes	Yes	Staff check it against the hallmark
Net gold weight (g)	Usually yes	Yes	Lets staff spot a swapped tag on the scale
Stone weight or count	If space allows	Yes	Net weight excludes stones
Item type / model	Short code	Full description	Helps find pieces on the display
Source (trader, workshop batch)	No	Yes	Traceability without clutter
Date received	No	Yes	Ageing of slow stock
Price	No	Computed at sale	Gold price moves daily

Keep the karat on the tag consistent with the hallmark. In Egypt, testing and stamping jewellery falls to the hallmarking authority under the Ministry of Supply and Internal Trade, and the stamp is the reference your tag should copy, not the other way round.

Printing the weight is a judgement call. It helps staff catch a tag moved from one piece to another, because the scale disagrees immediately. Some owners prefer to keep weight off customer-facing tags; if you do, make sure the counter screen shows it on every scan.

Choosing a code and a numbering scheme

You do not need anything exotic. A linear barcode or a small 2D code both work with ordinary retail scanners, so pick what fits your smallest tag and test it on your scanner before ordering labels in bulk.

Global standards exist for codes that travel between companies. GS1-128, for example, uses Application Identifiers that, in GS1's words, "describe what type of information is in the barcode", such as serial or batch numbers (GS1 Sweden). For a code that lives only inside your own shop, the usual practice is simpler: an internal number that your system looks up.

A numbering scheme that holds up in practice:

1. A short prefix for the branch, if you run more than one, so transfers stay traceable.
2. A sequential number that never repeats, even after the piece is sold. Reusing codes turns old reports into nonsense.
3. No meaning hidden in the digits beyond that. Encoding karat or weight in the number looks clever until a piece is re-made at a different karat.
4. A check on duplicates at creation. The system, not a person, should refuse a code that already exists.

The tagging routine, from receipt to display

1. Receive and weigh. Weigh each piece on the shop scale, net of stones, and read the karat from the hallmark.
2. Create the record. Enter weight, karat, stones, type and source; the system issues the code.
3. Print and attach. Ring tags on rings, hang tags on chains and bangles. Attach before the piece leaves the receiving table.
4. Scan to verify. Scan the tag, check the screen matches the piece and the scale. A tag that does not scan now will not scan at the counter either.
5. Move to display or safe. Record the location if you track it.
6. Sell by scan. At the counter, scanning pulls weight and karat; the price is computed from the day's rate plus making charge.
7. Retire the code when the piece is sold, or when it is moved to scrap. The code stays in history and is never issued again.

When pieces leave and come back: workshop, scrap, returns

The tag routine is tested at the edges, not at the counter.

Sent to the workshop. The code moves with the piece, and the piece moves from shop stock to the workshop's balance. If it comes back unchanged, the same code goes back on display. If it comes back re-made, resized or at a different weight, close the old code and issue a new one with the new weight. The batch arithmetic is covered in jewellery workshop and making charge accounts.

Taken in as scrap. Scrap is usually tracked by weight per karat rather than by piece, so it does not need a display tag. When scrap settles a trader account, convert it on one written fineness basis, as set out in gold shop accounting.

Customer return. Reweigh before accepting. If the weight differs from the record, you have found the problem at the counter, not at month end.

Scanning at stocktake

Per-piece codes pay for themselves at stocktake. Instead of counting pieces per tray, you scan every tag and let the system list what was expected but not found. Each missing code comes with its weight and karat, so the gap is specific from the first minute. Pair the scan with a weight check by karat, as the gold shop inventory count method describes, because a scan proves the tag is there, while the scale proves the gold is.

The weight recorded against each code is also what exposes a piece switched for a fake at the counter; see theft prevention for gold shops.

How Tibr handles this

According to the Tibr product page, every piece in Tibr carries a barcode, with total weights per karat for finished pieces and scrap. Selling is by barcode: scan the piece, confirm, done, and one invoice can hold several pieces. Customer scrap trade-in is part of the invoice, and every movement is recorded under the name of the person who made it, with no deletions.

To see how barcode selling fits with the rest of a gold shop system, start with the gold shop management software guide, or try it on sample data from the signup page.

FAQ

Do I need a separate barcode for every gold piece?

Yes, if you sell by weight. Identical-looking pieces never weigh exactly the same, so a shared code would force staff to weigh and type every sale. A code per piece pulls the recorded weight and karat on scan and lets a stocktake name exactly which piece is missing.

Should the price be printed on a jewellery tag?

Usually not. The metal value changes with the day's gold price, so a printed price is out of date quickly. Print the code, karat and weight, and let the system compute the price at the moment of sale from the current rate plus making charge.

What happens to the barcode when a piece goes to the workshop?

The code travels with the piece while it sits in the workshop's balance. If the piece returns unchanged, the code goes back on display. If it is re-made or its weight changes, close the old code and issue a new one with the new weight and karat.

Can I reuse barcodes from sold pieces?

No. A reused code links two different pieces to one history, which breaks sales reports, stocktake comparisons and any later dispute. Retire codes when pieces are sold or scrapped and keep issuing new numbers.

Do I need GS1 registration for jewellery barcodes?

GS1 standards are built for codes shared between companies along a supply chain. For codes used only inside your own shop, a simple internal number that your system looks up is common practice. If you sell through partners who require GS1 codes, ask them what they need.

Written by the Mindshift Team, Tibr product team.

Want every piece to sell by scan with its weight and karat? See how Tibr works on its official page.