Microsoft Business Central Developer

The Role

We're a small team running our entire operation on Microsoft Business Central (Essentials plan today, moving to Essentials with Tier 4 Advanced Warehousing in the near term). We're standing up a real fulfillment center and connecting Business Central to a Warehouse Management System extension to run it. We need a BC developer who can both write the AL code and deeply understand what they're doing — someone who can sit across from a physical warehouse problem and make the right call on how BC should model and process it.

This person becomes our owner of everything Business Central. In the beginning we'll hand-hold on business context (because that's the only way they can be effective). Over time, they grow into the advisor role for this entire area and become the point person on calls with our external BC consultants who are helping us plan and implement the warehouse buildout.

Must-Haves

• Modern Business Central AL development in VS Code. Custom extensions, table/page extensions, custom API pages, codeunits, XMLports, custom permission sets, custom reports. Not NAV-only.
• Deep, opinionated knowledge of Business Central's event-driven and data-driven architecture. Real experience subscribing to the event bus, knowing which events to hook, and understanding the downstream consequences. You should be able to teach us the nuances of BC end-to-end — inventory, warehousing, sales, purchasing, posting routines, accounting impacts.
• Job Queue and background processing experience. AL performance hygiene matters here — FlowFields, SIFT keys, Item/Reservation Entry calc cost. We already run a deferred-update queue architecture and you need to be at home in that world.
• Real experience with a Business Central environment that was connected to a Warehouse Management System. You should understand what that means for the BC document lifecycle (warehouse shipments, picks, put-aways, registration, posting). Direct experience with a specific WMS extension matters more than the brand. Slight preference for Insight Works Warehouse Insight or Lanham ACE WMS, but we're open.
• Warehousing fundamentals — bin locations, slotting strategies, zone-based velocity, wave/section picking, assembly-to-order flows. You should be able to push back on us when our physical-operations idea doesn't map cleanly to BC.
• Customizing the BC UI (page extensions, custom pages) and building custom reports.
• Source control, CI, version management, sandbox-to-production promotion. Git/VS Code AL workflow expected.
• Product-owner mindset. We're not looking for an order-taker. We'll bring a problem; you should think about tradeoffs between tech and physical operations and propose the pragmatic path. You should know when not to build something custom.
• Excellent English. Fluent, comfortable, and — most importantly — concise. We value people who know when to talk and when to stop. Grammar perfection isn't the bar; communication quality is.
• Comfortable working with AI tools, heavily. We're an AI-forward team and we want you using AI to speed up your workflow as much as you can. That said, we don't believe AI is perfect — attention to detail and knowing when AI is steering you wrong is part of the job.

Strong Bonuses

• TrueCommerce EDI integration with Business Central — how it sits inside the BC document lifecycle. We already depend on TrueCommerce. If you can absorb that area, that's a role we don't have to hire separately for.
• Power BI integrated with Business Central.
• Microsoft Copilot in Business Central — bringing it in and making it usable for us.
• Application Insights / telemetry on BC. We don't use it today; familiarity is enough.
• Experience onboarding a new legal entity / company into Business Central. Our main project is on a company already fully running on BC. A sister company may eventually port over from QuickBooks Desktop — that's a separate, later project, not the day-one work.

What Experience Looks Like to Us

Years of experience matter much less than what you've built, the complexity of it, what your actual role was, and how much ownership you took. Come prepared to talk about projects in detail — that's the interview.

What We're Not Looking For

• NetSuite-only or SAP-only backgrounds.
• Classic NAV experience without modern AL.
• People who need a fully-spec'd ticket to start working.