EDI Acknowledgments Speak The Partner's Language

Outbound 855 acknowledgments got two corrections that make them line up with what the retailer actually reads.

Lines can be acknowledged in the partner's own unit. Whole Foods orders in cases, Endless stores in eaches — an outbound 855 template could only echo back whatever unit the 850 arrived in, so there was no clean way to acknowledge a line back in the partner's code, and no way to state a corrected quantity in it either. Templates can now ask for the acknowledgment on a specific basis ("each", "inner pack") and the code the partner uses for that basis is pulled from the integration's UOM mapping — so renaming CA to CS for one partner is a one-token change on the mapping and needs no template edit. The same pass fixed several ways an acknowledgment could tell a retailer we had dropped a line they ordered (two lines of the same SKU collapsing, archived or unresolved products disappearing, partially numbered purchase orders cancelling their unnumbered lines).

The header now agrees with the detail. BAK02 — Amazon's mandatory "acknowledgment type" field — was hardcoded to AD ("completely accepted") on every 855, including ones whose per-line ACK segments rejected a line or cut a quantity, so the header was contradicting the detail on exactly the orders where the detail mattered. The header now reads AC ("cannot be fully accepted") whenever any line was rejected or short-shipped, and AD only when every line came back accepted.