Every Business Central partner pitch sounds broadly the same at the proposal stage. They all promise a smooth implementation, a single source of truth, and a team that understands retail. The differences only show up eighteen months in, when you are trying to add a fourth warehouse to a stock model that was only ever tested on one, or when a partner who built your original system has moved on to other clients and nobody left on their side remembers why a particular integration was configured the way it was.
For an IT Director running multi-site retail, the stakes of getting this wrong are specific and expensive. A partner who does not understand consolidated reporting across locations will build you a system that works for one site and needs rework for every site after it. A partner without a proper data migration methodology will hand you a go-live date that slips by months while stock records and pricing structures get reconciled manually. A partner with no real support model will leave you fielding out-of-hours incidents yourself because their SLA only covers office hours, and your stores do not close at 5pm.
This checklist sets out the questions worth asking before you sign, the evidence worth demanding instead of taking on trust, and the parts of a typical sales pitch that are worth ignoring entirely.
Most Business Central partners can demonstrate a clean implementation for a single site. Fewer can show you what happens when that same configuration needs to run consistently across ten sites, each with its own stock levels, pricing rules, and local promotions, while still rolling up into one consolidated view for head office.
Ask specifically how they structure location and stock transfers, how pricing exceptions are managed without creating a separate configuration per site, and how reporting is consolidated. If the answer is vague, or if they describe a workaround involving spreadsheets or manual exports, that is a strong signal the partner's experience is thinner on multi-site retail than the pitch suggests.
Every partner will tell you data migration is a solved problem. Ask them to walk you through an actual migration they have run: how they handled duplicate SKUs across legacy systems, how they validated stock quantities before cutover, and what their fallback plan was if reconciliation turned up discrepancies on go-live weekend.
A partner with a genuine methodology will have a documented, repeatable process for this. A partner without one will describe migration in generalities and expect you to discover the gaps once your historical data is already halfway into their system. Data migration is one of the areas where the difference between a proven migration methodology and an improvised one only becomes visible after the damage is done.
The sales conversation is about implementation. The relationship you are actually buying is about what happens for the years after implementation, when processes change, sites are added, and something inevitably breaks during trading hours.
Ask what their support model looks like in practice, not on paper. Does it cover retail trading hours, including evenings and weekends, or does it stop at a standard office day? Is there a named point of contact who knows your setup, or does every ticket start from zero with whoever picks it up? A retail business does not get to choose when a POS terminal fails, and a partner whose managed services model is built around office hours is not built for multi-site retail.
"We understand retail" is not evidence. Ask for specifics: how many multi-site retail clients has this partner delivered, what was the largest site count they have managed, and can they put you in touch with a reference client who will talk candidly about what went well and what did not.
A partner confident in their track record will offer this without hesitation. One that hedges, offers only marketing case studies with no named contact, or steers you toward single-site examples when you asked about multi-site scale, is telling you something about the limits of their real experience.
Growth should not mean starting the configuration conversation from scratch every time you open a new location. Ask how new sites are brought onto the system: is there a preconfigured, repeatable deployment process, or does every rollout involve a fresh scoping exercise and a fresh invoice?
A partner who has genuinely built for multi-site retail should be able to describe a standard playbook for adding a site: what is preconfigured, what needs local setup, and how long it typically takes from decision to go-live. If they cannot answer this without reaching for a calendar and a blank page, the system they built you was never designed to scale in the first place.
Implementation projects often involve a strong team on the partner's side: an experienced project manager, a senior consultant, people who clearly know what they are doing. The question worth asking is what happens to that relationship once the project ends. Do the same people stay involved, or does support get handed to a different team who is meeting your business for the first time through a support ticket?
For IT teams already stretched thin, a partner who treats post-go-live support as a lesser, outsourced function is asking you to re-explain your business every time something needs fixing. That undermines the "one connected ecosystem" a good Business Central and IT and infrastructure setup is supposed to deliver in the first place.
A fixed-fee proposal for the initial implementation is easy to compare across partners. What is harder to compare, and more important, is how pricing works once you are live: what does adding a site cost, what counts as a chargeable change versus standard support, and are licence fees passed through at cost or marked up.
Ask for this in writing before you sign, not after the first invoice for site two arrives. A partner who is transparent about ongoing costs from the outset is a partner who expects the relationship to hold up under scrutiny later.
BC4 has implemented and supported Microsoft Dynamics 365 Business Central and LS Central across networks from a single site to over 150 trading locations, processing more than 270,000 transactions a day with zero downtime. If you are evaluating partners for a multi-site retail project, get in touch and we will walk you through exactly how we approach it.
Ask how they handle stock and reporting consolidation across multiple sites, what their data migration methodology looks like in practice, what support coverage applies after go-live, and whether they can provide reference clients running a similar number of sites to yours. Vague answers to any of these are worth treating as a warning sign.
Ask for the largest site count they have delivered, request a reference client who will speak candidly, and ask them to describe their playbook for onboarding a new site. Genuine multi-site experience shows up as specific, repeatable process. Marketing language without detail usually means the experience is thinner than the pitch suggests.
The most common and costly risk is a system that was only ever designed and tested for a single site, which then requires expensive rework every time a new location is added. A close second is a support model that does not cover retail trading hours, leaving IT teams to handle out-of-hours incidents themselves.
Yes, when it is implemented and configured correctly for consolidated reporting, multi-location stock visibility, and location-level pricing. The technology itself is proven. The variable is whether the implementing partner has genuinely built for multi-site complexity or is adapting a single-site approach.
Yes. Ask specifically what it costs to add a new site once you are live, how licence fees are passed through, and what counts as standard support versus a chargeable change. A partner who sets this out clearly before you sign is far less likely to surprise you with it later.
This depends heavily on scope, but a partner with a genuine repeatable playbook should be able to give you a clear, specific timeline for onboarding each additional site after the first is live, rather than treating every new location as a fresh project from scratch.