SourceForge Software Services has shipped the SourceForge Retail for Business Central add-on, joining the AI Assistant, OCR Payable Agent, Reconciliation Agent, Global Payroll & HR, Plant & Maintenance and AI Mobile WMS extensions. Seven production BC extensions now live.
Retail for BC is the Business Central system-of-record AL extension for the broader SourceForge Retail Solution. The full retail stack ships as five composable components: this BC extension; a shared React core for the offline cart, pricing, promotion and loyalty evaluation; an Electron desktop POS shell with Node hardware adapters; an Android / Capacitor shell with Sunmi and PAX terminal plugins; and a multi-tenant sync-and-entitlement SaaS middleware that sits between the client shells and BC. The BC extension is the authoritative back-end; the other four components are delivered as separate workstreams against the same data model.
The bet that distinguishes this product: in retail, tills lose connectivity, phones get reset, networks reboot. An unposted sale is unaccounted revenue — and worse, a re-tried post can become a duplicate sale that finance has to chase down. The whole architecture is built around making outage and retry safe by construction. Every sale carries a client-generated transactionId. BC's Posted Sale Map records that ID against the resulting posted document on first successful post. Every subsequent attempt with the same ID returns the original document — never creates a new one. Failed posts stay staged with the error surfaced for retry. No sale is lost; no sale is duplicated.
Five country packs activate per-tenant at launch: India (GST + e-invoice IRN integration), United Arab Emirates (ZATCA QR + UUID + cryptographic stamp), Saudi Arabia (ZATCA Phase 2 e-invoicing), United States (state + local tax via projection), European Union (per-country VAT + reverse charge). Each pack ships an offline tax projection that the client uses to compute tax at the till for instant customer feedback; BC re-computes tax authoritatively on posting and remains the source of truth.
Operational coverage is substantial: a native loyalty engine with accounts, tiers (auto-progression on lifetime spend), accrual rules per category/tender/promotion, and a ledger with FIFO point expiry; a promotions engine supporting BOGO, Buy-X-Get-Y, mix-and-match, tiered, markdown — with coupon support and configurable stacking; pluggable tender types with country/store enablement and adapter style; till sessions hosting multiple shifts per day with per-shift cash variance; end-of-day posting that settles every tender plus variance to BC; the standard Fiscal Artefact table that holds signed payloads (IRN, ZATCA, GST, VAT); store hierarchy with weekly opening hours and calendar exceptions; barcode (Item Reference) and variant support via standard BC objects; PA-DSS-friendly card handling — we store only Card Last 4 and PSP Reference, never the PAN.
The integration contract is published as a stable v2.0 API under apiPublisher=sourceforge / apiGroup=retail. Pull endpoints (master to client) cover stores, store hours and calendar exceptions, POS items, item barcodes, POS customers, price list lines, promotions, tender types, country packs, tax projections, loyalty accounts and stock levels — all with lastModifiedDateTime for delta sync. Push endpoints (client to BC) cover POS sales with nested lines and payments, till sessions with cash movements and tender counts and shifts, fiscal artefacts, and device registration/heartbeat. Bound actions handle posting (postSale, postEndOfDay) and entitlement refresh (heartbeat). OAuth service-to-service authentication; the service account uses the SFR Retail – Sync permission set plus standard D365 sales and finance posting permissions.
Object range 52500-52799 with the SFR prefix on every object. Target is BC SaaS, minimum BC 25 (runtime 14.0). Distributed as a Per-Tenant Extension installed privately in your BC tenant. AppSource publication is on the roadmap for a later release.
Implementation typically runs 6-10 weeks for a single-store SMB deployment and 10-16 weeks for multi-store or multi-country rollouts. The BC extension itself installs in under an hour; the time is in business configuration (country pack activation, tender setup, store and lane and device master, promotions and loyalty rules), operator training, parallel running and cutover.
Full product page at /products/sourceforge-retail