Because this is build-to-order, typical delivery is around 2 to 3 weeks after a short discovery call where we confirm your Magento version, attribute model and Miravia seller account. We build against the current Miravia API, install on your staging environment first, validate sync flows with sample products, then promote to production. Complex catalogs or custom attribute requirements may extend the timeline, and we'll tell you up front.

Every build includes a post-delivery support window for bug fixes and for adjusting the connector when Miravia changes its API. We can also provide an ongoing maintenance plan covering Magento 2.4.x upgrades, new Miravia features and monitoring. Because you receive the full module source under app/code, your own team can maintain or extend it too — there is no lock-in.

Yes. The module is built for Magento 2.4.x on PHP 8.x and works on both Adobe Commerce and Magento Open Source. It uses standard Magento mechanisms — service contracts, di.xml, plugins/interceptors, observers, cron and MSI inventory — so it behaves consistently on either edition. We confirm your exact version during discovery and pin compatibility accordingly.

No. Magento remains the source of truth. Inventory sync reads MSI source quantities and supports a configurable buffer so the quantity sent to Miravia stays safe, reducing the risk of overselling. Price and content sync are direction-controlled and mapped per store view, and category/attribute mapping is validated before any product is published to Miravia.

Yes. Spanish content mapping pulls titles, descriptions and attribute values from your es_ES store view or a dedicated mapping so listings read correctly for Spanish buyers. The attribute-mapping layer aligns your Magento attribute sets with Miravia's per-category required attributes, and the bulk listing process validates that mandatory fields are present before publishing.