See it in 50 seconds
You are holding someone else's gold
Odoo Repairs knows how to fix your own products. It does not know what to do with a customer's ring.
A jewellery shop takes in pieces that belong to somebody else, keeps them in a safe, hands them to a jeweller, and gives them back weeks later. If anything is different when the customer collects it, the shop has to prove what it received. This module adds that layer on top of the native Repairs app: a permanent file per piece, typed photographs, signatures at every hand-over, scrap reconciliation with the jeweller, and quality control before anything is handed back.
The board every morning: who has what, promised for when, and which pieces are already late.
The piece is a file, not a line
The same ring comes back for service years later. It keeps its reference, its metal, its weight, its photographs and its whole service history, long after each repair is closed and archived.
It never enters your stock valuation
A customer's gold is not your asset. Pieces are held with the owner recorded on the quant, so they can be traced through Inventory without a single gram landing on your balance sheet.
Owner, metal, fineness, pure weight, measurements, tester reading and every photograph ever taken of it — on one record that outlives the repair.
Photos that are enforced, not suggested
You decide the shot list, and the module holds the counter to it. The checklist adapts to the piece in hand: ring size only on rings, length only on chains, the laser inscription only when there is a diamond. A piece with a required photo missing cannot be handed to the workshop — not a warning, a block.
- Photo kinds are configuration, not code: add, remove or rename them
- Registers without a camera show a QR that hands the job to a phone
- Photos taken against a repair are kept on the piece file for good
What is still owed before the piece may leave is written on the order itself, not left to memory.
The checklist itself is data: each shot says when it is asked for and what makes it apply.
Know the gold that did not come back
When you supply the metal, the module weighs the whole story: what you handed over, what came back as scrap, and how much heavier the pieces are — because that difference is metal that legitimately stayed in the work. Only what is left counts as loss.
| Handed to the jeweler | 10.000 g |
| Scrap returned | − 8.500 g |
| Stayed in the pieces | − 0.600 g |
| Real loss | 0.900 g · 9% |
Tolerance cascades: company default, overridden per jeweler, overridden again on a single hand-over. Going over is logged on the record and counted on the jeweller's scorecard.
Karat as a number, at last
Most shops keep the karat as free text on the product, which is useless for arithmetic. Map each value of the metal attribute you already use to its fineness once, and the pure metal weight of every piece is computed from then on. No parallel list of metals, no retyping your catalogue's vocabulary.
Signatures
Handwritten, on screen, at three moments: when the customer leaves the piece, when the jeweller takes it, and when it is handed back. Each one can be required or turned off.
Workshop dispatch
One document per jeweller with every piece they take — from different customers if need be — their signature, the metal supplied and the date they commit to.
Settlements
Rate card per jeweller, always editable on the piece. Settle job by job or run a weekly cut; external jewellers get a vendor bill out of it.
Built on Odoo Repairs, not around it
Service orders are native repair orders. Sell a repair service on a quotation and Odoo creates one order per line by itself; this module adds the states the trade needs — waiting authorization, inspection, rework, delivered — around the native ones rather than replacing them, so an upgrade of Odoo's own Repairs app does not take your workshop down with it.
- Customer portal: the owner follows the piece and sees the photographs
- Printable receipts on an 80 mm roll and on a full page
- Intake and delivery terms are yours to write, printed on the receipt
- Three permission levels: counter, workshop, manager
- English and Spanish (Mexico)
How strict the counter is, is a setting: shops with a tablet ask for every shot, shops without one ask for none and let the block fall on the workshop door instead.
Goes further with
Jewelry Repairs & Workshop — Point of Sale: receive, look up and
deliver pieces without leaving the register.
Jewelry Repairs & Workshop — WhatsApp: tell the customer the
moment the piece is ready, and chase the ones who never come back.
Requires only Community modules: Repairs, Sales, Inventory, Invoicing.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Repairs (repair) • Sales (sale_management) |
| Lines of code | 3383 |
| Technical Name |
xb_jewelry_service |
| License | OPL-1 |
| Website | https://www.xubax.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module