Gold, diamond and composite jewellery — inside Business Central.
A four-app suite for BC. Core platform handles composite pieces, daily rates, valuation, old-gold buyback, karigar and jangad workflows. A built-in Level 2 POS layers on top. India and GCC packs inject the jurisdiction rules — BIS hallmarking, GST, ZATCA Phase 2, Arabic bilingual layouts. Event-subscriber based, never modifies base BC.
- 4 apps: Core + Billing POS + India Pack + GCC Pack
- Composite piece + stone engine · daily multi-rate board
- Old-gold buyback · karigar · jangad · schemes · loyalty
- India: BIS HUID · GST · IRN · PAN / 269ST / TCS
- GCC: ZATCA Phase 2 · UAE FTA · Arabic bilingual
- Cloud-only · BC 27 · AppSource-pathed
Built for the jewellery retailers your finance team already serves
Jewellery is a different ERP problem. Most BC vertical add-ons get this wrong.
A jewellery piece is a composite — gold of varying purities, multiple stones, making charges, wastage. Today's price depends on a daily rate board you don't control. A sale frequently includes an old-gold buyback as a credit on the same invoice. Compliance varies sharply by jurisdiction — BIS HUID in India, ZATCA Phase 2 in Saudi, FTA reverse-charge in UAE. Most BC vertical add-ons either flatten the composite into a single SKU and lose the audit trail, or maintain a parallel posting path that finance teams hate. SFJM does neither. Core explodes the composite into correctly-grouped standard BC document lines; the customer's existing tax stack reads them as normal invoices. The jurisdiction rules live in regional packs that activate per company.
Core platform + Billing POS + India Pack + GCC Pack. Pick the packs that match the countries you operate in.
Gold by purity, stones by attribute, making charges, wastage — each modelled independently and valued at the rate effective at posting.
Strictly event-subscriber based. Co-exists with other AppSource extensions; survives BC monthly updates; never blocks roll-forward.
Core platform plus three composable apps.
Each app has its own object-ID block and ships independently. Core is the platform; packs inject jurisdiction rules through Core hooks — never the other way around.
SFJM Core
Composite piece + stone management, daily multi-rate board, valuation engine, old-gold buyback, karigar job work, jangad, loyalty, discounts, promotions, commission, gold-savings schemes, owner dashboard, e-commerce readiness.
SFJM Billing POS
Control add-in bundled inside the extension. Scan-to-line, inline old-gold exchange, multi-tender settlement, park-and-recall. Posts standard BC Sales Invoices through Core — never a parallel posting path.
SFJM India Pack
BIS hallmarking + HUID register, GST split taxation, e-invoice IRN/QR via E-Document framework, PAN / Section 269ST / TCS, gold-savings scheme regulatory guardrails. Inject through Core hooks; activate per company.
SFJM GCC Pack
Saudi ZATCA Phase 2, UAE FTA + reverse-charge on B2B gold/diamond, per-component investment-gold zero-rating, Dubai retail conventions (22K default, per-gram making), Arabic bilingual invoices with RTL.
Eight engines that make jewellery retail work inside BC.
All in Core — every retailer gets them. Country packs add the jurisdictional layer on top.
Composite piece & stone
Model gold of multiple purities, multiple stones with their own attributes, making charges and wastage — independently per component. The valuation engine walks the component list at the rate effective at the moment of valuation.
Daily multi-rate board
Per company per day per purity, with effective times. Manual entry, CSV ingest from your bullion supplier, or pluggable API source. Stale rates flagged; missing rates fail safely with a clear error.
Old-gold buyback
Assay (weight + purity) at counter; engine calculates buyback at today's rate; applied as a credit line to the same invoice. Old gold enters separate refining workflow. Finance sees one document.
Karigar & jangad
Karigar (artisan) job-work with issue / return reconciliation, wastage allowance, making-charge billing. Jangad (consignment) per-piece tracking with sale-or-return reconciliation. Standard BC item-tracking compatible.
Loyalty · discounts · promotions
Native customer loyalty (accounts, tiers, ledger), per-line and per-document discounts with manager-approval thresholds, time-bound promotions, festival-driven offers — all in Core, all visible at the till.
Gold-savings schemes
Customer pays instalments toward a future jewellery purchase. Core tracks subscriptions, ledger, maturity rules, redemption against piece purchase. India Pack adds the RBI / consumer-protection regulatory guardrails.
Commission
Sales-staff commission rules per piece category, per material, per discount level; auto-computed at posting; reconciled per-employee per-period for payroll handover.
E-commerce readiness
Catalogue surface with structured attributes (piece type, purity, weight, stone count, image URLs) ready for a connector. Inventory + price feed APIs exposed; reservation flow on order capture.
Level 2 touch POS, inside the extension.
SFJM Billing POS is a control add-in shipped inside the SFJM extension. It is deliberately a skin over standard BC posting, not a parallel system. Every transaction posts a standard BC Sales Invoice via the Core valuation and line-explosion engine.
- Scan-to-line with auto-loaded piece attributes (gold purity, weight, stones, making) from Core master.
- Inline old-gold exchange — capture weight + purity, engine values at today's rate, applied as credit line to the same invoice.
- Multi-tender settlement (cash, card, UPI, gold-savings-scheme redemption, store credit) on a single invoice.
- Park-and-recall for in-progress transactions when a counter staff steps away.
- No separate POS tenant or sync middleware — retailers reconcile in BC the moment payment hits.
Necklace 22K, 38.420 g, 2 stones ───────────────────────────────── Gold value (22K @ rate) ₹2,30,520 Stone value (rubies x2) ₹18,400 Making charges (15%) ₹34,578 Wastage allowance (1.5%) ₹3,458 ───────────────────────────────── Sub-total ₹2,86,956 Old-gold buyback (−12.30 g 24K) −₹85,624 GST split (CGST + SGST) ₹4,539 ───────────────────────────────── Invoice total ₹2,05,871 Posted as standard BC Sales Invoice, lines correctly grouped for tax / IRN / ZATCA.
Two packs at launch — India and GCC. More on the roadmap.
Packs activate per company; the same BC tenant can run different packs across companies. Each pack injects rules through Core hooks — never the other way around.
India Pack
Object range 80600–80699
- BIS hallmarking capture + HUID register (6-digit unique IDs per piece)
- GST split taxation across exploded value buckets (gold value vs making vs stone)
- E-invoice IRN + QR via BC's E-Document framework
- PAN capture + Section 269ST cash-limit enforcement + TCS on threshold sales
- Gold-savings scheme regulatory guardrails (RBI / consumer-protection)
GCC Pack
Object range 80700–80799
- Saudi Arabia ZATCA Phase 2 e-invoicing (XML + signed QR)
- UAE FTA readiness + reverse-charge on B2B gold/diamond trade
- Per-component investment-gold zero-rating vs standard-rated jewellery
- Dubai retail conventions (daily Dubai rate board, 22K default, per-gram making norms)
- Arabic bilingual invoice layouts with full right-to-left rendering
The architectural decisions that keep SFJM clean for the long run.
Every one of these decisions is enforced — by AppSourceCop, by our own ruleset, or by the SFJM guard workflow in CI.
Event-subscriber architecture
SFJM never modifies BC base codeunits, pages or tables. Co-exists with other AppSource extensions; survives BC monthly updates without breakage. Customers can always roll forward.
Compliance-agnostic Core
Core explodes transactions into correctly-grouped standard BC document lines. The customer's existing tax / e-invoicing stack reads them as normal invoices — Core never owns a parallel tax engine.
Gating order
SourceForge entitlement → customer enable/disable in Setup → per-module configuration. Three layers; each gate fails closed. Disabled modules hide their UI entirely.
AI is opt-in with non-AI fallback
Every Claude feature has a complete non-AI alternative. No API key, the feature quietly disables. Anthropic key in BC Isolated Storage. Zero AI dependency for the core retail workflow.
AppSourceCop enforced
Mandatory `SFJM` affix on every object. Permission sets required for every table. Validated in CI on every PR via the SFJM guard workflow.
Cloud-only by design
BC SaaS target only. No on-premises codepath, no .NET interop, no external HTTP except the optional Claude calls. Air-gappable for customers who never enable AI.
4-8 weeks single store. 8-16 weeks multi-store.
Implementation scales with the packs you activate. A single retailer in India with Core + India Pack is the fast-path; a mixed retail + wholesale chain across India + UAE + Saudi takes longer because the master data and operator training scale with the number of jurisdictions in flight.
Per-Tenant Extension installed in your BC tenant. AppSource roadmap-ready.
1
Existing catalogue review (piece types, purity mix, stone library). Rate source decision. Karigar / jangad processes mapped. India / GCC pack scope confirmed per company.
2
Publish Core to BC sandbox. Activate per-company modules. Install India and/or GCC pack as required. Seed rate sources, scheme templates, commission rules.
3
Migrate piece catalogue, stone library, customer list, karigar list. Configure GST groups (India) or ZATCA tax codes (GCC). Map G/L accounts for sales / buyback / making-charge / commission.
4
Train counter staff on POS (scan-to-line, old-gold exchange, multi-tender). Train back office on karigar / jangad reconciliation. Train finance on the exploded line structure.
5
Run one week against your existing system in parallel; reconcile invoice-by-invoice. Cut over. Daily check-ins through first month-end including IRN / ZATCA submissions.
Frequently asked questions
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. AppSource publication on the roadmap.
Bring a sample invoice. We will value it through the engine live.
A 60-minute working session, not a sales pitch. Bring a real jewellery invoice (or a piece description) and your daily rate. We sign you in to a BC sandbox, install Core + the right country pack, build the composite piece, run the valuation, post the invoice, and walk through the exploded line structure with you.
- Live install + country-pack activation in your BC sandbox
- Real-piece valuation through the Core engine
- Honest answer on whether you need Core + POS or Core only
- Written proposal within 48 hours