Note on Version Support
Early versions of Magento 2.x went through rapid changes. Many of the Magento platform releases prior to Magento 2.3.4 are not backwards compatible, and as a result we've optimized the integration for 2.3.4, 2.3.5, and 2.4.0. Recent releases bring welcome improvements to speed and stability.
- Each release gradually addresses known issues in Magento and adds new functionality.
- Existing integration clients can continue to use their existing Magento 2 version.
- Versions prior to 2.3.4 are not supported for new integration accounts.
Accumula integrates systems with different databases. Certain actions can lead to data integrity loss and data corruption.
It is essential to observe the following rules:
- DO NOT DELETE
- Contact Accumula Support
- If at all possible BEFORE you restore any integrated database
- When its not possible, stop your Magento 2 integration, and contact us as soon as possible.
- DO NOT modify or edit your Magento 2 database directly.
Multiple Magento Stores
If your Magento Environment is setup with multiple Magento Stores, Products will upload initially without being assigned to a Magento store and not be visible to shoppers. You can assign products manually to the desired stores or create a cron job to assign products periodically.
Products will only need to be assigned to the desired store once when first uploaded.
Note: The integration will not ignore stores. Orders from all store locations will sync to POS.
Magento 2 Databases and API IDs
In many cases a unique API ID is how data is referenced in the Magento 2 API scheme.
Though two databases may have all the same products in them, unless the second database is an exact copy, the API IDs for some data will be different. This also applies to restored databases where an ID may not exist in the restored copy but had already synced to Accumula after the restore point.
Changing Magento 2 servers or databases must be done with extreme caution. Our default position is that it is always safer to create a new Accumula account than to risk reconnecting data that may no longer line up with previous IDs.
Development and Production Accounts
In cases where a development environment is used the development environment should be promoted to production by simply changing the DNS or cloning the environment. Otherwise a new Accumula account, fresh configuration, and complete resync to/from production will be required.
Note: There is a fee association to this case when making a new Accumula account, re-configuration, and resync.
It is possible to connect separate Magento 2 development and production servers when using either Lightspeed Retail Cloud or Heartland Retail Cloud POS. This is done by using a different Accumula account for each instance.
Note: Running both a development and production account will require an Accumula plan for each account.
Third Party Extensions and Custom Code
Accumula uses the Magento 2 API to integrate with Magento 2. This ensures stability. We have seen cases where third party extensions and custom code used in Magento 2 can:
- Block access to API functionality and impact the integration.
- Creates orders, products, or customers which appear incomplete via the API. Cases Include:
- Orders missing tax details.
- Orders missing payment details.
- Products which are malformed via the API.
Please be sure that your third party extensions and custom code conform to best practices, consider downstream impacts to your other integrated systems, and do not modify how products are structured in the Magento 2 database.
Important: Magento 2's API will not provide visibility into internal Magento issues like this, and Accumula is unable to troubleshoot issues related to third party extensions and custom code.
Magento Server Hardware
Be sure that your Magento 2 server environment has sufficient hardware resources available. Real Time Integration requires almost continuous traffic to your Magento 2 server. A "Basic" hosting plan may be insufficient in both hardware resources and bandwidth.
Performance is usually impacted by these three factors the most:
- Configuration of Magento 2.
- Configuration of the server software.
- Integration Data volume.
There are a myriad of ways to configure both Magento 2 and server hosting your site. We are unable to provide hardware recommendations.
Note: In an ideal environment we would hope to see the Magento 2 server able to process at least 30 API requests per minute. Your business may see more or less actual volume.
Our support team recommends consulting with your Magento developer and/or host to determine the best hardware for your server needs. All that said, we can confidently state that a $25/month server account will be insufficient.