Adobe Commerce Integration FAQ

No, this integration cannot be used to administer users, data, or other Metapack integrations.

No, data migration issues are not relevant to this integration.

Yes.

Yes. In Magento, the selected shipping option's data is stored in the quote_shipping_rate table. There are columns, such as carrier, carrier_title, code, method, and method_description , which store the corresponding carrier details.

In addition to this, custom fields are used, such as mp_booking_code, mp_method_id, mp_method_code, mp_carrier_service_code, and mp_option_type, which are created for development purposes.

No. If you uninstall the Metapack Magento app, data will be deleted from your Adobe Commerce account but any orders created while using the app would remain in Adobe Commerce.

After downloading and installing the Metapack Magento app, you can customise the integration to suit your needs. However, if you customise the integration, you will be responsible for maintaining it. For example, if you add a map for store pickup, you would have to maintain it because the base integration does not support that feature.

If you elect not to customise the integration, you also have the option to install newer versions of the app from Magento marketplace when they are released.

Metapack Support and/or your Metapack Professional Services implementation consultant can help you troubleshoot this integration. If there is a problem specific to the Metapack Magento app, Metapack has a support agreement with the vendor, which will aid resolution.

Metapack.

Contact Metapack Support.