BUG: Aggregate-Count-Sheet gets confused by exceptions #451

New Issue

2026-06-29T08:38:14Z

rob commented

2026-06-29 08:38:14 +00:00

The ACS was created in the days when exceptions were handled separately, and relied on order-content (as opposed to shipment-content) to count relevant products.

Now that exceptions are in the main fulfillment stream, this causes errors. Example:

http://primacase-de.web2.estack.com/print-jobs/get/2018/eplOnly/0/xmlOnly/0/aggregate-count

First SKU (800038) is not on any labels:

http://primacase-de.web2.estack.com/print-jobs/avery/2018

But it's there because of an exception shipment:

http://primacase-de.web2.estack.com/retail/shipments/208240

which references an order that does have that SKU.

The ACS was created in the days when exceptions were handled separately, and relied on order-content (as opposed to shipment-content) to count relevant products. Now that exceptions are in the main fulfillment stream, this causes errors. Example: http://primacase-de.web2.estack.com/print-jobs/get/2018/eplOnly/0/xmlOnly/0/aggregate-count First SKU (800038) is not on any labels: http://primacase-de.web2.estack.com/print-jobs/avery/2018 But it's there because of an exception shipment: http://primacase-de.web2.estack.com/retail/shipments/208240 which references an order that does have that SKU.

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#451