LS Central Implementation: What It Actually Looks Like (2026 Guide)

You’re running five stores, maybe fifteen. Your POS is a patchwork — two stores on the system you bought in 2018, one on whatever the franchise agreement required, and the newest location running something the IT guy set up because “it was cheap and it works.” Reconciliation takes three days every month-end. Inventory numbers in the system and on the shelf don’t match. You’re losing money and you can’t prove where.

This is when retailers look at LS Central — Microsoft’s unified commerce platform built on Dynamics 365 Business Central. And this is when they discover that an LS Central implementation is not a software install. It’s a retail transformation project with hardware, store-level replication, cashier training, and a multi-store rollout strategy. Most mid-size retailers spend €40K–€80K with 4–7 months to go-live. This guide covers the real numbers, the real timeline, and the things nobody puts in the proposal.

---

What Makes LS Central Implementation Different From a Standard BC Deployment

A standard Business Central implementation focuses on the back office: finance, purchasing, maybe some warehouse. Users sit at desks. The internet is reliable.

An LS Central implementation is different in five critical ways.

POS hardware. Every till becomes a BC client. You’re deploying barcode scanners, receipt printers, cash drawers, customer-facing displays, and payment terminals — across every checkout lane in every store. This hardware breaks in ways servers don’t: receipt paper jams, scanner cables get kicked loose. Your plan has to account for physical devices, not just software.

Store-level replication. LS Central uses SQL Server replication to maintain a local store database that runs independently when the internet drops. A sale completes on the store server even with no WAN link, then syncs when connectivity returns. This is LS Central’s killer feature — and the part that needs the most rigorous testing. You don’t discover replication lag at 2PM on a Saturday.

Integration with retail peripherals. Scales, EFT terminals, loyalty engines, age-verification prompts — these aren’t optional, they’re core to checkout flow. A standard BC implementation has 2–3 integrations; an LS Central implementation has 6–8, and several are hardware-dependent.

Staff training shifts from desktop to counter. You’re not training accountants who understand business software. You’re training cashiers, some of whom have never used anything more complex than a basic POS. Training happens at the till with hands-on practice processing real-looking transactions.

Multi-store rollout with a template. You implement one pilot store, stabilize everything, then clone it. This pilot-and-template approach is the difference between a controlled rollout and fifteen simultaneous fires.

---

Honest Pricing: What LS Central Implementation Really Costs

LS Central implementation costs vary more than standard BC because the hardware dimension, store count, and integration complexity multiply. Here’s what we see across projects.

Component	Small Retail (1–3 stores)	Mid-Size (4–15 stores)	Large (15+ stores)
LS Central licenses	€75–95/user/month	€85–110/user/month	Volume negotiated
BC Essentials/Premium	€70/user/month	€70/user/month	€70/user/month
POS hardware per lane	€2K–€4K	€2K–€5K	€2K–€6K
Partner implementation	€15K–€30K	€40K–€80K	€80K–€150K+
Data migration	€3K–€8K	€8K–€15K	€15K–€30K
Training	€3K–€5K	€5K–€10K	€10K–€20K
Annual support & maintenance	€8K–€15K	€15K–€25K	€25K–€50K

Why the range is this wide. A 2-store boutique with standard POS hardware, clean data in a modern system, and no custom integrations will land at the bottom of every range — roughly €25K–€35K in partner fees, 3–4 months, straightforward. A 12-store grocery chain with deli scales, age-restricted products, a legacy POS from 2012 with eight years of messy transaction data, a loyalty program with 80,000 member records, and EFT terminals from two different payment processors will land at the top — closer to €100K+ in partner fees, 10–14 months, complex.

What drives cost up: store count (each store adds hardware, training, and rollout coordination), legacy data complexity (dirty records, incomplete inventory, unreconciled gift card balances), hardware replacement needs, integration count (loyalty, e-commerce, EDI, payment gateways), and customization depth (LS Central-specific AL development costs 30–50% more than standard BC because the developer pool is smaller).

What gives you negotiating leverage: multi-year support commitments, bundled hardware procurement through the partner, and volume license pricing directly with LS Retail.

Licensing note. LS Central licenses are additive to BC licenses. Every POS user needs both: BC Essentials (€70/user/month) plus an LS Central license (€75–110/user/month). Back-office staff who never touch the POS only need BC licensing. A store with 6 lanes and 2 back-office staff needs 6 BC + LS Central licenses and 2 BC-only licenses. This stack catches people off guard — factor it in from day one.

---

Timeline: How Long Does an LS Central Implementation Take?

The timeline is driven by the pilot-and-template approach. You prove everything on one store, then clone it. Here’s the phase-by-phase breakdown for a mid-size retailer (4–8 stores).

Phase 1: Discovery & Scoping (2–4 weeks)

We document your store layouts, hardware inventory, POS workflows, integration points, loyalty rules, and reporting requirements. The output is a detailed scope document that becomes the basis for the fixed-price proposal.

Phase 2: Solution Design (3–5 weeks)

We map your retail processes to LS Central: store hierarchy, POS menu layouts (button grids cashiers actually find usable), pricing and discount rules, payment mappings, receipt formats, loyalty integration, and replication topology. If you’re implementing full BC back-office — which most retailers do — we also design the chart of accounts, dimensions, and posting groups.

Phase 3: Pilot Store Setup (4–6 weeks)

POS hardware installation, LS Central configuration, back-office BC setup, integration build-out, and the first test migration. We validate that a sale at the POS updates inventory, financials, and loyalty points correctly.

Phase 4: Hardware Procurement & Setup (2–4 weeks, overlaps with Phase 2–3)

POS terminals, scanners, printers, cash drawers, and payment terminals are ordered, delivered, and tested. For rollout stores, hardware runs on a staggered schedule — order wave 2 while wave 1 trains. Don’t order all hardware upfront; refine the spec after the pilot validates it.

Phase 5: Data Migration & Integration (3–6 weeks)

Full migration: item master, customers (with loyalty balances), suppliers, open orders, gift cards, and opening stock with costs. Integration testing: payment terminals, loyalty, e-commerce order flow. The full migration runs at least twice — dress rehearsal, then go-live.

Phase 6: Staff Training (2–4 weeks per store)

Cashiers: 2–3 days hands-on till training. Store managers: full day on reporting and day-end. Back-office: role-based BC training. Pilot store training is partner-led; rollout stores use a train-the-trainer model.

Phase 7: Pilot Go-Live (week 16–20)

Partner staff on-site for the full first week. This is when edge cases surface: the return policy exception, the gift card balance mismatch, the payment terminal that worked in testing but won’t connect at 11:05 AM. Hypercare runs 2 weeks, then stabilization.

Phase 8: Rollout to Remaining Stores (4–8 weeks)

Waves of 2–4 stores each: hardware, configuration (cloned from pilot template), train-the-trainer, data migration, and go-live with 2–3 days of on-site support per store.

Total: 4–8 months for a 1–3 store retailer, 8–14 months for a 10+ store chain. The pilot store always takes the longest — typically 16–20 weeks. Each subsequent store adds 1–3 weeks depending on complexity.

---

Team & Roles: Who Needs to Be at the Table

An LS Central implementation spans retail operations, IT, finance, and the people who actually run the tills. If any of these groups aren’t represented during design, you’ll discover the gap during go-live — when it’s expensive to fix.

From Your Side

Role	Who	Time Commitment	Why They Matter
Project Sponsor	CEO, MD, or Retail Director	2–3 hours/month	Removes roadblocks. Approves scope changes. The person who tells the organization this project is non-negotiable.
Retail Operations Lead	Head of Retail, Store Operations Manager	10–15 hours/week during discovery/design, 6–10 hours/week during pilot testing	Owns the POS workflows, store procedures, and cashier experience. This is the most critical role on your side — if the ops lead is disengaged, the POS will reflect what the partner thinks stores need, not what they actually need.
IT Manager	Internal IT lead or external IT partner	6–10 hours/week during hardware/integration phases, 2–4 hours/week otherwise	Owns network, hardware, replication, and integration infrastructure. If your IT is outsourced, include their hours in the project budget.
Store Manager (Pilot)	Manager of the pilot store	4–6 hours/week during design, 15–20 hours/week during training and go-live	On-the-ground reality check. “That button placement looks good on paper but our cashiers will hit the wrong one 40 times a day.”
Key Cashiers (1–2)	Experienced cashiers from the pilot store	2–3 hours/week during design for feedback, 2–3 full days during training	These are the people who will catch UX problems nobody else notices. They’re also your change ambassadors for the rollout stores.
Finance Lead	CFO or Financial Controller	4–6 hours/week during design, 2–4 hours/week during UAT	If you’re implementing full BC back-office (which most retailers do), the finance lead owns CoA design, dimensions, posting groups, and financial reporting validation.

From the Partner Side

Role	What They Do
Project Manager	Timeline, budget, RAID log, status reporting. Your single point of contact.
BC/LS Central Functional Consultant	Configures BC back-office and LS Central POS. Designs store setup, POS layouts, pricing rules, and retail workflows.
Technical Consultant	SQL Server replication setup, performance tuning, infrastructure design, store server deployment.
Integration Specialist	Payment terminal integration, loyalty program connection, e-commerce sync, EDI if applicable.

Realistic time commitment for your team: During discovery and solution design, expect 8–15 hours/week from your retail operations lead and IT manager combined. During pilot testing and training, that peaks at 15–25 hours/week across the team. The project sponsor should be available for decisions within 24 hours — projects stall when the person who can say “yes” to a €3,000 change order takes two weeks to reply.

---

Hardware Considerations

LS Central’s POS client runs on Windows. OPOS compatibility is your gate — but it’s a spectrum, not a binary.

Must-Have Hardware

• POS terminals: All-in-one touchscreen units (HP, Toshiba, NCR) — €1,500–2,500 each. Avoid consumer-grade hardware; these run 12–16 hours/day, 360 days/year.
• Barcode scanners: Handheld USB (Zebra, Honeywell) — €150–400. Presentation scanners (hands-free) — €300–600.
• Receipt printers: Thermal, OPOS-compatible (Epson, Star) — €200–400. Verify receipt width (58mm or 80mm) and logo/barcode support.
• Cash drawers: Electronically triggered — €80–150. Confirm RJ12 trigger interface compatibility.
• Payment terminals: Provider-supplied, but must integrate via OPOS or middleware. Payment terminal integration is the #1 source of go-live-day issues — test with real transactions before signing.

Nice-to-Have

• Customer-facing displays: €200–500 per lane — reduces disputes as customers catch pricing issues before payment.
• Self-checkout kiosks: €8K–15K per kiosk — ROI only works at 8+ lanes with high volume.
• Handheld scanners for inventory: Zebra/Honeywell mobile computers — €800–1,500 each.

What Can You Reuse?

USB barcode scanners under 5 years old, OPOS-compatible receipt printers under 7 years, and payment terminals from major processors (Adyen, Worldpay, Ingenico) usually work. What needs replacing: POS terminals older than 5 years, proprietary hardware (IBM 4690, NCR Advanced Store), and cash drawers with proprietary trigger interfaces.

Cloud vs On-Premise POS Server

Cloud (Azure) eliminates store-level server hardware but requires reliable internet. On-premise needs a server per store (€1,500–3,000) plus backup. If your stores have connectivity issues, on-premise is safer.

Critical advice: Test your hardware before signing the partner contract. Spend €500–1,000 on a compatibility lab: one of each device, a test environment, 50 transactions. Find hardware issues during vendor selection, not go-live week.

---

Data Migration: What Moves From Your Old POS

Your old POS has years of history — not all of it needs to move, and some of it can’t.

What Migrates

• Item master: SKUs, descriptions, barcodes, variants, categories, suppliers, costs, prices. If items don’t migrate cleanly, nothing works.
• Stock levels: On-hand quantities by store and bin. Requires a physical stock count — the system migrates what you count, not what the old system thinks you have.
• Customer records: Names, contacts, loyalty IDs, point balances, store credit. Deduplicate before migration.
• Open transactions: Unpaid orders, layaways, open purchase orders, unprocessed returns.
• Gift cards: Serial numbers, issue dates, remaining balances. Audit gift card liabilities before migration — this is a magnet for data quality problems.

What Typically Doesn’t Migrate Cleanly

• Historical sales older than 2 years. Keep the old database as read-only archive for compliance.
• Promotion and discount rules. Recreate these in LS Central — it’s a design activity, not a migration.
• User permissions. Set them up fresh; old-to-new role mapping creates permission gaps.

The Non-Negotiable Rule

Trial migration twice minimum. First validates extraction scripts and data mapping. Second is a full dress rehearsal on the go-live timeline. Between migrations, fix what broke. Also: trial post a full business day’s transactions in the test environment before go-live.

---

Staff Training: The Retail Reality

Training is the line item every retailer cuts first and regrets most.

Cashiers need 2–3 days of hands-on training before go-live. Not a presentation in the break room — two full days at the till with a partner trainer. Day 1: basic transactions (sale, return, exchange, void). Day 2: edge cases (split payment, gift card, loyalty redemption, age verification, manager override).

Create a “cheat sheet” taped next to each POS. One page, laminated: how to log in, standard sale, return, discount, gift card, help desk number. Cashiers use it for 2 weeks until muscle memory kicks in. Don’t make them search a PDF.

First week post go-live: partner staff on-site in every store. Someone standing in the store who fixes problems in 30 seconds instead of 30 minutes on support. This is expensive (€800–1,200/day) and it’s the best money you’ll spend.

Common gotchas to drill: returns/exchanges (receipt, no receipt, gift receipt, cross-store), gift cards (issue, redeem, partial, multiple on one transaction), split payments (cash + card, two cards, card + gift card), and age-restricted items (the prompt is a legal requirement, not a convenience).

---

What Nobody Tells You About LS Central Implementations

1. Your Internet Will Fail During Peak Hours

Saturday at 1:30 PM, store packed, internet routing issue. If SQL Server replication is configured correctly, the store keeps running — transactions complete locally, sync back when the connection returns. If replication wasn’t tested, the store goes dark.

Test it: pull the network cable during a simulated busy period. Process 50 offline transactions. Reconnect and verify every one synced. Do it again with the payment processor’s test environment. This single test catches more problems than a week of conference-room demos.

2. The Pilot Store Will Run Perfectly Until 11:05 on Go-Live Morning

Every LS Central implementation follows this pattern. First hour: flawless. Team celebrating. 11:05: someone processes the one edge case nobody tested — a cross-store return of a pre-migration purchase, a gift card with a balance mismatch, loyalty points with a rounding error.

This isn’t failure. This is go-live. Budget partner on-site time for the full first week. Edge cases surface over days of real transactions, not a 2-hour test window.

3. Cashiers Will Hate the New System for 3 Weeks, Then Love It Forever

Week 1: transactions take twice as long. Week 2: faster but high error rates as muscle memory develops for wrong button sequences. Week 3: speed and accuracy converge. Week 4: cashiers discover features they didn’t have before — customer lookup, real-time inventory, loyalty balances at a glance.

Don’t overreact to week-1 complaints by changing the POS layout. Do keep a notebook next to each till for cashier feedback, reviewed weekly.

4. Your Old POS Data Will Not Be Perfect

Accept this: 5–10% of legacy data needs manual cleanup — customer typos, wrong units of measure, unreconciled gift cards, purchase orders received but never closed from 2019. This isn’t migration failure; it’s the reality of years of accumulated data nobody maintained. Budget 2–5 days of your team’s time or €2,000–5,000 in partner time.

5. LS Central Development Costs More Than Standard BC Development

The LS Central developer pool is smaller. A standard BC/AL developer charges €80–120/hour. An LS Central developer who understands POS, loyalty, promotions, and replication charges €100–150/hour — a 30–50% premium. Be selective about customizations. The LS Central standard feature set covers most retail scenarios.

---

Printable Go-Live Checklist

Before go-live day, every item on this checklist should be checked. Print it. Tape it to the project room wall.

Hardware

• All POS terminals delivered, installed, and tested at every store
• Receipt printers configured and printing test receipts with correct formatting
• Payment terminals processing test transactions (approve, decline, refund)
• Barcode scanners reading every barcode symbology you use (EAN-13, UPC-A, Code 128)
• Cash drawers triggering correctly from POS and from receipt printer

Software

• Pilot store data migration validated — all items, prices, customers, stock levels verified
• Replication tested — pull the network cable, process 50 transactions offline, reconnect, verify sync
• All financial reports signed off by finance lead (trial balance, P&L, inventory valuation)
• POS menu layouts approved by retail operations lead and pilot store manager

People

• All cashiers completed minimum 2-day hands-on training
• Store managers know the escalation path: who to call for what problem
• Partner support staff confirmed on-site for full first week at every live store
• Key cashier “champions” assigned as peer support for each store

Data

• Trial posting completed for a full business day’s transactions
• Opening stock counts verified — physical count matches system quantities
• Customer records and loyalty balances migrated and validated (spot-check 50 records)
• Gift card balances reconciled between old system and LS Central

---

FAQ

How long does an LS Central implementation take?

Plan 4–8 months for a small chain (1–3 stores) and 8–14 months for a larger chain (10+ stores). The pilot store takes 16–20 weeks; each additional store adds 1–3 weeks. Variables that extend the timeline: messy legacy data, custom integration requirements, and slow decision-making on your side. The fastest implementation we’ve seen — a 2-store boutique with clean data and no integration complexity — went live in 14 weeks.

What does LS Central implementation cost for a single store?

For a single store with 2–3 POS lanes: €15K–€25K in partner implementation fees, €4K–€8K in POS hardware, €3K–€5K in training, and €3K–€5K in data migration. Add licensing: approximately €145–165/user/month (BC Essentials + LS Central license). A single-store implementation is sometimes more efficient than multi-store because you skip the replication complexity and rollout coordination — but you also don’t get the economies of scale that a template-based multi-store rollout provides. Total first-year cost for a single store typically lands between €30K–€50K all-in.

Can we keep our existing POS hardware?

Yes, if it’s OPOS-compatible and less than 5–7 years old. USB barcode scanners from major brands (Zebra, Honeywell) almost always work. Thermal receipt printers from Epson or Star Micronics work if they’re OPOS-compatible. Payment terminals from major processors typically work through middleware. What usually needs replacing: proprietary POS terminals (IBM 4690, NCR Advanced Store) that were purpose-built for legacy software, and any hardware older than 7 years. Spend €500 on a hardware compatibility test before committing — buy or borrow one of each device type, connect it to a test LS Central environment, and verify it works end-to-end.

What happens if the internet goes down at the store?

This is what LS Central was designed for. Each store has a local SQL Server database that replicates with head office. When the internet drops, the store server continues processing transactions locally — sales, returns, payments, loyalty points, everything. When the connection returns, the store synchronizes with head office. POS terminals in the same store continue talking to the local store server over the LAN. The database can run independently for hours or days. The one thing that stops working: real-time inventory visibility across stores. You can’t check stock at another location until the connection is back. This is LS Central’s single biggest advantage over cloud-only POS systems — and the reason serious retailers choose it.

Is LS Central worth it versus staying with our current POS?

If your current POS covers your needs and reconciliation doesn’t eat 3+ days every month-end, probably not. LS Central’s value proposition is unification — one system for POS, inventory, purchasing, financials, and customer data. If you’re not feeling the pain of disconnected systems, the investment is hard to justify.

But if you’re experiencing any of these: month-end reconciliation that takes days instead of hours, stock discrepancies you can’t trace, loyalty program data that lives in a separate system, prices that are different online versus in-store because someone forgot to update them, or inventory that shows in-stock online but isn’t actually on the shelf — LS Central solves these at the architectural level because there’s only one database, one price engine, and one source of truth. For retailers with 3+ stores and growth plans, the operational savings from unification typically cover the implementation cost within 18–24 months.

---

Need a detailed LS Central implementation estimate for your specific stores? See our LS Retail services for a breakdown of what we cover — or take our ERP Readiness Scorecard to see if your retail operation is ready for the move to LS Central. If you’re still evaluating whether LS Central is the right fit, read our comparison guide: LS Central vs standalone POS.