Reconfigure Amazon Order Mappings for the Orders API v2026 Migration
Amazon is transitioning from the Selling Partner API Orders v0 to the new Orders API v2026-01-01(new API).
Amazon originally announced that the old API operations would be removed in August 2026. The removal date has now been extended to March 27, 2027, giving customers additional time to complete the transition.
Acumatica has updated the Amazon Connector to support the new API based on the initial August 2026 date. Customers with existing Amazon stores must complete an important manual configuration step after upgrading.
Please check the attached document for the old vs new mappings.
Who is affected?
This action applies to existing Amazon Connector implementations running one of the following Acumatica versions:
| Acumatica version | Minimum supported update |
|---|---|
| 2026 R2 | All builds |
| 2026 R1 | GA Patch 4 or later; build 26.100.0175.4 or later |
| 2025 R2 | GA Patch 9 or later; build 25.200.0248.9 or later |
Customers using these versions must review and reconfigure the mappings for the below entities:
- Sales Order
- Marketplace Fulfilled Order
The review should cover both standard mappings that were previously modified and any customer-specific mappings or formulas.
Why is manual reconfiguration required?
The new Orders API introduces a substantially different data structure from Orders API v0.
Many previously available Amazon objects and fields have been:
- Renamed
- Moved into nested objects
- Replaced by arrays
- Replaced by new enumerated values
- Deprecated without a direct replacement
Acumatica upgrades the Amazon Connector code to communicate with the new API. However, Acumatica does not automatically modify the existing mappings stored for an Amazon store.
Therefore, upgrading the Acumatica instance alone does not complete the migration.
Important: Existing Sales Order and Marketplace Fulfilled Order mappings must be reviewed and updated manually on the Entities form (BC202000).
If the old mappings remain in place, users may encounter synchronization errors when importing FBM or FBA orders. Some mapped values may also be missing or populated incorrectly.
Please check the attached document for the old vs new mappings.
What action should customers take?
1. Confirm the Acumatica build
Verify that the instance is running one of the applicable builds listed above.
2. Review the affected entities
Open the Entities form (BC202000) and select the applicable Amazon store.
Review these entities individually:
• Sales Order • Marketplace Fulfilled Order
3. Identify mappings that use the old API
Review the External Object and External Field/Value columns.
In this form:
- External Object represents the Amazon API object.
- External Field/Value represents the Amazon API field or mapping expression.
Identify mappings that still reference Orders API v0 objects or fields.
4. Select the corresponding V2026 fields
Replace the old external objects and fields with their new Orders API equivalents.
Pay particular attention to customized mappings and formulas. Default assumptions used with the old API might no longer be valid because some values are now returned through arrays or nested objects.
5. Test FBM and FBA order imports
After saving the mappings, test at least:
- One Fulfilled by Merchant order through the Sales Order entity
- One Fulfilled by Amazon order through the Marketplace Fulfilled Order entity
Confirm that the order, customer, address, fulfillment, item, quantity, and financial information is populated as expected.
6. Review Commerce Sync History
Review the processed records in Commerce Sync History and resolve any mapping-related errors before resuming normal scheduled processing.
Why should customers act now?
Although Amazon extended the removal deadline to March 27, 2027, the Acumatica Connector begins using the new API based on the initial date of August 2026.
Therefore, the mapping review should be performed as part of the Acumatica upgrade process—not postponed until Amazon’s final removal date.
Completing the change early provides time to:
- Validate FBM and FBA order scenarios
- Review customized mappings and formulas
- Correct data differences before production processing
- Avoid order-import interruptions as the Amazon deadline approaches
Additional information
For Amazon’s complete endpoint, attribute, status, fulfillment, and program mapping reference, see:
Amazon Orders API Migration Guide
If you require assistance reviewing your Amazon mappings, contact your Acumatica partner or Acumatica Support before processing production orders with the updated connector.
Please check the attached document for the old vs new mappings.