CSM for Amazon Release Notes - 4.1.2026081428.303621

Released: August 17, 2026

Added

Create New Listings from within Business Central

• Take an item through to a live Amazon listing without leaving Business Central. Search Amazon's catalog by keyword or ASIN to match an existing product or list manually.
• Amazon expects different attributes per product type. The form is built from Amazon's own definition for the type you pick, and values are checked before submission.
• Set the offer in the same flow: condition, SKU, price, currency, and fulfillment by Amazon or by you. Work in progress is held as a draft listing.
• Please note:
  • Some product types describe attributes in a form this release does not yet render, so Amazon may reject a submission for an attribute the form did not ask for. Contact Suite Engine if this happens.

Amazon Marketplaces and per-Marketplace Posting

• New Amazon Marketplaces list, populated on installation and upgrade. Settlements now record which marketplace they came from.
• New Amazon Event Type Overrides screen sets a different general ledger debit and credit account per financial event per marketplace. Existing accounts apply where no override exists.
• Financial Management Setup gains a default sales channel. Settlements with multi-channel fulfilment lines now route to the correct channel.

New Connection / Setup Wizard Rewrite

• We've greatly simplified the organization and collection of Amazon SP-API credentials, speeding up the input process. We have a new link to our KB document explaining how you can obtain these credentials. Each option in this wizard now has a helpful and updated tooltip to further explain the field.
• Credentials are tested before setup completes, with each stage reported separately (access token, AWS role, call to Amazon), so a failure names the credential that is wrong.
• Setup opens with a choice of Quick Setup (using pre-defined defaults) or Custom Setup. The wizard has been reorganized and reworded after customer testing.

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.

• MWS wizard fields are obsolete and only SP-API is supported. Any Sales Channel still on MWS reports the SP-API steps as missing.

• We ensure you can confirm your full API connection is functional.

• A first run does not reach back over a long history.

• We now match the numbering and naming used across other Channel Sales Manager modules.

• This includes a reworked CSM Setup ribbon, and the license check now reads Stripe subscription items directly.

• Existing data is retained.

Fixed

Settlement Transactions not Recording the Marketplace Currency

• This issue had previously resulted in foreign settlements posting incorrect amounts:
  • Amazon sends a settlement report per marketplace, each in that marketplace's currency. CSM left the currency blank on every transaction, so the worksheet posted those amounts as your ledger currency with no conversion.
  • Transactions now carry the settlement's currency and foreign settlements post as foreign currency, so Business Central applies your exchange rate. The currency shows next to the settlement total.
  • Single marketplace in your own currency: no change. In another currency: you were posting incorrect amounts and will now post correct ones, so your figures change going forward.
  • A settlement in a currency not set up in Business Central now stops worksheet creation with a message naming it, leaving existing lines intact.
  • If the LCY Code in General Ledger Setup is blank, you will be asked to fill it in the first time you process a settlement after upgrading.
• Please regenerate any unposted fee posting worksheet created before upgrading.
• Settlements imported earlier keep a blank currency and still post as local currency.

Shipping Service Level was Written to a Retired Field

• Retrieving a single order mapped the shipping service level to a field since retired in CSM Core, so the value did not appear. It now targets the current field, corrected automatically on upgrade.