সংযোজন আৰু API
সংযোজনৰ সীমাবদ্ধতাসমূহ কি?
Summary
Integrations depend on third-party provider availability, account approval, API access, provider rules, plan limits, connected app allowance, data quality, and technical setup. ShopIQ provides the integration layer where supported, but it does not control external provider pricing, downtime, approvals, serviceability, settlements, delivery performance, or policy changes.
Who this is for: Merchants who want a realistic understanding of what integrations can and cannot do.
What are integration limitations?
Integrations make ShopIQ more powerful, but they have limitations. These limitations usually depend on the third-party provider, merchant account setup, provider permissions, connected app limits, and available data. ShopIQ provides supported integration workflows, but it cannot control every external service.
Integrations depend on provider availability
Third-party providers may experience downtime, delays, API changes, outages, maintenance, or service limitations. If a provider is unavailable, the related integration may be affected. For example, payment checkout may fail if a payment gateway has downtime, tracking updates may delay if a logistics provider system is delayed, WhatsApp campaigns may fail if the provider has message delivery issues, and analytics data may be incomplete if tracking is blocked or misconfigured.
Integrations depend on provider approval
Some integrations require account approval or verification. Examples include payment gateway KYC, logistics account activation, WhatsApp Business verification, marketplace seller approval, ad account approval, and API access approval. ShopIQ does not control third-party approval decisions.
Integrations may have separate costs
- Payment gateway transaction fees
- Logistics shipping charges
- COD and RTO charges
- WhatsApp message charges
- Ad platform spend
- Marketplace commissions
- External SaaS subscription fees
These are separate from ShopIQ subscription billing.
Integrations depend on connected app limits
Each external third-party integration counts as a connected app. If the merchant reaches the connected app limit, they may need to disconnect an unused app or upgrade to a higher plan. Native ShopIQ features do not count as connected apps.
Integrations depend on correct setup
- Wrong API key
- Missing permissions
- Incorrect tracking ID
- Incomplete KYC
- Wrong pickup address
- Incorrect payment method setup
- Incorrect webhook or callback configuration
- Expired credentials
- Provider account restrictions
Merchants should test integrations before launch.
Integrations may not support every workflow
Not every provider supports every feature. For example, a payment gateway may not support every payment method, a logistics provider may not support every pin code, a WhatsApp provider may require template approval, a marketplace may not support every product category, an analytics tool may not capture all customer activity, and a courier may not support reverse pickup in all locations. Merchants should confirm feature availability before promising it to customers.
Data may not always sync instantly
- Payment status updates
- Shipment tracking updates
- Campaign data
- Analytics events
- Marketplace orders
- Inventory updates
- Return status
Merchants should check provider dashboards if data appears delayed or inconsistent.
API access is limited to approved use cases
ShopIQ APIs are available for selected capabilities such as website creation and image creation through the API Partner Program. API access is not an unrestricted public API for every feature. Partners should contact ShopIQ to understand available APIs, documentation, access, pricing, rate limits, and supported use cases.
Integrations should be tested before live usage. Merchants should keep provider accounts active, monitor connected apps, review errors, understand third-party fees, and verify critical workflows such as checkout, shipping, WhatsApp campaigns, and analytics.