SourceForge Software Services has shipped the SourceForge Jewellery Management add-on for Microsoft Dynamics 365 Business Central. It joins the AI Assistant, OCR Payable Agent, Reconciliation Agent, Global Payroll & HR, Plant & Maintenance, AI Mobile WMS, Retail for BC and Insight extensions, bringing the count to nine production BC extensions.
SFJM (the SourceForge Jewellery Management code-name) is structured as four composable apps. SFJM Core (object range 80000-80499) is the platform — composite piece + stone management, daily multi-rate board, valuation engine, old-gold buyback, karigar (artisan) job-work, jangad (consignment) tracking, loyalty, discounts, promotions, commission, gold-savings schemes, owner dashboard and e-commerce readiness. SFJM Billing POS (80500-80599) is a Level 2 touch point-of-sale delivered as a control add-in bundled inside the extension — scan-to-line, inline old-gold exchange, multi-tender settlement, park-and-recall. SFJM India Pack (80600-80699) adds BIS hallmarking with HUID register, GST split taxation, e-invoice IRN/QR via the BC E-Document framework, PAN capture, Section 269ST cash-limit enforcement, TCS on threshold sales, and gold-savings scheme regulatory guardrails. SFJM GCC Pack (80700-80799) adds Saudi Arabia ZATCA Phase 2 e-invoicing, UAE FTA readiness and reverse-charge on B2B gold/diamond trade, per-component investment-gold zero-rating, Dubai retail conventions (daily Dubai rate board, 22K default, per-gram making norms), and Arabic bilingual invoice layouts with full right-to-left rendering.
The architectural decision that shaped everything: jewellery is a composite-piece problem. A piece is gold of varying purities + multiple stones each with their own attributes + making charges + wastage. The Core models each component independently. Valuation walks the component list at the rate effective at the moment of valuation. When the piece posts, the engine explodes the value into correctly-grouped standard BC document lines so the customer's existing tax / e-invoicing stack reads them as normal invoices. SFJM never has to maintain its own tax engine and never has to be a parallel posting path.
Old-gold buyback is a first-class flow. A customer brings in old jewellery, the staff assays it (weight + purity), the engine calculates buyback value at today's rate, and applies it to the same invoice as a credit line. The old-gold itself enters a separate refining / re-stocking workflow inside Core. The transaction posts to BC as one invoice with positive (new) and negative (buyback) lines — finance never sees two separate documents. The India and GCC packs add their respective KYC and tax rules on the buyback leg.
Karigar and jangad workflows are wired through standard BC item-tracking conventions. Karigar (artisan) job-work tracks issued gold + stones, return weight reconciliation, wastage allowance, and bills the karigar via standard BC purchase / payment flow. Jangad (consignment) tracks pieces released to a counterparty for sale-or-return, per-piece, with reconciliation when they return or convert to a sale. Existing BC inventory reports keep working without modification.
AI features are additive and opt-in. Every Claude feature has a complete non-AI fallback so the system runs end to end without Claude if the customer prefers. AI features (describe-by-photo for catalogue ingestion, anomaly detection in the rate board, natural-language piece search) are key-gated — no API key, the features quietly disable themselves. Anthropic Claude is the sole provider; the key lives in BC Isolated Storage.
The product is strictly event-subscriber based. SFJM never modifies BC base codeunits, pages or tables. This is enforced by AppSourceCop and our own ruleset. It means SFJM cleanly co-exists with other AppSource extensions, survives BC monthly updates without breakage, and never blocks the customer from rolling forward to the latest BC release.
Target: Business Central 2025 release wave 2 (v27) and above. Cloud target only (SaaS) — no on-premises, no .NET interop. AL runtime 16.0. AppSourceCop-compliant with the SFJM mandatory affix. Object range 80000-80799 across the four apps. Distributed as a Per-Tenant Extension; AppSource publication on the roadmap.
Implementation typically runs 4-8 weeks for a single-store SMB retailer and 8-16 weeks for multi-store or multi-country (India + GCC) rollouts. The four-app architecture means a retailer can deploy Core + India first and add the GCC pack later without redeployment.
Full product page at /products/sourceforge-jewellery-management