Skip to main content


Offer difference prices per Barcode, not SKU: Exploring Possibilities in Business Central

Jun Wang Profile Picture Jun Wang 4,078 Super User
Offer difference prices per Barcode, not SKU: Exploring Possibilities in Business Central
In the realm of Microsoft Dynamics 365 Business Central (BC), the flexibility and functionality provided by Stock Keeping Units (SKUs) are well acknowledged. Typically, SKUs are central to managing inventory, ensuring that products are tracked consistently across various dimensions. But what happens when we delve into the specifics of barcoding, pricing, and offers? Let's unpack a scenario that many BC users might find intriguing.

In BC, it's common practice to link multiple barcodes to a single SKU. For instance, consider a SKU designated as 'x'. This SKU can be associated with several barcodes – let's call them 'a', 'b', and 'c'. This setup is particularly useful in retail environments, where scanning any of these barcodes at the Point of Sale (POS) system will bring up the same SKU 'x'. This association ensures streamlined inventory management, but it also raises an interesting question regarding pricing flexibility.

The query at hand is whether it's possible to configure BC so that each barcode, while linked to the same SKU, triggers a different price when scanned. This feature would offer a significant advantage in various retail scenarios, allowing for dynamic pricing strategies even when products are essentially the same.

Unfortunately, as per the standard functionalities provided by BC, this isn't directly feasible. BC's design allows for multiple SKUs to be created under one item card, primarily to support detailed inventory management and item replenishment. The pricing, however, is generally managed at the master item card level, meaning that all references (or barcodes) tied to the same SKU will inherently point to the same price.
Workarounds and Custom Solutions
For businesses looking to implement such a specific pricing strategy, the out-of-the-box features of BC might not suffice. Here are a couple of approaches that could be considered:
Creating Separate Item Cards: A straightforward workaround is to create different item cards for each barcode, thereby allowing for distinct pricing. However, this method could complicate inventory tracking and is not ideal for maintaining a streamlined product catalog.
Developing a Custom Extension: A more sophisticated solution involves developing a custom extension for BC. This extension could potentially allow for associating each barcode with a unique price, overriding the default price set at the item card level. Such customization would require careful planning to ensure seamless integration with the existing BC setup and to maintain data consistency across the system.
While the default capabilities of Business Central provide robust support for linking multiple barcodes to a single SKU, they fall short of allowing different prices for each barcode under the same SKU. Companies needing this functionality must look towards custom development or alternative workarounds. As always, any customization or extension should be undertaken with a clear understanding of the business requirements and potential impacts on the system's overall functionality.