This app is custom-built and installed for your store, not an instant App Store download. A typical build runs about 2-3 weeks from kickoff: scope and COGS-source confirmation, OAuth install and webhook setup, ad-platform connections, historical backfill, then a reconciliation pass against a period you already know. Timing depends on how many stores, currencies and ad channels are in scope and how your cost data is currently held.

Every build includes a post-launch support window for bug fixes and configuration adjustments (new products, changed fee structures, additional ad accounts). Because ECOSIRE builds and hosts the integration, we also keep it current with Shopify Admin API version changes. Longer-term maintenance and feature additions are available as an ongoing arrangement after the initial window.

COGS can be sourced three ways: entered manually, mapped from each variant's InventoryItem unitCost, or stored in dedicated metafields so it survives theme and catalog changes. We recommend the metafield approach for stores with frequent cost changes, because it gives you a single, versionable place to update costs and the dashboard recalculates margins from there.

Yes. We subscribe to the refunds/create and orders/updated webhooks, so when an order is refunded, returned or edited the profit ledger is adjusted — revenue, COGS and fees are reversed proportionally. This is a common blind spot in revenue-only dashboards and a core reason the net profit number here differs from Shopify's built-in reports.

Yes. The app can ingest orders from multiple stores and normalise everything to a base currency you choose using transaction-level exchange data, so you get a consolidated profit view plus per-store breakdowns. Each store is connected through its own scoped OAuth install.

No. This is a backend analytics integration that talks to Shopify's Admin GraphQL API and webhooks server-side. It does not inject scripts into your storefront theme or the checkout, so there is no impact on page speed or Core Web Vitals.