Skip to main content
Solved

The SHIP-1065144 shipment could not be exported because of the following error: There is an error in XML document (1, 1).

  • Nov 4, 2026 2:25 PM UTC
  • 6 replies
  • 38 views
  • Translate All

Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+16

Getting this error while performing Shipment sync in Amazon

V:25r1

Best answer by KarthikGajendran

​@Manikanta Dhulipudi This is a unexpected change from Amazon which is causing the shipments exports to fail. We are working on the hotfix. We will provide one soon. 

Could you please let us know version of your client? 

View original

6 replies

Steve Milner
Varsity III
Forum|alt.badge.img+6

@Manikanta Dhulipudi Before you reprocess it, look up the order in Seller Central. The shipment may already be confirmed on Amazon.

That error doesn't come from Amazon. The connector sends shipments as an XML feed and waits until Amazon finishes processing it. Then it downloads Amazon's processing report and reads it as XML. The (1, 1) error is thrown on that read, because the report doesn't start like an XML file. If Amazon had failed the whole feed, you'd see "An unexpected error occurred while processing feed documents in Amazon" instead. Amazon's verdict on your shipment is inside the report the connector couldn't read.

If Seller Central shows the order shipped with your tracking number, Amazon took it. Only the sync record in Acumatica is marked failed. Reprocessing it would send the confirmation again. Any other shipments in the same feed get this same message, so a batch of them can all come from one failed read.

If every shipment fails this way, it needs Acumatica support. No store setting changes how the report is read. In 25R1, XmlFeedDataProvider opens the report link as plain XML and doesn't check whether Amazon compressed it, and Amazon's docs say that report can come back compressed. A gzipped or JSON report gives exactly this (1, 1) error. The same code is in 25R2 and 2026 R1, so upgrading to either won't change it. Give support the shipment number and the time the sync ran.

Translate

Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+16

​@Steve Milner Every shipment is failing now and I am waiting for the upgrade to happen tonight.

Translate

Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+16

​@KarthikGajendran Any Inputs?

Translate

Steve Milner
Varsity III
Forum|alt.badge.img+6

@Manikanta Dhulipudi The code that reads Amazon's report is identical in builds 25.101, 25.200 and 26.101. The fixes lists in the release notes through 2026 R2 don't mention this error either. If support pointed you to the upgrade, ask them which build has the fix.

Open a few of the failed orders in Seller Central. If one shows shipped with your tracking number, Amazon accepted it and only the sync record in Acumatica failed. If it still shows unshipped, Amazon doesn't have that confirmation. Send support a few of each.

After the upgrade, be careful with the failed shipments. Reprocessing one sends it to Amazon again, and the connector doesn't check the order's status on Amazon first. Check them against Seller Central before you reprocess in bulk.

Translate

KarthikGajendran
Acumatica Moderator
Forum|alt.badge.img+3

​@Manikanta Dhulipudi This is a unexpected change from Amazon which is causing the shipments exports to fail. We are working on the hotfix. We will provide one soon. 

Could you please let us know version of your client? 

Translate

Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+16

​@KarthikGajendran Customer in 25r1 and planning to go live with an upgrade to 26r1 tonight.

Translate