September 2026 (2026.09)

This release adds a vendor purchase-order constraints interface, configurable payload transformations, and more predictable handling of large inbound loads.

New Features ✨

Vendor Purchase Order Constraints

• POST /vendor-constraints submits vendor purchase-order constraints: VendorCode, ReceiveLocationCode, POConstraintFamily, POQuantity, POUnitOfMeasure, POType, POIntegrity, POCostLimit and the related vendor attributes.
• Each submit replaces the complete set of constraints, so always send every constraint you want to keep. Requires the GAINS X build released alongside this version.

Payload Transformations

• Field-level transformations can now be configured on inbound submissions, outbound responses and webhook deliveries: trimming, case changes, prefixes and suffixes, truncation, empty-to-null, and numeric scaling or clamping. Nothing changes until a transformation is configured; contact your GAINS representative to set one up.

Enhancements 🔨

Inbound Interfaces

• POST /calendar/daily, POST /calendar/weekly, POST /calendar/monthly and POST /partners/vendor-parameters now accept a partly valid batch, like every other submit. The valid records are processed and the response is 207 with the rejected records listed. A batch with no valid record still answers 422.
• When GAINS Connect is already processing a large volume of inbound data, a submit now answers 429 Too Many Requests with a Retry-After header, instead of accepting data it cannot yet process. Nothing from the refused request is stored, and the same Idempotency-Key can be reused on the retry. Clients submitting large volumes should retry a 429 after the delay given in Retry-After.

Bug Fixes 🐜

• Rejected records returned by GET /tasks/{TaskId} now use the field names you submitted, such as RSQApplication, FOBCost and BTOKitItemCode, so a rejected record can be corrected and re-submitted as-is.
• Resolved an issue where a very large inbound load could leave GAINS Connect unresponsive.