No. This is a build-to-order engagement. ECOSIRE scopes, builds, installs and supports the connector as a per-tenant extension on your own Dynamics 365 F&O / Commerce environment. We deploy to your sandbox first, validate against real order and settlement data, then promote to production. There is no public AppSource listing — the solution is tailored to the marketplaces, number sequences, dimensions and fulfilment topology you actually run.

A typical single-marketplace build is delivered in roughly 3 to 6 weeks from kickoff: discovery and channel mapping, build in a sandbox, a validation run reconciling orders/inventory/settlements, then production promotion and handover. Multi-marketplace or complex fulfilment scopes extend that. We confirm a firm timeline after a short scoping call — we won't quote a date before we understand your environment.

The marketplaces with a documented seller/listings API — for example Amazon (SP-API), eBay, Walmart Marketplace and similar — are in scope. Each marketplace's API is integrated as part of the build, so the contracted marketplaces are fixed in the statement of work. Adding a new marketplace later is a follow-on engagement that reuses the same channel framework, so it's faster than the first.

ECOSIRE. We retain the source and provide an ongoing support and update agreement. Marketplace APIs and Microsoft's Commerce/F&O platform both change on their own cadence, so the agreement covers API contract updates, fixes, and revalidation against your environment after major Microsoft service updates. You're not left maintaining bespoke integration code in-house.

We build using supported extension and event-handler patterns and extend core retail objects rather than modifying them destructively, which is the safest position for Microsoft's continuous-update model. We deploy and test in your sandbox first on every change. As part of the support agreement we revalidate the connector against major platform updates so you're not caught out at a One Version service update.