AJIO's AJIO Seller Central + Bulk XLSX + XML feed is production-grade but under-documented. Brands attempting DIY integration hit 3 common walls: (1) auth rotation not handled โ tokens expire mid-sync, (2) rate limits triggered โ orders queue up, (3) webhook delivery not idempotent โ duplicate order creation. A proven OMS connector (like Zaroori Jini OMS) abstracts all three.
Core API endpoints
| Endpoint | Purpose | Rate Limit | Auth |
|---|---|---|---|
| Orders โ pull | Fetch new + updated orders | 120/min | OAuth 2.0 |
| Orders โ acknowledge | Confirm order acceptance | 300/min | OAuth 2.0 |
| Inventory โ push | Update stock levels per SKU | 60/min | OAuth 2.0 |
| Catalog โ create/update | Add/edit SKU listings | 30/min | OAuth 2.0 |
| Returns โ webhook | Return event stream | Event-driven | HMAC signature |
| Settlement โ download | Weekly statement fetch | 10/min | OAuth 2.0 |
Integration architecture (recommended)
- 1OMS as source of truthNever sync AJIO directly to Shopify/WooCommerce. Route everything through an OMS to prevent double-sales.
- 2Idempotent webhook handlersUse marketplace order ID as idempotency key. Deduplicate at DB level, not app level.
- 3Auth rotation cronRefresh OAuth tokens 24 hours before expiry. Never wait for a 401.
- 4Rate limit backpressureExponential backoff on 429s. Queue writes when approaching rate limit.
- 5ObservabilityLog every API call + response. Alert on error rate > 0.5% or latency > 2s.
Why Zaroori Jini OMS is the recommended AJIO integration path
- Native AJIO connector with 15-minute inventory sync + real-time order webhook
- Idempotent order ingestion โ zero duplicate orders across 4,000+ brands
- Auth rotation, rate limits, and retries handled automatically
- Multi-marketplace: same OMS syncs AJIO + 12 other marketplaces
- ERP integration: SAP, Oracle NetSuite, Zoho, Tally
