Using Revenue Recognition Bundle Functionality to Support Selling Kits in D365 (Part 2 of 2)

Posted on: January 10, 2022 | By: Guy Logan | Microsoft Dynamics AX/365, Microsoft Dynamics Manufacturing

Authored by: Rosey McAdams

This blog is the second part of a two-part series on Kitting. In part one of this blog series, we took a look at how to configure and use the D365 revenue recognition functionality to support kitting in your business.  In part two of this series, we will look at some important known “gotchas” when using this functionality to support kits.  Understanding these potential roadblocks is important so that these do not come as a surprise when your company begins to implement this functionality.

Bundle item component pricing cannot be set up via trade agreement.

1. • This means that when a bundle is created, we can only have one base price for each of the components to split the revenue across the bundle, which does not allow us to have different pricing splits per customer.
   • This can also become an issue if we do not use base pricing in our system at all, and like to keep our base prices as zero to signify that we are missing a trade agreement when entering a sales order.

When using bundles the system does not allow us to partially ship or partially invoice bundle components.

1. • If your company is used to being able to partially ship kit components, you will need to make a modification to support this behavior.
   • However, warehouse management functionality does allow us to release partial bundles to the warehouse and pick/put these components, which may cause some issues during shipping.

On sales orders there is not a clear tie between a top-level bundle item and its components, so you may choose to implement an enhancement to make this more straightforward to the users.

---

---