November 2025 (2025.11)

New Features ✨

Added POST /partners/vendor-parameters, the first endpoint a vendor can call directly against a GAINS client's environment. A vendor submits the SKU-Location constraints they own — standard cost, capacity units, weight and price breaks — for the items and locations they supply, and the payload is processed through the usual integration task.
Extended data is supported, so vendor-supplied records can carry the same custom attributes you have configured elsewhere in your integration.

A partner authenticates with credentials GAINS issues for the specific client environment they are integrating with. Those credentials grant access to the partner inbound endpoints only; anything else is refused. Contact your GAINS representative to have a partner set up.
Each SupplierCode in the payload is validated against the suppliers configured for that partner and environment.

A rejected record now says which record it was. Every inbound submit that returns rejected records reports each reason alongside the key of the record it applies to, so a failure inside a batch of several hundred can be traced to the item and location that caused it without matching messages back by hand.
This changes the shape of Reasons on inbound responses. It was a list of strings and is now a list of objects, each carrying a Reason and the RecordKey that identifies the record. Integrations that read the rejection detail will need to account for the new shape; the set of endpoints and status codes is unchanged.