Integrations that work on day one
The integrations a real ecommerce business needs, already wired in. Everything else stays programmable.
Extensibility without marketplace dependency
Commerce without ecosystem dependency. Core capabilities are first-party. Everything else remains programmable through APIs, webhooks, MCP and enterprise integrations.
Extensions exist, and Mercemur connects to plenty of them. The difference is that Mercemur does not require an extension marketplace to make the core platform useful. Catalog, inventory, orders, customers, promotions, marketing, returns, loyalty, digital products, subscriptions and the storefront are first-party capabilities, maintained as part of the platform rather than bought separately.
Beyond that core there are four routes out: native integrations where they make sense, REST and webhooks for everything else, MCP for agent-driven workflows, and enterprise integration work for the unusual requirements. Some things — SMS, WhatsApp, push, external systems of record — are integrations rather than native functionality, and are listed as such.
Payments
Four real payment integrations, each maintained as part of the platform:
Stripe
Razorpay
Dodo Payments
Adyen
Manual payments
Shipping
ShipRocket (India)
ShipEngine (international)
Manual fulfillment
Resend
Analytics
Google Analytics 4
Meta Pixel
Storage
Digital product file delivery uses secure cloud storage with short-lived signed links. Files do not leave the platform's controlled storage perimeter except through signed delivery to the customer who paid for them.
Why pluggable
Every category (payment, shipping, email) is built around pluggable integrations. If a merchant on Enterprise needs:
The platform supports adding integrations through the developer API. The default integrations cover most merchants. Anyone with a specific need builds against the same public API, on their own infrastructure and their own schedule.
How to connect
Each integration has its own admin connection flow:
Stripe. Restricted key flow. Create a restricted key in your Stripe dashboard, paste it into the admin, and charges run on your own account.
Razorpay. API key flow. Generate API keys in your Razorpay dashboard, paste into the admin.
Dodo. API key flow. Generate API keys in your Dodo dashboard, paste into the admin.
Adyen. API credentials flow. Enter your Adyen API credentials, account discovery selects the merchant account, and they are validated on save.
ShipRocket. Account credentials flow. Enter your ShipRocket login, the integration handles the rest.
ShipEngine. API key flow. Paste your ShipEngine key into the admin.
Resend. Domain setup flow. Add your sender domain, follow the DKIM and SPF setup guide, verify.
GA4. Measurement ID flow. Paste your GA4 measurement ID into the storefront settings.
Meta Pixel. Pixel ID flow. Paste your Meta Pixel ID into the storefront settings.
Each connection is per-merchant. Multi-tenant isolation means your credentials are your own, not shared with other merchants on the platform.
How integrations work together
A complete order flow touches multiple integrations:
Customer visits the storefront : GA4 and Meta Pixel fire page view
Customer adds to cart : Meta Pixel fires AddToCart
Customer checks out : Meta Pixel fires InitiateCheckout, GA4 fires begin_checkout
Customer pays through Razorpay (India) or Stripe (international)
Payment captures : the full amount lands in your own Stripe or Razorpay account, with no Mercemur cut
Order completes : GA4 fires purchase, Meta Pixel fires Purchase
Resend sends order confirmation under your sender domain
ShipRocket (or ShipEngine) gets a shipment request
Carrier label generates, tracking number assigned
Resend sends shipped notification with tracking link
All of it happens automatically. No glue code, no manual reconciliation.
Use cases
India DTC brand
Razorpay for payments, ShipRocket for shipping, Resend for email, GA4 and Meta Pixel for analytics. One platform handles the full operation.
International software vendor
Stripe for payments (subscription billing for SaaS), Dodo for cross-border tax compliance on certain regions, Resend for transactional and marketing email, GA4 and Meta Pixel for traffic and conversion attribution.
Multi-region brand
Razorpay for India region, Stripe for US and EU regions, Dodo for the rest of the world. ShipRocket for India shipments, ShipEngine for international. Resend for email under a multi-region sender domain setup.
Subscription box business
Stripe subscriptions for recurring billing. ShipEngine (or ShipRocket if in India) for monthly box shipments. Resend for transactional and pre-shipment emails. GA4 and Meta Pixel for acquisition.
Multi-brand operator
Each brand has its own Stripe, Razorpay, ShipRocket, Resend, and GA4 accounts. The platform routes each brand's traffic and transactions to the brand's own provider connections.
Agency
Each client store connects its own provider accounts. The agency operator has admin access without needing access to the client's actual Stripe or Resend credentials.
Native connectors on the roadmap
These are first-party connectors we intend to build and maintain. They are roadmap directions, not commitments, and depend on merchant demand. Anything listed here can already be integrated today through the developer API, covered in the next section.
Additional payment providers for specific regional markets
Additional shipping aggregators for non-India, non-US-international markets
SMS and push notification channels
Marketplace integrations (eBay, Amazon, Etsy)
Social commerce (Instagram Shopping, TikTok Shop)
ERP integrations
Accounting integrations (QuickBooks, Xero)
Custom integrations through the developer API
If the built-in integrations do not cover your need, or a maintained native connector is still on the roadmap, the integration is available today through the API:
Common custom integrations
Frequently asked questions
Best practices for managing integrations
What to connect in what order
A clean launch sequence keeps the setup practical: collect money first, fulfill second, then layer in communication and attribution.
Day 1
Payments first
Day 1
Stripe, Razorpay, Adyen, or Dodo. You cannot sell without payments. Connect at least one first.
Day 2
Shipping next
Day 2
ShipRocket and ShipEngine. You cannot ship without carriers. Connect after payments.
Day 3
Email setup
Day 3
Resend. You cannot do transactional or marketing email without it. Connect domain, configure DKIM and SPF, verify, start sending.
Day 4
Analytics on
Day 4
GA4 and Meta Pixel. Optional but recommended on day one. Pixels start building data the moment you turn them on.
Day 5
Cross-border ready
Day 5
Dodo Payments (if you sell digital cross-border). Cross-border merchant-of-record handling. Useful for international digital sales without local tax registration.
See every integration in detail.
Start fast, compare plans, or talk through the details with us.