Stage Checklist

  • ✓ Research (.md file)
  • ✓ POC App
  • ✓ POC UI (templates)
  • ✗ Microservice
  • ✗ Containerized (Dockerfile)
  • ✗ Helm Chart
  • ✗ CI/CD Pipeline
  • ✗ Frontend Page
Download Research Download Implementation Guide

AI Research

Last researched: 2026-03-05

Refund Rules

Zoho Inventory follows a subscription-based SaaS model with limited refund options. Refunds are typically only provided for billing errors or technical issues preventing service usage within the first 30 days. No refunds for unused portions of billing cycles, downgraded plans, or mid-cycle cancellations. Annual subscription discounts are forfeited upon early cancellation. Custom enterprise contracts may have different terms.

Credit Policies

Zoho offers service credits for documented downtime exceeding their SLA (99.9% uptime commitment). Credits are applied as account balance for future billing cycles, not cash refunds. No credits for planned maintenance, force majeure events, or issues caused by third-party integrations. Credits must be claimed within 30 days of the incident. No credits for unused features or capacity.

Contractual Terms

Auto-renewal enabled by default for all subscription plans. 30-day notice required for cancellation to avoid automatic renewal. Price increases limited to once per year with 30-day advance notice. Standard terms prohibit price increases exceeding 10% annually. Cancellation takes effect at the end of current billing period. Enterprise contracts may have different notice periods and price protection clauses. Data export available for 30 days post-cancellation.

Integration Complexity

★★★☆☆

Technical Notes

OAuth 2.0 with region-specific domains (US, EU, IN, AU, etc.) - must detect correct API domain from token response. All requests require organization_id parameter obtained from /organizations endpoint. Rate limits: 100 requests/minute per access token. Pagination uses page/per_page parameters (max 200 per page). Non-standard auth header format: 'Zoho-oauthtoken {token}'. API responses wrapped in standard envelope with code/message fields. Some operations require specific scopes beyond basic read access.