Top Business Central Extensions & Add-Ons Every Company Should Know
Search AppSource for Business Central and you'll find thousands of apps, many promising to fix the exact problem your team complained about last week. Most companies need only a handful. The hard part isn't finding extensions. It's knowing which gaps are real, which ones the base product already covers, and which publisher will still be maintaining its app three upgrade cycles from now.
We help growing distributors, light manufacturers and services firms choose AppSource extensions as part of our Business Central projects, and we've learned to evaluate categories before products. This article covers the categories that come up most often (EDI, advanced warehousing, AP automation, e-commerce, payments, sales tax, reporting and field service), what to evaluate in each, and the checklist we use before any extension touches a live tenant. We deliberately don't crown a "best" app per category: the right answer depends on your volumes, trading partners and processes.
What Are Business Central Extensions?
Business Central is customized through extensions rather than changes to Microsoft's code. An extension is a package written in AL, Business Central's development language, that adds fields, pages, logic and integrations on top of the base application. Because the base app stays untouched, Microsoft can update your environment with two major release waves a year (spring and fall) plus monthly updates, and your extensions come along as long as their publishers keep them compatible.
You'll meet two kinds. AppSource apps are built by independent software vendors, pass Microsoft's technical validation, and install from the Extension Marketplace inside Business Central. Per-tenant extensions are custom code built for one company, usually by a partner, and uploaded directly to your environment. Validation checks technical quality and compatibility. It doesn't prove an app fits your process; that part is your job.
What Does Business Central Already Do Without Add-Ons?
Before buying anything, check what's in the box, because Microsoft keeps moving common gaps into the base product. Business Central includes bins and directed warehousing, a Shopify Connector that Microsoft builds and maintains, US sales tax setup through tax areas, jurisdictions and groups, Power BI apps for areas such as finance, sales and inventory, an incoming documents and e-documents framework, approval workflows and, in Premium, service management. Any of these may be enough, and a native feature is one less vendor to manage. Our walkthrough of Business Central inventory management shows how far the standard warehouse features go.
Some gaps, though, almost always need an add-on or a separate service. US payroll is the clearest example, since Business Central doesn't include it.
Which Extension Categories Should Every Company Know?
EDI
If you sell to big-box retailers, grocery chains or large distributors, EDI usually isn't optional. An EDI extension translates documents such as the 850 purchase order, 855 acknowledgment, 856 advance ship notice and 810 invoice into Business Central sales orders, shipments and invoices, and back again.
What to evaluate: whether trading-partner maps are included or billed per partner, who updates maps when a retailer changes its requirements, support for GS1-128 labels on shipments, and whether it connects through a VAN or directly. Ask how errors surface: a rejected ASN should appear in Business Central as someone's task, not in an inbox nobody reads. Retailer chargebacks for late or wrong ASNs can quietly erode margin, so compliance features matter as much as mapping.
Advanced warehousing, scanning and shipping
Business Central's warehouse documents are capable, but on their own they assume someone is clicking through pages at a desk. Warehouse extensions typically add handheld scanning for receiving, put-away, picking and counting, plus label printing and carrier integration for rate shopping and shipping labels.
What to evaluate: whether the app drives Business Central's standard warehouse documents or replaces them with its own logic (the former usually upgrades more smoothly), which scanner hardware it supports, what happens when Wi-Fi drops at the back of the building, and how tracking numbers flow back to the sales shipment. Pilot it in a sandbox with your real bins and items.
AP automation and document capture
Keying vendor invoices is one of the first jobs companies want gone. Capture extensions read PDF and emailed invoices, extract header and line data, match them to purchase orders and receipts, and route exceptions for approval. Microsoft is adding native capability here too, so compare against the current base product.
What to evaluate: extraction accuracy on your own vendors' invoices (send fifty real ones, not the demo set), line-level matching to receipts with tolerances, how non-PO invoices are coded and approved, and pricing by document volume. Confirm the audit trail links the original image to the posted invoice.
E-commerce connectors
Microsoft's Shopify Connector covers many direct-to-consumer and B2B Shopify stores. Connectors for other storefronts and marketplaces come from third parties.
What to evaluate: which records sync in each direction (items, variants, prices, inventory, customers, orders, refunds), how often, how variants map, multi-store support, and how taxes, discounts, shipping charges and payment fees post. The ugliest go-live issues we see involve refunds and partial shipments, so test those specifically.
Payments
Payment extensions let you take card or ACH payments against orders and invoices, add pay-by-link options to emailed invoices, and apply settlements automatically.
What to evaluate: whether you're locked into the publisher's processor or can bring your own, how card data is tokenized and what that means for your PCI scope, how processor fees and deposits reconcile, and whether surcharging rules can be configured for the states you sell into.
Sales tax
Native tax areas and jurisdictions work when you file in a few states. Since the 2018 Wayfair decision, many sellers have economic nexus in far more states, and maintaining rates by hand stops being realistic. Tax-engine connectors (Avalara is the name most buyers know) calculate tax at the address level and support filing.
What to evaluate: address validation, exemption certificate management, how tax is recalculated when an order becomes an invoice, behavior when the tax service is unreachable, and transaction-based pricing tiers.
Reporting and analytics
Between financial reporting, Microsoft's Power BI apps, analysis mode on list pages and Excel layouts, native reporting is broader than many buyers expect. Add-ons fill gaps in Excel-based financial reporting, budgeting and planning, and multi-company consolidation.
What to evaluate: who will build and maintain reports, live versus scheduled refresh, licensing for designers versus viewers, and whether the tool understands Business Central dimensions. Our beginner tutorial on connecting Dynamics 365 and Power BI covers the native route first.
Field service
Business Central Premium includes service management (service items, contracts and service orders), and Microsoft offers an integration with Dynamics 365 Field Service for more advanced scheduling. Third-party apps add technician mobile apps and dispatch boards.
What to evaluate: offline mobile use, scheduling and dispatch, parts consumption from van stock (often modeled as a location per van), contract billing, and photo or signature capture on completion.
How Do the Categories Compare?
| Category | Typical trigger | Key question to ask | Common pricing models |
|---|---|---|---|
| EDI | A retail or distributor customer mandates it | Who maintains trading-partner maps? | Per partner and/or per document |
| Warehouse and scanning | Paper picking errors, slow receiving | Does it use standard warehouse documents? | Per device or per user |
| AP capture | Hundreds of invoices keyed each month | How accurate is it on our vendors' invoices? | Document volume tiers |
| E-commerce | Web orders re-keyed into the ERP | How are refunds and partial shipments handled? | Subscription, sometimes per store |
| Payments | Card or ACH payments taken outside the ERP | Can we choose our own processor? | Subscription plus processing fees |
| Sales tax | Nexus in many states | What happens when the service is down? | Transaction volume tiers |
| Reporting | Finance lives in exported spreadsheets | Who builds and maintains reports? | Per designer or per viewer |
| Field service | Technicians on paper or a disconnected app | Does the mobile app work offline? | Per technician |
How Do You Vet a Business Central Extension?
Whatever the category, every candidate goes through the same checklist before it goes near production:
- Publisher track record. How long have they built for Business Central, and how many customers do they support in the US and in your industry?
- Update cadence. Do compatible versions ship promptly for each release wave? Ask for their history, not their intentions.
- Support model. Who answers tickets, in which time zones, with what response targets? Is support included or extra?
- Licensing. Per user, per company, per environment or per transaction? Do light users count? What happens at renewal?
- Permissions and data. Which permission sets does it install, what data leaves your tenant, and where is it stored?
- Dependencies and conflicts. Does it rely on other apps, and has it run alongside the extensions you already have?
- Performance. Apps that hook into posting routines can slow them down, so ask about high-volume customers.
- Exit path. What happens to your data if you uninstall, and can you export it first?
- References. Speak to two customers of similar size, ideally one live through several upgrades.
- Sandbox trial. Test your own scenarios on a copy of your data, not the vendor's demo script.
Every extension is another publisher, contract, upgrade dependency and support queue. If two apps overlap, pick one. If a gap can be closed with configuration or a Power Automate flow, try that first; our article on ERP workflow automation has examples.
Pro tip: Ask each publisher how soon after the last major release wave their compatible version shipped. The answer tells you more about long-term support than any brochure.
Conclusion
The best Business Central extension strategy is a short list. Start with what the base product already does, close the gaps that genuinely hurt, such as EDI mandates, warehouse scanning, invoice volumes and multistate tax, and vet every candidate on support, update cadence, licensing and exit path as hard as you vet features. Choosing carefully up front keeps upgrades uneventful, which is exactly what you want from an ERP.
If you'd like help shortlisting extensions for your Business Central environment, the Brightmoor Dynamics team is always happy to compare notes.
Frequently Asked Questions
What is the difference between an extension and a customization in Business Central?
In Business Central, customizations are delivered as extensions. Microsoft's base code isn't modified; extensions add fields, pages and logic on top, which makes upgrades far less painful than in older on-premises systems. The distinction that matters now is between AppSource apps serving many customers and per-tenant extensions built for one company.
Are AppSource extensions approved by Microsoft?
AppSource apps pass Microsoft's technical validation before publication, which covers areas such as code quality and compatibility. Validation doesn't confirm that an app suits your processes or that the publisher's support is good. Treat it as a minimum bar, then do your own testing and reference checks.
How much do Business Central extensions cost?
Pricing models vary: per user per month, flat per company or environment, tiered by transaction or document volume, sometimes with a setup fee. Some apps offer free tiers or trials. Check current pricing on the publisher's listing, and budget for configuration and testing time as well as the subscription.
Do extensions break when Business Central updates?
They can if a publisher falls behind. Microsoft makes preview versions available ahead of each major release so publishers can test, and well-run publishers ship compatible versions on time. Ask for their track record across recent waves, and test updates in a sandbox before they reach production.
