Typical delivery is one working week after we scope your catalog and Michaels' current attribute requirements. The first week is mapping and configuration; the rest is build, staging install, and a smoke-test pass. Complex multi-source or large attribute-set catalogs can extend the timeline, and we confirm a firm date during scoping before any build work starts.

No. This is build-to-order. There is no one-click Marketplace listing — ECOSIRE builds the module against your Magento version, theme, and taxonomy, installs it on your staging environment, and supports it after go-live. You get a connector tailored to your store rather than a generic extension you have to adapt yourself.

Every build includes a post-deployment support window for bug fixes and configuration help, plus compatibility maintenance for the Magento version you're pinned to. If Michaels changes its marketplace API or attribute requirements, we offer paid update work to keep the connector current. Support terms are confirmed in writing before delivery.

Yes. The module targets Magento 2.4.x on both Open Source and Adobe Commerce, and supports MSI multi-source inventory and multi-store setups. We build and test against your specific Magento minor version so the di.xml, plugins, and queue configuration match your environment.

Stock changes are captured via observers and plugins on Magento's source-item save events, then reconciled to Michaels through cron-driven sync jobs and the message queue. Sync is idempotent and retry-aware, so a transient API failure is retried rather than silently dropped, and the admin sync grid shows the last-synced quantity and timestamp per SKU.

Listings are validated against Michaels' required taxonomy before submission, so most issues are caught pre-submit. Anything Michaels still rejects appears in the admin rejection grid with the specific error, so your team can correct the attribute or category mapping and resubmit without digging through API logs.