Multi-brand hospitality operators in Bahrain live or die on how fast they can open the next concept. For this Novasoft customer — a Riffa-headquartered F&B group with five brands across international café, Arabic casual dining, Greek bakery, hospitality and juice-bar — the back office doesn't change when a new brand lands. One Business Central tenant, one LS Central price book, one POS template, one month-end close. New restaurant, familiar system. That is the whole case study.
Open a café chain and a shisha concept and an Arabic restaurant and a Greek bakery and a juice-bar franchise on separate POS stacks, and the back office stops being a back office. Month-end turns into Excel. VAT returns to the National Bureau for Revenue (NBR) get filed brand by brand instead of in one submission. Loyalty programmes that were supposed to pull a customer across concepts never talk to each other. Procurement loses leverage because every brand buys independently. And when a new outlet opens — which, for a group like this, is three or four times a year — the IT team either builds the new POS from scratch or waits for the brand's regional master franchisor to ship a template that may or may not fit NBR's receipt rules.
The Novasoft customer in this case study decided, three years ago, that this was the wrong architecture. The right architecture is one tenant and one chart of accounts for the group, with LS Central running the POS at every outlet regardless of brand, and the brand itself expressed as configuration — menus, prices, printers, modifiers, loyalty rules — on top of that single system. That decision is what makes this month's two new openings a one-day job for the small concept and a one-week job for the full restaurant, instead of a two-month project each.
|
5+
brands live on one BC + LS Central tenant
|
~1 day
to onboard a small-menu brand on the shared POS template
|
1
chart of accounts for the entire group — one month-end close
|
The group runs Microsoft Dynamics 365 Business Central (Essentials) as the group financial back-office — general ledger, accounts receivable and payable, procurement, inventory, fixed assets and NBR-compliant VAT. On top of that sits LS Central, which extends Business Central with the retail and hospitality capabilities: an item master structured for F&B (modifiers, deals, recipes), the POS engine, promotion rules, loyalty, kitchen printing and end-of-day cash procedures. The POS at every outlet — whichever brand — runs on LS Central Retail Device for Retail & Hospitality licences, with a Store licence per outlet, so onboarding a new restaurant is a Store subscription and a configuration pass, not a new environment.
The configuration that makes a POS "a café" versus "a Greek bakery" versus "an Arabic rice-and-grill restaurant" lives entirely in LS Central: button grids, menu layouts, modifier chains, printer routing, barista versus counter versus table-service flow, local-currency receipt format with the Arabic/English bilingual legal text NBR expects. One template with five expressions, not five templates.
Here is what changes for the group when a new concept is added — what the common "every brand its own POS" model costs, and what the shared BC + LS Central model gives back.
| Area | Five brands, five systems | BC + LS Central as a group platform |
|---|---|---|
| New brand launch | Six to eight weeks of system build per brand; franchise templates rarely fit NBR rules without rework. | One day for a small-menu concept, one week for a full restaurant — config, not build. |
| Month-end close | Five sets of extracts consolidated in Excel; brand P&Ls land late. | One ledger, brand/outlet dimensions; group and per-brand P&L straight out of BC. |
| NBR 10% VAT return | Brand-by-brand filings or awkward manual aggregation; receipt format varies. | Group filing at the correct BHD three-decimal rounding; uniform bilingual receipt from LS Central. |
| Procurement & inventory | Each brand buys separately; shared ingredients (dairy, oil, rice, poultry) sourced five times. | Group procurement in BC; shared vendors; one price list and inventory valuation. |
| POS deployment | Different POS vendor per brand; separate support contracts, separate hardware stacks. | One POS platform (LS Central Retail Device); one managed-support contract (NovaCare). |
| Loyalty across brands | Not practical — different POS systems don't share a customer record. | One customer card, group earn-and-burn across brands when the operator chooses to switch it on. |
The group's IT lead opens a new ticket with Novasoft when a new outlet or brand is signed. The sequence from that ticket to a live POS is the same every time — and that repeatability is the point.
A detail worth calling out: because every brand runs on the same LS Central platform under one Business Central tenant, the group can retire a brand or an outlet and redirect its licences to a new one without re-contracting. In the most recent round of openings, two existing POS Store licences — previously assigned to concepts that are being retired or restructured — were simply reassigned to a new international café branch and a new Arabic restaurant. The group paid for one additional Store licence instead of three.
That is impossible when each brand sits on its own POS platform. On a shared platform it is a Novasoft support ticket.
A platform case study is nothing without the local context. The group operates in Bahrain and three things about the Bahrain market shape how BC + LS Central are configured for them.
NBR 10% VAT with BHD three-decimal rounding. Bahrain's National Bureau for Revenue requires receipts in Arabic and English with specific legal content and taxes computed to three decimal places in Bahraini Dinar. LS Central's receipt template is configured once at group level and inherited by every brand's POS, which means a new restaurant goes live NBR-compliant on day one — not a week after launch when someone realises the receipt is wrong.
Bahrainization and Tamkeen. HR responsibilities for Bahrainization quotas and Tamkeen-supported employment live outside BC in the group's HR system; BC consumes the headcount data via a simple integration for payroll journal postings. The Novasoft team sized the ERP role deliberately to not overlap with HR, keeping the scope narrow.
Operating hours and shift patterns. Bahraini F&B often runs late — shisha concepts and family restaurants trade until 02:00 or later — and LS Central's day-close is configured to handle a trading day that spans the calendar midnight without splitting sales, which the group's finance team had asked for in the original design.
Delivery of a multi-brand F&B platform at this cadence depends on having a partner that lives inside both Business Central and LS Central every day — not one or the other — and that has done enough Bahrain NBR work to not learn it on the customer's receipt.
|
5x
LS Retail Diamond Partner, 2022–2026 — the only Gulf partner at that tier five years running
|
100+
live LS Central customers across MENA including grocery, hypermarket, fashion and F&B
|
8+
years delivering Microsoft Dynamics 365 Business Central across the GCC
|
Novasoft runs three live customer references in Bahrain today: a leading supermarket and hypermarket operator (announced go-live early 2026), a Bahrain airport-based food and beverage operator on Business Central, and the multi-brand F&B group described in this case study. Full customer names are held confidential at the clients' request.
Book a 30-minute assessment with a Novasoft consultant. We'll map your brand portfolio onto a single Business Central + LS Central platform and tell you honestly where it saves time and where it doesn't.
Book free assessment LS Central in BahrainOnce the shared POS template, item master and NBR-compliant receipt are in place, a small-menu concept (five to twenty SKUs, counter service) goes live in roughly one day of configuration plus a half-day of staff training. A full-service restaurant with modifiers, kitchen printing and table service takes about a week. The constraint is almost always the shop-fit and the chef team, not IT.
Yes, when the design uses brand and outlet dimensions on the chart of accounts, items and transactions. BC's dimension model is designed for exactly this — grouped reporting rolls up across brands, and per-brand P&L is a dimension filter. Separate legal entities (companies in BC) are used only when the Bahraini commercial registration (CR) genuinely requires it; most multi-brand groups in Bahrain run a single CR and therefore a single BC company with dimensions.
LS Central ships specifically with a Retail & Hospitality licence pattern — the Retail Device for Retail & Hospitality licences this group uses, Store subscriptions per outlet, and base full-user licences for consultants and managers. The hospitality capability covers modifiers, kitchen printing, deals and set menus, split checks, table service and shift handover. It is not a retrofit of retail POS; it is a first-class F&B surface inside the same product.
NovaCare is Novasoft's steady-state managed-support service for live LS Central and Business Central estates. For a multi-brand F&B group it covers ticket triage with documented SLAs, LS Central POS and kitchen-printing support across every outlet of every brand on the platform, Business Central back-office support for finance and procurement, change requests estimated and approved before build, hour pools reconciled monthly, and quarterly reviews with the IT lead. New outlet openings are run as project work on top of the NovaCare retainer, not inside it.
Yes. Novasoft has been an LS Retail Diamond Partner for 5 consecutive years (2022–2026) — the only Gulf partner at that tier — with 100+ live LS Central customers across MENA. Bahrain live customers include a leading supermarket and hypermarket operator, an airport-based F&B operator on Business Central, and the multi-brand F&B group described in this case study. Customer names are held confidential at the clients' request.