Prevent Base Prefix from Acting as Discount Code

Functions
1

Hi everyone, when using the discountRedeemCodeBulkAdd mutation to add multiple redeem codes under a single discount (e.g., codes like MYPREFIX-ABC, MYPREFIX-XYZ), we’ve observed that the prefix itself (MYPREFIX) also functions as a valid discount code. Is there a specific configuration or flag either in the discount setup or within the bulk add process to prevent the base prefix from being redeemable, ensuring only the fully generated codes work?

Thanks in advance

1 Like
2

Hi! Are you sure that MYPREFIX wasn’t set as a code when creating the discount? If you share the request ID from a request where you’re querying for the specific discount node that’s exhibiting the behaviour, I can take a closer look.

3

Hi Jonathan,

To my understanding, yes, MYPREFIX was set as a code when we created the discount.

The workflow in our app looks like this:

  1. Create a discount code using discountCodeAppCreate, e.g. MYPREFIX.
  2. Then, add more codes using discountRedeemCodeBulkAdd, .eg. MYPREFIX-ABC, MYPREFIX-123.

We currently don’t have a request ID on hand, unfortunately. But we can try to get one eventually.

Is there an API that can be used to disable just MYPREFIX as a redeem code?

If not, what would happen if we called discountRedeemCodeBulkDelete with an arguments object that only contained MYPREFIX? Would the other redeem codes continue to work?

Thanks,
Tobe

4

Yes, you can use discountRedeemCodeBulkDelete on just MYPREFIX and the other codes would work just fine. That would solve your problem.

1 Like