marketplacemetering_batch_meter_usage: Amazon Web Services Marketplace is introducing Concurrent...

In paws.cost.management: 'Amazon Web Services' Cost Management Services

Amazon Web Services Marketplace is introducing Concurrent Agreements, enabling buyers to make multiple purchases per Amazon Web Services account

Description

Amazon Web Services Marketplace is introducing Concurrent Agreements, enabling buyers to make multiple purchases per Amazon Web Services account. Starting June 1, 2026, new SaaS products must use CustomerAWSAccountId (instead of CustomerIdentifier), LicenseArn (instead of ProductCode) to support this feature. batch_meter_usage does not support CustomerIdentifier for new integrations. Existing integrations continue to work. Review the new integration for Concurrent Agreements here. For additional implementation details, see BatchMeterUsage code example with LicenseArn in the Amazon Web Services Marketplace Seller Guide.

See https://www.paws-r-sdk.com/docs/marketplacemetering_batch_meter_usage/ for full documentation.

Usage

marketplacemetering_batch_meter_usage(UsageRecords, ProductCode = NULL)

Arguments

UsageRecords

[required] The set of UsageRecords to submit. batch_meter_usage accepts up to 25 UsageRecords at a time.

ProductCode

Product code is used to uniquely identify a product in Amazon Web Services Marketplace. The product code should be the same as the one used during the publishing of a new product. ProductCode is required only for legacy integrations that use CustomerIdentifier. For new integrations using LicenseArn (Concurrent Agreements), do NOT include ProductCode at the request level. The LicenseArn in each UsageRecord identifies both the product and the specific agreement. Sending metering records with both ProductCode and LicenseArn for the same customer within the same hour will result in duplicate billing. If you are migrating from product-based metering to license-based metering, stop sending ProductCode before you start sending LicenseArn.

paws.cost.management documentation built on Oct. 8, 2026, 1:08 a.m.