Hi Palash, You are correct that because productPromoCodeId is the primary key in the ProductPromoCode entity, the system does not currently allow for multiple records with the same code. To address your requirement, the entity definition would need to be updated.
*Proposal*: You could remove productPromoId from the ProductPromoCode entity and create a new entity, such as ProductPromoCodeAssoc. This would allow you to associate a single promo code ID with multiple promotions. These associations can then be managed using a fromDate and thruDate pattern to enable or disable them as needed. Kind Regards, Arun Patidar VP of Information Systems *HotWax CommerceReal OmniChannel. Real Results.* m: +91 9827353082 w: www.hotwax.co <https://www.linkedin.com/company/hotwaxcommerce/> <https://www.facebook.com/HotWaxCommerce/> <https://twitter.com/hotwaxcommerce> On Mon, Jan 19, 2026 at 7:14 PM Palash Bajaj <[email protected]> wrote: > I am looking for the ability to reuse the same promo code multiple times > *(one > active at a time),* for example: every year, driving the Christmas offer > with the same promo code (XMAS25). This would help me maintain consistent > offer branding between customers, with slightly different rules, but still > having the same promo code. > > The existing OFBiz out-of-the-box workflow defines the productPromoCodeId > field as the primary key in the ProductPromoCode entity, with > productPromoId serving as a foreign key. Hence, there can always be only > one ProductPromoCode record existing for an individual promoCode. This data > modelling does not allow me to refer/use the same promo code for different > promotions. > > Looking forward to your thoughts on it. > > > Kind Regards, > Palash Bajaj >
