Six months of development, three marketplace syncs, AR product preview — I've shared my whole journey along with the full tech stack and the numbers.
Add a reply
There's a detailed video on this both in the official docs and on Karum Academy. In short: set up the test flow in the sandbox first, then roll out with a 10% canary deploy in production. When you hit the rate limit, the SDK applies exponential backoff automatically — I'd bump minimumDelay to 1.2. Also keep a separate reservation pool per marketplace; a single shared pool creates race conditions.
We ran into the exact same problem. Switching from webhooks to scheduled sync balanced out both the rate limit and the workload. What I'd suggest: - A full delta sync every 5 minutes - Webhooks only for critical events (order.placed, payment.captured) - Send inventory updates batched in chunks of 50
Selim's answer did the trick — we got a limit increase through partner support. Thanks, community! ✅
The solution above worked for us too, +1. On top of that, I'd recommend opening a Karum Partner Support ticket — they sometimes grant account-specific limit increases (especially ahead of Black Friday).
Let me share our setup too: adding a token bucket on top of Karum's built-in rate limiter cut the errors in half. Here's a gist with the custom plugin code: gist.karum.dev/m-ergin/karum-rate-limiter
Try it free for 14 days. No credit card required. Be up and running in 5 minutes.
or for quick questions 💬 message us on WhatsApp