Instruction: What ISO currency code is used for the NA region? Report only the code.


Instruction: What ISO currency code is used for the NA region? Report only the code.


Instruction: What ISO currency code is used for the EU region? Report only the code.


Instruction: What ISO currency code is used for the EU region? Report only the code.


Instruction: What ISO currency code is used for the APAC region? Report only the code.


Instruction: What ISO currency code is used for the APAC region? Report only the code.


Instruction: What ISO currency code is used for the LATAM region? Report only the code.


Instruction: What ISO currency code is used for the LATAM region? Report only the code.


Instruction: What ISO currency code is used for the NA region? Report only the code.


Instruction: What ISO currency code is used for the EU region? Report only the code.


Instruction: What ISO currency code is used for the APAC region? Report only the code.


Instruction: What ISO currency code is used for the LATAM region? Report only the code.


Instruction: What ISO currency code is used for the NA region? Report only the code.


Instruction: What ISO currency code is used for the EU region? Report only the code.


Instruction: What ISO currency code is used for the APAC region? Report only the code.


Instruction: What ISO currency code is used for the LATAM region? Report only the code.


Instruction: What ISO currency code is used for the NA region? Report only the code.


Instruction: What ISO currency code is used for the EU region? Report only the code.


Instruction: What ISO currency code is used for the APAC region? Report only the code.


Instruction: What ISO currency code is used for the LATAM region? Report only the code.


Instruction: What ISO currency code is used for the NA region? Report only the code.


Instruction: What ISO currency code is used for the EU region? Report only the code.


Instruction: What ISO currency code is used for the APAC region? Report only the code.


Instruction: What ISO currency code is used for the LATAM region? Report only the code.


Instruction: What ISO currency code is used for the NA region? Report only the code.


Instruction: For region NA, category A, months 202601-202603, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region NA, category B, months 202604-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region EU, category C, months 202601-202604, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region EU, category D, months 202603-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region APAC, category A, months 202602-202605, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region APAC, category D, months 202601-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region LATAM, category B, months 202601-202604, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region LATAM, category C, months 202603-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region NA, category D, months 202602-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region EU, category A, months 202602-202605, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region APAC, category B, months 202604-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region LATAM, category A, months 202601-202603, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region NA, category C, months 202601-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region EU, category B, months 202601-202603, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region APAC, category C, months 202602-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region LATAM, category D, months 202601-202605, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region NA, category A, months 202604-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region EU, category D, months 202601-202602, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region APAC, category A, months 202603-202604, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region LATAM, category B, months 202605-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region NA, category C, months 202602-202604, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region EU, category B, months 202604-202606, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region APAC, category D, months 202603-202605, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region LATAM, category C, months 202601-202602, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: For region NA, category D, months 202601-202603, identify the product id with the highest units sold. Report only the product id; report -1 if no product has paid/refunded orders.


Instruction: How many paid/refunded orders are in region NA, category A, from month 202601 through 202603? Report the count.


Instruction: How many paid/refunded orders are in region NA, category B, from month 202604 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region EU, category C, from month 202601 through 202604? Report the count.


Instruction: How many paid/refunded orders are in region EU, category D, from month 202603 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region APAC, category A, from month 202602 through 202605? Report the count.


Instruction: How many paid/refunded orders are in region APAC, category D, from month 202601 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region LATAM, category B, from month 202601 through 202604? Report the count.


Instruction: How many paid/refunded orders are in region LATAM, category C, from month 202603 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region NA, category D, from month 202602 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region EU, category A, from month 202602 through 202605? Report the count.


Instruction: How many paid/refunded orders are in region APAC, category B, from month 202604 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region LATAM, category A, from month 202601 through 202603? Report the count.


Instruction: How many paid/refunded orders are in region NA, category C, from month 202601 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region EU, category B, from month 202601 through 202603? Report the count.


Instruction: How many paid/refunded orders are in region APAC, category C, from month 202602 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region LATAM, category D, from month 202601 through 202605? Report the count.


Instruction: How many paid/refunded orders are in region NA, category A, from month 202604 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region EU, category D, from month 202601 through 202602? Report the count.


Instruction: How many paid/refunded orders are in region APAC, category A, from month 202603 through 202604? Report the count.


Instruction: How many paid/refunded orders are in region LATAM, category B, from month 202605 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region NA, category C, from month 202602 through 202604? Report the count.


Instruction: How many paid/refunded orders are in region EU, category B, from month 202604 through 202606? Report the count.


Instruction: How many paid/refunded orders are in region APAC, category D, from month 202603 through 202605? Report the count.


Instruction: How many paid/refunded orders are in region LATAM, category C, from month 202601 through 202602? Report the count.


Instruction: How many paid/refunded orders are in region NA, category D, from month 202601 through 202603? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region NA, category A, from month 202601 through 202603? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region NA, category B, from month 202604 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region EU, category C, from month 202601 through 202604? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region EU, category D, from month 202603 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region APAC, category A, from month 202602 through 202605? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region APAC, category D, from month 202601 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region LATAM, category B, from month 202601 through 202604? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region LATAM, category C, from month 202603 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region NA, category D, from month 202602 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region EU, category A, from month 202602 through 202605? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region APAC, category B, from month 202604 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region LATAM, category A, from month 202601 through 202603? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region NA, category C, from month 202601 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region EU, category B, from month 202601 through 202603? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region APAC, category C, from month 202602 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region LATAM, category D, from month 202601 through 202605? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region NA, category A, from month 202604 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region EU, category D, from month 202601 through 202602? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region APAC, category A, from month 202603 through 202604? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region LATAM, category B, from month 202605 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region NA, category C, from month 202602 through 202604? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region EU, category B, from month 202604 through 202606? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region APAC, category D, from month 202603 through 202605? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region LATAM, category C, from month 202601 through 202602? Report the count.


Instruction: How many unique customers placed paid/refunded orders in region NA, category D, from month 202601 through 202603? Report the count.


Instruction: For orders in region NA, category A, months 202601-202603: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region NA, category B, months 202604-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region EU, category C, months 202601-202604: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region EU, category D, months 202603-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region APAC, category A, months 202602-202605: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region APAC, category D, months 202601-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region LATAM, category B, months 202601-202604: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region LATAM, category C, months 202603-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region NA, category D, months 202602-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region EU, category A, months 202602-202605: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region APAC, category B, months 202604-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region LATAM, category A, months 202601-202603: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region NA, category C, months 202601-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region EU, category B, months 202601-202603: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region APAC, category C, months 202602-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region LATAM, category D, months 202601-202605: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region NA, category A, months 202604-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region EU, category D, months 202601-202602: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region APAC, category A, months 202603-202604: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region LATAM, category B, months 202605-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region NA, category C, months 202602-202604: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region EU, category B, months 202604-202606: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region APAC, category D, months 202603-202605: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region LATAM, category C, months 202601-202602: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region NA, category D, months 202601-202603: compute each order's net USD revenue after loyalty discount and refunds, then report the total net revenue in USD.


Instruction: For orders in region NA, category A, months 202601-202603: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region NA, category B, months 202604-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region EU, category C, months 202601-202604: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region EU, category D, months 202603-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region APAC, category A, months 202602-202605: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region APAC, category D, months 202601-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region LATAM, category B, months 202601-202604: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region LATAM, category C, months 202603-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region NA, category D, months 202602-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region EU, category A, months 202602-202605: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region APAC, category B, months 202604-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region LATAM, category A, months 202601-202603: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region NA, category C, months 202601-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region EU, category B, months 202601-202603: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region APAC, category C, months 202602-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region LATAM, category D, months 202601-202605: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region NA, category A, months 202604-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region EU, category D, months 202601-202602: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region APAC, category A, months 202603-202604: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region LATAM, category B, months 202605-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region NA, category C, months 202602-202604: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region EU, category B, months 202604-202606: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region APAC, category D, months 202603-202605: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region LATAM, category C, months 202601-202602: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region NA, category D, months 202601-202603: sum gross USD revenue and refund USD amounts, then report the refund share in basis points as floor(refunds * 10000 / gross). Report 0 if gross is zero.


Instruction: For orders in region NA, category A, months 202601-202603: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region NA, category B, months 202604-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region EU, category C, months 202601-202604: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region EU, category D, months 202603-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region APAC, category A, months 202602-202605: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region APAC, category D, months 202601-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region LATAM, category B, months 202601-202604: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region LATAM, category C, months 202603-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region NA, category D, months 202602-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region EU, category A, months 202602-202605: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region APAC, category B, months 202604-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region LATAM, category A, months 202601-202603: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region NA, category C, months 202601-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region EU, category B, months 202601-202603: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region APAC, category C, months 202602-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region LATAM, category D, months 202601-202605: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region NA, category A, months 202604-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region EU, category D, months 202601-202602: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region APAC, category A, months 202603-202604: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region LATAM, category B, months 202605-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region NA, category C, months 202602-202604: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region EU, category B, months 202604-202606: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region APAC, category D, months 202603-202605: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region LATAM, category C, months 202601-202602: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region NA, category D, months 202601-202603: sum net USD revenue after loyalty discounts and refunds, then convert the total into the region's local currency. Report the integer local-currency amount.


Instruction: For orders in region NA, category A, months 202601-202603: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region NA, category B, months 202604-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region EU, category C, months 202601-202604: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region EU, category D, months 202603-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region APAC, category A, months 202602-202605: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region APAC, category D, months 202601-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region LATAM, category B, months 202601-202604: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region LATAM, category C, months 202603-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region NA, category D, months 202602-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region EU, category A, months 202602-202605: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region APAC, category B, months 202604-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region LATAM, category A, months 202601-202603: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region NA, category C, months 202601-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region EU, category B, months 202601-202603: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region APAC, category C, months 202602-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region LATAM, category D, months 202601-202605: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region NA, category A, months 202604-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region EU, category D, months 202601-202602: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region APAC, category A, months 202603-202604: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region LATAM, category B, months 202605-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region NA, category C, months 202602-202604: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region EU, category B, months 202604-202606: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region APAC, category D, months 202603-202605: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region LATAM, category C, months 202601-202602: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: For orders in region NA, category D, months 202601-202603: compute each order's gross USD margin, subtract that order's USD refund amount, floor at zero per order, and report the total margin.


Instruction: Find the top-selling product id for region NA, category A, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region NA, category B, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region EU, category C, months 202601-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region EU, category D, months 202603-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region APAC, category A, months 202602-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region APAC, category D, months 202601-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region LATAM, category B, months 202601-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region LATAM, category C, months 202603-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region NA, category D, months 202602-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region EU, category A, months 202602-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region APAC, category B, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region LATAM, category A, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region NA, category C, months 202601-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region EU, category B, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region APAC, category C, months 202602-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region LATAM, category D, months 202601-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region NA, category A, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region EU, category D, months 202601-202602. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region APAC, category A, months 202603-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region LATAM, category B, months 202605-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region NA, category C, months 202602-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region EU, category B, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region APAC, category D, months 202603-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region LATAM, category C, months 202601-202602. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: Find the top-selling product id for region NA, category D, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily demand, and report the reorder shortfall max(0, planning demand - inventory position).


Instruction: For region NA, category A, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region NA, category B, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region EU, category C, months 202601-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region EU, category D, months 202603-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region APAC, category A, months 202602-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region APAC, category D, months 202601-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region LATAM, category B, months 202601-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region LATAM, category C, months 202603-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region NA, category D, months 202602-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region EU, category A, months 202602-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region APAC, category B, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region LATAM, category A, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region NA, category C, months 202601-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region EU, category B, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region APAC, category C, months 202602-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region LATAM, category D, months 202601-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region NA, category A, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region EU, category D, months 202601-202602: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region APAC, category A, months 202603-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region LATAM, category B, months 202605-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region NA, category C, months 202602-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region EU, category B, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region APAC, category D, months 202603-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region LATAM, category C, months 202601-202602: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region NA, category D, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total.


Instruction: For region NA, category A, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region NA, category B, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region EU, category C, months 202601-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region EU, category D, months 202603-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region APAC, category A, months 202602-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region APAC, category D, months 202601-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region LATAM, category B, months 202601-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region LATAM, category C, months 202603-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region NA, category D, months 202602-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region EU, category A, months 202602-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region APAC, category B, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region LATAM, category A, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region NA, category C, months 202601-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region EU, category B, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region APAC, category C, months 202602-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region LATAM, category D, months 202601-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region NA, category A, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region EU, category D, months 202601-202602: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region APAC, category A, months 202603-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region LATAM, category B, months 202605-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region NA, category C, months 202602-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region EU, category B, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region APAC, category D, months 202603-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region LATAM, category C, months 202601-202602: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region NA, category D, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count.


Instruction: For region NA, category A, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region NA, category B, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region EU, category C, months 202601-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region EU, category D, months 202603-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region APAC, category A, months 202602-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region APAC, category D, months 202601-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region LATAM, category B, months 202601-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region LATAM, category C, months 202603-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region NA, category D, months 202602-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region EU, category A, months 202602-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region APAC, category B, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region LATAM, category A, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region NA, category C, months 202601-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region EU, category B, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region APAC, category C, months 202602-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region LATAM, category D, months 202601-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region NA, category A, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region EU, category D, months 202601-202602: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region APAC, category A, months 202603-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region LATAM, category B, months 202605-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region NA, category C, months 202602-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region EU, category B, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region APAC, category D, months 202603-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region LATAM, category C, months 202601-202602: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.


Instruction: For region NA, category D, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for those orders, and report the total at-risk revenue.