Overview
Completely Rebuilt Setup Experience
- The Magento setup wizard now follows the same Quick and Custom setup structure as the Amazon, Shopify and BigCommerce wizards, and it can test your Magento credentials before you commit to them, so connection problems surface during setup instead of on the first sync attempt.
Product Support for Multiple Websites and Special Pricing
- Products now publish to every Magento website they are listed on rather than a single website, and campaign pricing set up in Business Central now flows to Magento as special pricing with its own start and end dates. Businesses running more than one Magento sales channel will also find that setting up a second channel no longer disturbs the automation schedule of the first.
Note: Upgrading to 4.4 automatically updates your existing Magento API configuration so that product creation and updates send the full website list, and so that product price updates carry the special price fields. No manual reload of the API configuration is needed for these changes.
Added
Publish Products to Multiple Websites
- When a product is created or updated in Magento, Suite Engine now sends the full set of Magento websites that the item is listed on, rather than the single website recorded on one sales channel.
- The website list is worked out per product by matching the channel item SKU across every Magento sales channel where that product already exists in Magento.
- Businesses running several Magento websites from one Business Central company no longer need a separate product record per website to make a product visible in more than one storefront.
- A new value processing function, Get Available Sites for Product, is available if you need to use the same website list in your own API configuration.
Campaign Pricing Syncing as Special Pricing
- Campaign prices set up in Business Central now sync to Magento as the product's special price, together with the special price start date and end date.
- Where several campaigns cover the same product, Suite Engine picks the same price Business Central itself would apply: expired campaign rows are ignored, a campaign that is running today wins (lowest price first, and where prices tie, the one that started earliest), and if no campaign is running yet the next one due to start is sent.
- Both the current price list setup and the older sales price setup are supported, so this works whether or not your company has moved to the newer pricing experience.
- When no campaign price applies to a product, a blank special price is sent, which clears the promotion in Magento rather than leaving an old one in place.
- Three new value processing functions cover this: Get Special Price, Get Special From-Date and Get Special To-Date.
Updated
Dependency Requirements
- Requires Suite Engine API Engine Library 1.22.2026081428.303683, Channel Sales Manager Core 4.10.2026081428.303406, and Suite Engine Variations Library 1.7.2026081428.303403. These are released together.
Setup Wizard
- Quick and Custom Setup Paths
- The Magento setup wizard has been rebuilt around two clearly separated paths, matching the wizards used by the other Suite Engine channel connectors:
- Quick Setup takes a Magento host URL and API key on a single screen, tests the connection, shows a review of what will be created, and finishes. If the wizard detects that Magento is already configured in the company, it explains this on screen instead of letting you create a duplicate configuration.
-
-
- Custom Setup walks through the sales channel, the API connection, credentials, and API operation loading as separate steps. You can create a new sales channel with immediate validation of the code you type or select an existing Magento channel. You can likewise create a new API connection or reuse an existing Magento one.
- Both paths end with a review step that lists what is about to be created and a finish step that points you to the settings worth checking next, including order processing and listing management.
- Test Connection Feature
- A Test Connection action on the credentials screen calls Magento directly and reports back before you continue, so an incorrect host URL or an expired API key is caught during setup.
- The result distinguishes between a server that cannot be reached and a server that rejected the credentials, and it includes the reason Magento gave.
- A missing host URL or API key is reported immediately rather than producing a failed call.
Automation Schedules are Now Specific to Each Sales Channel
- The order management and listing management automation groups created during setup now carry the sales channel code in their name.
- Previously, running setup for a second Magento sales channel wrote over the automation group belonging to the first, which could leave the original channel's schedule altered without warning. Each channel now gets its own group.
- Newly created automations are also given a sync start date taken from the wizard, rather than starting with an empty last-run timestamp.
Legacy Magento 1.x Setup Removed from the Wizard
- The wizard now always sets up the current API Engine configuration. It can no longer create the older Channel Sales Manager API set, and the Magento 1.x options and the Load CSM Triggers choice have been removed.
- Fields and options that were replaced remain present but hidden and marked as obsolete, so existing installations continue to work and existing data is untouched.
Fixed
Testing Communication
- Partially Configured Magento Channel
- Using Test Communication on a Magento sales channel that had no API configuration, or an incomplete one, produced a hard error naming a missing API function. The test now simply does nothing in that situation, and where the channel has no API connection recorded at all it leaves the test to whichever component is responsible for it.
- False Failure Message
-
- On sales channels using the current API Engine, a connection test could report a failure line alongside the genuine result, because an older handler claimed the test without ever running it. That handler now stays out of the way unless the older configuration it depends on actually exists, so the reported result matches what was tested.
Retrieving Single Order
- Retrieving one specific order from Magento skipped the extra response handling that runs when orders are retrieved as a list, so parts of the order were not filled in. Single order retrieval now goes through the same handling as list retrieval.
API Set Description Discarded During Setup
- The description typed into the setup wizard for the API connection was not saved. It is now applied to the API set that the wizard creates.
Credentials Not Saved When Reusing Existing API Connection
- Choosing to reuse an existing API connection and then entering a Magento host URL and API key silently discarded them, because credentials were only ever written when none existed. Newly entered credentials now update the existing record.