The functionality that generates the broker claims should be aligned across all the commerce channels including unified pricing. This has a major business justification because the broker contract is an agreement with the vendor which must be honored, irrelevant if the customer re-sells the product to its customers via POS, via Call Center or via E-commerce. The vendor expects that the broker agreement is always honored including those transactions sold via the POS channel (both Call Center and POS are Retail Sales Orders so they should behave the same).
Comments
Technical Analysis: The root cause appears to be linked to the MCRBrokerCommission records generated from the POS channel. Key findings include: The MarkUpTransRecID field in these records is not populated, leading to erroneous zero values in the broker charge display methodology. A method in the Retail Call stack, specifically RetailTransactionServiceOrder::createMarkupTrans(), deletes the existing MarkupTrans record and fails to re-establish the relationship with the MCRBrokerCommission record, unlike in the Call Center order process where the record is retained.
Category: Order processing and fulfillment
We are experiencing a critical issue related to broker contracts and claims specifically when Retail Sales Orders are generated from the POS channel. While functionality operates correctly for orders made via the HQ Call Center channel—with proper broker claims being generated—orders from the POS channel fail to reflect accurate broker charges or create broker claims, severely impacting our compliance with vendor agreements and our perception as an omnichannel retailer. Issue Details: POS Channel Orders: When a Retail Sales Order is generated through the retail statement posting of the POS channel, a broker charge record is created but consistently displays a value of zero. Despite identical customer, item, and quantity details with the Call Center orders, no corresponding broker claim is generated. Business Justification: This inconsistency undermines our agreements with vendors, as we cannot claim to uphold broker contracts for some transaction channels while disregarding others. Such discrepancies inhibit our ability to represent D365 Commerce as a true omnichannel solution.
Category: Order processing and fulfillment