Integrations
One integration layer for the systems your teams already trust
Support Master sits between channel chaos and internal discipline: orders, inventory, settlements, ads, logistics, and finance events normalize into a single commerce model. Connectors, file bridges, and APIs are built for retries, drift, and audit—not “check the box” screenshots.
Named systems below reflect typical enterprise stacks and partner adapter roadmaps. Availability varies by region, contract tier, and compliance review—confirmation happens in your solution design packet.
REST & GraphQL APIs
Idempotent writes, versioning, and rate-limit aware clients for bilateral sync.
Webhooks & event bus
Signed callbacks, replay safety, and dead-letter handling for operational events.
Batch files & SFTP
CSV, XML, and partner-specific layouts for ERPs and legacy stacks.
iPaaS / MuleSoft / Workato
Orchestrate long-tail internal tools without forking core product logic.
Integration catalog
Connectors by category
Each category can combine multiple transport modes—for example marketplace webhooks plus nightly settlement files to accounting. Your blueprint documents authoritative sources per entity and channel.
Marketplaces & large-format retail
Order, catalog, inventory, and settlement signals normalized into one OMS graph—channel-specific quirks handled in adapters.
- Amazon (Seller Central / Vendor paths)
- Flipkart
- Myntra
- Meesho
- Nykaa
- Ajio
- Tata CLiQ
- JioMart
- Snapdeal
- FirstCry
- Purplle
- Noon (MEA)
- eBay
Food & on-demand delivery
Ticket ingestion, menu sync, status callbacks, and payout reconciliation for high-volume kitchen and outlet operations.
- Swiggy
- Zomato
- Uber Eats (regional)
- DoorDash (partner programs)
- aggregator webhooks & batch settlements
Quick commerce & hyperlocal
Dark-store SLAs, ATP buffers, and cut-off aware sync so promos do not outrun pick capacity.
- Blinkit
- Zepto
- Instamart / Swiggy Instamart
- BigBasket (partner/API paths)
- Dunzo for Business
D2C storefronts & headless
Cart-to-fulfillment lineage for your owned channels with webhook and batch options.
- Shopify
- Shopify Plus
- WooCommerce
- Adobe Commerce (Magento)
- Salesforce Commerce Cloud
- Custom headless (REST / GraphQL bridges)
POS & in-store
When retail execution runs on Support Master Retail OS or bridged POS, store inventory participates in the same ATP rules as online.
- Retail OS native
- POS API bridges (vendor-specific)
- Barcode / scale peripherals
Payments, checkout & fraud signals
Capture authorization state, refunds, and payouts alongside orders for finance-grade reconciliation.
- Razorpay
- Stripe
- PayU
- Cashfree
- CCAvenue
- Paytm / PhonePe (ACQ paths)
- Apple Pay / Google Pay (via PSP)
Carriers, 3PL & last mile
AWB creation, scan events, NDR, RTO signals, and returns handoffs—idempotent updates during peak.
- Delhivery
- Blue Dart
- DTDC
- Ecom Express
- XpressBees
- Shadowfax
- Shiprocket
- Pickrr / Shipsy ecosystem
- Aramex
- DHL eCommerce
Ads, analytics & attribution
Catalog feeds, offline conversions, and guardrail hooks so spend aligns with operational stock and margin.
- Meta Marketing API
- Google Ads
- Google Merchant Center
- TikTok for Business
- Snapchat Ads
- GA4 exports (via warehouse)
Accounting, tax & invoicing
Structured journals, tax registers, and filing-adjacent exports—always validated with your counsel per jurisdiction.
- Tally (Prime / ERP)
- Zoho Books
- QuickBooks Online
- Xero
- Busy
- Cleartax (filing handoff patterns)
- CSV / XML statutory packs
ERP, WMS & planning
Respect the ledger and master: Support Master orchestrates commerce velocity; posting rules stay yours.
- SAP S/4 & ECC patterns
- Oracle NetSuite
- Microsoft Dynamics 365
- Infor
- Odoo bridges
- Custom WMS / IMS APIs
People systems (with HRMS module)
Employee master, attendance devices, and payroll bank files—scoped to implementations that activate people workflows.
- greytHR
- Keka
- Darwinbox (export / API)
- BambooHR (global)
- Workday (custom enterprise)
Identity, access & collaboration
Enterprise login, audit, and operational alerting without duplicating user stores.
- Okta
- Microsoft Entra ID (Azure AD)
- Google Workspace SSO
- SAML 2.0 / OIDC
- Slack notifications
- Microsoft Teams webhooks
Data platform & BI
Batch and incremental loads for the warehouse you already run—so finance builds on one governed feed.
- Snowflake
- Google BigQuery
- Amazon Redshift
- Azure Synapse
- Databricks ingestion
- Tableau / Power BI (via warehouse)
- Fivetran / Airbyte partner paths
CRM, support & ticketing
Customer timelines and safe actions for agents sit on the same order keys as OMS.
- Salesforce Service Cloud
- Zendesk
- Freshdesk
- Zoho Desk
- Intercom
- Custom ticketing APIs
Data domains
What typically syncs—and how it is governed
| Domain | Examples | Patterns |
|---|---|---|
| Orders & fulfillment | States, line items, cancellations, partial ship, returns | Webhooks + reconciliation sweeps |
| Inventory & ATP | Nodes, reservations, buffers, 86 | Near-real-time + periodic full refresh |
| Catalog & pricing | Listings, MAP, promos, channel-specific attributes | Delta feeds + validation queues |
| Settlements & fees | Payouts, adjustments, chargebacks | Batch files + ledger mapping |
| Logistics events | AWB, scans, NDR, POD | Carrier APIs + exception routing |
| Customer & tickets | Identity keys, consent, CRM notes | API + field-level privacy controls |
Philosophy
Operational trust beats connector count
- Normalize first: Every source maps into one commerce model so ops does not maintain parallel definitions per channel.
- Own edge cases: Retries, delayed webhooks, status mismatches, and recon variance are integration responsibilities—not nightly heroics in Excel.
- Stay extensible: The long tail of internal tools matters; APIs, exports, and adapters scale where SKU-level nuance lives.
Enterprise readiness
Security, segregation, and audit
- Role-based access, environment separation (non-prod vs prod), and secrets hygiene for third-party credentials.
- PII minimization, retention windows, and regional deployment options aligned to your DPA.
- Immutable integration event logs for investigations: what payload arrived, what transformed, what posted downstream.
FAQ
Integration program questions
Is every connector available on day one?
Roadmaps depend on your region, channel mix, and contract. Discovery produces a concrete connector list with transport mode (API, file, iPaaS) and cutover milestones.
Can we build custom adapters?
Yes. Enterprise rollouts often include proprietary WMS, legacy ERP, or bespoke marketplaces—implemented as governed adapters with your IT security sign-off.
How do you handle reconciliation drift?
Scheduled sweeps compare platform truth to internal ledgers; exceptions land in operator queues with explainable diffs instead of silent overrides.
Do you support our SI or MuleSoft team?
Yes. We publish patterns for coexistence: core orchestration in Support Master, orchestration glue in your iPaaS where that is the house standard.
Need a connector that is not in your region list yet?
Share your stack diagram and file samples—we will respond with adapter approach, security checklist, and phased cutover.