Dynamics 365 Business Central label printing: AL extensions, REST and file integration
Print item, lot, bin and shipping labels from Business Central (cloud or on-premises) with an AL extension calling the REST API, watched folders, or SQL views — scenarios and checklist for SMB warehouses.
Business Central is the ERP of thousands of manufacturers and distributors that outgrew spreadsheets, and its label printing is usually an afterthought: a report layout sent to a Windows printer. When the company adds a second warehouse, a thermal printer of another brand or a mobile picking flow, that approach breaks. EtikStudio plugs into BC through paths that do not require touching the base application.
Which integration paths fit Business Central
| Path | Fit | Why |
|---|---|---|
| REST API via AL extension | Best | A small AL extension adds a 'Print label' action on item, lot or shipment pages and calls the REST API with HttpClient. Works in cloud and on-premises. |
| Watched folder | Good | Job queue exports (CSV/XML) to a folder or FTP; EtikStudio prints the batch. No AL development. |
| Embedded data (SQL / ODBC) | On-premises | Read-only views on the BC database; for cloud tenants use the API pages or an exported replica. |
| Connector + relay | Good | BC online prints to the warehouse printers through the linked connector — no VPN, no public IP. |
Typical scenarios
| Process | Label | Trigger |
|---|---|---|
| Purchasing | Item and lot labels at receiving | Warehouse receipt posting |
| Manufacturing | Finished-goods labels with lot and expiry, GS1-128 | Output journal posting |
| Warehouse | Bin and location labels, pick labels | Bin creation, pick creation |
| Sales | Shipping labels with SSCC and ship-to | Sales shipment posting |
Recommended flow
For most SMBs the AL extension is a day of work: a codeunit that builds the JSON from the record and calls the REST server, plus an action on the relevant pages and a setup table mapping locations to printers. Companies without a partner start with the watched folder and add the extension later.
Implementation checklist
- Decide cloud vs on-premises: cloud tenants reach the REST server through the connector; on-premises can call it directly on the LAN.
- Create a setup table: location code → printer name → default template.
- Include lot and expiry in the call for GS1-128 and GS1 DataMatrix labels; EtikStudio formats the AIs.
- Test with the longest item descriptions in the item list to avoid overflow.
- Keep the AL extension minimal: data out, job id back; label design stays in EtikStudio.
How EtikStudio handles it
Label design, printer language and fleet changes stay out of AL. Business Central sends the record; EtikStudio renders, prints on the right printer at the right location and keeps the print history the auditor asks for.
Integration details vary by ERP version, deployment and licensing. Adapters and worked examples are provided during implementation.