This is build-to-order, not an instant Adobe Commerce Marketplace download. After we confirm scope (locales, product types, mapping rules) and receive your eMAG API credentials and a staging environment, a typical build, install and test cycle runs about one working week. We give you a firm date in writing before starting and deploy first to staging, then production.

Because we wrote the module and ship you the source, we support it directly. Post-launch we include a warranty window for fixes, and we offer maintenance for eMAG API changes and Magento upgrades (Open Source or Adobe Commerce). When eMAG revises its API or characteristic requirements, we update the connector under a maintenance agreement rather than leaving you to patch it yourself.

Yes. The module follows standard Magento 2 architecture — app/code module, di.xml, observers, service contracts, cron and admin ACL — so it installs on Magento Open Source and Adobe Commerce alike. Adobe Commerce specifics such as B2B catalogs or additional MSI sources are handled during the build if they apply to your store.

Stock is read from Magento MSI salable quantity, so multi-source (multi-warehouse) setups are supported — we map which source or aggregate feeds each eMAG offer. Prices come from your catalog price plus any rules you specify per marketplace, and sync runs on cron at the interval you choose, with on-demand push from the admin.

Yes. Each eMAG marketplace — Romania, Bulgaria and Hungary — is configured as its own channel with its own API credentials, VAT and locality mapping, scoped per website or store view. You can start with one country and add others later; additional locales beyond the initial scope are quoted as a small extension to the build.