Oracle Retail · Rate Limits

Oracle Retail Rate Limits

Oracle Retail Cloud Services REST APIs (Merchandising, Pricing, Integration, Order Management) do not publish per-second or per-minute rate-limit numbers. Throughput is governed by the underlying Retail Cloud pod capacity and by the Retail Integration Cloud Service (RICS) job-throttling configuration for bulk merchandise, inventory, and order events. Customers experiencing throttling are directed to Oracle Retail Support to raise capacity via a service request.

Oracle Retail Rate Limits is the machine-readable rate-limit profile for Oracle Retail on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring varies and concurrent_jobs.

The profile also includes 4 backoff/retry policies defined and response codes documented for unauthorized, forbidden, notFound, serverError, and serviceUnavailable.

Tagged areas include Retail, Oracle Cloud, Rate Limiting, and Omnichannel.

3 Limits
RetailOracle CloudRate LimitingOmnichannel

Limits

REST API Throughput tenancy
varies
bound by Oracle Retail Cloud pod capacity
Throughput is governed by the underlying Retail Cloud pod and may be raised via an Oracle Retail Support service request.
RICS Bulk Job Concurrency tenancy
concurrent_jobs
see RICS administration guide
Concurrent bulk synchronization jobs are configured per Retail Integration Cloud Service deployment.
Xstore POS Offline Mode lane
varies
lane-local capacity
Xstore Point of Service operates store-local and continues offline; in that mode rate limits are bounded by the lane's local hardware rather than by a centrally-published rate.

Policies

Capacity-Bound Throttling
Throughput limits are determined by the Retail Cloud pod and RICS job-throttling settings rather than a published per-tenancy rate-limit table.
Backoff Strategy
Clients should implement exponential backoff with jitter on 5xx responses; honor any Retry-After header when present.
Bulk Patterns
For high-volume merchandise, inventory, and order synchronization prefer the Retail Integration Cloud Service (RICS) bulk job patterns over hitting transactional REST endpoints.
Capacity Adjustment
Sustained high-volume integration requirements should be coordinated through Oracle Retail Support; tenancies on dedicated pods can request capacity increases.

Sources